You are not logged in.
Hi,
I'm trying out the Nouveau drivers on a machine with a Nvidia 1050 GPU (the proprietary drivers were causing graphical corruption and froze often, and this machine uses Wayland and doesn't game so Nouveau seems like a good fit). I followed the ArchWiki instructions and am successfully running Nouveau; so far it has not frozen while I was using it which is great!
However, once the machine suspends, there is no waking it back up. The fans spin and mouse lights turn on, but the screen remains on "no signal" and no button combination I've tried has brought it back.
I am using the stable mesa package and have NVK installed (though it disables itself as my GPU is not supported, so I might as well remove it). Here are my logs from a boot where I instantly suspended and tried to wake it up:
https://0x0.st/X4Jl.txt
I have not had much luck googling for this, though I am also not sure which line in the log is relevant. There's a few red lines from Nouveau when resuming, and then a ton of stack traces.
Thanks for your help!
Offline
How do you suspend it?
I have to say I also use nouveau on older card, but I never dare to suspend system with it. I just turn it off as it starts rather quick for me.
Offline
Normally I use the suspend button on GNOME's interface, but I was able to repro it just now with systemctl suspend. Does suspend normally cause issues with nouveau?
Unfortunately I've experienced some freezing again on the Nouveau drivers, so maybe it's not Nvidia related or perhaps there is a bug in nouveau that is also causing the freezes? I just run Firefox and a GTK messaging app on this computer, so I thought it'd be a good fit.
There's zero info in the logs when the freeze happens, the logging just stops without printing any errors. Not really sure where to look...
Offline
You may try to setup and use SysRq:
https://wiki.archlinux.org/title/SysRq
or try this procedure:
https://bbs.archlinux.org/viewtopic.php … 5#p2186125
Update:
The 'nouveau.config=NvGspRm=1' parameter, according to what I found, will not work with your card - you need newer card for this like Turing and up (16X0, 20X0-40X0).
You may try 'atomic=1' kernel boot parameter if it something changes...
Last edited by xerxes_ (2024-08-19 18:41:44)
Offline