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

[Bo Berglund]

On Tue, 26 Nov 2024 18:59:04 +0100, Bo Berglund <bo.berglund at gmail.com> wrote:

>
>OK thanks!
>
>I checked on my system:
>
>apt policy linux-image-generic-hwe-20.04
>linux-image-generic-hwe-20.04:
>  Installed: (none)
>  Candidate: 5.15.0.126.136~20.04.1
>
>So I used the server install line for 20.04 LTS:
>
>sudo apt-get install --install-recommends linux-generic-hwe-20.04
>
>There were a number of warnings
>
>Warning: The home dir /var/lib/usbmux you specified can't be accessed: No such
>file or directory
>Adding system user `usbmux' (UID 125) ...
>Adding new user `usbmux' (UID 125) with group `plugdev' ...
>Not creating home directory `/var/lib/usbmux'.
>usbmuxd.service is a disabled or a static unit, not starting it.
>
>W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for
>module amdgpu
>W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module
>amdgpu
>
>But it reacheda done final stage....
>
>And now I have:
>
>$ uname -r
>5.4.0-89-generic
>
>dpkg --list 'linux-image*' | grep ^ii
>ii  linux-image-5.15.0-126-generic          5.15.0-126.136~20.04.1 amd64
>Signed kernel image generic
>ii  linux-image-5.4.0-200-generic           5.4.0-200.220          amd64
>Signed kernel image generic
>ii  linux-image-5.4.0-89-generic            5.4.0-89.100           amd64
>Signed kernel image generic
>ii  linux-image-generic                     5.4.0.200.196          amd64
>Generic Linux kernel image
>ii  linux-image-generic-hwe-20.04           5.15.0.126.136~20.04.1 amd64
>Generic Linux kernel image
>
>Do I have to reboot to finalize this kernel upgrade?
>
>
>If so I have a window between 8 and 11 tomorrow mmorning when the server is not
>scheduled for anything important.


I switched off a non-important task which opened up the window for reboot
between 9 and 10 tonight and rebooted today...

The logon message after the reboot reads:

Expanded Security Maintenance for Applications is enabled.

Your Hardware Enablement Stack (HWE) is supported until April 2025.

*** Kernel upgrade required. Kernel 5.4.0-89.100-generic Livepatch coverage has
ended ***

And checking the system:

$ uname -r
5.4.0-89-generic

$ dpkg --list 'linux-image*' | grep ^ii
ii  linux-image-5.15.0-126-generic          5.15.0-126.136~20.04.1 amd64
Signed kernel image generic
ii  linux-image-5.4.0-200-generic           5.4.0-200.220          amd64
Signed kernel image generic
ii  linux-image-5.4.0-89-generic            5.4.0-89.100           amd64
Signed kernel image generic
ii  linux-image-generic                     5.4.0.200.196          amd64
Generic Linux kernel image
ii  linux-image-generic-hwe-20.04           5.15.0.126.136~20.04.1 amd64
Generic Linux kernel image

So it seems like now the situation is that there are several later kernels on
the system but it still uses the very oldest....

How can I make it upgrade to the latest kernel???

It seems like it keeps the old kernel and boots back to it after the
installations have been done...

How can I make the system boot to the new kernel?
Is there some tool to modify the grub menu to boot into the new kernel?

As I said I have no hardware access, just SSH (using PuTTY)....

-- 
Bo Berglund
Developer in Sweden