ERROR: specified kernel image does not exist: /boot/vmlinuz-6.0-x86_64

Support
1

When updated mkinitcpio, after uninstalled linux-6.0:

Building image from preset: /etc/mkinitcpio.d/linux60.preset: ‘default’
→ -k /boot/vmlinuz-6.0-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.0-x86_64.img
==> ERROR: specified kernel image does not exist: /boot/vmlinuz-6.0-x86_64' ==> Building image from preset: /etc/mkinitcpio.d/linux60.preset: 'fallback' -> -k /boot/vmlinuz-6.0-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.0-x86_64-fallback.img -S autodetect ==> ERROR: specified kernel image does not exist: /boot/vmlinuz-6.0-x86_64’

What I done was to add .pacsave to /etc/mkinitcpio.d/linux60.preset

2

This entry can be deleted alternatively - as the specified kernel does not exist any longer…
→ uninstalled linux-6.0
Building image from preset: /etc/mkinitcpio.d/linux60.preset
fails, because “uninstalled linux-6.0” before…
/etc/mkinitcpio.d/linux60.preset now is just an unwanted leftover

1 Like
3

Yes, i know, I renamed it because there were already other uninstalled kernels with the .pacsave ending in the folder.

4

Once you manually modify the preset (is it your case?), I think the preset is kept somehow when the kernel is removed, I have this “issue” from time to time because I forget to manually check and remove what is left behind, when I remove a kernel for which I have modified its preset before.

2 Likes
5

I’ve never seen this before, i thought it was renamed by pacman/pamac once it was uninstalled.
It don’t appear in pacdiff.

1 Like
6

Who knows - is it a feature or a bug? :innocent:

1 Like