Bookworm : graphic glitches all over my screen after upgrade

[rudu]

Hi,

Coming back from holidays, I did a pretty huge upgrade of my Bookworm
system on my aging desktop (2009).
After a reboot, what I could see is best described via this snapshot :
https://wtf.roflcopter.fr/pics/rVcN0HFu/vgQCGy7g.png

What I tried so far :
- replacing my nouveau driver by a proprietary one, but :
$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C
[GeForce 9400 GT] [10de:0641] (rev a1)

Checking card:  NVIDIA Corporation G96C [GeForce 9400 GT] (rev a1)
Your card is only supported by the 340 legacy drivers series, which is
only available up to buster.

- installed the last kernel for testing :
$ dpkg -l linux-image-* | grep ^ii
ii  linux-image-5.18.0-4-amd64          5.18.16-1    amd64 Linux 5.18
for 64-bit PCs (signed)
ii  linux-image-5.7.0-2-amd64           5.7.10-1     amd64 Linux 5.7 for
64-bit PCs (signed)
ii  linux-image-5.7.0-3-amd64           5.7.17-1     amd64 Linux 5.7 for
64-bit PCs (signed)
ii  linux-image-amd64                   5.18.16-1    amd64 Linux for
64-bit PCs (meta-package)
... no change.

- reconfigured window display management between lightdm/sddm/gdm3 :
Curiously, only sddm showed no sign of being affected, until I opened a
graphic environment (LXDE, XFCE4, Gnome-Xorg/wayland,
Plasma-Xorg/wayland) where the problem was always back.

- I looked into /var/log/apt/term.log resulting from my last upgrade and
tried to find something relevant and I saw this :
cat /var/log/apt/term.log | grep xserver
Préparation du dépaquetage de .../38-xserver-common_2%3a21.1.4-1_all.deb ...
Dépaquetage de xserver-common (2:21.1.4-1) sur (2:21.1.3-2) ...
Préparation du dépaquetage de
.../39-xserver-xorg-core_2%3a21.1.4-1_amd64.deb ...
Dépaquetage de xserver-xorg-core (2:21.1.4-1) sur (2:21.1.3-2+b1) ...
Préparation du dépaquetage de
.../359-xserver-xephyr_2%3a21.1.4-1_amd64.deb ...
Dépaquetage de xserver-xephyr (2:21.1.4-1) sur (2:21.1.3-2+b1) ...
Paramétrage de xserver-common (2:21.1.4-1) ...
Paramétrage de xserver-xephyr (2:21.1.4-1) ...
Paramétrage de xserver-xorg-core (2:21.1.4-1) ...

I don't know what to do or where to look, my system is barely usable now
and freezes regularly ...

Any help would be warmly appreciated
Rudu

[piorunz]

On 23/08/2022 14:13, rudu wrote:
> Hi,
>
> Coming back from holidays, I did a pretty huge upgrade of my Bookworm
> system on my aging desktop (2009).
> After a reboot, what I could see is best described via this snapshot :
> https://wtf.roflcopter.fr/pics/rVcN0HFu/vgQCGy7g.png

Only one thing I can think of is nouveau driver issue.
If I am not mistaken, Bookworm has libdrm-nouveau2 and
xserver-xorg-video-nouveau packages to provide nouveau driver.
Only libdrm-nouveau2 has seen new upstream release landing in bookworm
recently.

See in your apt logs if these packages were part of the upgrade you
undertaken recently? For me, history.log shows upgrade entry on
2022-08-03 (20 days ago): libdrm-nouveau2:amd64 (upgrade from version
2.4.110-1 to version 2.4.112-3).

Also please show output of
inxi -G
command in terminal. Install inxi if you haven't already.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

[Sven Joachim]

Seems you are experiencing bug #1017499[1], for which no solution
currently exists. Try downgrading your installed packages from
src:mesa.

Good luck,
Sven


1. https://bugs.debian.org/1017499

[rudu]

Piotr, Sven, Thank you for your help, see below.

I've been already trying some downgrades, of :
Downgrade: xserver-xorg-video-nouveau:amd64 (1:1.0.17-2, 1:1.0.17-1),
xserver-xorg-input-evdev:amd64 (1:2.10.6-2+b1, 1:2.10.6-2),
xserver-xorg-core:amd64 (2:21.1.4-1, 2:1.20.11-1+deb11u1)
Purge: xserver-xephyr:amd64 (2:21.1.4-1)
Downgrade: xserver-xorg:amd64 (1:7.7+23, 1:7.7+22), xserver-common:amd64
(2:21.1.4-1, 2:1.20.11-1+deb11u1)
... the stable versions of those packages.
But nothing changed.

Then, Piotr drew my attention to this libdrm-nouveau2 :
Downgrade: libdrm-nouveau2:amd64 (2.4.112-3, 2.4.104-1),
libdrm-nouveau2:i386 (2.4.112-3, 2.4.104-1)
... still no luck.

Looking at its dependencies, I noticed a libdrm2 and libdrm-common
packages. Their downgrade had some consequences :
Install: libllvm11:amd64 (1:11.1.0-6+b2, automatic),
kwin-wayland-backend-x11:amd64 (4:5.25.4-2, automatic),
libdrm-intel1:amd64 (2.4.104-1, automatic)
Downgrade: libglx-mesa0:amd64 (22.2.0~rc2-1, 20.3.5-1), libgbm1:amd64
(22.2.0~rc2-1, 20.3.5-1), libgl1-mesa-dri:amd64 (22.2.0~rc2-1,
20.3.5-1), libdrm-common:amd64 (2.4.112-3, 2.4.104-1), xwayland:amd64
(2:22.1.3-1, 2:1.20.11-1+deb11u1), libglapi-mesa:amd64 (22.2.0~rc2-1,
20.3.5-1), libdrm-amdgpu1:amd64 (2.4.112-3, 2.4.104-1),
libdrm-radeon1:amd64 (2.4.112-3, 2.4.104-1), libdrm-radeon1:i386
(2.4.112-3, 2.4.104-1), libdrm2:amd64 (2.4.112-3, 2.4.104-1),
libdrm2:i386 (2.4.112-3, 2.4.104-1), libegl-mesa0:amd64 (22.2.0~rc2-1,
20.3.5-1), libdrm-intel1:i386 (2.4.112-3, 2.4.104-1)
Remove: libxcb-present0:i386 (1.15-1), libglx-mesa0:i386 (22.2.0~rc2-1),
libglvnd0:i386 (1.4.0-1), libxshmfence1:i386 (1.3-1), libdecor-0-0:i386
(0.1.0-3), libfltk1.1:i386 (1.1.10-29), libwayland-cursor0:i386
(1.21.0-1), libxcb-dri2-0:i386 (1.15-1), libxcb-dri3-0:i386 (1.15-1),
libgbm1:i386 (22.2.0~rc2-1), libwayland-server0:i386 (1.21.0-1),
libglx0:i386 (1.4.0-1), libdrm-nouveau2:i386 (2.4.104-1), libllvm14:i386
(1:14.0.6-2), kwin-wayland-backend-drm:amd64 (4:5.25.4-2), libz3-4:i386
(4.8.12-1+b1), libxcvt0:amd64 (0.1.2-1), libgl1-mesa-dri:i386
(22.2.0~rc2-1), libxkbcommon0:i386 (1.4.1-1), freeglut3:i386 (2.8.1-6),
libxcb-glx0:i386 (1.15-1), libwayland-egl1:i386 (1.21.0-1),
libglapi-mesa:i386 (22.2.0~rc2-1), libsdl2-2.0-0:i386 (2.0.22+dfsg-6),
libdrm-amdgpu1:i386 (2.4.112-3), libgl1:i386 (1.4.0-1),
libwayland-client0:i386 (1.21.0-1), libxcb-sync1:i386 (1.15-1),
libatomic1:i386 (12.1.0-8), libxcb-xfixes0:i386 (1.15-1)

Then a reboot and ... bingo ! The artefacts were gone, everything back
in order.

So Sven, you must be right as I can see some mesa packages removed or
downgraded in my last move, hope that bug will be resolved soon.

I know it's a bit late, but Piotr asked me for an output, here it is :
$ inxi -G
Graphics:
  Device-1: NVIDIA G96C [GeForce 9400 GT] driver: nouveau v: kernel
  Display: x11 server: X.Org v: 1.20.11 with: Xwayland driver: X:
    loaded: modesetting gpu: nouveau resolution: 1920x1080~60Hz
  OpenGL: renderer: NV96 v: 3.3 Mesa 20.3.5

And for good mesure :
$ uname -a && cat /etc/debian_version
Linux birdynam 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64
GNU/Linux
bookworm/sid

Thanks again to Piotr and Sven and all the subscribers of this great list
Rudu

[piorunz]

On 24/08/2022 10:39, rudu wrote:
> Then a reboot and ... bingo ! The artefacts were gone, everything back
> in order.
>
> So Sven, you must be right as I can see some mesa packages removed or
> downgraded in my last move, hope that bug will be resolved soon.
>
> I know it's a bit late, but Piotr asked me for an output, here it is :
> $ inxi -G
> Graphics:
>   Device-1: NVIDIA G96C [GeForce 9400 GT] driver: nouveau v: kernel
>   Display: x11 server: X.Org v: 1.20.11 with: Xwayland driver: X:
>     loaded: modesetting gpu: nouveau resolution: 1920x1080~60Hz
>   OpenGL: renderer: NV96 v: 3.3 Mesa 20.3.5
>
> And for good mesure :
> $ uname -a && cat /etc/debian_version
> Linux birdynam 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64
> GNU/Linux
> bookworm/sid
>
> Thanks again to Piotr and Sven and all the subscribers of this great list
> Rudu

Great to hear! I am glad you can enjoy your Debian system again. :)

Looking at your kernel version, why you are running two years old
kernel? Support for this kernel has ended upstream, your system is
vulnerable to security issues.

--
With kindest regards, Piotr.

[rudu]

Le 24/08/2022 à 22:32, piorunz a écrit :
> Looking at your kernel version, why you are running two years old
> kernel? Support for this kernel has ended upstream, your system is
> vulnerable to security issues.
>

That's because I experienced hibernation issues from this kernel up.
The screen shuts down ok, but the power never goes off, I have to use
the button.
And next boot is a standard one.
Don't know where to look for a clue here.

Regards
Rudu

[piorunz]

That's very sad to hear.
Have you tried to report this to Debian BTS?
How about LTS kernel 5.10? That didn't worked either?

You are on Debian Testing and using older kernel than Debian Stable,
that's very uncommon.

[rudu]

  bthLe 25/08/2022 à 23:51, piorunz a écrit :
> On 25/08/2022 09:13, rudu wrote:
>> Le 24/08/2022 à 22:32, piorunz a écrit :
>>> Looking at your kernel version, why you are running two years old
>>> kernel? Support for this kernel has ended upstream, your system is
>>> vulnerable to security issues.
>>>
>>
>> That's because I experienced hibernation issues from this kernel up.
>> The screen shuts down ok, but the power never goes off, I have to use
>> the button.
>> And next boot is a standard one.
>> Don't know where to look for a clue here.
>>
>> Regards
>> Rudu
>>
>>
> That's very sad to hear.
> Have you tried to report this to Debian BTS?
> How about LTS kernel 5.10? That didn't worked either?
>
> You are on Debian Testing and using older kernel than Debian Stable,
> that's very uncommon.

You should be right, but after booting on both 5.10 kernels I found in
my repositories :
ii  linux-image-5.10.0-13-amd64          5.10.106-1   amd64 Linux 5.10
for 64-bit PCs (signed)
ii  linux-image-5.10.0-16-amd64          5.10.127-1   amd64 Linux 5.10
for 64-bit PCs (signed)

... the hibernation process fails as described above ...

With Linux birdynam 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23)
x86_64 GNU/Linux hibernation works as expected.

Rudu

[piorunz]

On 26/08/2022 10:18, rudu wrote:

> You should be right, but after booting on both 5.10 kernels I found in
> my repositories :
> ii  linux-image-5.10.0-13-amd64          5.10.106-1   amd64 Linux 5.10
> for 64-bit PCs (signed)
> ii  linux-image-5.10.0-16-amd64          5.10.127-1   amd64 Linux 5.10
> for 64-bit PCs (signed)
>
> ... the hibernation process fails as described above ...
>
> With Linux birdynam 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23)
> x86_64 GNU/Linux hibernation works as expected.

I suggest you should report this error as soon as possible.

[Computer Enthusiastic]

Hello,

Il giorno 26 ago 2022, alle ore 19:31, piorunz <pio...@gmx.com> ha scritto:

On 26/08/2022 10:18, rudu wrote:

You should be right, but after booting on both 5.10 kernels I found in

my repositories :

ii  linux-image-5.10.0-13-amd64          5.10.106-1   amd64 Linux 5.10

for 64-bit PCs (signed)

ii  linux-image-5.10.0-16-amd64          5.10.127-1   amd64 Linux 5.10

for 64-bit PCs (signed)

... the hibernation process fails as described above ...

With Linux birdynam 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23)

x86_64 GNU/Linux hibernation works as expected.

I suggest you should report this error as soon as

A bug report is already opened [1]. A workaround (using kernel boot parameters) and a kernel patch are reported in [1]. Working is in progress to let the patch reach upstream kernel [2]. I have successfully used both the workaround parameters or the patch and I’m currently using a custom Debian kernel with the aforementioned patch to solve this bug.

HTH

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705

[2] https://lists.freedesktop.org/archives/nouveau/2022-August/040756.html

[rudu]

Thank you very much, the boot parameters trick worked like a charm.
Now whatever Kernel I choose to boot, the hibernation process works as expected.

Rudu

[Computer Enthusiastic]

Hello,

Il giorno 29 ago 2022, alle ore 17:49, rudu <ru...@cegetel.net> ha scritto:

 Le 27/08/2022 à 11:42, Computer Enthusiastic a écrit :

Hello,

[…]

Thank you very much, the boot parameters trick worked like a charm.
Now whatever Kernel I choose to boot, the hibernation process works as expected.

Rudu

I’m happy I helped you to sort it out.  :-)

Please, if you can, report it to the Debian bug tracking system updating the bug report at [1]. 

Thanks.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705