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

[Nio Wiklund]

Hi again Fritz,

Is the problematic system your main system or 'only' a test system? If a 
test system you might just reinstall it to get rid of the problem.

Best regards
Nio

Den 2022-09-16 kl. 21:17, skrev Fritz Hudnut:
> Nio:
> 
> Thanks for getting back to me about it . . . .  I haven't had the time 
> to mess with it just yet.  I was thinking that that UUID number didn't 
> match anything in, what, "blkid" . . . ???  I couldn't find in my notes 
> how to see what my master grub in TW is using to identify the UUID 
> numbers of each of the 8 systems "/" filesystem to know where to boot it??
> 
> And, then I wasn't sure if I needed to fix that "resume from swap" 
> issue, or if that is correct and what should be resumed from???  I have 
> had this issue show up over the years, learned how to fix it, fixed it . 
> . . but then time passes and I forget the way to fix it . . . .
> 
> It's not the end of the world, it's just that kinetic is now stuck in 
> 5.13 . . . instead of 5.19 . . . .  The question is, whether the problem 
> is something in Lubuntu that "messed with itself" OR as "historically," 
> something in "ubuntu" grub cut across into the master grub file data in 
> TW and created a problem for Lubuntu????
> 
> On Fri, Sep 16, 2022 at 11:55 AM Nio Wiklund <nio.wiklund at gmail.com 
> <mailto:nio.wiklund at gmail.com>> wrote:
> 
>     Hi Fritz,
> 
>     I think (but am not sure) that 'resume' means resume from hibernation
>     using the swap space at the specified target. Please check if that UUID
>     matches a swap partition.
> 
>     Best regards
>     Nio
> 
>     Den 2022-09-11 kl. 20:45, skrev Fritz Hudnut:
>      > Top posting:
>      >
>      > This is the current data from Lubuntu, and that UUID number
>     doesn't show
>      > up anywhere in "sudo blkid" from in the Lu system.  But I did
>     write that
>      > number down from some "error" reports showing in the console
>     during the
>      > last apt dist-upgrade that I ran yesterday in Lu.  Somehow
>     perhaps apt
>      > did something to  mess itself up??
>      >
>      > [CODE] sudo cat /etc/default/grub
>      > # If you change this file, run 'update-grub' afterwards to update
>      > # /boot/grub/grub.cfg.
>      > # For full documentation of the options in this file, see:
>      > #   info -f grub -n 'Simple configuration'
>      >
>      > GRUB_DEFAULT=0
>      > GRUB_TIMEOUT=0
>      > GRUB_DISTRIBUTOR='lubuntu1910'
>      > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
>      > resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0"
>      > GRUB_CMDLINE_LINUX="" [/CODE]
>      >
>      > Do I want to edit that "quiet splash resume" data to match the
>     /dev/sdc7
>      > location of the Lubuntu "/" UUID??
>      >
>      > [CODE] /dev/sdc7: UUID="17bcb813-d05e-4cc3-bcdf-16d283156780" 
>     [/CODE]
>      >
>      > And, then try to again run the grub bootloader to get it to find
>     a newer
>      > location of Lu that would then allow upgrading to 5.19 xx kernel???
>      >
>      > F
>      >
>      > F
>      >
>      > On Sat, Sep 10, 2022 at 5:05 PM Fritz Hudnut
>     <este.el.paz at gmail.com <mailto:este.el.paz at gmail.com>
>      > <mailto:este.el.paz at gmail.com <mailto:este.el.paz at gmail.com>>> wrote:
>      >
>      >     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 11:55 AM Nio Wiklund
>      >         <nio.wiklund at gmail.com <mailto:nio.wiklund at gmail.com>
>     <mailto:nio.wiklund at gmail.com <mailto: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
>      >
>      >
>