Removing Missing Firmware Warnings From mkinitcpio

Does anyone know how to remove or blacklist the firmware modules that get flagged as missing when running:

sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 5.13.9-zen1-1-zen
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 5.13.9-zen1-1-zen
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful

I don’t have any hardware the warnings relate to on my system, so I don’t really want to install the related AUR packages to make them go away.

You can install the firmware for those devices. But overall these warnings do no harm and just look ugly. As long as everything works, you should just ignore it. Also keep in mind, it’s just a warning, not an error.

For example, this is the firmware for wd719x.

1 Like

Just ignore them, they are normal.

3 Likes

Do they not irritate you? My eyes are fine-tuned to warnings.

I got used to seeing them after a while and they just became normal. :nerd_face:

4 Likes

As long as you know what the warning means, it simply is working as intended. When I look at that output, I just see that everything is as it should be.

but @I0F is right - you can install them, and while they have no use - the errors would go away.

Isn’t there any sensible way to configure mkinitcpio telling it what modules to include and what not? Installing packages you’re never going to use seems just a tad wrong.

2 Likes

:upside_down_face:

1 Like

I also have them. They are just messages that inform. They are not really errors.

2 Likes

You could blacklist them maybe? I don’t know. I’m not going to modifiy mkinitcpio just so I can not see 3 lines asking me to install something completely irrelevant.

2 Likes

Arch Wiki:

https://wiki.archlinux.org/title/mkinitcpio#Possibly_missing_firmware_for_module_XXXX

These appear to any Arch Linux users, especially those who have not installed these firmware modules. If you do not use hardware which uses these firmwares you can safely ignore this message. Currently, the only solution for suppressing warnings for wd719x and aic94xx modules is actually installing firmware packages for them.

“These appear to any Arch Linux users, especially those who have not installed these firmware modules” - well, yeah :laughing:.

4 Likes

So as per post from @Stagger_Lee - I stand corrected, other than installing them, no there isn’t.

1 Like

There I installed ALL the firmware so the messages are gone not that it was needed. :laughing:

==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.10.56-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.10.56-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
(5/5) Update grub after installing or removing a kernel or microcode.
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

Press ENTER to close this window: 

@Feakster

I am a little anal (not saying you are, but I am) and those warnings used to irritate me also. :crazy_face:

But a friend said to consider this an exercise for controlling my anal behavior. :grimacing:
Soon I accepted this as pacman doing it’s job and nothing more. :smiley:
Don’t worry, be happy.

This method is far easier and better than trying to eliminate the warnings.

Pudge

9 Likes

Clutter up the system with useless stuff to suppress harmless warnings that only appear on kernel updates.

Makes sense.

3 Likes

To me they are just messages. But i installed the firmware anyway. The two are for scsi, the other is for usb 3.0 hardware.

Edit: Now i got more Bloat! :rofl:

1 Like

Totally off topic here. Stagger_Lee is your user name based on the song Stagger Lee by LLoyd Price?

EDIT:
Man am I ever dating myself on this one.

Pudge

1 Like

You’re not warning free just yet! :stuck_out_tongue:

2 Likes

Yes, which is based on a real event, by the way.

Though I am partial to the version by Nick Cave & the Bad Seeds, from their Murder Ballads album (warning - exceptionally Not Safe For Work).

3 Likes