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

[Fritz Hudnut]

@Is:

Yes.  I did both, reinstalled grub and then "mkconfig'd" it and on cold
boot, selecting Lubuntu now brings verbose log in/dmesg, or it shows up . .
. in the fairly slow boot process . . . but got there!!  And uname -r shows
5.19xxx kernel . . . 

It takes a village . . . in my case.  I guess the thing was, after erasing
the 5.13 kernel I edited the individual grub item data, but didn't run
another "grub2-mkconfig" to solidify the edits??  Or, in this case, find
the newer kernel and register it, etc.

I started a new thread on Discourse, but since I'm now running Lubuntu I
can't post an update there . . . ?  : - 0

On Wed, Sep 21, 2022 at 10:00 AM Fritz Hudnut  wrote:

> Is:
>
> Thanks for the reply . . . I do "know" which distro is handling grub . . .
> the TW install, but they don't do the same "update-grub" command in SUSE,
> as I recall from past exploits trying to get grub tidied up . . . .  They
> do a command like "grub2-mkconfig xxx" which I did run yesterday.  They
> do offer reinstall with "grub2-install" . . . .
>
> I guess it wouldn't hurt to run that to see if it picks up the newer
> kernel in Lu . . . now that 5.13 is gone there should be a more clear
> "choice" . . . .
>
>
>
> On Wed, Sep 21, 2022 at 9:33 AM Israel Dahl  wrote:
>
>> Hey Fritz,
>>
>> The best way to update grub is using the `update-grub` CLI utility.
>> But you have to do it from the distro you installed grub with.  If you
>> can remember which one you installed grub with, simply run that command
>> using `sudo` and it should automatically detect the most recent kernel and
>> do it for you.
>>
>> If you cannot figure out which one you installed it with, reinstall grub
>> from the distro you use the most.
>>
>> On 9/21/22 11:06, Fritz Hudnut wrote:
>>
>> et al:
>>
>> Spoke too soon . . . not out of the woods on this one yet.  Seems like
>> the edits made in the grub "EFI" menu are not maintained on reboot??
>> Doesn't seem to be any hints on how to "save" the edits . . . just make
>> them and then boot them???  But, then it appears that the edits are lost
>> and it's back to the previous version??
>>
>> After I got 5.19 to boot I used the GUI mainline kernel app to remove the
>> old 5.13 kernel, to try to get the system to default to 5.19, but on trying
>> today it said, "5.13 not found, hit any key to continue" and back into Grub
>> menu we went.
>>
>> Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 5.19
>> and it booted up.
>>
>> Question is, why doesn't it hold the data??  I've changed both line
>> items, the "Lubuntu" and the "advanced options" data and I can boot it, one
>> time . . . .  I tried "ctrl o" but that didn't do anything . . . .  Do I
>> need to take it to "command line" and then try to "ctrl o" it to save it??
>>
>> F
>>
>> On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut 
>> wrote:
>>
>>> Top posting, with impunity!!
>>>
>>> So, I got a hint over on Discourse to "check the grub EFI menu" . . .
>>> and once I figured out how to do that, indeed, Lubuntu was listing itself
>>> as "19.10" and set to be booting 5.13 . . . took some more time to figure
>>> out how to edit that data, to the correct wording for the kernel . . . and
>>> that did seem to boot Lubuntu to 5.19!!!
>>>
>>> Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
>>> site loads as a white page . . . of whiteness.  I'll have to reboot into a
>>> non-Lu system to get it to load . . . .
>>>
>>> So far now it seems like the solution has been invoked . . . .
>>>
>>> F
>>>
>>>
>>> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund 
 wrote:

> 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
>
>
>
>
>> --
>> 
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

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

[Fritz Hudnut]

Is:

Thanks for the reply . . . I do "know" which distro is handling grub . . .
the TW install, but they don't do the same "update-grub" command in SUSE,
as I recall from past exploits trying to get grub tidied up . . . .  They
do a command like "grub2-mkconfig xxx" which I did run yesterday.  They
do offer reinstall with "grub2-install" . . . .

I guess it wouldn't hurt to run that to see if it picks up the newer kernel
in Lu . . . now that 5.13 is gone there should be a more clear "choice" . .
. .



On Wed, Sep 21, 2022 at 9:33 AM Israel Dahl  wrote:

> Hey Fritz,
>
> The best way to update grub is using the `update-grub` CLI utility.
> But you have to do it from the distro you installed grub with.  If you can
> remember which one you installed grub with, simply run that command using
> `sudo` and it should automatically detect the most recent kernel and do it
> for you.
>
> If you cannot figure out which one you installed it with, reinstall grub
> from the distro you use the most.
>
> On 9/21/22 11:06, Fritz Hudnut wrote:
>
> et al:
>
> Spoke too soon . . . not out of the woods on this one yet.  Seems like the
> edits made in the grub "EFI" menu are not maintained on reboot??  Doesn't
> seem to be any hints on how to "save" the edits . . . just make them and
> then boot them???  But, then it appears that the edits are lost and it's
> back to the previous version??
>
> After I got 5.19 to boot I used the GUI mainline kernel app to remove the
> old 5.13 kernel, to try to get the system to default to 5.19, but on trying
> today it said, "5.13 not found, hit any key to continue" and back into Grub
> menu we went.
>
> Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 5.19
> and it booted up.
>
> Question is, why doesn't it hold the data??  I've changed both line items,
> the "Lubuntu" and the "advanced options" data and I can boot it, one time .
> . . .  I tried "ctrl o" but that didn't do anything . . . .  Do I need to
> take it to "command line" and then try to "ctrl o" it to save it??
>
> F
>
> On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut 
> wrote:
>
>> Top posting, with impunity!!
>>
>> So, I got a hint over on Discourse to "check the grub EFI menu" . . . and
>> once I figured out how to do that, indeed, Lubuntu was listing itself as
>> "19.10" and set to be booting 5.13 . . . took some more time to figure out
>> how to edit that data, to the correct wording for the kernel . . . and that
>> did seem to boot Lubuntu to 5.19!!!
>>
>> Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
>> site loads as a white page . . . of whiteness.  I'll have to reboot into a
>> non-Lu system to get it to load . . . .
>>
>> So far now it seems like the solution has been invoked . . . .
>>
>> F
>>
>>
>> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund 
>>> wrote:
>>>
 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




> --
> 
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

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

[Israel Dahl]

Hey Fritz,

The best way to update grub is using the `update-grub` CLI utility.
But you have to do it from the distro you installed grub with.  If you 
can remember which one you installed grub with, simply run that command 
using `sudo` and it should automatically detect the most recent kernel 
and do it for you.


If you cannot figure out which one you installed it with, reinstall grub 
from the distro you use the most.


On 9/21/22 11:06, Fritz Hudnut wrote:

et al:

Spoke too soon . . . not out of the woods on this one yet. Seems like 
the edits made in the grub "EFI" menu are not maintained on reboot??  
Doesn't seem to be any hints on how to "save" the edits . . . just 
make them and then boot them??? But, then it appears that the edits 
are lost and it's back to the previous version??


After I got 5.19 to boot I used the GUI mainline kernel app to remove 
the old 5.13 kernel, to try to get the system to default to 5.19, but 
on trying today it said, "5.13 not found, hit any key to continue" and 
back into Grub menu we went.


Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 
5.19 and it booted up.


Question is, why doesn't it hold the data??  I've changed both line 
items, the "Lubuntu" and the "advanced options" data and I can boot 
it, one time . . . .  I tried "ctrl o" but that didn't do anything . . 
. .  Do I need to take it to "command line" and then try to "ctrl o" 
it to save it??


F

On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut  
wrote:


Top posting, with impunity!!

So, I got a hint over on Discourse to "check the grub EFI menu" .
. . and once I figured out how to do that, indeed, Lubuntu was
listing itself as "19.10" and set to be booting 5.13 . . . took
some more time to figure out how to edit that data, to the correct
wording for the kernel . . . and that did seem to boot Lubuntu to
5.19!!!

Only "problem" seems to be that when I'm booted in Lubuntu the
Discourse site loads as a white page . . . of whiteness.  I'll
have to reboot into a non-Lu system to get it to load . . . .

So far now it seems like the solution has been invoked . . . .

F


On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund
 wrote:

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





--

-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

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

[Fritz Hudnut]

et al:

Spoke too soon . . . not out of the woods on this one yet.  Seems like the
edits made in the grub "EFI" menu are not maintained on reboot??  Doesn't
seem to be any hints on how to "save" the edits . . . just make them and
then boot them???  But, then it appears that the edits are lost and it's
back to the previous version??

After I got 5.19 to boot I used the GUI mainline kernel app to remove the
old 5.13 kernel, to try to get the system to default to 5.19, but on trying
today it said, "5.13 not found, hit any key to continue" and back into Grub
menu we went.

Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 5.19
and it booted up.

Question is, why doesn't it hold the data??  I've changed both line items,
the "Lubuntu" and the "advanced options" data and I can boot it, one time .
. . .  I tried "ctrl o" but that didn't do anything . . . .  Do I need to
take it to "command line" and then try to "ctrl o" it to save it??

F

On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut  wrote:

> Top posting, with impunity!!
>
> So, I got a hint over on Discourse to "check the grub EFI menu" . . . and
> once I figured out how to do that, indeed, Lubuntu was listing itself as
> "19.10" and set to be booting 5.13 . . . took some more time to figure out
> how to edit that data, to the correct wording for the kernel . . . and that
> did seem to boot Lubuntu to 5.19!!!
>
> Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
> site loads as a white page . . . of whiteness.  I'll have to reboot into a
> non-Lu system to get it to load . . . .
>
> So far now it seems like the solution has been invoked . . . .
>
> F
>
>
> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund  wrote:
>>
>>> 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
>>>
>>>
>>>
>>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

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

[Fritz Hudnut]

Top posting, with impunity!!

So, I got a hint over on Discourse to "check the grub EFI menu" . . . and
once I figured out how to do that, indeed, Lubuntu was listing itself as
"19.10" and set to be booting 5.13 . . . took some more time to figure out
how to edit that data, to the correct wording for the kernel . . . and that
did seem to boot Lubuntu to 5.19!!!

Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
site loads as a white page . . . of whiteness.  I'll have to reboot into a
non-Lu system to get it to load . . . .

So far now it seems like the solution has been invoked . . . .

F

On Fri, Sep 16, 2022 at 5:58 PM Fritz Hudnut  wrote:

> Nio:
>
> Well, good question . . . based upon which system is the "problematic"
> one.  The Lubuntu install is one of the first that went on this machine . .
> . on the OEM HDD.  The grub handler is TW, and that also is fairly "old" .
> . . neither one of them is "test" per se . . . or ALL of them are.  Way
> back before I understood that I shouldn't let each install have a grub
> file, when I had a problem I would just do a fresh install, which would
> then freshen grub list and I'd be "OK" until the next fresh "bootloader"
> install, etc.
>
> Then I figured out (with the help of a forum slap upside the head) that
> only one system should handle grub.  The "wild card" in this is that ubuntu
> seems to have decided that it doesn't want to relinquish grub control, it
> keeps some strings attached . . . and I have two ubuntu based systems
> installed now, Lu & LM . . . .
>
> So, based upon knowing what has happened in the recent past when
> installing ubuntu, I'd somewhat like to avoid installing Lubuntu again . .
> . .  But, I have been considering a fresh install of TW into an SSD for "/"
> and that might tidy everybody else up in the process . . . ???
>
> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund  wrote:
>
>> 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
>>
>>
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

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

[Fritz Hudnut]

Nio:

Well, good question . . . based upon which system is the "problematic"
one.  The Lubuntu install is one of the first that went on this machine . .
. on the OEM HDD.  The grub handler is TW, and that also is fairly "old" .
. . neither one of them is "test" per se . . . or ALL of them are.  Way
back before I understood that I shouldn't let each install have a grub
file, when I had a problem I would just do a fresh install, which would
then freshen grub list and I'd be "OK" until the next fresh "bootloader"
install, etc.

Then I figured out (with the help of a forum slap upside the head) that
only one system should handle grub.  The "wild card" in this is that ubuntu
seems to have decided that it doesn't want to relinquish grub control, it
keeps some strings attached . . . and I have two ubuntu based systems
installed now, Lu & LM . . . .

So, based upon knowing what has happened in the recent past when installing
ubuntu, I'd somewhat like to avoid installing Lubuntu again . . . .  But, I
have been considering a fresh install of TW into an SSD for "/" and that
might tidy everybody else up in the process . . . ???

On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund  wrote:

> 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  > > 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
> > mailto:este.el@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 xxx" to get it to run os-prober and make
> > a new
> >  > grub . . . .  Shut down.  Cold booted to grub and selected Lu
> > . . .
> >  > 

Re: [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 > 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
mailto:este.el@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 xxx" 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
 >         mailto:nio.wikl...@gmail.com>
>> wrote:
 >
 >             Hi Fritz,
 >
 >             This is what I think:
 >
 >             If the active 

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

[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  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  > > 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 xxx" 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
> > mailto:nio.wikl...@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
> >
> >
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 

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

[Nio Wiklund]

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 > 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 xxx" 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
mailto:nio.wikl...@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





--
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

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

[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  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 xxx" 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 
>> 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
>>>
>>>
>>>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [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 xxx" 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  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 
> 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
>>
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users