ricardo_brz

I'd like to congratulate you for a great release (24.2.1) with KDE! I was looking for a guide to install KDE in a minimum version, but I could not trim it down enough, and this release solved my issues. Everything is working smoothly, video acceleration is there, Wi-Fi (AX210) is there, bluetooth is there! A real pleasure to use. Best, team!

Did you try any of the rolling builds from GitHub, to check it could work? As DroZDI said: we need kernel 6.1 as a minimum.

Great, @Igor! That fixed the last warning I got! Thank you!

Hi the error is back: GPG error: http://mirrors.jevincanders.net/armbian/apt noble InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 I tried to add the key, but apt-key is deprecated: $wget -qO - http://mirrors.jevincanders.net/armbian/apt/armbian.key | sudo apt-key add - Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). OK From man page it should be using a new .asc file, instead of the .key: If your existing use of apt-key add looks like this: wget -qO- https://myrepo.example/myrepo.asc | sudo apt-key add - Then you can directly replace this with (though note the recommendation below): wget -qO- https://myrepo.example/myrepo.asc | sudo tee /etc/apt/trusted.gpg.d/myrepo.asc So just seat and wait for the repos to adjust. EDIT: I run armbian-config again to reconfigure mirrors, and I get this one: http://armbian.chi.auroradev.org/apt that runs fine. In the end I got a warning: W: http://apt.armbian.com/dists/noble/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details I did the upgrade and then tried updating again, and I got the same issue.

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

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 ...

The one posted by Efe here is official, do you mean you want something more official than that?

did you also check the power supply? Another thing I noticed was that among your trial you used: Maybe you have installed this at some point and it kinda breaks the process and you need to reinstall the "plus" one again to fix it?

I use 154! I understand it will use C.UTF-8 as locale. That's what I've been using forever, and it just works...

Maybe it's being recognized as a different type of device? Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (Driver CDROM Mode) Try searching for "wifi usb recognized as mass storage", maybe you'll need something like this: https://wiki.archlinux.org/title/Mobile_broadband_modem

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!

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?