Issue bookworm new kernel 5.14

[ejohb]

Hi friends, I'm having an issue in bookworm following the latest kernel update, when I boot with the kernel 5.14 the image from the gpu feed (nvidia gt 630) gets all blurry can't see anything I had to blindly login my user and systemctl reboot my computer.

If I use the older kernel things work fine, so its not such a big deal but just wondering if anyone else ran in the same issue and if there is anything I can do to fix it, so that I can use the newest kernel.

Message I'm getting in journalctl -b -1 -p warning is the following, when booting with the newest kernel:

Sep 28 19:01:05 coisa kernel: nouveau 0000:01:00.0: DRM: core caps notifier timeout
Sep 28 19:01:07 coisa kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
Sep 28 19:01:09 coisa kernel: nouveau 0000:01:00.0: DRM: base-0: timeout
Sep 28 19:01:09 coisa kernel: nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon

I'm guessing here is the issue? I'm a begginer and don't know much that is why I'm posting in begginers area.

Thanks for reading

[@ttila]

I observed that the folder "/lib/modules/5.14.0-1-amd64/updates/dkms" is missing, so no nvidia drivers are available for my pc with bookworm. That folder exists for the 5.10 kernel.

[ejohb]

I observed that the folder "/lib/modules/5.14.0-1-amd64/updates/dkms" is missing, so no nvidia drivers are available for my pc with bookworm. That folder exists for the 5.10 kernel.

I also saw some people complain that use the nvidia driver that the new kernel doesn't work with them, not sure though what it all means

[ejohb]

bumping the thread to give an update, the issue has been fixed with the new linux-image-amd64 update =) at least for the nouveau that I use

[ejohb]

bumping the thread, now I have a new issue with the latest bookworm update of linux-image, using AMD Ryzen APU ryzen 3400g and using the amd proprietary firmware.
ii linux-image-5.14.0-4-amd64 5.14.16-1 amd64 Linux 5.14 for 64-bit PCs (signed)

I type startx to load up my GUI, I use i3-wm, and now when I type startx the computer freezes, no num-lock or caps-lock light are reactive, can't access other ttys, and I have to push the reset button

[NorthEast]

Lots of things to think about here.

I'm a begginer and don't know much

Debian bookworm, that is, the current testing version, can pose difficulties for beginners because it breaks at times due to the "testing" nature of the installaton. That can make great demands on one's debian knowledge base to get around and may involve climbing a steep learning curve quickly. The stable release avoids a lot of that.

using the amd proprietary firmware.

It's difficult to unravel issues with such firmware if you've followed the proprietor's exact instructions, or other instructions known to work, but still failed to have it work. You can't get inside the software to do anything much to help yourself.

I type startx to load up my GUI ... the computer freezes

Does the Xorg log file have any info in it? It's often located at /home/<user>/.local/share/xorg/Xorg.0.log.

[stevepusser]

It does no use to make bug reports here; this is not the Debian Developer's Forum, and they don't hang out here.