You can install linux-firmware-qlogic to get rid of those errors, but unless you actually have qlogic stuff, you shouldn’t be worried about those warnings.
I also can reproduce that. Interesting though: These warnings only occur with the fallback initcpios not the regular ones. Shouldn’t the fallbacks include less stuff than the regular initcpios?
Of course, this will only work if you are not using any SCSI hardware on your rig (which, probably, will be true for most of us here).
Small advantage: Leaving out all the SCSI drivers in the initcpio build process, will speed things up a little bit when running mkinitcpio -P.
For convenience, here’s a patch doing the changes discussed.
--- /usr/lib/initcpio/install/block 2021-12-03 16:06:50.000000000 +0100
+++ /usr/lib/initcpio/install/block 2022-01-24 12:55:17.792192681 +0100
@@ -5,8 +5,10 @@
map add_module sd_mod? sr_mod? usb_storage? mmc_block? firewire-sbp2? virtio_blk?
- # pata, sata, scsi, nvme
- for filter in 'scsi/.*ata' '/(block|scsi|fusion|nvme)/' 'ata/[ps]ata_' \
+ # pata, sata, nvme
+ # scsi removed to avoid unnecessary missing firmware warnings
+ # on systems not using scsi
+ for filter in '/(block|fusion|nvme)/' 'ata/[ps]ata_' \
'ata/(ahci|pdc_adma|ata_piix|ata_generic)'; do
add_checked_modules "$filter"
done
@@ -34,8 +36,11 @@
help() {
cat <<HELPEOF
This hook loads the necessary modules for most block devices using pata, sata,
-scsi, firewire, usb, or mmc. Detection will take place at runtime. To minimize
+firewire, usb, or mmc. Detection will take place at runtime. To minimize
the modules in the image, add the autodetect hook too.
+In this version of the hook, the scsi drivers have been omitted to avoid
+missing firmware warnings when running mkinitcpio -P.
+Hence, DO NOT use this hook if you are using SCSI in your system.
HELPEOF
}
in addition to the changes mentioned i also saw, “sd_mod? sr_mod?” being omitted in the SCSI-less configuration.
decided to keep things as is, building fallback-initramfs with less drivers will indeed take slightly less time and will make it smaller. however considering the frequency it takes place and meddling with driver configuration (applies globally) that i have no idea about, I’ll pass on this. great work finding this BTW
The kernel runs well here - only drawback is that the Nvidia driver 495 is not compatible with it:
In file included from /home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/common/inc/nv-procfs.h:26,
from /home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/nvidia/nv-procfs.c:31:
/home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/nvidia/nv-procfs.c: In function 'nv_procfs_open_gpu_info':
/home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/common/inc/nv-procfs-utils.h:106:28: error: implicit declaration of function 'PDE' [-Werror=implicit-function-declaration]
106 | #define NV_PDE_DATA(inode) PDE(inode)->data
| ^~~
/home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/common/inc/nv-procfs-utils.h:127:27: note: in expansion of macro 'NV_PDE_DATA'
127 | NV_PDE_DATA(inode)); \
| ^~~~~~~~~~~
Looks like in this driver, some #includes are missing or set incorrectly.
The Nvidia beta driver 510.39.01 runs with kernel 5.17-rc1, without visible problems so far.
For driver 495.46, I have prepared a tentative patch and uploaded it here: The easiest way to host your text
Feel free to test it and kindly provide feedback.
But affected by what? You went digging for old issues and solution, for a problem that is explained, so what? Is your card in the list? Do you have an issue?
I kept seeing the error, “removing jack2 breaks dependency ‘jack2=1.9.20’ required by lib32-jack2” which would result in failure, came here, noticed and followed this subtle hint of a post and all’s well.