There have been multiple 6.18.x kernel updates. When reporting an issue it is important to fully update both Fedora and vendor firmware so you aren’t chasing a solved problem and to maximize the chances that others will be using the same software.
Hi George, thanks for the suggestion. I updated everything as recommended:
Fedora fully updated via sudo dnf upgrade --refresh
Kernel is now: 6.18.9-200.fc43.x86_64
fwupdmgr get-updates shows no available firmware updates (System Firmware/UEFI all up to date)
NVIDIA driver is: 580.119.02 (KDE on Wayland; nvidia-smi works and shows the RTX 4060 in use)
nvidia-suspend.service, nvidia-resume.service, and nvidia-hibernate.service are all enabled.
Unfortunately the issue persists: after suspend, the laptop powers back on but the screen stays black (no image). I usually have to hard power-cycle to recover.
What would you recommend as the next troubleshooting step?
I am having the exat same issue, and I have tried the exact same steps as @lseijas , my laptop is a little bit different is an HP Victus with an RTX 5050. The system shows a dual gpu, the IGPU with intel graphics and the rtx 5050
Are you able to get a text console with <Ctrl-Alt-F3> when the screen goes black? This is helpful for troublshooting.
“All linux issues are transparent given enough eyeballs”, so you need to provide hardware details and journal records as web-searchable (pre-formatted) text (from the + menu at the top of the text entry panel). This may be found by others with similar hardware and issues.
Post full hardware details by running inxi -Fzxx in a terminal and posting as web searchable text.
Read man journalctl along with https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/, then experiment with “filters” to select relevant entries from the massive detail collected in the journal. There are lots of examples in this forum, not necessarily related to graphics. Use the manual to understand the filters so you can devise one specific to your issue.
Same issue here, my friend. I think we will need a correction on a next version.
After blocking de session, i can not return. Black screen with a cursor above, blinking. At least, we can acess comand lines. I type ctrl+alt+del to restart, my only option. Its not a blackscreen at all, the computer remains active.
After blocking a session, the sistem automaticaly blocks all after suspention I don´t know why. There is a option of it on Sistem Configurantion > ScreenBlock, to shutdown block after suspention. But aparently, does not work.
In my specific case i couldn’t get nothing by pressing CTRL + ALT +F3, nor any F keys
I kinda fixed it with sudo grubby --update-kernel=ALL --args="i915.modeset=0", I say “kinda” because that’s something chatgpt told me to do but i don’t understand why does it fix it or what it does… so I’m not sure if I should recommend doing it.
Also it seems the command works for my specific model of laptop, an HP Victus with Intel i5 210H and RTX 5050, but I can’t guarantee it will work elsewhere.
AI seemed pretty sure it had something ot do with the laptop having 2 GPUs, the integrated gpu and the dedicated GPU.
I have the same issue with black screen but active keyboard (numLock and CapsLock working). I had to try many combinations of keys to activate the screen and sometimes it worked, but recently it doesn’t. Windows + Esc seemed to be the one working best.
Then I changed the options in System> Energy Management >
Automatic black screen > NO and
Suspend > NO
And now I have a black screen with disabled keyboard and had to operate a hard reboot.
Following some suggestions found by AI, I had deleted the words rghb and quiet from GRUB, but it doesn’t seem to be a stable solution, since these words come back every time.
My system is:
Fedora used to work perfect before I installed the NVIDIA drivers that really change the experience, but this black screen issue is very annoying.
Any suggestion for a more stable solution?
Please treat me as a beginner with Linux since I installed it only one month ago for the first time.
Thank you in advance for any help.
Your 750 Ti card isn’t officially supported by the Nvidia 580 drivers. The latest version to support it is the 470 driver, which is available from RPMFusion. But that driver doesn’t support Wayland, so Fedora 43 Workstation will have problems with it.
The best solution to run Fedora 43 Workstation on your card is probably to stick with the nouveau drivers (which is what you would have had before installing the proprietary Nvidia driver).
This thread has Workstation and KDE and assorted vendors, leaving Nvidia 580.119.02 as the common factor. Does nouveau work ( RPM Fusion Nvidia Howto has a section on switching back to nouveau)?
Thank you, NOUVEAU used to work just fine, how do I move back to the previous driver now? Simply uninstalling NVIDIA add-on?
I have to admit that the experience with the new drivers is dramatically different, but I’ll give it another try to see if I can find something that comes close using the nouveau drivers.
Finally, is there a chance that a new driver will be offered for my 750 Ti Card, supporting Wayland? It looks like a stupid error, just annoying, not preventing to work in the first place.
After removing the drivers as suggested by @gnwiii , @pg-tips & @anotheruser above, you should verify that the nouveau driver is enabled by running the following commands (before rebooting). cat /etc/kernel/cmdline and cat /etc/default/grub
If either of those commands show rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core in the output then you may need to permanently enable the nouveau driver by using the command sudo grubby --update-kernel=ALL --remove-args='rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core'
That grubby command will edit everything necessary to remove the blacklist from the kernel command lines in grub and enable use of nouveau.
Note that the use of grubby here is only predicated on the possibility that removing the nvidia drivers as suggested by others above might not alter the kernel command lines as noted. If those args are already removed from the files noted then using grubby that way is not required.
Thank you, very kind and fast to respond, too.
In the meantime, by disabling the suspend and the energy saving automatism, the PC of course didn’t run into the black screen issue. For a Desktop like mine this can be an option, too, since there’s no problem at booting. For a Laptop I believe it may not be acceptable.
