Ubuntu 20.04.6 LTS apt problems - how to upgrade f/w?

Bo Berglund bo.berglund at gmail.com
Wed Nov 27 09:31:16 UTC 2024


On Wed, 27 Nov 2024 07:58:08 +0000, Colin Law <clanlaw at gmail.com> wrote:

>On Wed, 27 Nov 2024 at 07:09, Bo Berglund <bo.berglund at gmail.com> wrote:
>>
>> Exactly *how* do I change the default kernel in grub via an SSH terminal
>> connection??
>> And to which should I point it?
>>
>> There seems to be no easily editable file to handle this unless you mean I
>> should edit the /etc/default/grub file.
>
>At some point you, or someone else, must have edited /etc/default/grub.
>
>Edit /etc/default/grub, change it back to 0 and run
>sudo update-grub
>and reboot.
>
>Colin L.

This morning I had already changed:
GRUB_DEFAULT=3
to
GRUB_DEFAULT=4

then:

sudo update-grub
sudo reboot

And it came back up with the same kernel...

Now following your advice above:

GRUB_DEFAULT=0

sudo update-grub
sudo reboot

And it still comes back up like this:

$ uname -r
5.4.0-89-generic

My complete active /etc/default/grub looks like this:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

Everything else is comments.

This is driving me nuts...
It looks like no matter what I do it comes up with the last kernel still active.

Do I have to move to the server location, connect a keyboard and monitor to the
PC and then reboot there to actually see the grub menu and hopefully be able to
select the new kernel to load?

There seems to be a setting hidden somewhere else that forces grub to always
bring up the latest booted kernel (or grub entry)....


-- 
Bo Berglund
Developer in Sweden




More information about the ubuntu-users mailing list