My problem after waking the monitor from sleep still occurs on 580.95.05 as well. I attached the log you requested in my previous post.
This user in [Bug] External monitor fails to wake up from powersave mode if refresh rate is higher than 30Hz - #53 by dedmoroz reports it is now working fine with latest arch kernel. I shall test this and report back.
re: seems to be an issue with arch’s packaging of
nvidia-openthat’s missing firmware or something.nvidiapackage works.
Unfortunately nvidia is not possible for Blackwell and future GPUs. Are you sure it is related to packaging by Archlinux? Or could it be a side effect of the driver’s architecture differences? Have you tried with nvidia, with GSP active or not?
I can only tell you what I tried, this pissed me off so much I downgraded to 580.82.09 immediately after.
But nvidia-open was buggy AF, didn’t load the firmware properly. 0 issue on that regard with nvidia, but it caused other bugs (like refresh rate issues).
Version 580.95.05 introduced a new bug: connecting and external TV screen via hdmi to my laptop freezes the system. External monitors work normally. Downgrading to 580.82.09 fixes it. More details at Lenovo Legion laptop + NVIDIA drivers 580.95.05 = tv screen freezes the system - #4 by MichelN - Kernel, boot, graphics & hardware - EndeavourOS
I also have a legion (Legion 5 Slim, 16AHP9). The 95.05 release is completely ■■■■■■ up.
Are you on X11 or Wayland?
Wayland
I still have the no wake up from deep saving mode bug with 580.95.05. Putting the omputer to sleep and then waking it up however wakes up the screen…
I do not know if this is in a ticket already, but Baldur’s Gate 3 with Vulkan renderer still needs __GL_13ebad=0x1 %command% to prevent massive loss of performance (this was automatically fixed for Doom Eternal/Indiana Jones machinegames Vulkan games). It is important to whitelist BG3 the same way than Doom Eternal, now they have released a native Linux version, which uses Vulkan by default.
Hello MelanieB, Can you please share exact system power setting and screen setting to get inhouse repro of this bug?
Thanks, we are tracking this with bug id 5570122.
Hello, This is fixed, Can you please check on latest 580.95.05 driver and share an update.
@vrachatte you seem to be more active here. can you comment on the status of this bug?
#5497358
@recolor.trial658 @deebzzz if any of you have an account on gitlab.archlinux.org, can u report it there as well?
since that vrachatte dude hasn’t replied to any of us lol.
@karabaja4 are u on Arch/an Arch-based distro too?
edit: same bug also reported here. Lenovo Legion laptop + NVIDIA drivers 580.95.05 = tv screen freezes the system - Kernel, boot, graphics & hardware - EndeavourOS
and we all have a Legion laptop + Arch-based distro on the latest drivers mh.
Try disabling GSP by setting nvidia.NVreg_EnableGpuFirmware=0 in kernel parameters and using the proprietary kernel module.
I am on Arch, yes.
But I don’t necessarily believe this has to do with Arch or Arch packaging, I think it’s just more likely that people on 580.95.05 will also be people on Arch due to the rolling release - so we’re the test bunnies :)
My issue with the refresh rate after resume is sporadic, sometimes it resumes fine with 240Hz, sometimes it drops to 60Hz. And sometimes I can bump it from 60Hz to 240Hz using xrandr after resume, sometimes I can’t due to xrandr: Configure crtc 0 failed error. Strange.
Setting nvidia.NVreg_EnableGpuFirmware=0 kernel parameter does not seem to change anything about the issue.
P. S. Sorry for all the edits, writing this as I’m testing :)
Ah well: It happened… 575 has been dropped from my distribution.
I can now either go with 580, and use no games at all because Vulkan cannot initialize.
Or I go back to 570 which has all sorts of other buggy behavior which 575 fixed for me.
Please, NVIDIA, investigate.
Through reading different sources, the problem might stem from me using nvidia-drm.modeset=1 and nvidia-drm.fbdev=1 which I desperately need for obs-vkcapture to work.
I will still have to confirm whether this would be an issue for my specific problem. But I’m posting this here already so other people with my problem could confirm whether they are using those options, or don’t.
Are you able to reproduce this issue on some other external Display as well? We are tracking this under bug ID 5512946.
Afaik NVIDIA drivers get super quickly added to all distros, to me the common denominator here is Arch + laptop.
A bit awkward how nobody from NVIDIA is acknowledging this blatant regression.
Also reported on reddit: [NVIDIA 580.95.05-1] Connecting external monitor results in system freeze/crash : archlinux