Re: NM insists on connecting to a non-existent wired connection.
On Fri, 2007-06-15 at 07:23 +0200, Michael Biebl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Biebl wrote: Dan Williams wrote: On Thu, 2007-06-07 at 22:42 +0200, Michael Biebl wrote: 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: FWIW I experience the same bug. I have my ethernet nic on eth0 (8139cp) and the wireless nic on wlan0 (ipw2100). On startup NM always tries to establish a connection via eth0 although no cable is plugged in (and it receives a LL IP address via avahi-autoipd, so the actual connection via wlan0 is not established because NM thinks it has a connection). The problem seems to be, that NM does not correctly init the eth0 device and so mistakenly thinks it has a link. cat /sys/devices/pci:00/:00:1e.0/:02:01.0/net/eth0/carrier yields: Invalid argument directly after loading the module. Hmm, are you using 0.6.4? 0.6.5 relies on netlink exclusively for asynchronous carrier detection and only checks /sys/class/net/ethX/carrier after a successful activation. Do you have a /sys/class/net/eth0/carrier? Does what's in SVN head for NETWORKMANAGER_0_6_0_RELEASE work for you? I applied r2578 against 0.6.5 and now the problems seems to be gone. Unfortunately I started celebrating too soon. The problem is still there. I added a cat /sys/class/net/eth0/carrier in the init script, right before the daemon is started. On startup I get a invalid argument, then NM is started, Yeah, 'carrier' may not be there if the device is down. believes the link is up, activates eth0, eth0 gets and LL ip. After I login, cat /sys/class/net/eth0/carrier yields 0, and nm-tool shows no link. The version is 0.6.5 with r2578 applied. I've gotten at least one report with traces showing that the fix I committed has made the problem better, but not completely fixed it. dan Michael - -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGciJnh7PER70FhVQRAhdoAJ4kEOHJTcvxAAEfmYaCyY9+WERCoQCgvBxD HU9yE9VHyJ/lg20hGUwxhoI= =VCuW -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM insists on connecting to a non-existent wired connection.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Thu, 2007-06-07 at 22:42 +0200, Michael Biebl wrote: 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: FWIW I experience the same bug. I have my ethernet nic on eth0 (8139cp) and the wireless nic on wlan0 (ipw2100). On startup NM always tries to establish a connection via eth0 although no cable is plugged in (and it receives a LL IP address via avahi-autoipd, so the actual connection via wlan0 is not established because NM thinks it has a connection). The problem seems to be, that NM does not correctly init the eth0 device and so mistakenly thinks it has a link. cat /sys/devices/pci:00/:00:1e.0/:02:01.0/net/eth0/carrier yields: Invalid argument directly after loading the module. Hmm, are you using 0.6.4? 0.6.5 relies on netlink exclusively for asynchronous carrier detection and only checks /sys/class/net/ethX/carrier after a successful activation. Do you have a /sys/class/net/eth0/carrier? Does what's in SVN head for NETWORKMANAGER_0_6_0_RELEASE work for you? I applied r2578 against 0.6.5 and now the problems seems to be gone. Michael - -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGaWfvh7PER70FhVQRAqg3AJ0UnCnLlwigjB55gQQx2PSRV5PoDQCdFdF6 H0HW1AaHXXUAenyx+onMEho= =r54K -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM insists on connecting to a non-existent wired connection.
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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM insists on connecting to a non-existent wired connection.
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: FWIW I experience the same bug. I have my ethernet nic on eth0 (8139cp) and the wireless nic on wlan0 (ipw2100). On startup NM always tries to establish a connection via eth0 although no cable is plugged in (and it receives a LL IP address via avahi-autoipd, so the actual connection via wlan0 is not established because NM thinks it has a connection). The problem seems to be, that NM does not correctly init the eth0 device and so mistakenly thinks it has a link. cat /sys/devices/pci:00/:00:1e.0/:02:01.0/net/eth0/carrier yields: Invalid argument directly after loading the module. If I run ip link set eth0 up the above correctly returns 0 for carrier. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM insists on connecting to a non-existent wired connection.
Dan Williams wrote: 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 Hi Dan, First up, glad to hear that this issue has been fixed and pushed. Secondly to satiate your curiosity, lspci on my machine gives the following information: 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300] 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) 03:01.0 CardBus bridge: Texas Instruments PCI6515 Cardbus Controller 03:01.5 Communication controller: Texas Instruments PCI6515 SmartCard Controller 03:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) hope that info helps you... Another bit of info, earlier I used to download the ipw2200 driver separately, but this time I noticed that NM was picking up my device well and nice, so I did not install that driver. Do you think that could be an issue? later, Rogue ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM insists on connecting to a non-existent wired connection.
On Thu, 2007-06-07 at 22:42 +0200, Michael Biebl wrote: 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: FWIW I experience the same bug. I have my ethernet nic on eth0 (8139cp) and the wireless nic on wlan0 (ipw2100). On startup NM always tries to establish a connection via eth0 although no cable is plugged in (and it receives a LL IP address via avahi-autoipd, so the actual connection via wlan0 is not established because NM thinks it has a connection). The problem seems to be, that NM does not correctly init the eth0 device and so mistakenly thinks it has a link. cat /sys/devices/pci:00/:00:1e.0/:02:01.0/net/eth0/carrier yields: Invalid argument directly after loading the module. Hmm, are you using 0.6.4? 0.6.5 relies on netlink exclusively for asynchronous carrier detection and only checks /sys/class/net/ethX/carrier after a successful activation. Do you have a /sys/class/net/eth0/carrier? Does what's in SVN head for NETWORKMANAGER_0_6_0_RELEASE work for you? Dan If I run ip link set eth0 up the above correctly returns 0 for carrier. Cheers, Michael ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
