#kernel image not copied to /boot by update, mkinitcpio, or kernel-install

26 messages · Page 1 of 1 (latest)

toxic olive
#

I'm at my wit's end. I have installed the latest kernel but the bootloader can only load the old version, meaning I cannot load modules and can only boot to emergency mode. I am 100% sure that /boot was mounted during my last update. None of the old forum solutions do a thing for me. This is a manual install with systemd-boot

weak lintel
#

can u retry install

toxic olive
#

I have tried reinstalling linux and reupdating from the iso

weak lintel
toxic olive
#

yes

weak lintel
#

what if u install linux lts

#

boot that

#

and if it works

#

delete and reinstall kernel

#

maybe?

toxic olive
#

would we expect pacman hooks to copy lts to boot automagically on installation? or is there another step?

#

during installation I used kernel-install to generate the loader entries but I thought mkinitcpio had handled the vmlinuz for me successfully. I don't understand why it's failing now

weak lintel
weak lintel
#

after getting lts

toxic olive
#

thanks for your ideas, i'm very worried that lts would break next time it was updated, too, cause i've done something wrong in the config

#

i have read the mcinitcpio wiki page over and over too many times tho if I do it again i'll scream

toxic olive
#

running kernel-install from the chroot generated a new loader entry but it doesn't work

#

6.8.9 IS finally in /boot, but the loader entry I use is still referring to 6.8.8, I still have to figure out why mkinitcpio is failing

#

6.8.8 is still in /boot as well. it's getting messy

#

does anyone know why the loader entries generated by kernel-install point to /boot/######/6.8.9-arch1-1/linux instead of /boot/vmlinuz-linux as documented in the wiki?

spare hull
toxic olive
#

no it generates a long serial number where I put ######

toxic olive