Description of problem: After upgrading to f20 my dlink usb adapter stopped being recognized as a wireless adapter and is only recognized as an Ethernet adapter. Since iwconfig recognizes it I assume it's a NetworkManager problem. $ lsusb .... Bus 003 Device 007: ID 07d1:3303 D-Link System DWA-131 802.11n Wireless N Nano Adapter(rev.A1) [Realtek RTL8192SU] .... $ iwconfig enp0s20u4 unassociated Nickname:"rtl_wifi" Mode:Auto Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 lo no wireless extensions. em1 no wireless extensions. $ dmesg |grep firmw [ 3.551592] usb 3-2: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 807728 [details] Network manager window Here showing the network manager window showing it as an ethernet instead of a wireless adapter
What does 'iw dev enp0s20u4 info' say? Also, what does "journalctl -b | grep WEXT" say? Next, what does "iwgetid --protocol" say?
$ iw dev enp0s20u4 info command failed: No such device (-19) $ journalctl -b | grep WEXT Oct 04 17:10:03 funkotron NetworkManager[773]: <info> WEXT support is enabled $ iwgetid --protocol <no output>
*** Bug 1019525 has been marked as a duplicate of this bug. ***
cb-rhbugz.uk, what does your device report for: iwconfig wlan0 ?
$ iwconfig wlan0 wlan0 802.11bgn Nickname:"rtl8192E" Mode:Managed Frequency=2.417 GHz Access Point: Not-Associated Bit Rate:1 Mb/s Retry min limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Also, everyone please run: cat /sys/class/net/wlan0/uevent and report the output. Thanks!
I believe I've fixed the problem upstream, the fix will appear in the next snapshot.
I get: $ cat /sys/class/net/wlan0/uevent INTERFACE=wlan0 IFINDEX=3
FWIW, this horrible script can be used to work around the problem. #!/bin/bash rm -Rf /tmp/nmhack mkdir /tmp/nmhack echo 'DEVTYPE=wlan' > /tmp/nmhack/uevent grep INTERFACE /sys/class/net/wlan0/uevent >> /tmp/nmhack/uevent grep IFINDEX /sys/class/net/wlan0/uevent >> /tmp/nmhack/uevent mount --bind /tmp/nmhack/uevent /sys/class/net/wlan0/uevent systemctl restart NetworkManager
NetworkManager-0.9.9.0-17.git20131003.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-17.git20131003.fc20
Package NetworkManager-0.9.9.0-17.git20131003.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.9.0-17.git20131003.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-21504/NetworkManager-0.9.9.0-17.git20131003.fc20 then log in and leave karma (feedback).
NetworkManager-0.9.9.0-17.git20131003.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.