ricardo_brz Posted December 17, 2023 Share Posted December 17, 2023 After looking at this message from @Seb042 I thought it would be better to open a new topic to discuss this. From what I saw from my install: $ dmesg ... [ 6.166453] iwlwifi 0002:21:00.0: api flags index 2 larger than supported by driver [ 6.166480] iwlwifi 0002:21:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [ 6.167021] iwlwifi 0002:21:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [ 6.267334] iwlwifi 0002:21:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [ 6.273748] iwlwifi 0002:21:00.0: reporting RF_KILL (radio disabled) [ 6.450150] iwlwifi 0002:21:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x1f [ 6.450175] iwlwifi 0002:21:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 6.450189] iwlwifi 0002:21:00.0: WFPM_AUTH_KEY_0: 0x90 [ 6.450206] iwlwifi 0002:21:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 6.450997] iwlwifi 0002:21:00.0: Detected RF GF, rfid=0x10d000 [ 6.517606] iwlwifi 0002:21:00.0: base HW address: ab:cd:ef:01:23:45 [ 6.571168] iwlwifi 0002:21:00.0 wlP2p33s0: renamed from wlan0 ... I had the same error, with the same chip (AX210). I looked for each of the message and maybe, and this is just an assumption, we, AX201 users, will have to wait until the the driver is updated for the 6.7 line? Is that right? 0 Quote Link to comment Share on other sites More sharing options...
Solution Werner Posted December 18, 2023 Solution Share Posted December 18, 2023 Probably. (bleeding) edge follows upstream not much involvement from Armbian developers there. If you want stuff working use legacy 5.10.y kernel. 0 Quote Link to comment Share on other sites More sharing options...
ricardo_brz Posted December 18, 2023 Author Share Posted December 18, 2023 Yeah, but how boring would the world be if there were no (bleeding) edge users to complain about things not working and everything just works! Thanks for the reply, btw! 0 Quote Link to comment Share on other sites More sharing options...
ricardo_brz Posted January 2 Author Share Posted January 2 (edited) Tried the latest version, still no lucky with the Wi-Fi, but I noticed this: iw reg get global country 00: DFS-UNSET (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) phy#0 (self-managed) country 00: DFS-UNSET ... And I was not able to set the country for phy#0 at all. I've tried iw reg set BR but will only change global, but phy#0 will stay the same. Also, this config is lost once I reboot. In the legacy version, this configuration is fine: ... phy#0 (self-managed) country BR: DFS-UNSET ... Edited January 2 by ricardo_brz 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted January 3 Share Posted January 3 Have you installed armbian-firmware-full via apt? 0 Quote Link to comment Share on other sites More sharing options...
ricardo_brz Posted January 3 Author Share Posted January 3 6 hours ago, Werner said: Have you installed armbian-firmware-full via apt? Yes, no lucky. Have set all the location information in armbian-config, but it's locked in phy#0 (self-managed) country 00: DFS-UNSET 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.