GNOME Bugzilla – Bug 674681
NetworkManager 0.9.4 breaks wl broadcom driver
Last modified: 2012-04-26 18:36:24 UTC
After upgrading nm to 0.9.4 the wl broadcom driver stopped working with nm (it works well with wpa_supplicant + dhcpd) Here is the log Apr 23 21:12:43 localhost NetworkManager[659]: <info> Networking is enabled by state file Apr 23 21:12:43 localhost NetworkManager[659]: <warn> failed to allocate link cache: (-10) Operation not supported Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): driver 'wl' does not support carrier detection. Apr 23 21:12:43 localhost NetworkManager[659]: <error> [1335226363.697424] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (eth0): unable to read permanent MAC address (error 0) Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): new Ethernet device (driver: 'wl' ifindex: 2) Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): now managed Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): bringing up device. Apr 23 21:12:43 localhost NetworkManager[659]: nm_netlink_monitor_get_flags_sync: assertion `self != NULL' failed Apr 23 21:12:43 localhost NetworkManager[659]: <warn> (eth0): couldn't get carrier state: (-1) unknown Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): carrier now OFF (device state 20, deferring action for 4 seconds) Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): preparing device. Apr 23 21:12:43 localhost NetworkManager[659]: <info> (eth0): deactivating device (reason 'managed') [2]
What distro is this? NM 0.9.4 allows builders to disable WEXT, which is probably what's happening here. But WEXT is enabled by default, so packagers/builders have to explicitly pass --without-wext or --with-wext=no at configure time to make this happen.
ie, this might be a dupe of bug 674650
Hi, I think wext works well since I use this option in the wpa_supplicant command line when using iwconfig, wpa_supplicant and dhcpd I'm using ArchLinux
(In reply to comment #3) > Hi, > > I think wext works well since I use this option in the wpa_supplicant command > line when using iwconfig, wpa_supplicant and dhcpd > > I'm using ArchLinux Right, but we need to make sure NetworkManager is built to allow WEXT too. Otherwise it'll detect the Broadcom driver as wired, because the broadcom driver uses the deprecated WEXT API instead of the kernel's preferred nl80211 API. And if NM detects it as a wired device, then obviously it's not going to work as a wifi device.
I see now, Archlinux seems to be built with wext support https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/networkmanager
(In reply to comment #5) > I see now, > > Archlinux seems to be built with wext support > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/networkmanager Yeah, it seems to be. Would you mind reconfirming that your local build has WEXT enabled by rebuilding it, at least up until it starts compiling stuff, and then grab the 'config.h' file from the build directory? We're looking for HAVE_WEXT or WITH_WEXT in that file.
Hi, thanks for your help. Appears that ArchLinux build had the --no-wext flag and it was removed now due to another bug. This was a distro mistake. Regards, Marcelo
No problem; thanks for the report.