https://bugzilla.suse.com/show_bug.cgi?id=1219192 Bug ID: 1219192 Summary: On the intel AX200 WiFi there is an issue with 5 GHz (2.4 GHz is fine) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs@suse.de Reporter: R_Nik_C@proton.me QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- There is no way to connect to WiFi at 5 GHz (2.4 GHz is fine), there is a "configuration interface" and that's it. When I boot older - 6.6.11 kernel, everything seems fine.. issues are on newer - 6.7.1 kernel.
lspci | grep Network 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
zypper se -is iwlwifi kernel-default NetworkManager S | Name | Type | Version | Arch | Repository ---+----------------------------------+---------+--------------+--------+------------------ i+ | kernel-default | package | 6.6.11-1.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.6.10-1.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.7.1-1.1 | x86_64 | repo-oss i | kernel-default-devel | package | 6.6.11-1.1 | x86_64 | (System Packages) i | kernel-default-devel | package | 6.6.10-1.1 | x86_64 | (System Packages) i | kernel-default-devel | package | 6.7.1-1.1 | x86_64 | repo-oss i | kernel-firmware-iwlwifi | package | 20240115-1.1 | noarch | repo-oss i | libKF5NetworkManagerQt6 | package | 5.114.0-1.1 | x86_64 | repo-oss i+ | NetworkManager | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-bluetooth | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-branding-openSUSE | package | 42.1-6.1 | noarch | repo-oss i | NetworkManager-dns-dnsmasq | package | 1.0-1.2 | noarch | repo-oss i | NetworkManager-openconnect | package | 1.2.10-2.1 | x86_64 | repo-oss i | NetworkManager-openvpn | package | 1.10.2-3.1 | x86_64 | repo-oss i | NetworkManager-pptp | package | 1.2.12-2.2 | x86_64 | repo-oss i | NetworkManager-tui | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-wwan | package | 1.44.2-4.2 | x86_64 | repo-oss
2.4GHz connected, then I tried switch to 5GHz. When it couldn't do that, it connected to 2.4 again. here dmesg about that. [ 2116.959020] wlp4s0: AP is in CSA process, reject auth [ 2132.615435] wlp4s0: AP is in CSA process, reject auth [ 2143.199413] wlp4s0: AP is in CSA process, reject auth [ 2159.041293] wlp4s0: 80 MHz not supported, disabling VHT [ 2159.061350] wlp4s0: authenticate with b0:4e:26:80:7f:03 (local address=b0:7d:64:63:f2:59) [ 2159.062684] wlp4s0: send auth to b0:4e:26:80:7f:03 (try 1/3) [ 2159.094116] wlp4s0: authenticated [ 2159.098723] wlp4s0: associate with b0:4e:26:80:7f:03 (try 1/3) [ 2159.108670] wlp4s0: RX AssocResp from b0:4e:26:80:7f:03 (capab=0x411 status=0 aid=2) [ 2159.176913] wlp4s0: associated [ 4993.544199] wlp4s0: deauthenticating from b0:4e:26:80:7f:03 by local choice (Reason: 3=DEAUTH_LEAVING) [ 4994.135435] wlp4s0: AP is in CSA process, reject auth [ 4997.149938] wlp4s0: AP is in CSA process, reject auth [ 4998.975834] wlp4s0: AP is in CSA process, reject auth [ 5000.552059] wlp4s0: AP is in CSA process, reject auth [ 5010.486930] wlp4s0: AP is in CSA process, reject auth [ 5020.067885] wlp4s0: AP is in CSA process, reject auth [ 5032.642366] wlp4s0: AP is in CSA process, reject auth [ 5045.645518] wlp4s0: AP is in CSA process, reject auth [ 5056.675184] wlp4s0: AP is in CSA process, reject auth [ 5073.646655] wlp4s0: AP is in CSA process, reject auth [ 5084.415274] wlp4s0: AP is in CSA process, reject auth [ 5099.885612] wlp4s0: 80 MHz not supported, disabling VHT [ 5099.908004] wlp4s0: authenticate with b0:4e:26:80:7f:03 (local address=b0:7d:64:63:f2:59) [ 5099.909377] wlp4s0: send auth to b0:4e:26:80:7f:03 (try 1/3) [ 5099.941025] wlp4s0: authenticated [ 5099.946520] wlp4s0: associate with b0:4e:26:80:7f:03 (try 1/3) [ 5099.965937] wlp4s0: RX AssocResp from b0:4e:26:80:7f:03 (capab=0x411 status=0 aid=2) [ 5100.034375] wlp4s0: associated
dmesg | grep iwlwifi [ 7.297412] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002) [ 7.311782] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000 [ 7.311820] iwlwifi 0000:04:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100 [ 7.346507] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver [ 7.346525] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 7.346760] iwlwifi 0000:04:00.0: loaded firmware version 77.ad46c98b.0 cc-a0-77.ucode op_mode iwlmvm [ 7.528107] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 7.693344] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100 [ 7.769562] iwlwifi 0000:04:00.0: base HW address: b0:7d:64:63:f2:59 [ 7.790114] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0 [ 9.613899] iwlwifi 0000:04:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0 -- You are receiving this mail because: You are on the CC list for the bug.