Re: [DNG] Problems with amdgpu in the latest kernel upgrade? Ort just a glitch for me?
Hi, Ludovic Bellière via Dng writes: > [[PGP Signed Part:Undecided]] > Hello terryc, > > You seem to have a variety of kernel installed. Could you tell us which > version > works for you, and which version showed the errors? > > In doubt, I would revert back to stable — not backport (bpo). So you want the > latest of the 5.10 series, which should come from security. > > Care must be taken when dealing with backport kernels, as they don't usually > get > shipped as a whole: the signing and verification process takes some time. Once > you're on the kernel from the stable-security channel, you can then purge all > the others you do not use. You could do that by marking all `linux-image` and > `linux-headers` as automatically installed (1) followed by a call to `apt > autoremove` (2). If your system is properly configured, it should remove all > package that: > > a) are not required by another package and > b) are automatically installed > > (1) sudo aptitude markauto ~nlinux-headers ~nlinux-image > (2) sudo apt autoremove In the default setup, that last command will leave configuration files. That's what resulted in the rc linux-image-5.10.0-6-amd64 5.10.28-1 amd64 Linux 5.10 for 64-bit PCs (signed) entries in the original post. sudo apt purge --auto-remove will get rid of the configuration files as well. # There are some inconsistencies in what is parsed correctly and what # not between apt and apt-get as well as the autoremove and auto-remove # subcommands and options. I normally use the above. > Using the automated functions of apt is of great help when trying to keep a > system somewhat clean of unwanted, or uneeded packages. Indeed and tweaking a few configuration options goes a long way to keeping your system lean and mean. Just in case anyone is interested, here's what I have in my /etc/apt.conf // Install packages based on their own merits, not because Debian // or Devuan maintainers think you might want them. APT::Install-Recommends "false"; APT::Install-Suggests "false"; // Remove installed packages as soon as they are no longer needed // by other packages. This complements the above settings. Note // that this only kicks in when installing or removing packages. // It does *not* apply when just upgrading installed packages. APT::AutoRemove::RecommendsImportant "false"; APT::AutoRemove::SuggestsImportant "false"; // Configuration files are tracked with `etckeeper` so there is a // whole history of any such file in its repository. Whatever is // *not* in the repository was either not worth tracking or a bit // too sensitive (in which case some other backup mechanism would // normally have been available or configured). APT::Get::Purge "true"; Note, you'll need to install etckeeper to make that comment on purging configuration true for your system. I do and tend to muck around with the apt and network configurations quite a bit but for most part there is a lot of configuration that I use as is. Hope this helps, -- Olaf MeeuwissenFSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Problems with amdgpu in the latest kernel upgrade? Ort just a glitch for me?
Hi,
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 :09:00.0: amdgpu: SMU: I'm not done with your
> previous command!
> [ 25.797572] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your
> previous command!
> [ 30.325590] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your
> previous command!
> [34.857594] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous
> command!
> [ 39.378689] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your
> previous command!
> [ 43.914156] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your
> previous command!
> [48.439014] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous
> command!
> [ 54.227334] amdgpu :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 amd64Linux
> 5.10 for 64-bit PCs (signed)
> rc linux-image-5.10.0-7-amd64 5.10.40-1 amd64Linux
> 5.10 for 64-bit PCs (signed)
> rc linux-image-5.10.0-8-amd64 5.10.46-5 amd64Linux
> 5.10 for 64-bit PCs (signed)
> rc linux-image-5.10.0-9-amd64 5.10.70-1 amd64Linux
> 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+1amd64Linux
> 5.14 for 64-bit PCs (signed)
> ii linux-image-5.15.0-0.bpo.2-amd64 5.15.5-2~bpo11+1amd64Linux
> 5.15 for 64-bit PCs (signed)
> ii linux-image-5.15.0-0.bpo.3-amd64 5.15.15-2~bpo11+1 amd64Linux
> 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=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 MeeuwissenFSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Softwarehttps://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Problems with amdgpu in the latest kernel upgrade? Ort just a glitch for me?
Hello terryc, You seem to have a variety of kernel installed. Could you tell us which version works for you, and which version showed the errors? In doubt, I would revert back to stable — not backport (bpo). So you want the latest of the 5.10 series, which should come from security. Care must be taken when dealing with backport kernels, as they don't usually get shipped as a whole: the signing and verification process takes some time. Once you're on the kernel from the stable-security channel, you can then purge all the others you do not use. You could do that by marking all `linux-image` and `linux-headers` as automatically installed (1) followed by a call to `apt autoremove` (2). If your system is properly configured, it should remove all package that: a) are not required by another package and b) are automatically installed (1) sudo aptitude markauto ~nlinux-headers ~nlinux-image (2) sudo apt autoremove Using the automated functions of apt is of great help when trying to keep a system somewhat clean of unwanted, or uneeded packages. Cheers, Ludovic On Tue, 22 Feb 2022, terryc wrote: 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. [...] 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 user@system: dpkg --list | grep linux-image rc linux-image-5.10.0-6-amd645.10.28-1 amd64Linux 5.10 for 64-bit PCs (signed) rc linux-image-5.10.0-7-amd645.10.40-1 amd64Linux 5.10 for 64-bit PCs (signed) rc linux-image-5.10.0-8-amd645.10.46-5 amd64Linux 5.10 for 64-bit PCs (signed) rc inux-image-5.10.0-9-amd645.10.70-1 amd64Linux 5.10 for 64-bit PCs (signed) ii linux-image-5.14.0-0.bpo.2-amd64 5.14.9-2~bpo11+1 amd64Linux 5.14 for 64-bit PCs (signed) ii linux-image-5.15.0-0.bpo.2-amd64 5.15.5-2~bpo11+1 amd64Linux 5.15 for 64-bit PCs (signed) ii linux-image-5.15.0-0.bpo.3-amd64 5.15.15-2~bpo11+1 amd64Linux 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. T.I.A. terryc signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Problems with amdgpu in the latest kernel upgrade? Ort just a glitch for me?
On Tuesday, 22 February at 23:11, terryc wrote: 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 :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 25.797572] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 30.325590] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [34.857594] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 39.378689] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 43.914156] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [48.439014] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 54.227334] amdgpu :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 user@system: dpkg --list | grep linux-image rc linux-image-5.10.0-6-amd645.10.28-1 amd64Linux 5.10 for 64-bit PCs (signed) rc linux-image-5.10.0-7-amd645.10.40-1 amd64Linux 5.10 for 64-bit PCs (signed) rc linux-image-5.10.0-8-amd645.10.46-5 amd64Linux 5.10 for 64-bit PCs (signed) rc inux-image-5.10.0-9-amd645.10.70-1 amd64Linux 5.10 for 64-bit PCs (signed) ii linux-image-5.14.0-0.bpo.2-amd64 5.14.9-2~bpo11+1 amd64Linux 5.14 for 64-bit PCs (signed) ii linux-image-5.15.0-0.bpo.2-amd64 5.15.5-2~bpo11+1 amd64Linux 5.15 for 64-bit PCs (signed) ii linux-image-5.15.0-0.bpo.3-amd64 5.15.15-2~bpo11+1 amd64Linux 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. T.I.A. terryc I wouldn't know about your graphics card not being done with previous commands (maybe a driver update?), but isn't linux-image-amd64 a meta-package? It doesn't contain anything but requires the most recent version of the kernel package (in your case linux-image-5.15.0-0.bpo.3-amd64), and when the kernel version is upgraded, the package itself doesn't change versions but the requirement does change. - Antoine -- Elegance is not a dispensable luxury but a quality that decides between success and failure. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Problems with amdgpu in the latest kernel upgrade? Ort just a glitch for me?
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 :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 25.797572] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 30.325590] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [34.857594] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 39.378689] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 43.914156] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [48.439014] amdgpu :09:00.0: amdgpu: SMU: I'm not done with your previous command! [ 54.227334] amdgpu :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 user@system: dpkg --list | grep linux-image rc linux-image-5.10.0-6-amd645.10.28-1 amd64Linux 5.10 for 64-bit PCs (signed) rc linux-image-5.10.0-7-amd645.10.40-1 amd64Linux 5.10 for 64-bit PCs (signed) rc linux-image-5.10.0-8-amd645.10.46-5 amd64Linux 5.10 for 64-bit PCs (signed) rc inux-image-5.10.0-9-amd645.10.70-1 amd64Linux 5.10 for 64-bit PCs (signed) ii linux-image-5.14.0-0.bpo.2-amd64 5.14.9-2~bpo11+1 amd64Linux 5.14 for 64-bit PCs (signed) ii linux-image-5.15.0-0.bpo.2-amd64 5.15.5-2~bpo11+1 amd64Linux 5.15 for 64-bit PCs (signed) ii linux-image-5.15.0-0.bpo.3-amd64 5.15.15-2~bpo11+1 amd64Linux 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. T.I.A. terryc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
