Warnings on update

Since I additionally installed the 5.4 LTS kernel, I get some warnings with every update.

==> WARNING: Possibly missing firmware for module:

Here the last output from today:

Updates from upstream:
Name        Current   ->  New       DownloadSize
----        -------   --  ---       ------------
cryptsetup  2.3.3-1   ->  2.3.4-1   562,38 KiB
gnutls      3.6.14-2  ->  3.6.15-1  2,72 MiB
Updating, elevated privileges required. Passwort: 
:: Synchronisiere Paketdatenbanken...
 core                                        132,5 KiB  2007 KiB/s 00:00 [----------------------------------------] 100%
 extra ist aktuell
 community                                     5,2 MiB  20,1 MiB/s 00:00 [----------------------------------------] 100%
 multilib                                    160,6 KiB  52,3 MiB/s 00:00 [----------------------------------------] 100%
 endeavouros ist aktuell
:: Starte vollständige Systemaktualisierung...
Löse Abhängigkeiten auf...
Suche nach in Konflikt stehenden Paketen...

Pakete (2) cryptsetup-2.3.4-1  gnutls-3.6.15-1

Gesamtgröße des Downloads:           3,28 MiB
Gesamtgröße der installierten Pakete:  8,91 MiB
Größendifferenz der Aktualisierung:  0,03 MiB

:: Installation fortsetzen? [J/n] j
:: Empfange Pakete...
 cryptsetup-2.3.4-1-x86_64                   568,3 KiB  5,97 MiB/s 00:00 [----------------------------------------] 100%
 gnutls-3.6.15-1-x86_64                        2,7 MiB  24,7 MiB/s 00:00 [----------------------------------------] 100%
(2/2) PrĂĽfe SchlĂĽssel im SchlĂĽsselring                                   [----------------------------------------] 100%
(2/2) Überprüfe Paket-Integrität                                         [----------------------------------------] 100%
(2/2) Lade Paket-Dateien                                                 [----------------------------------------] 100%
(2/2) PrĂĽfe auf Dateikonflikte                                           [----------------------------------------] 100%
:: Verarbeite Paketänderungen...
(1/2) Aktualisiere cryptsetup                                            [----------------------------------------] 100%
(2/2) Aktualisiere gnutls                                                [----------------------------------------] 100%
:: Starte post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating linux initcpios...
==> 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.4.62-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 gzip-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.4.62-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.8.6-arch1-1
  -> 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: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.8.6-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
(3/4) Inform user to reboot after certain system package upgrades.
(4/4) Updating the info directory file...

upstream update done!
Press ENTER to close this window:

Here is a thread about he same warnings:

Ok, I wrote the blacklist, but how I can rebuild the initframe?

You have to neither write the blacklist nor rebuild the initramfs. The conclusion in that thread was that this would not make any difference and those warnings are harmless. I still get them and my system works just fine.

6 Likes

Many thanks @pebcak :ok_hand:t2:

1 Like

this one is new the 2 others are there for longer…


it is only a warning and only an issue on special hardware needing this firmwares to work.

Obviously I then have this hardware. But I cannot do anything with this link, how should I be able to load this firmware? The problem with these warnings did not occur until I installed the 5.4 LTS kernel additionally. If I leave the 5.9 LTS kernel as fallback and the 5.4 is deleted, the problem should be solved, right? As I said, the messages did NOT come up when I only installed the mainline kernel.

Possibly missing firmware it says :wink: the firmware seems not to be included in the kernels from Archlinux.

see here:
https://wiki.archlinux.org/index.php/Mkinitcpio#Possibly_missing_firmware_for_module_XXXX

first check if you have linux-firmware package installed:

core/linux-firmware 20200817.7a30af1-1 (121.6 MiB 562.5 MiB) (Installed)
    Firmware files for Linux

then provide hardware info:

inxi -Fxxc0z --no-host | curl -F 'f:1=<-' ix.io

I installed the linux-firmware:

[uwe@HAL ~]$ sudo pacman -Si linux-firmware
[sudo] Passwort fĂĽr uwe: 
Repositorium             : core
Name                     : linux-firmware
Version                  : 20200817.7a30af1-1
Beschreibung             : Firmware files for Linux
Architektur              : any
URL                      : https://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=summary
Lizenzen                 : GPL2  GPL3  custom
Gruppen                  : Nichts
Stellt bereit            : Nichts
Hängt ab von             : Nichts
Optionale Abhängigkeiten : Nichts
In Konflikt mit          : Nichts
Ersetzt                  : Nichts
Größe des Downloads      : 121,57 MiB
Installationsgröße       : 562,54 MiB
Packer                   : Laurent Carlier <lordheavym@gmail.com>
Erstellt am              : Do 20 Aug 2020 06:43:39 CEST
Verifiziert durch        : MD5-Summe  SHA-256-Summe  Signatur

[uwe@HAL ~]$ 

with inxi -Fxxc0z --no-host | curl -F 'f:1=<-' ix.io

i became this:

http://ix.io/2wpE

System:    Kernel: 5.8.7-arch1-1 x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 wm: xfwm4 
           dm: LightDM Distro: EndeavourOS 
Machine:   Type: Desktop Mobo: ASUSTeK model: P8H61-M LE/USB3 v: Rev x.0x serial: <filter> UEFI: American Megatrends 
           v: 0801 date: 09/26/2011 
CPU:       Info: Quad Core model: Intel Core i5-2500K bits: 64 type: MCP arch: Sandy Bridge rev: 7 
           L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 26340 
           Speed: 1717 MHz min/max: 1600/3700 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 4: 1596 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
           vendor: Sapphire Limited driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:67df 
           Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 2560x1440~60Hz s-dpi: 96 
           OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.38.0 5.8.7-arch1-1 LLVM 10.0.1) 
           v: 4.6 Mesa 20.1.7 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Sapphire Limited 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aaf0 
           Sound Server: ALSA v: k5.8.7-arch1-1 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8P67 and other motherboards driver: r8168 v: 8.048.03-NAPI port: d000 bus ID: 04:00.0 
           chip ID: 10ec:8168 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.87 TiB used: 510.59 GiB (12.9%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB speed: 3.0 Gb/s serial: <filter> 
           ID-2: /dev/sdb vendor: Samsung model: ST2000DM008-2FR102 size: 1.82 TiB speed: 3.0 Gb/s serial: <filter> 
           ID-3: /dev/sdc vendor: Samsung model: ST2000DM008-2FR102 size: 1.82 TiB speed: 3.0 Gb/s serial: <filter> 
Partition: ID-1: / size: 219.28 GiB used: 8.03 GiB (3.7%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 1.79 TiB used: 502.56 GiB (27.4%) fs: ext4 dev: /dev/sdb1 
Swap:      ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A gpu: amdgpu temp: 32.0 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 906 
Info:      Processes: 191 Uptime: 9m Memory: 7.75 GiB used: 1.99 GiB (25.7%) Init: systemd v: 246 Compilers: 
           gcc: 10.2.0 Packages: pacman: 904 Shell: Bash v: 5.0.18 running in: xfce4-terminal inxi: 3.1.06 
Off Topic Doubt

What happens if I uninstall this ??

1 Like

i do not see such device at your system, if you could provide journal from last boot i can validate 100% :wink:
simple search journal for firmware:
journalctl -b -0 | grep firmware

you will miss all firmware files it includes, and devices needing such will not work properly, if you have any that needs such …

[uwe@HAL ~]$ journalctl -b -0 | grep firmware
Sep 07 14:42:31 HAL kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
Sep 07 14:42:32 HAL kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Sep 07 14:42:32 HAL kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Sep 07 14:42:32 HAL NetworkManager[462]: <info>  [1599482552.7201] manager[0x557c3d38e030]: monitoring kernel firmware directory '/lib/firmware'.
Sep 07 14:47:09 HAL dbus-daemon[461]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.349' (uid=0 pid=2141 comm="sudo pacman -Si linux-firmware ")
Sep 07 14:47:09 HAL sudo[2141]:      uwe : TTY=pts/0 ; PWD=/home/uwe ; USER=root ; COMMAND=/usr/bin/pacman -Si linux-firmware
[uwe@HAL ~]$ 

So I have to uninstall it to find out if I really need it , right ?

Well , I like experiments :smiling_face_with_three_hearts: :hugs:

2 Likes

with yay -Rns -linux-firmware or only yay -R linux-firmware?

no firmware loading error, so all good.

1 Like

i would say in most cases you will see no difference… but let’s test it oi do also:

FOR SCIENCE :vulcan_salute:t4:

3 Likes

sudo pacman -R linux-firmware
sudo mkinitcpio -P

==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: csiostor
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: advansys
==> WARNING: Possibly missing firmware for module: cxgb4
==> WARNING: Possibly missing firmware for module: cxgb3
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: isci
==> WARNING: Possibly missing firmware for module: xhci_pci
==> WARNING: Possibly missing firmware for module: ums_eneub6250
==> WARNING: Possibly missing firmware for module: smsmdtv

:exploding_head: :man_technologist:t4:

╭─joekamprad@empowered64 ~  
╰─$ journalctl -b -0 | grep firmware                                                          
Sep 07 17:00:13 empowered64 NetworkManager[788]: <info>  [1599490813.6494] manager[0x56135449a030]: monitoring kernel firmware directory '/lib/firmware'.

not that interesting…

Their is a simple answer to this
If it was not on the fallback img it would be a problem
Its not on the fallback img that means you do not have the modules so the firmware is not installed.
Fallback image tries to load all modules whether installed or not as its a fallback img so nothing to worry yourself with, its all in the arch wiki somewhere

Unless you are in a VM, I would be somewhat hesitant to remove the linux-firmware package. It contains a lot of firmware beyond what would be needed by your initramfs.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/

If you do remove it, make sure you have a cached copy of the package first as you may lose your network.

1 Like