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 779788 - WLAN device not detected
WLAN device not detected
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-review
 
 
Reported: 2017-03-09 07:40 UTC by Paul Menzel
Modified: 2017-04-04 12:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
journalctl -b -u NetworkManager -u wpa_supplicant | tee /dev/shm/20170309–NetworkManager–wpa_supplicant.log (41.04 KB, text/x-log)
2017-03-09 07:40 UTC, Paul Menzel
Details
journalctl -u NetworkManager -b | tee /dev/shm/20170318–journalctl–nm-messages.txt (612.69 KB, text/plain)
2017-03-18 17:59 UTC, Paul Menzel
Details

Description Paul Menzel 2017-03-09 07:40:56 UTC
Created attachment 347526 [details]
journalctl -b -u NetworkManager -u wpa_supplicant | tee /dev/shm/20170309–NetworkManager–wpa_supplicant.log

The system starts NetworkManager at start, then I plug in the USB WLAN device, and lastly I start the NetworkManager applet. But, it says there is no WLAN (wireless not enabled). `ip a` shows the WLAN device though.

Restarting NetworkManager with `sudo systemctl restart NetworkManager.service` fixes the issue.

Please find the corresponding error message below.

```
Mär 09 07:26:08 myasrocke350m1 wpa_supplicant[1445]: Successfully initialized wpa_supplicant
Mär 09 07:28:19 myasrocke350m1 NetworkManager[766]: <error> [1489040899.2366] (wlan0): couldn't get driver range information (19).
Mär 09 07:28:19 myasrocke350m1 NetworkManager[766]: <info>  [1489040899.2367] (wlan0): driver WEXT range request failed
Mär 09 07:28:19 myasrocke350m1 NetworkManager[766]: <warn>  [1489040899.2368] (wlan0) failed to initialize Wi-Fi driver for ifindex 3
```

Please find the full log attached.
Comment 1 Thomas Haller 2017-03-09 10:01:32 UTC
please enable debug logging and attach the full logfile. Thanks
Comment 3 Paul Menzel 2017-03-18 17:59:53 UTC
Created attachment 348233 [details]
journalctl -u NetworkManager -b | tee /dev/shm/20170318–journalctl–nm-messages.txt

I did that, and it looks like WPA_Supplicant is at fault. I plugged in the WLAN USB device during startup.

```
$ lsusb -d 0bda:8172
Bus 001 Device 003: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter
$ ip link show dev wlx24050f362ad8
3: wlx24050f362ad8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 24:05:0f:36:2a:d8 brd ff:ff:ff:ff:ff:ff
$ LANG=C nmcli device
DEVICE  TYPE      STATE      CONNECTION                  
eth6    ethernet  connected  Kabelgebundene Verbindung 1 
lo      loopback  unmanaged  --
$ journalctl -u wpa_supplicant -b
-- Logs begin at Thu 2015-04-09 07:05:46 CEST, end at Sat 2017-03-18 18:33:04 CET. --
Mär 18 17:57:53 myasrock systemd[1]: Starting WPA supplicant...
Mär 18 17:57:54 myasrock wpa_supplicant[1407]: Successfully initialized wpa_supplicant
Mär 18 17:57:54 myasrock systemd[1]: Started WPA supplicant.
$ sudo wpa_cli -i wlx24050f362ad8
wpa_cli v2.4
Copyright (c) 2004-2015, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.



Interactive mode

Could not connect to wpa_supplicant: wlx24050f362ad8 - re-trying
```

Please find the output of `journalctl -u NetworkManager -b` with log level *trace* attached.
Comment 4 Beniamino Galvani 2017-03-19 09:24:06 UTC
How about something like bg/wext-refresh-ifname-bgo779788 (only compile tested)?
Comment 5 Beniamino Galvani 2017-04-04 12:12:54 UTC
Merged to master:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d3b1e08c9abde0448a6304f90e888207e08f55e1

This should fix race conditions with drivers using wireless extensions.