5 GHz WiFi broken after Feb 2018 update

I have a Raspberry Pi 2 with a D-Link DWA-171 wireless adapter that’s been working fine for the last year or so, but right after applying the February update and rebooting, the WiFi didn’t come back up. I found that it’s only the 5 GHz connection that doesn’t work. I’m able to connect via 2.4 GHz to the same AP, though 2.4 GHz in my area is so congested that it’s not usable for streaming anything.

I included the dmesg output below, with my SSID and BSSID masked. Has anything changed in the rtl8812au driver in this release? mySSID-5G is the 5 GHz SSID, and mySSID is the 2.4 GHz one. Thanks.

[    4.858753] usbcore: registered new interface driver rtl8812au
[...snip...]
[  171.767676] RTL8812: set ssid [mySSID-5G] fw_state=0x00000008
[  171.767918] RTL8812: set bssid:xx:xx:xx:xx:xx:xx
[  171.796713] RTL8812: start auth
[  173.349362] RTL8812: indicate disassoc
[  182.359553] RTL8812: set ssid [mySSID-5G] fw_state=0x00000008
[  182.359895] RTL8812: set bssid:xx:xx:xx:xx:xx:xx
[  182.446522] RTL8812: start auth
[  182.448619] RTL8812: auth success, start assoc
[  182.459342] RTL8812: indicate disassoc
[  185.979403] RTL8812: nolinked power save enter
[  186.623041] RTL8812: nolinked power save leave
[  192.498298] RTL8812: set ssid [mySSID-5G] fw_state=0x00000008
[  192.498379] RTL8812: set bssid:xx:xx:xx:xx:xx:xx
[  193.301227] RTL8812: start auth
[  193.314993] RTL8812: auth success, start assoc
[  193.319346] RTL8812: indicate disassoc
[  203.259441] RTL8812: nolinked power save enter
[  206.428350] RTL8812: nolinked power save leave
[  212.319818] RTL8812: set ssid [mySSID] fw_state=0x00000008
[  212.320068] RTL8812: set bssid:xx:xx:xx:xx:xx:xx
[  212.581491] RTL8812: start auth
[  212.662152] RTL8812: auth success, start assoc
[  212.691046] RTL8812: assoc success
[  212.693936] UpdateHalRAMask8812A => mac_id:0, networkType:0x0b, mask:0x000fffff
                 ==> rssi_level:0, rate_bitmap:0x000ff005
[  212.707731] RTL8812: send eapol packet
[  212.721347] RTL8812: send eapol packet
[  212.722818] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  212.724207] RTL8812: set pairwise key to hw: alg:4(WEP40-1 WEP104-5 TKIP-2 AES-4) camid:4
[  212.724230] RTL8812: set group key to hw: alg:4(WEP40-1 WEP104-5 TKIP-2 AES-4) keyid:1
[  213.581668] UpdateHalRAMask8812A => mac_id:0, networkType:0x0b, mask:0x000fffff
                 ==> rssi_level:2, rate_bitmap:0x000ff000
[  286.381845] UpdateHalRAMask8812A => mac_id:0, networkType:0x0b, mask:0x000fffff
                 ==> rssi_level:1, rate_bitmap:0x000f0000

Please post full logs. Snippets are not sufficient for us to get a full picture.

What logs do you want to see? Those are the only lines related to the wireless adapter in the dmesg output.

My preference is for grab-logs -A. It’s better to have too much information than too little.

Hi,

I have similar problem. To access my osmc, I had to enable the onboard wifi of my RPi3. My usb 5G dongle was working fine until I updated. According to dmesg, the dongle is detected, however the “wireless” option of “My OSMC” tool isn’t present anymore after the update. My complete logs can be found here: https://paste.osmc.tv/ajabebepak

Thanks!

My guess is the Realtek module is missing from the latest Kernel as already reported in another thread.

Which exact Wifi Dongle do you have?

Hi

Hopefully the issue is now addressed with the following commit:

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Edit the file /etc/apt/sources.list
  3. Add the following line: deb http://apt.osmc.tv stretch-devel main
  4. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  5. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.

I’m assuming this change did fix my issue, but I didn’t try it, given the follow-on issue with RTL8812-based adapters mentioned at

Updating to the 2018-03 release with the 4.14.26-2 kernel image did restore my 5 GHz functionality, though. Thanks!