On Sat, 09 Nov 2019 04:59:50 -
Not Random wrote:
> The confusing thing is that the output of 'grub2-editenv list' and grubby
> both show that currently the correct (newest) kernel is the saved kernel.
> This kernel isn't what is actually selected at boot though!
That sounds as if grub may
Tim:
>> Doing a bit of googling, /boot/grub2/grubenv file cannot be manually
>> edited. Use the following command instead:
>>
>> [root@host ~]# grub2-set-default 0
>> [root@host ~]# grub2-editenv list
>> saved_entry=0
>>
>> That 0 should mean the most recently installed kernel.
(I should add tha
> I think the problem is that just tells Fedora to use the previously
> saved entry as its default, and there's other things (perhaps more than
> one) that determine what will actually be the default.
>
> In the old grub (which was easier to follow the instructions) if you
> wanted a particular bo
On Fri, 2019-11-08 at 06:20 +, Not Random wrote:
> /etc/default/grub contains:
> GRUB_DEFAULT=saved
> which as you say is the default for Fedora.
>
> There's no benefit in changing /etc/default/grub as it is already set
> correctly.
I think the problem is that just tells Fedora to use the pre
> I have no idea how it determines the newest, but the saved
> kernel is saved in the grubenv file which you can edit
> with the grub2-editenv command (but only after getting
> hundreds of errors because the command line syntax
> for editenv is very obscure and easy to scre up :-).
Thank you.
T
On Fri, 08 Nov 2019 06:20:30 -
Not Random wrote:
> I need to understand how Fedora/grub determines the newest kernel as that
> logic is somehow broken.
I have no idea how it determines the newest, but the saved
kernel is saved in the grubenv file which you can edit
with the grub2-editenv com
> What is the output of "grub2-editenv list"?
As mentioned:
# grub2-editenv list
saved_entry=2dc3a3c6f8494c8fb93c27f99dc3a246-5.3.8-300.fc31.x86_64
boot_success=1
boot_indeterminate=0
kernelopts=root=UUID=ac6336b1-7fd2-43d7-af44-51b592f3ab8f ro rhgb quiet
The saved_entry field matches what grubb
Thanks!
# grub2-editenv list
saved_entry=2dc3a3c6f8494c8fb93c27f99dc3a246-5.3.8-300.fc31.x86_64
boot_success=1
boot_indeterminate=0
kernelopts=root=UUID=ac6336b1-7fd2-43d7-af44-51b592f3ab8f ro rhgb quiet
For reference, I now have 2 Fedora 31 kernels:
# rpm -q kernel
kernel-5.3.7-301.fc31.x86_64
I bet it's something to do with the change to BootLoaderSpec-style
configuration files in fedora 30!
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to u
On 11/7/19 10:20 PM, Not Random wrote:
While I could remove the Fedora 30 kernel(s), that doesn't fix the problem. As
soon as I end up with 3 bootable kernels again it always selects the wrong one!
/etc/default/grub contains:
GRUB_DEFAULT=saved
which as you say is the default for Fedora.
Wha
I just tested removing one of the old kernels again. It is still stubbornly
booting the 3rd entry, which is now the Recovery option!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.
Thank you!
I wrote that post from memory, so please excuse the mistake with the grub2
switch, without that switch the correct kernel is returned as the default boot
kernel.
While I could remove the Fedora 30 kernel(s), that doesn't fix the problem. As
soon as I end up with 3 bootable kernels
...
> * Grubby seems to thing the default kernel is selected...but grub never boots
> it:
> # grubby --grub2 --default-kernel
man grubby
=> no parameter "--grub2"
> /boot/vmlinuz-5.3.7-301.fc31.x86_64
> # rpm -q kernel
> kernel-5.2.18-200.fc30.x86_64
> kernel-5.3.7-200.fc30.x86_64
>
Hello,
I've had a confusing problem with grub2 for some time now. I'm now running
Fedora 31, but ever since upgrading to to Fedora 30 grub has always defaulted
to selecting the 3rd entry. This means that unless I stop it, Grub will always
boot my oldest installed kernel.
* My system is dual
14 matches
Mail list logo
