Re: LinuxKPI (iwlwifi, rtw8x) Please test! Important! (also in stable/15 now)
Date: Fri, 27 Feb 2026 13:06:00 UTC
Seems to be working for me as well. Same performance as before. iwlwifi0: <iwlwifi> mem 0x604111c000-0x604111ffff at device 20.3 on pci0 iwlwifi0: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000 iwlwifi0: PCI dev 06f0/0070, rev=0x351, rfid=0x10a100 iwlwifi0: Detected Intel(R) Wi-Fi 6 AX201160MHz iwlwifi0: successfully loaded firmware image 'iwlwifi-QuZ-a0-hr-b0-77.ucode' iwlwifi0: loaded firmware version 77.30b1cbd8.0 QuZ-a0-hr-b0-77.ucode op_mode iwlmvm iwlwifi0: Detected RF HR B5, rfid=0x10a100 iwlwifi0: base HW address: 58:6c:25:4a:ef:3e Kind regards Ben On 2/27/26 10:45, Bjoern A. Zeeb wrote: > On Wed, 25 Feb 2026, Bjoern A. Zeeb wrote: > > I've done the MFCs and all changes are also all in stab;e/15 now. > So please test! > > Lots of health, > /bz > > >> Hi, >> >> about 3 years ago, some of you may remember, we were hunting down the >> constant (firmware) crashes with iwlwifi due to net80211 not playing >> nice >> and the LinuxKPI 802.11 sta state machine not able to deal with it to >> make >> the firmware happy. >> >> In that course I unfolded some state machine bits, which resultet in >> code >> duplication and some other complications. Fast forward, I just >> undone some >> of that in main. This is probably one of the more risky changes as >> of late. >> I tried to test it but as we also have learnt in the last years, the >> testing >> of many will reveal problems more likely than me trying to test in my >> limited >> capacity. >> >> >> >> So please all test main now! >> >> Prepare yourself in case of trouble (boot envorments, or otherwise, >> in case >> you need to roll back know how to). >> Let it run for a few hours or a day or two and then please report >> back if >> it is still working without extra troubles compared to before. >> In case you hit any hiccup please report right away! >> I will try to reply promptly (I do sleep occassionally) but real life >> currently also takes some share so it may be a day before I get to the >> emails. >> Please include driver and chipset/firmware you are using if possible >> along with any possible problem report. >> >> >> >> Why is this important (now)? >> >> There'll be follow-up changes needed to get the iwlwifi update into main >> as well so that all drivers are on the same level (v6.19) for a change >> again. The reason this is important now is that this will be our base >> for 15.1-RELEASE so we will have 6ish weeks still to sort out any >> problems. >> >> In addition (bonus points) if things go smoothly there is the next >> branch >> waiting for me to merge to bring further improvements still during March >> (at least to main and possibly stable/15). >> >> >> What if you are on stable/15? >> >> I believe you could just grab the last changes and merge them yourself. >> I will go and have a look and try to merge anything I can Thu or Fri >> (before the weekend) to keep the diff minimal in case that helps! >> >> >> Lots of health! >> Bjoern >> >> >