After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674650 - Networkmanager 0.9.4.0-2 Realtek RTL8188CUS 802.11n WLAN usb Device not ready
Networkmanager 0.9.4.0-2 Realtek RTL8188CUS 802.11n WLAN usb Device not ready
Status: RESOLVED NOTABUG
Product: NetworkManager
Classification: Platform
Component: ModemManager
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-04-23 20:06 UTC by Conor Kinnear
Modified: 2012-04-24 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Conor Kinnear 2012-04-23 20:06:19 UTC
Update of network manager from version 0.9.2.0-3 to 0.9.4.0-2 causes Realtek RTL8188CUS 802.11n WLAN usb to be seen as not ready. 

This cannot be started at all, rebuilding drivers does not work.

Downgrading to version 0.9.2.0-3 allowed this to work again.

Additional info:
Networkmanager 0.9.2.0-3 to 0.9.4.0-2
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=48&Level=5&Conn=4&ProdID=274

A similar problem with a RTL8189SU USB adapter.
It seems that NetworkManager-0.9.4 sees this adapter as a wired adapter instead of a wireless adapter as shown in the log below:

Apr 23 19:12:57 tao NetworkManager[898]: <info> (wlan0): driver 'r8712u' does not support carrier detection.
Apr 23 19:12:57 tao NetworkManager[898]: <info> (wlan0): new Ethernet device (driver: 'r8712u' ifindex: 3)
Apr 23 19:12:57 tao NetworkManager[898]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 23 19:12:57 tao NetworkManager[898]: <info> (wlan0): now managed
Apr 23 19:12:57 tao NetworkManager[898]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 23 19:12:57 tao NetworkManager[898]: <info> (wlan0): bringing up device.
Apr 23 19:12:58 tao NetworkManager[898]: <warn> (wlan0): couldn't get carrier state: (-1) unknown
Apr 23 19:12:58 tao NetworkManager[898]: <info> (wlan0): carrier now OFF (device state 20, deferring action for 4 seconds)
Apr 23 19:12:58 tao NetworkManager[898]: <info> (wlan0): preparing device.
Apr 23 19:12:58 tao NetworkManager[898]: <info> (wlan0): deactivating device (reason 'managed') [2]
Apr 23 19:12:58 tao NetworkManager[898]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb5/5-2/5-2:1.0/net/wlan0
Comment 1 Dan Williams 2012-04-23 22:09:41 UTC
It's being seen as a wired device for some reason.  Is this a vendor driver, or an upstream kernel driver, or a kernel staging driver?  It's likely that the driver doesn't identify itself as a wifi device properly.
Comment 2 Nuno Araujo (IRC: russo79) 2012-04-24 04:40:13 UTC
The r8712u is a kernel staging driver.
It seems to be a networkmanager regression though.
With networkmanager 0.9.2, the device is seen as a wireless device.

What kind of information would be useful to help debug this problem?

iwconfig sees the interface as a wireless device.
Would this be the case if the driver was not identifying itself as a wifi device property?
Comment 3 Nuno Araujo (IRC: russo79) 2012-04-24 04:47:55 UTC
By the way, here is the output of udevadm info --query=all --path=/sys/class/net/wlan0

P: /devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb4/4-2/4-2:1.0/net/wlan0
E: DEVPATH=/devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb4/4-2/4-2:1.0/net/wlan0
E: ID_BUS=usb
E: ID_MODEL=RTL8191S_WLAN_Adapter
E: ID_MODEL_ENC=RTL8191S\x20WLAN\x20Adapter\x20
E: ID_MODEL_FROM_DATABASE=RTL8191SU 802.11n WLAN Adapter
E: ID_MODEL_ID=8172
E: ID_REVISION=0200
E: ID_SERIAL=Manufacturer_Realtek_RTL8191S_WLAN_Adapter_00e04c000001
E: ID_SERIAL_SHORT=00e04c000001
E: ID_TYPE=generic
E: ID_USB_DRIVER=r8712u
E: ID_USB_INTERFACES=:ffffff:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Manufacturer_Realtek
E: ID_VENDOR_ENC=Manufacturer\x20Realtek\x20
E: ID_VENDOR_FROM_DATABASE=Realtek Semiconductor Corp.
E: ID_VENDOR_ID=0bda
E: IFINDEX=3
E: INTERFACE=wlan0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/wlan0
E: TAGS=:systemd:
E: USEC_INITIALIZED=2878752
Comment 5 Conor Kinnear 2012-04-24 16:52:54 UTC
┌─[conor]──[shodan]:~$
└──>>udevadm info --query=all --path=/sys/class/net/wlan0
P: /devices/pci0000:00/0000:00:0b.1/usb1/1-6/1-6:1.0/net/wlan0
E: DEVPATH=/devices/pci0000:00/0000:00:0b.1/usb1/1-6/1-6:1.0/net/wlan0
E: ID_BUS=usb
E: ID_MODEL=802.11n_WLAN_Adapter
E: ID_MODEL_ENC=802.11n\x20WLAN\x20Adapter
E: ID_MODEL_FROM_DATABASE=RTL8188CUS 802.11n WLAN
E: ID_MODEL_ID=8176
E: ID_REVISION=0200
E: ID_SERIAL=Realtek_802.11n_WLAN_Adapter_00e04c000001
E: ID_SERIAL_SHORT=00e04c000001
E: ID_TYPE=generic
E: ID_USB_DRIVER=rtl8192cu
E: ID_USB_INTERFACES=:ffffff:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Realtek
E: ID_VENDOR_ENC=Realtek
E: ID_VENDOR_FROM_DATABASE=Realtek Semiconductor Corp.
E: ID_VENDOR_ID=0bda
E: IFINDEX=2
E: INTERFACE=wlan0
E: SUBSYSTEM=net
E: USEC_INITIALIZED=6932506

If any other out output is required please let me know.
Comment 6 Dan Williams 2012-04-24 18:23:12 UTC
Conor: any idea how your package of NM got built?  Make sure there isn't "--without-wext" in the configure options, which we've found being passed on Gentoo already.  NM 0.9.4 allows builders to disable WEXT, but it's on by default to ensure that using the same configure options as used with 0.9.2 don't result in WEXT being disabled.  But if somebody updated your distro's build configuration to disable WEXT explicitly, you'll get the problem described here.

Unfortunately, the Realtek drivers are still using WEXT, and they're still in staging, which means they may not work as well as the official kernel wifi drivers.
Comment 7 Ionut Biru 2012-04-24 18:25:41 UTC
Dan thanks for letting us know. This is right, we built networkmanager without WEXT.
Comment 8 Nuno Araujo (IRC: russo79) 2012-04-24 19:14:08 UTC
I think this can be closed as NOTABUG.
I just upgraded to the latest version of the package which doesn't disable WEXT and everything runs smoothly :-)
Comment 9 Conor Kinnear 2012-04-24 20:47:21 UTC
Will test once I get a chance to use 0.9.4.0-4.  Still only showing me 0.9.4.0-3
Comment 10 Conor Kinnear 2012-04-24 21:07:46 UTC
Update to 0.9.4.0-4 has resolved this.  Many thanks.