[SOLVED] mkinitcpio fails in image generation

Greenstuff · 2025-03-09 07:36:49

After a recent update, I noticed there was an error in creating the new kernel image, here is the output of mkinitcpio -P:

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: '6.13.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> 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 zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.13.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
  -> 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: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
cat: write error: No space left on device
bsdtar: Write error
bsdtar: Write error
==> ERROR: Early uncompressed CPIO image generation FAILED: 'sort' reported an error

I did not change the way my /boot partition is mounted, and this has never happened to me before. Any help will be appreciated.

EDIT: The problem was the kms hook. I removed it and specified my video driver, and now image generation works. According to this:

https://bbs.archlinux.org/viewtopic.php?id=293333

the problem seems to be a nvidia driver that is included even when it's not needed.

Last edited by Greenstuff (2025-03-09 08:06:33)

mithrial · 2025-03-09 07:47:41

Do you have enough space left on /boot?

Greenstuff · 2025-03-09 07:50:38

mithrial wrote:

Do you have enough space left on /boot?

According to df it is 100% full. How do I free space from it?

ReDress · 2025-03-09 08:47:38

Greenstuff wrote:

mithrial wrote:
Do you have enough space left on /boot?
According to df it is 100% full. How do I free space from it?

Maybe remove unused/old kernels?

Greenstuff · 2025-03-09 14:22:09

I solved this by removing kms from the HOOKS array and adding my graphics card model to the MODULES array in /etc/mkinitcpio.conf

see the edit to the original post for more details.

ReDress · 2025-03-09 16:26:15

Greenstuff wrote:

I solved this by removing kms from the HOOKS array and adding my graphics card model to the MODULES array in /etc/mkinitcpio.conf
see the edit to the original post for more details.

Not surprising as removing removing item from the HOOKS array probably results in a smaller initramfs(which probably fits in the available space in /boot)

That might as well be a solution

Head_on_a_Stick · 2025-03-09 16:31:29

The solution would be for the mkinitcpio devs to remove the kms hook from the default configuration and instead rely on the user to add the modules manually for early KMS. I suppose a warning message would be acceptable but kms for everybody doesn't seem consistent with the Arch Way (IMO).

EDIT: actually doesn't that simpledrm device provide early KMS even without the modules?

Last edited by Head_on_a_Stick (2025-03-09 16:32:53)

Arch Linux

#1 2025-03-09 07:36:49

[SOLVED] mkinitcpio fails in image generation

#2 2025-03-09 07:47:41

Re: [SOLVED] mkinitcpio fails in image generation

#3 2025-03-09 07:50:38

Re: [SOLVED] mkinitcpio fails in image generation

#4 2025-03-09 08:47:38

Re: [SOLVED] mkinitcpio fails in image generation

#5 2025-03-09 14:22:09

Re: [SOLVED] mkinitcpio fails in image generation

#6 2025-03-09 16:26:15

Re: [SOLVED] mkinitcpio fails in image generation

#7 2025-03-09 16:31:29

Re: [SOLVED] mkinitcpio fails in image generation

Board footer