After kernel upgrade, still attempting to boot 5.13

[bralz]

I recently made the upgrade from 5.13 → 5.15. And everything is working fine.

However, when rebooting my computer I am given an error:

error: file '/boot/vmlinuz-5.13.-x86_64 not found.
error: you need to load the kernel first.

That makes sense, because I removed 5.13 after installing 5.15. So now, everytime I reboot I need to go into the emacs-like editor and manually replace instances of 5.13 with 5.15 to get the kernel to load.

How can I edit whatever file that is (the one that is opened by the emacs-like editor) so I can get this machine to stop trying to boot 5.13? Thanks in advance.

[brahma]

post output from:
mhwd-kernel -li

[bralz]

Sure:

Currently running: 5.15.46-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux515

[brahma]

run these commands and post outputs from them:
sudo update-grub
sudo mkinitcpio -P

[bralz]

Found the problem after running sudo update-grub:

/etc/default/grub: line 8: i915.enable_dpcd_backlight=0: command not found

I am running a toughbook that has backlight issues with Manjaro. I had to edit grub to get the screen to stop being pitch black.

I’ve removed that line and run the commands and they were both successful afterwards though.

[brahma]

i wanted to see if those commands detects the 5.13 kernel…

[bralz]

Ok here’s those outputs:

Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.46-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> 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'
  -> -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.46-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> 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

[brahma]

not detected…
and from these:
ls /etc/mkinitcpio.d/*.preset
sudo ls /boot/initramfs-*
sudo ls /boot/vmlinuz-*
sudo ls /usr/lib/modules/*

[bralz]

/etc/mkinitcpio.d/linux515.preset

/boot/initramfs-5.15-x86_64-fallback.img  /boot/initramfs-5.15-x86_64.img

/boot/vmlinuz-5.15-x86_64

/usr/lib/modules/5.15.46-1-MANJARO:
extramodules   modules.alias.bin          modules.builtin.modinfo  modules.order        pkgbase
kernel         modules.builtin            modules.dep              modules.softdep      vmlinuz
kernelbase     modules.builtin.alias.bin  modules.dep.bin          modules.symbols
modules.alias  modules.builtin.bin        modules.devname          modules.symbols.bin

/usr/lib/modules/extramodules-5.15-MANJARO:
version

[brahma]

no 5.13, also check here:
cat /boot/grub/grub.cfg
under menu entries if the 5.13 is detected

[bralz]

There is nothing related to 5.13 in the output from grub.cfg. It looks like the 5.13 entries I was manually editing have been replaced by 5.15.

[brahma]

so reboot and see if it happens again

[bralz]

Works fine now. It must have been that backlight option I had set in grub.

[mootiny]

Exact same problem… instead of i915 (intel builtin?) my system was amdgpu (I imagine the other backlight issue is in play any time the backlight isn’t targeting a virtual device)…

So, seems if you’ve implemented the backlight workaround (at least two variations), it’d be a solid idea to make sure everything was generated as expected, before rebooting.

To that end, go ahead and take the time to revisit your workaround and see if there’s a more easily managed fix (this was the 3rd time the workaround that worked for me botched and automated process in a way that was more frustrating than my backlight issue itself… I’ve changed my stance on it).