Linux Firmware differences

Hi there,
Today i recorded the problem also with the newest `linux-firmware 20240409.1addd7dc-1.2’ of today update. See the log below, it also include the previous boot with the running rev.1 firmware.
Strange that the rev.1.2 of the firmware is proposed to me in the testing branch, i understood it should be for unstable only.
I proceeded to update the mkinitcpio.conf file comparing and adding the differences with the mkinitcpio.conf.pacnew and restarted the PC, but did not solve the problem.
In any case, it seems that the problem is because the individual compressed files in ZST are not correctly decompressed even with the Mkinitcpio version 39.1-2.

journalctl -b  | grep firmware                                                                                                                               ✔ 
mag 14 09:33:26 SEi8-ViSpi kernel: i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
mag 14 09:33:26 SEi8-ViSpi kernel: i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
mag 14 09:33:26 SEi8-ViSpi kernel: i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-59.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-58.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-57.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-55.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-54.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-53.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-52.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-51.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-48.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-46.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-45.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-44.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-43.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-42.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-41.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-40.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-39.ucode failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: no suitable firmware found!
mag 14 09:33:27 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
mag 14 09:33:27 SEi8-ViSpi NetworkManager[602]: <info>  [1715672007.7506] manager[0x562674a27ec0]: monitoring kernel firmware directory '/lib/firmware'.
mag 14 09:33:27 SEi8-ViSpi kernel: r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
mag 14 09:33:27 SEi8-ViSpi kernel: r8169 0000:01:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-2)
mag 14 09:33:32 SEi8-ViSpi systemd[1]: Startup finished in 5.046s (firmware) + 2.359s (loader) + 2.276s (kernel) + 7.782s (userspace) = 17.465s.
 journalctl -b -1 | grep firmware                                                                                                                             ✔ 
mag 14 08:54:30 SEi8-ViSpi kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
mag 14 08:54:30 SEi8-ViSpi kernel: iwlwifi 0000:03:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm
mag 14 08:54:31 SEi8-ViSpi NetworkManager[524]: <info>  [1715669671.1850] manager[0x55cc158b87b0]: monitoring kernel firmware directory '/lib/firmware'.
mag 14 08:54:36 SEi8-ViSpi systemd[1]: Startup finished in 4.586s (firmware) + 3.105s (loader) + 1.659s (kernel) + 8.139s (userspace) = 17.491s.
mag 14 09:26:56 SEi8-ViSpi NetworkManager[524]: <info>  [1715671616.4531] manager: kernel firmware directory '/lib/firmware' changed

mkinitcpio has no impact on firmware loading AFAIK.

That’s a more than 3 year old kernel.
Please try newer kernels. There are 5.15, 6.1 and 6.6 (all LTS!) available. Your Bluetooth surely cannot be broken on all of those?

See my previous post, the BT with new kernel doesn’t work after a cold restart. That is the reason why i use the 5.10.216. All the higher version 5.15, 6.1 and 6.6 are giving BT timeout error after a cold restart.

Weird, but for the sake of investigating the firmware loading problem: did it present itself in the same way on all those kernels or does kernel choice have an impact?

The BT issue (with some Intel based PC) is well known for dual boot installation with W11, even with W11 fastboot disabled.
Here below other Users in the past have come to my conclusion.

The last working kernel was the 5.14.
The newest Kernel gives the same problem.