/boot/initramfs-%PKGBASE%.img

[Oldhabbits]

Just installed this new kernel 5.15.104-2 (to test), it installed (and boots) just fine but I see that mkinitcpio makes mistakes in naming the files in my /boot folder !

/boot/initramfs-%PKGBASE%.img
/boot/initramfs-%PKGBASE%-fallback.img
/boot/vmlinuz-%PKGBASE%

During install of the kernel, I see this msg : “line 270: printf: ‘P’: invalid sign” :

Updating linux initcpios...                                                                                                   [3/4]
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
/usr/lib/initcpio/functions: regel 270: printf: 'P': ongeldig opmaakteken
  -> -k /boot/vmlinuz-==> Starting build: '5.15.104-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> 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-%PKGBASE%.img'
==> Image generation successful

Could this be a (new) problem with this version of mkinitcpio (35.1-4) or with the new kernel ??
Thanks !
Eddy

[Oldhabbits]

I think I found the problem; it’s an error in /etc/mkinitcpio.d/linux515.preset !

# mkinitcpio preset file for the '%PKGBASE%' package

ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-%PKGBASE%"
ALL_microcode=(/boot/*-ucode.img)

PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-%PKGBASE%.img"
#default_uki="/efi/EFI/Linux/arch-%PKGBASE%.efi"
#default_options="--splash /usr/share/systemd/bootctl/splash-arch.bmp"

#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-%PKGBASE%-fallback.img"
#fallback_uki="/efi/EFI/Linux/arch-%PKGBASE%-fallback.efi"
fallback_options="-S autodetect"

That’s not looking right, doesn’t it ?

Cheers,
Eddy

[jrichard326]

It looks fine here with mkinitcpio 35.1-4 and kernels 6.1 and 6.2, Unstable:

Building image from preset: /etc/mkinitcpio.d/linux62.preset: 'default'
  -> -k /boot/vmlinuz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2-x86_64.img
==> Starting build: '6.2.8-1-MANJARO'
  -> 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: [filesystems]
  -> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.2-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux62.preset: 'fallback'
  -> -k /boot/vmlinuz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2-x86_64-fallback.img -S autodetect
==> Starting build: '6.2.8-1-MANJARO'
  -> 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: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.2-x86_64-fallback.img'
==> Image generation successful

[Yochanan]

@Oldhabbits

I think I found the problem

Yep, just figured out what was causing that a few minutes ago. Fixed with mkinitcpio 35.1-5.