I get a few Warnings with mkinitcpio, should i ignore it?

I just merged mkinitcpio.pacnew file.

after that i used command:

sudo mkinitcpio -P

And saw 7 Warnings:

==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.125-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.125-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
==> Image generation successful

Hi @Kobold,

AFAIK if your system isn’t negatively impacted, ignoring any Warning is fine, it’s Errors you should be concerned about.

Hope this helps!

3 Likes

You can safely ignore those warnings, but if you’re tired of seeing them, install the package linux-firmware-qlogic from the repository. :arrow_down:

sudo pacman -S linux-firmware-qlogic

:wink:

1 Like

Check the file /etc/vconsole.conf
$ cat /etc/vconsole.conf

$ cat /etc/vconsole.conf

KEYMAP=de
FONT=
FONT_MAP=
  1. Try to change it to:
KEYMAP=de

without two last lines FONT= and FONT_MAP=

  1. Run $ sudo mkinitcpio -P, check if this warning is gone.
1 Like

I changed the file and did this command again.

But the logs are identical… should i maybe need to restart the system after edit vconsole.conf
maybe no changes because of caching?

Now I know.

When mkinitcpio loads the hook consolefont, you need to define a custom font FONT=[font name] (e.g. FONT=ter-220n) in /etc/vconsole.conf, that will change font for boot log.

OR

If you do not want a custom font for boot log, just remove the hook consolefont in /etc/mkinitcpio.conf

I don’t have any mention of consolefont in my /etc/mkinitcpio.conf, but I get that warning too. I do however have the two FONT lines in my /etc/vconsole.conf. :wink:

Are you using the hook systemd and sd-vconsole in mkinitpcio.conf?

I checked mkinitcpio without the hook systemd and no consolefont in VM, this warning is gone.
If I added the hook consolefont and font is empty in /etc/vconsole.conf , the warning appears.

I am, yes. :wink: :arrow_down:

HOOKS=(base systemd autodetect modconf kms block keyboard sd-vconsole filesystems)

I dont.

HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems fsck)

If you remove sd-vconsole, the warning may be gone?
but that is bad idea, because you would lose the function KEYMAP=.
sd-vconsole = consolefont + keymap
https://wiki.archlinux.org/title/mkinitcpio#Common_hooks

1 Like

Then in your case, remove the consolefont from that line and run… :arrow_down:

sudo mkinitcpio -P

… again. :wink:

1 Like

@Aragorn
@Zesko
Im a little confused :smiley:

Im actually doing file Merging my pacnew files to maintain my system.

But where is the reason, why this actually brandnew pacnew file has this “outdated” changes that lead to even more warnings.

All this made me think that this pacnew mergings are atleast to 70% nonsense. :upside_down_face:

Yes, it’ll only properly work upon the next reboot, unless you restart systemd-vconsole-setup.service. :arrow_down:

sudo systemctl restart systemd-vconsole-setup.service

Commenting out the two FONT entries in /etc/vconsole.conf also gets rid of the warning. :wink:


.pacnew files usually only contain default values and/or examples of such.

The idea is that you’d look at them, compare them to your own configuration, and if there’s anything new that needs to be added, copy that over into your own configuration file, or adapt it to your own configuration.

There’s no need to replace your own configuration by the one in the .pacnew — that may even be undesirable.

1 Like

That’s why it’s merge. Combined.

Sometimes, I think, settings can also become totally unnecessary, change…or even compulsory, and you have to adapt your configuration to it. Otherwise the software may stop working. It literally changes between and from person-to-person. There’s no one-size-fits-all sollution.

:man_shrugging:

1 Like

And by the way, some of those warnings regarding missing firmware are for driver modules which are not supplied. One of them is available from the AUR — it’s an Adaptec SAS RAID driver for the AIC-94xx adapter family — but the others are neither in the repositories nor in the AUR.

1 Like

Nobody is perfect, including the manjaro developers. Just as a reference: in the current (May) install iso, this is the default setting. Consolefont as hook and then missing consolefont in .conf. (DE locale and xfce). Which produces this warning.
Well, somebody missed it. Does not matter much in that case.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.