GNOME Bugzilla – Bug 314768
Wired by default, when no cable inserted
Last modified: 2006-01-18 08:58:02 UTC
Distribution/Version: Ubuntu Breezy When logging into my GNOME desktop, NM automatically brings up the wired connection eth0 (creating it's own subrange, I think), though there's no cable attached (ethtool: Link detected: no), how can I debug this? I'm using j^'s ubuntu breezy packages: http://bootlab.org/~j/NetworkManager-breezy/
Right after boot, can you do this and post the result here? cat /sys/class/net/eth0/carrier That file is controlled by the driver's netlink messages to userspace, which NetworkManager reads. If that file says "1", and you have no cable attached, then your driver is borked and the driver needs to get fixed. If that file says "0" and you don't have a cable attached, then we'll need to debug a bit more. BTW, do you know what driver is bound to your eth0 and what the card's PCI device and vendor ID are? That would be helpful as well. If you need help on finding those out, just say so and I'll be glad to post instructions. Thanks! Dan
Could you also include your kernel version too? Thanks!
It's a broadcom B44: ruben@tokyo:~ $ cat /sys/class/net/eth0/carrier 0 ruben@tokyo:~ $ lspci | grep -i net 0000:02:00.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 0000:02:03.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05) ruben@tokyo:~ $ dmesg | grep -i b44 [4294669.282000] b44.c:v0.95 (Aug 3, 2004) [4294707.836000] b44: eth0: Link is down. ruben@tokyo:~ $ uname -a Linux tokyo 2.6.12-7-686 #1 Fri Aug 19 13:08:28 UTC 2005 i686 GNU/Linux
I have the same problem archer:~> cat /sys/class/net/eth0/carrier 0 archer:~> lspci|grep -i net 0000:02:00.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 0000:02:03.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05) archer:~> uname -a Linux archer 2.6.12-7-386 #1 Fri Aug 19 12:50:02 UTC 2005 i686 GNU/Linux archer:~> ruben: do we have the same laptop? ;p
(oh, I am also using j^'s breezy packages, FWIW) it doesnt seem to detect the link going up either, and their is a wireless AP available carrier is set to 1 when it is in
So, i should clarify. With the cable out, it is 0 with it in, it is 1
This seems to be fixed (in Ubuntu Dapper), so I'm going to mark it RESOLVED FIXED. Trent: If you're still having the problem with the latest NM, please re-open this bug. But given the fact that we have the same laptop, I don't expect it to be the case.