You are not logged in.

#1 2019-04-17 14:46:13

jaswantp
Member
Registered: 2019-04-17
Posts: 1

intel 9462 doesn't connect, iwlwifi firmware version > 38 malfunctions

So, I've been a long time arch linux user, but I've never faced the need to post a thread until now as this forum has pretty much everything there is. But this issue has been bothering me a lot, so I did some research and have no clue how to proceed. I would like the more elite arch users or someone else facing the same problem with a greater experience working with linux kernel pick it up from here.

Some information : I run the latest linux kernel provided by arch core repositories i.e, linux-5.0.7 as on 17/04/2019.

[jaswant@lemon ~]$ uname -r
5.0.7-arch1-1-ARCH

lspci output:

[jaswant@lemon ~]$ lspci -nnkd 8086:a370
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] (rev 10)
	DeviceName: Onboard - Ethernet
	Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:02a4]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

There are two ways the wireless problem manifests itself.

  1. Connect to a standard non-fancy Wi-Fi router using NetworkManager on my laptop.

  2. Setup a hotspot on my laptop and let other devices connect to it.

In the first instance, I was unable to connect to any wireless SSID, be it unsecure or WPA protected. In the second instance, I use create_ap as a systemd service to start a hotspot. The logs of which are here
Upon taking a glance at the logs, at the timestamp 18:24:36, the hotspot disconnected my mobile device:

Apr 17 18:24:36 lemon create_ap[570]: ap0: AP-STA-DISCONNECTED cc:61:e5:ce:d1:91

and from 18:24:54 on-wards, the logs show a repeated message that reads

Apr 17 18:24:54 lemon create_ap[570]: ap0: STA cc:61:e5:ce:d1:91 IEEE 802.11: did not acknowledge authentication response

If this by any means makes you think that hostapd is faulty, I think that's probably not. I decided to check dmesg for errors and this is what I get: dmesg with firmware version 43
So, to be sure that this is a firmware related issue, I installed the linux-lts kernel and did a reboot.

[jaswant@lemon ~]$ uname -r
4.19.34-1-lts

This time, there were no disconnects and output of dmesg didn't show errors apart from

BIOS contains WGDS but no WRDS

This doesn't hamper the functionality of the wireless card, so it's fine.
Here are the logs of create_ap with linux-lts. Nothing erroneous, hotspot couldn't be any better and no disconnects at all. I can also connect to other SSIDs with my laptop.
The dmesg logs with linux-lts are

[jaswant@lemon ~]$ dmesg -Tx | grep -i -E '00:14.3|wlp|iwl|80211'
kern  :debug : [Wed Apr 17 19:06:18 2019] pci 0000:00:14.3: [8086:a370] type 00 class 0x028000
kern  :debug : [Wed Apr 17 19:06:18 2019] pci 0000:00:14.3: reg 0x10: [mem 0xa4314000-0xa4317fff 64bit]
kern  :debug : [Wed Apr 17 19:06:18 2019] pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
kern  :notice: [Wed Apr 17 19:06:20 2019] cfg80211: Loading compiled-in X.509 certificates for regulatory database
kern  :notice: [Wed Apr 17 19:06:20 2019] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
kern  :info  : [Wed Apr 17 19:06:20 2019] cfg80211: failed to load regulatory.db
kern  :info  : [Wed Apr 17 19:06:20 2019] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
kern  :info  : [Wed Apr 17 19:06:20 2019] iwlwifi 0000:00:14.3: loaded firmware version 38.755cfdd8.0 op_mode iwlmvm
kern  :info  : [Wed Apr 17 19:06:21 2019] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x318
kern  :info  : [Wed Apr 17 19:06:21 2019] iwlwifi 0000:00:14.3: base HW address: 7c:2a:31:a8:61:46
kern  :debug : [Wed Apr 17 19:06:21 2019] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
kern  :info  : [Wed Apr 17 19:06:21 2019] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
kern  :info  : [Wed Apr 17 19:06:23 2019] iwlwifi 0000:00:14.3: Conflict between TLV & NVM regarding enabling LAR (TLV = enabled NVM =disabled)
kern  :err   : [Wed Apr 17 19:06:23 2019] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
kern  :info  : [Wed Apr 17 19:06:23 2019] iwlwifi 0000:00:14.3: Conflict between TLV & NVM regarding enabling LAR (TLV = enabled NVM =disabled)
kern  :err   : [Wed Apr 17 19:06:23 2019] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS

The linux-lts loaded iwlwifi firmware version 38. From intel's firmware support, it's apparent that I require iwlwifi-9000-pu-b0-jf-b0-xx.ucode. So, what I did was get back to linux-5.0.7 and take a backup of all the other versions that were in /usr/lib/firmware/ except version 38 and below. The firmware present in /usr/lib/firmware were

[jaswant@lemon ~]$ ls /usr/lib/firmware/ | grep iwlwifi-9000
iwlwifi-9000-pu-b0-jf-b0-33.ucode
iwlwifi-9000-pu-b0-jf-b0-34.ucode
iwlwifi-9000-pu-b0-jf-b0-38.ucode
iwlwifi-9000-pu-b0-jf-b0-41.ucode
iwlwifi-9000-pu-b0-jf-b0-43.ucode

With version 41 on linux-5.0.7, it worked fine for about 20 minutes after which the error repeated. So far, I've been able to get it working consistently with version 38.

Also note that lspci reports my wireless card to be 9560, whereas dmesg shows the correct card i.e, 9462
So, I think I've been able to isolate the problem to firmware iwlwifi-9000-pu-b0-jf-b0-43.ucode and iwlwifi-9000-pu-b0-jf-b0-41.ucode. But I'm not really sure if this is it. It might be something else. If anyone is able to reproduce this or give a resolution, I would be thankful.

Offline

#2 2020-07-03 19:22:02

lukicdarkoo
Member
Registered: 2020-07-03
Posts: 1

Re: intel 9462 doesn't connect, iwlwifi firmware version > 38 malfunctions

I had a similar error. I tried to make an access point, but a few minutes after configuring everything and making sure it works I would get the following error from hostapd:

... IEEE 802.11: did not acknowledge authentication response

(same as yours)

This is my configuration:
- kernel version: 5.7.1
- firmware version: iwlwifi-9000-pu-b0-jf-b0-46.ucode
- hardware: Intel Wireless-AC 9560

Downgrading firmware version to iwlwifi-9000-pu-b0-jf-b0-38.ucode helped! Thanks!

Therefore, you isolated the issue well, the error is definitely caused by the new firmware.

Offline

Board footer

Powered by FluxBB