-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black X11 Screen and partial lockup when upgraded to 515.76 on RTX3060 #380
Comments
Exact same issue here, started with the update. Can't even set up a fresh system. Unable to use the system completely after boot. |
exactly this issue. Just a black screen with nothing. Can't even change to TTY. |
Changing to tty doesn't work if gdm / lightdm / sddm is enabled. KMSCON doesn't work. Starting Hyprland before starting |
Same issue. Black screen, TTY not working. Had to chroot from a live USB and revert back to 515.65.01 OS: Solus |
I've been experiencing the black screen at boot with the 515.76 driver as well but I can get around it by having my monitor off during the boot process/having the HDMI unplugged and then starting it after the session is up. No clue if it works for everyone else but would be nice to know if it works or not. |
@PixeL-se that doesn't seem to work for me. |
Please set kernel parameter nvidia-drm.modeset=1 and see if it fixes the issue. |
Already did. Neither setting it to 1 nor 0 works. I also run mkinitcpio with nvidia stuff configured. EDIT: Suspend also make the issue appear. I already ran
|
It actually worked to plug in the hdmi after system is up and running. |
It almost worked for me. in addition, I had to restart sddm.service (logged in remotely) |
I'm using SDDM but I didn't have to restart sddm.service or anything. What I usually do is that I just unplug the HDMI cable, start my system, wait for the POST to give me the white light on my motherboard (for VGA), then I plug it back in and wait for it to go through my bootloader (systemd-boot), and then I start the monitor when the display manager loads. It has worked for me each and every time I've done it (about 7 times now) but I guess it doesn't work for everyone? |
Thanks for the suggestion! This actually work for me on 515.76:
So it looks like there is something in the console initialization code specific to HDMI. |
I can confirm that keeping your HDMI connected monitor turned off during boot mitigates this issue. Still not sure if the culprit is only the 515.76 driver or the recent 5.19.12 kernel as well, which has it's own share of issues with black screens or flickering on systems. Might be just a strange coincidence that both of these stable releases are breaking displays. |
Arch Linux The aforementioned "workaround" does not work for me. I can use the computer like normal (minus the GUI) if I don't start X. I have tried leaving the TV off (hdmi->hdmi) after entering bios password as well as for complete boot (tv off before boot, entering bios password, waiting, logging in, starting x, waiting, tv on). Keyboard unresponsive after I can only reboot from ssh to recover this bad state, and after I do |
Same issue with new
RPM Fusion bugtracker. |
Same here on a fully upgraded Fedora Workstation 36.
Here is a Fedora discussion about it: https://www.reddit.com/r/Fedora/comments/xu5lco/linux_nvidia_driver_51576_causes_black_screen/ I am gonna have to learn how to compile my own NVIDIA driver packages for emergencies like this, because I cannot figure out how to downgrade the official Fedora packages. |
We have filed a bug 3817621 internally for tracking purpose. https://forums.developer.nvidia.com/t/515-76-nvidia-drivers/229132 |
@amrit1711 Thank you. So far I have been reading every discussion thread in the list posted here: https://www.reddit.com/r/Fedora/comments/xu5lco/comment/iqu4bqi/ Across distros the common denominators appear to be that it (only?) happens to the RTX 30xx series, and mostly (only?) affects people with HDMI ports as their output. Several people reported success by using DisplayPort instead. One person said that a DisplayPort to HDMI cable adapter didn't work. Several people reported that is the machine is started without any HDMI connected, and you then SSH into the machine to run some command (startx was mentioned), you can then plug in the HDMI afterwards to get an image. Tedious method of course, but points towards a HDMI initialization issue. At least one person mentioned logs saying that EDID failed to be read via HDMI För the connected displays. Some people with 30x0-series GPUs have working HDMI ports. So perhaps it is an issue with specific displays with specific data in their EDID that trips things up. Which would explain why the bug wasn't discovered by you during testing. I have tried different kernel versions. All of these are confirmed NOT working with 515.76 driver: 5.19.8, 5.19.11, 5.19.12. The only thing that worked for me was downgrading to NVIDIA driver 515.65.01, and I am on kernel 5.19.12 with no issues. |
I tracked down a problem with modeset sequencing for RTX 30 series GPUs when the boot display is on HDMI. If you're affected, could you please give this commit a try? |
@aaronp24, fixes the problem for me on RTX 3090 and Linux 6.0. |
@aaronp24 So I tried that commit, but after putting "options nvidia NVreg_OpenRmEnableUnsupportedGpus=1" in /etc/modprobe.d/nvidia.conf it boots to the same black screen. I followed the install guide: This is on 5.19.4-arch1-1, 3080ti with KDE and SDDM. Maybe I did something wrong, not sure. |
You built from the main branch, rather than using the mentioned commit. |
I figured out how to do it and it works. |
I can only access grub because of this issue. How can I bypass this Nvidia bug through grub so I can at least downgrade my Nvidia drivers? |
This solved my problem. Using either a second monitor or tty: |
NVIDIA Open GPU Kernel Modules Version
515.76
Does this happen with the proprietary driver (of the same version) as well?
Yes
Operating System and Version
Description: Arch Linux
Kernel Release
Linux eren 5.19.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 20 Sep 2022 15:17:59 +0000 x86_64 GNU/Linux
Hardware: GPU
GPU 0: NVIDIA GeForce RTX 3060 (UUID: GPU-e54c64bb-4893-74a7-ab52-e7131045d25a) GPU 1: NVIDIA GeForce RTX 3060 (UUID: GPU-5f6a0370-1efa-8e2c-1ca0-4a8f0e558957)
Describe the bug
Black X11 Screen and partial lockup when upgraded to 515.76 and dual RTX3060
After upgrading to 515.76 on my system (Amd CPU, Asus Moterboard, 2 X RTX3060, see the nvidia-bug-report.log.gz for detailed configuration) I get a blank screen when I run startx. I can login remotely, I can take a nvidia-bug-report (although it takes a lot to finish) but reboot hangs (with the last message “kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67d:0:0:1119”) so I suspect a problem at kernel level.
Things I tried:
Let me know if you need more information,
Thanks!
To Reproduce
Just run startx (or directly xinit)
Bug Incidence
Always
nvidia-bug-report.log.gz
nvidia-bug-report.log.gz
More Info
The text was updated successfully, but these errors were encountered: