[lubuntu-devel] Lu 20.10 running 5.4 kernel . . . still???

[Fritz Hudnut]

@wxl:

Top posting:  I do have an Nvidia card in the MPro, but I'm using nouveau
in most of my distros, because nvidia isn't really supporting this older
card anymore, so no point in being "current" . . . nouveau is running the
show just fine now, as far as reviving from suspend and so forth.

Ran yr command apt list --upgradable:  [CODE] nothing to do.  uname -r
5.4.0-42 [/CODE]

Just had an issue where I copied the data from the terminal, but then
nothing pasted into this email, but otherwise just the overall "slowness"
continues.  : - ))

As far as staying in one venue, I'm comfortable with email and list-serve .
. . I believe this thread was started here, and then it was only because
guiverc asked a follow-up question on one of my older posts there, that I
answered on Discourse, thinking it was about "the slowness" . . . but I
think that thread was on "failure to revive from suspend" . . . had a few
complaints, so I just rattled on about the "slowness" and then one of the
other gents kind of bled the threads across from this one to there . . . .

F



On Tue, Dec 29, 2020 at 12:55 PM Walter Lapchynski <wxl at ubuntu.com> wrote:

> On Sat, Dec 26, 2020 at 10:33:27AM -0800, Fritz Hudnut wrote:
> > On Fri, Dec 18, 2020 at 9:58 AM Walter Lapchynski <wxl at ubuntu.com>
> wrote:
>
> > pc:~$ find /etc/apt -type f -name *.list -print0 | \
> > >  xargs -0 grep -h ^deb | grep -v ^# | \
> > >  egrep -v '(ubuntu|canonical).com'
> > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > deb http://ppa.launchpad.net/mkusb/unstable/ubuntu groovy main
>
> So you've got the PPA for mkusb and the Google Chrome repository.
> Nothing there should be requiring a specific kernel.
>
> > pc:~$ apt-mark showhold
>
> So you've got nothing held.
>
> > pc:/etc/apt/preferences.d$ ls
> > grub2-common  grub-efi-amd64-bin     grub-pc      shim-signed
> > grub-common   grub-efi-amd64-signed  grub-pc-bin
>
> There's all the packages that you've pinned which we also see in the
> results of `apt-cache policy`:
>
> > Pinned packages:
> >      grub-common -> 2.04-1ubuntu30 with priority 1001
> >      grub2-common -> 2.04-1ubuntu30 with priority 1001
> >      grub-pc -> 2.04-1ubuntu30 with priority 1001
> >      grub-pc-bin -> 2.04-1ubuntu30 with priority 1001
> >      grub-efi-amd64-bin -> 2.04-1ubuntu30 with priority 1001
> >      shim-signed -> 1.43+15+1552672080.a4a1fbe-0ubuntu2 with priority
> 1001
> >      grub-efi-amd64-signed -> 1.151+2.04-1ubuntu30 with priority 1001
>
> Running `apt-rdepends` against each of those packages, there's no
> specific kernel required.
>
> That said, I don't think that we're going to find our solution in
> pinning or holding. However, as kc2bez [mentioned][1] on the Discourse
> forum, there are other possible packaging reasons:
>
> > There are many possible reasons why the kernel is not updating but one
> > that came to me is any dkms modules you have installed could also be
> > blocking that. For example, if you have an Nvidia video card and you
> > are using the Nvidia drivers then you have a dkms module loaded for
> > that.
>
> So you should look into that.
>
> Also, is there a new kernel listed when you run `apt list --upgradable`?
>
> Oh, and we should probably pick one or the other place to discuss this
> as it will otherwise be really difficult for anyone else to follow the
> conversation.
>
> [1]:
> https://discourse.lubuntu.me/t/a-few-issues-with-lu-20-10-remain/1726/9
> --
>        @wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20201231/efda9706/attachment.html>