Warning while updating initramfs-linux.img

Hello.
I have noticed that when there is an update on my Raspberry PI4 that affects the kernel, I get this worrying message when the update process generates initramfs-linux.img

WARNING: errors were encountered during the build. The image may not be complete.

I uploaded the complete log here: http://ix.io/4LVm
After this update I correctly rebooted the system, but I don’t think that message is a good thing…
Any idea?
Thanks in advance.

[2023-11-19T20:32:49+0100] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2023-11-19T20:32:49+0100] [ALPM-SCRIPTLET] → Running build hook: [block]
[2023-11-19T20:32:51+0100] [ALPM-SCRIPTLET] → Running build hook: [filesystems]
[2023-11-19T20:32:51+0100] [ALPM-SCRIPTLET] → Running build hook: [fsck]
[2023-11-19T20:32:51+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2023-11-19T20:32:52+0100] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: ‘/boot/initramfs-linux.img’
[2023-11-19T20:32:55+0100] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.

If I am not mistaken, this issue may arise if you have the hook: consolefont in /etc/mkinitcpio.conf and you haven’t explicitly set it in /etc/vconsole.conf.

I guess you would need either remove the said hook from /etc/mkinicpio.conf (the HOOK= … ) or set it in the other file mentioned above.

1 Like

Ok, thank you, I removed consolefont from the HOOK line in /etc/mkinitcpio.conf.
Anyway, this is strange: I have never modified either /etc/mkinitcpio.conf or /etc/vconsole.conf.

That sounds strange indeed!

Anyways, remeber to rebuild your initramfs. And if the issue is resolved, please mark the post pointing to solution, as solution :blush:

To reproduce the problem I re-run the update of the same packages (and also because my knowledge is not very deep and I wouldn’t know how to do the build of initramfs and be sure not to do any damage… by the way, how do you do it?).
Anyway, the situation is still the same: the message on consolefont is gone, but the pacman output is this: http://ix.io/4LVA
and it contains the same warning.

Unfortunately I don’t have access to an EnOS ARM installation at the moment to troubleshoot this further.

What I suggested above was from the top of my head.

You would need to run sudo mkinitcpio -p X replacing X with the name of the kernel.

In this case, sudo mkinitcpio -p linux-rpi (hope I got the name of the kernel package right).

I will add my info as well, because I also started to get warning

WARNING: errors were encountered during the build. The image may not be complete.

after latest update of mkinitcpio, and no luck in debugging this issue.

It happens for me only when preparing linux-lqx from https://liquorix.net/archlinux/$repo/$arch

Other kernels: zen, lts, linux - are not affected.

Debug info with -v switch does not bring anything meaningful. I made sure to install mkinitcpio-firmware, so at this point I do not get any other warnings. But original one is still present.

1 Like

This seems to be a repeat from about a year ago as described in this Thread. In this case mkinitcpio was upgraded from ver 32 to ver 33
https://bbs.archlinux.org/viewtopic.php?id=281468

That thread reads like the same problem we are having now.

As long as you get readable text in a tty console (such as Crtl-Alt-F3) then you are Okay.

If it really bugs you, then as suggested in the above thread

edit /etc/mkinitcpio.conf, find "HOOK=()" and delete "consolefont"

IMHO this nothing more than an irritation and will cause no harm. Give it some time and like a year ago they will fix this.

Another solution is to switch to dracut. For ARM, I am working on this today because of mkinitcpio problems like this.

Pudge

EDIT:
After I resolve a few bugs, I will be releasing dd compatible images for RPi 4b, and Odroid N2 with the new Galileo version of Calamares.

FYI: Removing consolefont hook does not solve it and thread you posted says about different error. We are discussing WARNING: errors were encountered during the build. The image may not be complete.