You are not logged in.
Downgrade "how"?
The only way that's gonna "just work" w/ an 6.9 kernel is https://aur.archlinux.org/packages/nvidia-535xx-dkms
Just downgrading to a precompiled module from the ALA will leave you w/ no module for the current kernel and the dkms packages in the ALA won't build against 6.9 anymore.
You'll the likely end up w/ the VESA driver.
The plan was to simply delay the graphical target, not test the behavior on the console. Which is indeed surprising and doesn't fit the VRAM decay problem at all.
Do you still have the framebuffer console disabled and only an 80x25 console on the multi-user.target?
Offline
The only way that's gonna "just work" w/ an 6.9 kernel is https://aur.archlinux.org/packages/nvidia-535xx-dkms
Thanks, that indeed worked, and seems to have fixed the problem (or I got lucky, will know for sure in a couple of days).
Do you still have the framebuffer console disabled and only an 80x25 console on the multi-user.target?
yes for the framebuffer, but I'm back at graphical.target
if you believe this can help the community I can run some other tests/upload logs, otherwise I'll just stay on 535xx while I can
Offline
I've been setting up a new computer and experiencing this same issue on a desktop with a 4080 Super that I wasn't experiencing with a 3050 in my laptop. I'm running XFCE 4.18, linux 6.9.2.arch1-1, nvidia 550.78-6 on my end. (To be entirely fair, the latest kernel / nvidia driver isn't working with one of XFCE or LightDM on the laptop so I'm still on 6.8.9 / 550.78-2 and don't know if 6.9.2 / 550.78-6 has the same issues on there.)
I just wanted to say that turning off xfwm's compositor also worked for me, though I also want to add that I found a decent workaround. I'm leaving the compositor on, and for the time being, simply opening the terminal (keyboard shortcut) actually fixes the black screen for me.
Last edited by jadespace (2024-05-27 23:50:50)
Offline
@Lem0nHead you're probably running into https://bbs.archlinux.org/viewtopic.php?id=293400 and the xfwm compositor is just very likely to trigger that
@jadespace, feel free to try the 535xx driver as well
There's already a 555xx beta driver but afaiu that has another set off issues (or maybe it's just still the same bug)
Offline
simply opening the terminal (keyboard shortcut) actually fixes the black screen for me.
do you mean you login blindly (assuming you have a GUI lock screen) and press a shortcut to open the terminal (again GUI) and this fixes the issue? or do you go to another terminal (ctrl-alt-Fx)?
if the former, I'm curious to what else fixes the problem.. e.g. does alt-tab also recovers?
Offline
do you mean you login blindly (assuming you have a GUI lock screen) and press a shortcut to open the terminal (again GUI) and this fixes the issue?
Not quite. This might be a difference with me using LightDM, but I'm still reaching my greeter (lightdm-gtk-greeter) - it's after the login where it's black with only the mouse, which is probably why me making the window manager do something works.
does alt-tab also recovers
I would suspect so, but in trying to test that right now, it actually stopped being as easily reproducible. Not sure if I'd have to leave it in suspend for a longer period of time than a few minutes, but I don't have an answer right now.
Offline