Re: NM insists on connecting to a non-existent wired connection.

[Dan Williams <dcbw redhat com>]

On Fri, 2007-06-08 at 01:16 +0530, Rogue wrote:
> Hi All,
> 
> I am seeing a very strange behavior on my Dell D810 laptop. Everytime I 
> start up the system, NM chooses to connect to a non-existent wired 
> network. I see the following in the log files:
> 
> Jun  8 00:53:17 Xymnotune NetworkManager: <info>  starting...
> Jun  8 00:53:17 Xymnotune NetworkManager: <info>  eth1: Device is 
> fully-supported using driver 'ipw2200'.
> Jun  8 00:53:17 Xymnotune NetworkManager: <info>  nm_device_init(): 
> waiting for device's worker thread to start
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  nm_device_init(): 
> device's worker thread started, continuing.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Now managing wireless 
> (802.11) device 'eth1'.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Deactivating device eth1.
> Jun  8 00:53:18 Xymnotune kernel: ADDRCONF(NETDEV_UP): eth0: link is not 
> ready
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  eth0: Device is 
> fully-supported using driver 'tg3'.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  nm_device_init(): 
> waiting for device's worker thread to start
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  nm_device_init(): 
> device's worker thread started, continuing.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Now managing wired 
> Ethernet (802.3) device 'eth0'.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Deactivating device eth0.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Will activate wired 
> connection 'eth0' because it now has a link.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  SWITCH: no current 
> connection, found better connection 'eth0'.
> Jun  8 00:53:18 Xymnotune dhcdbd: message_handler: message handler not 
> found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Will activate 
> connection 'eth0'.
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Device eth0 activation 
> scheduled...
> Jun  8 00:53:18 Xymnotune NetworkManager: <info>  Activation (eth0) 
> started...
> 
> 
> This has started occurring after I installed Fedora 7 on my laptop. Now 
> I am wondering if this is a Fedora bug of a NM bug.
> 
> Any pointers on how to fix this issue are welcome.

It's been fixed in SVN and built as an NM update for F7.  See:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194124

Should hit the mirrors in the next few days.  Out of curiosity though,
what does /sbin/lspci say?

Dan


> thanks,
> Rogue
> 
> Fedora 7 / NM Applet 0.6.5
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list