WiFi issues with Intel AX200

nickbrandt · May 17, 2024, 1:57am

Hello,

I installed EOS today after using a live installer ISO (selected nvidia option, if that is of note). I was unable to connect to WiFi during installation so I just USB tethered my iPhone, but am still unable to connect to a network via WiFi.

In the UI, I am able to see a large list of nearby networks, and when I select my network however and enter the password, the system continually tries to connect but never does.

EndeavourOS rolling x86_64
Linux 6.8.9-arch1-2

I’ve been perusing the forums for quite a bit trying to figure out what is wrong. This is where I noticed my WiFi module appear by name, and that others had the same or similar issues when they also had Windows installed. I will note that this is currently dual booted with Windows 11, however I have triple-checked that Fast Boot is disabled in Windows and I have even tried twiddling some settings in my motherboard’s BIOS that I saw in other threads but no avail. Any ideas?

inxi reports the following:

inxi -Na
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 05:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2723 class-ID: 0280

nmcli dev:

nmcli dev
DEVICE          TYPE      STATE                     CONNECTION
enp8s0f3u3c4i2  ethernet  connected                 Wired connection 3
wlan0           wifi      connecting (configuring)  My WiFi Network's name
lo              loopback  connected (externally)    lo
p2p-dev-wlan0   wifi-p2p  disconnected              --
enp5s0          ethernet  unavailable               --
enp6s0          ethernet  unavailable               --

ip link:

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:2f:74:2d:c1:2e brd ff:ff:ff:ff:ff:ff
3: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:2f:74:2d:c1:2d brd ff:ff:ff:ff:ff:ff
4: enp8s0f3u3c4i2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 72:b3:06:56:35:31 brd ff:ff:ff:ff:ff:ff
5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether 1a:d4:e0:61:d7:01 brd ff:ff:ff:ff:ff:ff permaddr 08:5b:d6:d9:33:ca

Any extra information or help would be incredibly appreciated

s4ndm4n · May 17, 2024, 3:52am

Welcome to forums.

Can you try the LTS kernel? Use Enos tool akm to install the LTS kernel and then boot using that kernel and see if this issue persists.

nickbrandt · May 17, 2024, 1:44pm

Hey, thanks for the response. I have just used akm to install and boot into the LTS kernel (6.6.30-2-lts), but still, no luck.

s4ndm4n · May 17, 2024, 1:48pm

Do you dual boot or Enos only?

nickbrandt · May 17, 2024, 1:51pm

In my OP, you can see:

s4ndm4n · May 17, 2024, 2:10pm

Seems like almost every post about this leads to disabling fast-boot. The only other solution I found is this. That reply has a link to another post where disabling power management.

Schlaefer · May 17, 2024, 2:24pm

Intel AX200 here, no issues - just as a data point.

As a hardware check https://wiki.archlinux.org/title/Network_configuration/Wireless#Check_the_driver_status might be worthwhile.

For example I have:

sudo dmesg | grep iwlwifi
[   14.076606] iwlwifi 0000:08:00.0: enabling device (0000 -> 0002)
[   14.089625] iwlwifi 0000:08:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
[   14.089924] iwlwifi 0000:08:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100
[   14.096828] iwlwifi 0000:08:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[   14.097213] iwlwifi 0000:08:00.0: loaded firmware version 77.a20fb07d.0 cc-a0-77.ucode op_mode iwlmvm
[   14.294089] iwlwifi 0000:08:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[   14.449736] iwlwifi 0000:08:00.0: Detected RF HR B3, rfid=0x10a100
[   14.522236] iwlwifi 0000:08:00.0: base HW address: 18:26:49:c6:3b:f8
[17889.431566] iwlwifi 0000:08:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1

But from what you post it seems the AX200 is correctly detected, but something goes wrong connecting to the network. I would probably move somewhat away from a AX200 hardware issue and look into more general WIFI config related problems.

I would try:

Open up the terminal and run journalctl -f to look at new log messages
Try to connect to the WIFI network
See what wifi/network related messages show up in the log

nickbrandt · May 17, 2024, 2:31pm

Checking the driver status looks almost identical there;

sudo dmesg | grep iwlwifi
[    5.022237] iwlwifi 0000:07:00.0: enabling device (0000 -> 0002)
[    5.025721] iwlwifi 0000:07:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
[    5.025729] iwlwifi 0000:07:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100
[    5.029253] iwlwifi 0000:07:00.0: api flags index 2 larger than supported by driver
[    5.029267] iwlwifi 0000:07:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[    5.029487] iwlwifi 0000:07:00.0: loaded firmware version 77.a20fb07d.0 cc-a0-77.ucode op_mode iwlmvm
[    5.187658] iwlwifi 0000:07:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    5.310044] iwlwifi 0000:07:00.0: Detected RF HR B3, rfid=0x10a100
[    5.376220] iwlwifi 0000:07:00.0: base HW address: 08:5b:d6:d9:33:ca
[    6.272916] iwlwifi 0000:07:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1

I will see what journalctl says

nickbrandt · May 17, 2024, 2:37pm

Here’s journalctl:

EDIT:

After reading through that log… I was pretty sure that the password was just entered incorrectly I’m sorry for wasting anyone’s time, thanks for the help!

Schlaefer · May 17, 2024, 2:45pm

OK, the important lines seem to be:

wlan0: 78:67:0e:be:cc:63 denied authentication (status 1)
...
wpa_supplicant[1040]: wlan0: CTRL-EVENT-AUTH-REJECT 78:67:0e:be:cc:62 auth_type=3 auth_transaction=2 status_code=1

For some reason the authentication is denied. First things that comes to mind would be MAC-address blocking or wrong password.

Schlaefer · May 17, 2024, 3:26pm

No problem. Happens to the best of us.

s4ndm4n · May 17, 2024, 3:26pm

@nickbrandt mark your post as solved friend.

system · May 19, 2024, 3:27pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.