Open PatrickDaG opened 1 month ago
Oof. Out of curiosity, what happens if you:
Does that unfreeze it?
Tried it. The screen remained frozen. I wasn't able to switch TTY.
Hmm okay, thanks for trying. I think it would probably be a safe bet to revert my PR then. In the meantime you could probably use a workaround like
hardware.nvidia.modesetting = false;
boot.kernelParams = [ "nvidia-drm.modeset=1" ];
to get the old behavior. Not sure if there's anything that makes decisions based on hardware.nvidia.modesetting
though.
I think it would probably be a safe bet to revert my PR then.
On second thought, there are quite a few of backlinks from https://github.com/NixOS/nixpkgs/pull/324921 about it fixing things for people, so maybe it's not so cut and dry...
It might help to know some more about your setup to debug this:
Also, can you SSH into the machine while the screen is frozen?
It's a gtx 1080 in a desktop. I have 3 monitors all connected directly to the graphics card. I can ssh into the PC after it froze it seems to startup just fine, journal also contains no unexpected errors as far as I can see. This should be all the relevant configuration I have set.
I have also encountered some issues with my display after https://github.com/NixOS/nixpkgs/pull/324921 was merged.
Every time I booted into my computer, right before the login screen was supposed to appear my screen would turn black with a message in the middle saying "Not Optimum Mode, Recommended Mode 3840x2160 60Hz" (this is a Samsung monitor).
I could work around this issue by changing my display to HDMI2 and back to HDMI1, which would fix the issue.
The config workaround mentioned above works for me, thanks for sharing it
Not sure how much this helps, just wanted to share another instance where this option fails.
(Something of note might be that my hardware has some ACPI issues, since I have to use the libata.noacpi=1
kernel parameter to get rid of some errors. I've heard that ACPI may be related to the "Not optimum mode" message, but it hasn't appeared before the PR mentioned above. (I've tried getting rid of the kernel param, but it didn't help))
I also encountered the same issue where my computer finishes booting, but the screen stays frozen before it reaches the TTY login. I also cannot switch TTYs.
I'm on a desktop GTX 1070 with my main monitor connected with DP and the second one HDMI. The workaround mentioned here to use the old behavior does fix the issue for me. The before and after of journalctl matches the same output as the original post, I'm using Nvidia drivers 555.58.02
.
Hmm okay, thanks for trying. I think it would probably be a safe bet to revert my PR then. In the meantime you could probably use a workaround like
hardware.nvidia.modesetting = false; boot.kernelParams = [ "nvidia-drm.modeset=1" ];
to get the old behavior. Not sure if there's anything that makes decisions based on
hardware.nvidia.modesetting
though.
Have the same issue as everyone else, however the work around does not work for me. I'm able to boot, however when I try into a wayland compositor with the command Hyprland
my screen just turns black, I also tried other compositers and the issue persists.
CPU: i7 8700k GPU: GTX 1080
Describe the bug
The kernel param option introduced in https://github.com/NixOS/nixpkgs/pull/324921 results in my system graphical output freezing on boot.
Steps To Reproduce
Boot on my config with the newest nixos-unstable.
Additional context
Journal on non working setup when the screen freezes:
Journal on working boot:
Notify maintainers
@CobaltCause
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a :+1: reaction to issues you find important.