Hi, there
Considering the following two Firmware
You can check yourself what changed:
It should be the same besides the PKGBUILD changes.
There are no differences except for the ZST compression of the individual firmware files.
But I had to downgrade the Rev.1.0 and return to the previous one (Rev.1) because WiFi and BT of the Ax200 no longer worked.
Since I repeated the installation more than once on two different PCs I have to think that there is some bugs in the packaging of the Rev. 1.0
Well we might need more info.
For example … do you have zstd?
I guess I might also wonder about your kernel.
What kernel are you using?
uname -r
Please check a previous boot log when linux-firmware 20240409.1addd7dc-1.0 was installed.
Increment the number in the following to check previous boots
journalctl -b -1 | grep firmware
You should see something like this when the firmware is loaded:
May 11 14:16:56 gazelle kernel: iwlwifi 0000:00:14.3: loaded firmware version 86.fb5c9aeb.0 so-a0-hr-b0-86.ucode op_mode iwlmvm
May 11 14:16:56 gazelle kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
May 11 14:16:56 gazelle kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi
I am on a kde Plasma testing branch
The update was runnig without error and the ZSTD 1.5.5-1 is installed.
My Beelink mini-PC is based on an intel i5-8259u cpu and was running well on a 5.10 kernel (the most recent kernel was tested but not working well with BT).
Kernel
5.10.216-1-MANJARO
mar 14 09:01:40 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm
mar 14 09:01:40 SEi8-ViSpi kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
mar 14 09:01:41 SEi8-ViSpi NetworkManager[523]: <info> [1710403301.1436] manager[0x557626f63160]: monitoring kernel firmware directory '/lib/firmware'.
mar 14 09:01:42 SEi8-ViSpi kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
mar 14 09:01:42 SEi8-ViSpi kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
mar 14 09:01:44 SEi8-ViSpi kernel: Bluetooth: hci0: Waiting for firmware download to complete
mar 14 09:01:47 SEi8-ViSpi systemd[1]: Startup finished in 4.523s (firmware) + 5.859s (loader) + 1.647s (kernel) + 8.752s (userspace) = 20.781s.
Have you tried a newer kernel like 5.15, 6.1 or 6.6?
The firmware was found. was that boot with 20240409.1addd7dc-1.0 or 20240409.1addd7dc-1?
Long story
From the first installation of Manjaro, about two years ago, I faced a problem with BT (at Cold Restart after one night, the BT was not discovered and I have to boot once again or more to activate the BT) the solution was the use of Kernel 5.10, this solves everything, all the other kernels works until I leave the PC off for one night.
The boot log was relevant to the working firmware the 20240409.1addd7dc-1.
I did a Timeshift restore.
To create a log of the new firmware i have to reinstall the update.
You could, however like I mentioned, you can retrieve logs from previous boots. Say you’ve rebooted twice since you did the Timeshift restore, use -b -2:
journalctl -b -2 | grep firmware
A boot log from March likely would not include an update from April.
Maybe journalctl -b -2 instead?
Sorry for mistake, i discovered now that the logs are recorded in a reverse order.
The most recent is with higher index and that was confusing me.
Here below two logs, one doesn’t detect correctly the wifi.
In any case to achieve a clear log a will update in the next day the system and i will record the logs.
journalctl -b 29 | grep firmware
mag 11 21:46:13 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: loaded firmware version 77.ad46c98b.0 cc-a0-77.ucode op_mode iwlmvm
mag 11 21:46:14 SEi8-ViSpi kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
mag 11 21:46:14 SEi8-ViSpi NetworkManager[444]: <info> [1715456774.4945] manager[0x5596733275e0]: monitoring kernel firmware directory '/lib/firmware'.
mag 11 21:46:19 SEi8-ViSpi systemd[1]: Startup finished in 4.544s (firmware) + 6.449s (loader) + 1.448s (kernel) + 8.497s (userspace) = 20.939s.
mag 11 23:54:21 SEi8-ViSpi NetworkManager[444]: <info> [1715464461.1823] manager: kernel firmware directory '/lib/firmware' changed
journalctl -b 28 | grep firmware
mag 11 18:06:41 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: loaded firmware version 77.ad46c98b.0 cc-a0-77.ucode op_mode iwlmvm
mag 11 18:06:41 SEi8-ViSpi kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
mag 11 18:06:41 SEi8-ViSpi kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
mag 11 20:03:09 SEi8-ViSpi NetworkManager[473]: <info> [1715450589.3415] manager[0x55e7a5d46850]: monitoring kernel firmware directory '/lib/firmware'.
mag 11 20:03:14 SEi8-ViSpi systemd[1]: Startup finished in 4.560s (firmware) + 5.003s (loader) + 1.434s (kernel) + 8.800s (userspace) = 19.800s.
Ah, you’re right. I edited my posts above.
29? 28? 
How do you figure?
I did not use negative index, so to find the most recent logs i need to increase the index number to 28 and 29.
The 29 did not detect the BT (sorry not wifi)
Hi,
I have the same issue just after today’s update : the wifi stopped to work.
dmesg | grep iwl
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-66.ucode failed with error -2
Could you please explain the different steps to downgrade
Thank you for your help
uname -r
5.15.158-1-MANJARO
sudo pacman -Syu manjaro-downgrade
sudo downgrade linux-firmware
Dont do these things lightly, and dont forget about it.
(Hey you. If you are reading this thinking “Oh hey, thats a great idea for me to roll back to Plasma5”… dont. Dont do it. You’ve been warned.)
Thank you very much for your swift answer.
I just want my wifi back. What could be the best solution ?
As a temporary solution, if some of the above posts are accurate, you can downgrade the firmware package.
This should be considered safe in this scenario because of the reports but also because the difference is really the compression.
wait a tic.
Hey so. Just wondering. Since the issue is the compression…
Do you have zstd package?
Please update the linux-firmware packages to 20240409.1addd7dc-1.1.
Note that it make take a little while for all mirrors to update.