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
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
So, following up on my investigations . . . synaptic "kernels" does show
"5.19" as "installed" . . . but uname -r still shows that 5.13 is being
selected???
I installed "mainline" some time back, but forgot how to use it . . . until
I found the github page tabbed in FF. I ran a couple commands
I jumped the queue and booted Lu this morning . . . it was still showing
5.13 as the kernel . . . ran a 93 package upgrade . . . no mention of a
kernel in the list . . . went through w/o error . . . .
Booted over into master grub control system . . . updated the grub
bootloader . . . then back
Nio:
I guess there was a post on the list that I didn't get, as I'm on digest .
. . . But, thanks guys for checking on the "5.19" . . . I'm doing "weekly"
apt update/upgrade and pretty sure I saw it was attempting to install
5.15??? (something less than 5.19) and then now seems to have selected
Den 2022-09-06 kl. 20:57, skrev Israel Dahl:
On 9/6/22 09:31, Fritz Hudnut wrote:
> . . . . On cold boot FF came back.
>
> But, the question of what happened with apt was the more important
> question . . . was it trying to install a too new kernel and then
> tried to back out
On 9/6/22 09:31, Fritz Hudnut wrote:
> . . . . On cold boot FF came back.
>
> But, the question of what happened with apt was the more important
> question . . . was it trying to install a too new kernel and then
> tried to back out of it? It was an odd episode . . . .
>
> . . . . On cold boot FF came back.
> >
> > But, the question of what happened with apt was the more important
> > question . . . was it trying to install a too new kernel and then
> > tried to back out of it? It was an odd episode . . . .
> >
> > F
> >
> Hey Fritz,
>
> You could search for
On 9/5/22 10:32, Fritz Hudnut wrote:
(snip)
Ralf:
Alrighty, thanks for the reply . . . the "disappearing Firefox" thing
only was a problem as far as wanting a browser to search for answers
to the problem of apt "hanging" in the process of updating the system
. . . . On cold boot FF
On Sun, 2022-09-04 at 10:38 -0700, Fritz Hudnut wrote:
> > [snip] running kinetic this morning and executed "apt update && apt
> > dist-upgrade" [snip]
> > FireFox disappeared from the internet menu [snip]
>
> Hi,
>
> Firefox is not provided by the apt repositories.
>
> It's a "Transitional
On Sun, 2022-09-04 at 10:38 -0700, Fritz Hudnut wrote:
> [snip] running kinetic this morning and executed "apt update && apt
> dist-upgrade" [snip]
> FireFox disappeared from the internet menu [snip]
Hi,
Firefox is not provided by the apt repositories.
It's a "Transitional package - firefox ->
Folks:
Once again in Lu can't access Discourse, so posting here . . . running
kinetic this morning and executed "apt update && apt dist-upgrade" . . .
showed a few hundred packages to install . . . midway through on #52???
there was a "hang" on what might have been "initrd - 5.15x" and there
12 matches
Mail list logo
