You are not logged in.
Test nouveau first.
You'll have to add this key to your known gpg keys, https://aur.archlinux.org/cgit/aur.git/ … -kdump#n13 or skip checking, https://wiki.archlinux.org/title/Makepk … e_checking
gpg --search 2DDF72E5A5A55BA89DAA42E1C23D91F3A125FEA8To stress that, "rebooting" the crash kernel is not like a regular reboot where you'd restart the system, the BIOS posts etcetc, you're booting another kernel while the system keeps running.
You do have the nvidia kernel module installed for the kernel version (I guess you're changing from the main to the LTS one?) you're using as crash kernel?
(This is btw. not necessary - you can use the same kernel binary for both functions, it's a bit like running "exec bash" from a bash prompt)
Offline
Running Nouveau as I speak. Sleep issue still there. No changes in that. No brightness control either but that's not the issue here, so it can wait. Either go back to proprietary or find other ways. Anyways,
kexec e
Still gives a black screen. It's possible it isn't a GPU issue too.
"rebooting" the crash kernel is not like a regular reboot where you'd restart the system, the BIOS posts etcetc, you're booting another kernel while the system keeps running.
I didn't know it just changed kernel while running. If kernel is crashed, how will it boot into same kernel again? Considering I'm using same binary (linux lts) for both crash and regular operations...
Also do inform if you need journal for nouveau REISUB too
Last edited by silverfos_ (Today 05:50:34)
Offline
If kernel is crashed, how will it boot into same kernel again?
Same way you'd start eg. your browser again after the browser crashes.
Still gives a black screen.
w/ kdump setup??
Does this also happen when only booting the mulit-user.target?
Do you have the suspend issues when booting the multi-user.target along the "nomodeset" kernel parameter?
(2nd link below)
Offline
With my own kdump setup, at least screen used to go dark. With simple-kdump it just freezes on last screen when testing. Imma try without gui and get back in a while.
Does this also happen when only booting the mulit-user.target?
Also, if multi-user.target is same as graphical.target, then yes? Well, when links are made it says multi-user.target.wants so yes if going by that logic.
Anyways, assuming nomodeset is without gpu, imma try and get back
So I tried setting default as multi-user since I wasn't sure if it's same or not. And it opened without a graphical interface. To conclude, no it doesn't wake up after suspend WITHOUT nomodeset.
Imma update in a min about with it.
And.... Nope. No wake even with nomodeset
Also can I switch back, away from nouveau? It's bad, I can't lie. 2 tabs and the display looks like a picture taken from a fast moving vehicle.
Last edited by silverfos_ (Today 13:49:56)
Offline