@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.
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.
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
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
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
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.
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
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
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
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
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
11 matches
Mail list logo
