After restarting, the monitor turned off during the startup

Message

vvgloo · Post by **vvgloo** » Sun Jan 05, 2025 11:26 am

I did emerge world --exclude=gentoo-sources, then to restart computer.
After restarting, the monitor turned off during the startup.
I see that the character interface is starting, showing that the hard drive is scanning and mounting, and has not yet started to the location where the username is entered. Then the monitor lost signal.
I checked the hardware and it's fine. The other system on my computer is working properly. And it's still in the character interface, so it shouldn't have anything to do with X. I did not update kernel, so the kernel is old.
I am currently unable to access the system and am looking for a boot disk to check again. What should I check for this issue?
Thank you all first.

sublogic · Post by **sublogic** » Mon Jan 06, 2025 2:52 am

Temporary workaround: if you use a bootloader and know how to change the kernel command line, try adding nomodeset .

Your framebuffer seems to work, but the final graphics driver seems to fail. The kernel option above will leave you in the framebuffer. It's not a solution, but you should be able to log in and investigate. For example, look at the dmesg output.

vvgloo · Post by **vvgloo** » Mon Jan 06, 2025 2:24 pm

thanks
ssh can be connected fortunately.
I have tried add nomodeset in boot, but no difference.
I reinstall nvidia-drivers in all editions, it's not work either.

my dmesg: https://pastebin.com/1w8er1ar
I didn't find any useful information

vvgloo · Post by **vvgloo** » Mon Jan 06, 2025 2:41 pm

Miraculously, I was able to log in and execute startx on a black screen by blind typing into X. The display worked. This glitch only occurs in the second half of the character screen, so what should I be checking for?
the dmesg:
nvidia: module license 'NVIDIA' taints kernel.[ 3.790000] Disabling lock debugging due to kernel taint
is this a key?

Post by Hu » Mon Jan 06, 2025 3:24 pm

No, that is a standard error whenever you use closed source drivers, due to their historical reliability reputation.

hujuice · Post by **hujuice** » Wed Jan 08, 2025 11:33 am

I have a similar (?) issue when I resume from hibernation.
My two screens turn black when the graphical mode starts. rc-status shows that everything is fine and I find an error in dmesg:

Code: Select all

nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0:417

The issue comes after heavy updates and also after changing the graphic card (GeForce GT 1030, x11-drivers/nvidia-drivers 550.142 and ~565.77).

Googling around, I find similar stories related to old driver versions: https://forums.developer.nvidia.com/t/e ... /242543/16

Is it related?
Any workaround?

Regards,
HUjuice

hujuice · Post by **hujuice** » Wed Jan 08, 2025 11:41 am

Also, wiki page suggests this check in the troubleshooting section:

All power saving options turned off in the system firmware setup.

(https://wiki.gentoo.org/wiki/NVIDIA/nvi ... om_freezes)
I have no idea of what does it mean.

HUjuice

vvgloo · Post by **vvgloo** » Sun Jan 12, 2025 4:44 am

echo on > /sys/bus/pci/devices/0000\:06\:00.0/power/control
I tried this,no change.
I found another way, I replaced the hdmi cable with a dp cable and it was fine

hujuice · Post by **hujuice** » Tue Jan 21, 2025 7:49 pm

vvgloo wrote:I replaced the hdmi cable with a dp cable and it was fine

That's quite bizzarre. I have a DP connected monitor and a HDMI connected monitor.
Do you suggest to buy another DP cable and adapters?

vvgloo · Post by **vvgloo** » Sun Feb 09, 2025 4:42 am

hujuice wrote:
vvgloo wrote:I replaced the hdmi cable with a dp cable and it was fine
That's quite bizzarre. I have a DP connected monitor and a HDMI connected monitor.
Do you suggest to buy another DP cable and adapters?

you can try it, I think it is useful.