[lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Welp . . . not getting it . . . .  I ran mainline to --install-latest   and
it installed 5.19.5 kernel.  It said on the console, "reboot to select new
kernel."  Rebooted over to TW and ran "grub2-mkconfig xxxxxxx" to get it to
run os-prober and make a new grub . . . .  Shut down.  Cold booted to grub
and selected Lu . . . and still running kernel is 5.13 . . . ???

I tried to uninstall oldest kernel but mainline said, "error: can't find
running kernel."  Ssked mainline to list the kernels and then it showed
5.13 as "running" . . . and there are two 5.19 kernel options showing as
installed in the list???

I had a similar type of problem with Pop_OS! at one point, where they use
the /efi/boot partition to install the kernel . . . and it over-filled the
directory with kernels . . . and couldn't get grub to select the newer
kernel . . . .  Turned out there, there was hardware issues . . . it all
got rather "complicated" after a lot of messing around.  Here I saw
somewhere in apt it was saying "trying to boot from /dev/sdc9" . . . and
that is a swap partition . . . .

Couldn't find my notes on how to show uuid  in efibootmgr to see what is
showing up there.  Perhaps I'll use mainline to remove the 5.19 kernels and
see then the next time if apt dist-upgrade will upgrade the kernel???

F

On Sat, Sep 10, 2022 at 12:45 PM Fritz Hudnut <este.el.paz at gmail.com> wrote:

> Nio:
>
> Right you are . . . there is something that "grub" is missing . . . .
> **Ordinarily** I can just refresh the bootloader in TW, which is the master
> controller and that picks up the weekly kernel changes . . . .  But,
> sometimes possibly something happens that messes up something like the
> UUID's for the partitions and then I have to run a command to make the new
> grub listing . . . .
>
> I've tried to disable grub in the non-controller systems, but seems like
> in ubuntu they don't want to relinquish control over grub???  I and others
> had a bug report going on it . . . possibly this is why at times grub
> "loses track" of the kernel options . . . ???
>
> And, then combined with old guy memory of what was done to fix stuff . . .
> .  Historically I have had to "chroot" into the TW install to update grub
> due to these "conflicts" over who gets to run grub . . . .
>
> But, thanks for the reminder on it . . . .  : - 0  "What day is this???"
> [senior question that older folks used to ask when I was do acu treatment
> in hospitals]  Seize the day and update-grub!!
>
> F
>
> On Sat, Sep 10, 2022 at 11:55 AM Nio Wiklund <nio.wiklund at gmail.com>
> wrote:
>
>> Hi Fritz,
>>
>> This is what I think:
>>
>> If the active grub is controlled by some other distro in a dual-boot or
>> multi-boot setup,
>>
>> sudo update-grub
>>
>> of Lubuntu will not upgrade which kernel it points to. You should boot
>> into the system that controls the active grub and run
>>
>> sudo update-grub
>>
>> or some corresponding command. Chances are that it will make Lubuntu
>> boot into the 5.19 kernel.
>>
>> Best regards
>> Nio
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-users/attachments/20220910/94ceeceb/attachment.html>