On 11/11/2023 22.12, Mike Wright wrote:
On 11/11/23 19:48, Robin Laing wrote:
> Hello,
>
> I did an upgrade today from from FC37 to FC39 and all went well except
> that the kernel is NOT in grub.
>
> All the apps are now FC39 but no option to boot with the FC39 kernel.
>
> I tried to reinstall the kernel to see if it would be picked up by
> grub that that didn't work either.
>
> RPM shows that the kernel is installed.
>
> How do I progress from here?
sudo update-grub ?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
I tried that and it didn't work.
I got help on the Fedora Discord and it was a strange issue related to
previous upgrades.
I had a directory on my system pointing to the FC39 kernel.
-rwx------. 1 root root 35973272 Nov 11 19:24
/boot/efi/1a7fd46e52044d0b903f101cf47a634d/6.5.11-300.fc39.x86_64/initrd
The instructions I got were to remove that directory and run the command
rpm -q --scripts kernel-core | grep add
Which brought me to this script to run.
/bin/kernel-install add 6.5.11-300.fc39.x86_64
/lib/modules/6.5.11-300.fc39.x86_64/vmlinuz || exit $?
The FC39 kernel now shows up when I run
grubby --info=ALL
From the help on Discord, the comment was:
The existence of the directory
/boot/efi/1a7fd46e52044d0b903f101cf47a634d triggers the update to
generate systemd-boot configuration. In previous version it did not
always do that.
I have done what I have been instructed remotely and will try booting in
the morning to see if it worked.
Will post an update.
Robin