Hi,

terryc <terryc@???> writes:

> I've just performed to apt trio (update, upgrade and dist-upgrade) and
> following a reboot my system went very glitchy, especially o the screen.
>
> There was a warning in the stop start boot up, along with copious
> errors like this;
> [ 21.260287] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [ 25.797572] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [ 30.325590] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [34.857594] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [ 39.378689] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [ 43.914156] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [48.439014] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
> [ 54.227334] amdgpu 0000:09:00.0: amdgpu: SMU: I'm not done with your previous command!
>
> I temporarily fixed the problem by rebooting to the previous kernel,but
> in investigating came across this oddity in the naming of my
> installed kernels

I'm not sure whether it makes a difference but do you have a *recent*
firmware-amd-graphics installed? One that "matches" your kernel. On
packages.debian.org (not on pkginfo.devuan.org, though), I see several
timestamp versioned packages. Based on the kernel version you seem to
be using (from {bullseye,chimaera}-backports), I'd say you may need one
from 2021 and maybe even August (i.e. the one in {bookworm,daedalus}).

> user@system: dpkg --list | grep linux-image
> rc  linux-image-5.10.0-6-amd64         5.10.28-1           amd64        Linux 5.10 for 64-bit PCs (signed)
> rc  linux-image-5.10.0-7-amd64         5.10.40-1           amd64        Linux 5.10 for 64-bit PCs (signed)
> rc  linux-image-5.10.0-8-amd64         5.10.46-5           amd64        Linux 5.10 for 64-bit PCs (signed)
> rc  linux-image-5.10.0-9-amd64         5.10.70-1           amd64        Linux 5.10 for 64-bit PCs (signed)

You can safely remove the configuration files that are still lingering
from the above. As root

  dpkg --list \
    | grep -E '^rc *linux-image-' \
    | awk '{ print $2 }' \
    | xargs dpkg --purge

If you use sudo to get root, stick that between xargs and dpkg.

> ii  linux-image-5.14.0-0.bpo.2-amd64   5.14.9-2~bpo11+1    amd64        Linux 5.14 for 64-bit PCs (signed)
> ii  linux-image-5.15.0-0.bpo.2-amd64   5.15.5-2~bpo11+1    amd64        Linux 5.15 for 64-bit PCs (signed)
> ii  linux-image-5.15.0-0.bpo.3-amd64   5.15.15-2~bpo11+1   amd64        Linux 5.15 for 64-bit PCs (signed)
> ii   linux-image-amd64

>
> Looking for clubies on why the last image doesn't fit the pattern, and
> the best way to purge it.

As Antoine mentioned linux-image-amd64 is a meta package that depends on
the latest versioned linux-image-$version-amd64 package. See

https://pkginfo.devuan.org/cgi-bin/package-query.html?c=package&q=linux-image-amd64=5.15.15-2~bpo11+1

for what I think is what you have installed. If your APT also pulls the
Translation file (contains translated, full package descriptions), you
can check with `apt show $pkgname` as well.

Hope this helps,
--
Olaf Meeuwissen                    FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join