Bug 1324009

Summary: D-Link DWA-131 (rtl8712u) USB WLAN adapter no longer visible in NetworkManager after upgrade to 1.0.12-1
Product: [Fedora] Fedora Reporter: Vesa Halttunen <vesuri>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 23CC: bgalvani, dcbw, lkundrak, psimerda, reneploetz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-11 07:43:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dnf log for the updates that caused the problem none

Description Vesa Halttunen 2016-04-05 10:37:21 UTC
Created attachment 1143746 [details]
dnf log for the updates that caused the problem

Description of problem:
After upgrading NetworkManager and the associated components from 1.0.10-3.fc23 to 1.0.12-1.fc23 the D-Link DWA-131 (rtl8712u) USB WLAN adapter is no longer visible in NetworkManager. "dmesg" shows the interface gets a name (wlp0s29f7u1) and is shown in "iwconfig" but it's not shown in "ifconfig" or "nmcli d". Doing "ifconfig wlp0s29f7u1 up" manually will bring the interface up and "iwconfig wlp0s29f7u1 ..." allows the connection to be initiated. Also, the adapter still works at least on an OS X computer.

Version-Release number of selected component (if applicable):
NetworkManager-1.0.12-1.fc23.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Attach D-Link DWA-131 to a USB port

Actual results:
"dmesg" shows
[ 2625.806230] usb 2-1: New USB device found, idVendor=07d1, idProduct=3303
[ 2625.806235] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2625.806238] usb 2-1: Product: 11n Adapter
[ 2625.806241] usb 2-1: Manufacturer: Manufacturer Realtek 
[ 2625.806243] usb 2-1: SerialNumber: 00e04c000001
[ 2625.806802] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 2625.806807] usb 2-1: r8712u: USB_SPEED_HIGH with 4 endpoints
[ 2625.807356] usb 2-1: r8712u: Boot from EFUSE: Autoload OK
[ 2626.214352] usb 2-1: r8712u: CustomerID = 0x0000
[ 2626.214358] usb 2-1: r8712u: MAC Address from efuse = c8:be:19:d6:0f:23
[ 2626.214361] usb 2-1: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
[ 2627.247370] r8712u 2-1:1.0 wlp0s29f7u1: renamed from wlan0

"iwconfig" shows
wlp0s29f7u1  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

"nmcli d" does not show the device

"ifconfig" does not show the device

Network connection will not be made.

Expected results:
A network device is automatically configured, the device is visible in all the management tools and a network connection will be made using the adapter.

Additional info:
Everything did work until the Networkmanager update last night. The DNF log is attached to this bug.

Comment 1 Sam Irlapati 2016-04-08 02:41:35 UTC
I have the same problem. Here are the relevant lines from journalctl

Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: new high-speed USB device number 6 using ehci-pci
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=8172
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: Product: RTL8191S WLAN Adapter 
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: Manufacturer: Manufacturer Realtek 
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: SerialNumber: 00e04c000001
Apr 07 21:19:47 Salem.irlanet.org kernel: r8712u: register rtl8712_netdev_ops to netdev_ops
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: r8712u: USB_SPEED_HIGH with 4 endpoints
Apr 07 21:19:47 Salem.irlanet.org kernel: usb 2-1: r8712u: Boot from EFUSE: Autoload OK
Apr 07 21:19:48 Salem.irlanet.org kernel: usb 2-1: r8712u: CustomerID = 0x000a
Apr 07 21:19:48 Salem.irlanet.org kernel: usb 2-1: r8712u: MAC Address from efuse = 08:10:78:70:d2:3a
Apr 07 21:19:48 Salem.irlanet.org kernel: usb 2-1: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Apr 07 21:19:48 Salem.irlanet.org NetworkManager[933]: <info>  (wlan0): driver does not support SSID scans (scan_capa 0x00).
Apr 07 21:19:48 Salem.irlanet.org NetworkManager[933]: <info>  (wlan0): using WEXT for WiFi device control
Apr 07 21:19:48 Salem.irlanet.org mtp-probe[7380]: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:13.2/usb2/2-1"
Apr 07 21:19:48 Salem.irlanet.org mtp-probe[7380]: bus: 2, device: 6 was not an MTP device
Apr 07 21:19:49 Salem.irlanet.org kernel: r8712u 2-1:1.0 wlp0s19f2u1: renamed from wlan0
Apr 07 21:19:51 Salem.irlanet.org ModemManager[740]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:13.2/usb2/2-1': not supported by any plugin

Comment 2 Sam Irlapati 2016-04-08 02:42:52 UTC
I was able to get things working by downgrading NetworkManager to 1.0.12-1

Comment 3 Rene Ploetz 2016-04-08 22:58:34 UTC
I have the same issue using an TP-LINK Archer T2U using an out-of-tree kernel driver (from https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916). Downgrading works.

Maybe this is some general issue with either out-of-tree drivers or (some?) 802.11n-devices?

Comment 4 Beniamino Galvani 2016-04-11 07:43:29 UTC
Hi, bug 1325631 is for the same issue, could you please attach debug logs there? Thanks!

*** This bug has been marked as a duplicate of bug 1325631 ***