ricardo_brz

So the non oibaf releases don't come with the ppa only? If I configure it I'll have the same benefits as the Gnome one? Sorry, I just prefer other WM/DE than Gnome , but I'd like to have all the latest and greatest as in that release.

Can you help me with the contents of the file name? I understand edge, vendor, but then there are other suffixes that are not clear to me: are gnome-oibaf_desktop the same "kernel release" as the xfce_desktop or minimal? Or there are patches that are applied only to a specific version? Thanks!

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.

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?