[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38



Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@outlook.com

After 4 relatively quiet months with 5.15 and 5.16, and with May and its hot
temperatures just around the corner, I got the upgrade to 5.17(.3) four days
ago and a (probably) new issue has emerged.

Since the upgrade to 5.17, I get lockups in just minutes, if not seconds, after
xorg starts. The system keeps running, I can connect to it via ssh and reboot
it, but there is no input with the keyboard or the mouse. Once it reboots, it
runs fine until it is completely shut down again. If it is left off for hours,
which is quite common on my end, the issue reappears on the next boot. I then
reboot it via ssh or via reisub and pray it works on next boot.

This line in dmesg however shows that something more critical is happening

NVRM: GPU at 0000:01:00.0 has fallen off the bus.

After a quick search, I found out that it happens when the gpu gets less power
than what it needs. However, my 9500gt just has 50w of tdp and is powered only
by the pcie slot.
Assuming that it is an issue with 5.17, because it did not happen at all with
5.15 or 5.16 those 4 months, and as usual I will troubleshoot it on my own. So,
how can I install 5.16 now that it is gone from the repo?
Yes, when I install a new kernel, I remove the old one to make space because
the size of the amd64 kernels has become huge since a few years ago.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


Reply to: