I decided to update my GPU drivers using the RPM guide because I thought this was causing the black screen I would experience sometimes after waking up my computer from sleep. I believe I did wait the necessary amount of time before rebooting, but now I just have a black screen and haven’t been able to find a solution to this issue now. If anyone has any ideas I would greatly appreciate it. Thank you.
That is the guide that I followed. I typically just use that same command as well, but while trying to troubleshoot on my own (I’m pretty new) it seems I made a mistake haha…
Do you know how I would go about uninstalling the drivers?
I was able to boot after adding -nomodeset in grub. It is actually running significantly better with this? Would the commands you just suggested be the best next step?
Running additional commands is entirely up to you.
Is the system working as expected? Probably nothing else needed.
Is there a specific issue that you can identify and focus on? Then assistance with that issue should be requested.
Those who depend on AI and random advice from searching the internet are often just asking for more problems. Asking here for advice is a very good choice since many here are experienced and can provide the best suggestions to reach a solution.
Could you post the result of cat /proc/cmdline for us to look at?
Currently I am not seeing any issues. I am not familiar enough with Linux to understand if adding nomodeset is a permanent or appropriate fix to this issue. I still do not understand what the exact issue was.
Edit: I rebooted to see if the issue persisted and it went straight back to the black screen. I went back into grub and added nomodeset again in order to boot properly.
As I understand it, using nomodeset doesn’t load the driver until you get to starting X11. If that works then you should be able to permanently add nomodeset to the grub command line so that you don’t have to do it every single time. I believe you can do that by editing the config file but right now I don’t have that information. I know there is a post on here somewhere that explains the procedure.
I am using Workstation (GNOME) and after removing rhgb from the kernel cmdline it booted properly. Removing this just removes the graphical boot screen, correct?
Should I permanently remove rhgb instead of adding nomodeset to the grub command line? I’m still not understanding why updating my nvidia drivers caused this issue.
I personally don’t have the rhgb flag on my kernel parameters, I prefer to see the boot messages so that if anything fails or something out of the ordinary happens, I can see it.
Whether you remove it is entirely up to you. You should be able to hit escape when plymouth is displaying its boot screen to remove it anyway.
The nomodeset parameter tells the kernel to not try to set the graphics mode when it starts but to leave it to the graphics driver, whatever that driver happens to be. Kernels try to perform mode-setting by default so we can have nice high-res screens (for plymouth to display its pretty picture as an example) as early as possible in the boot process and to avoid a nasty flicker when the graphics driver is eventually loaded and tries to perform that same task.
Unfortunately this does not always work and the end result is usually a black screen. On my wife’s MSI motherboard and old GTX 980 this can sometimes display random garbage in patches of the screen which are purely cosmetic but look like something is failing. As soon as the drivers load, it’s cleaned up and it’s fine.
By adding the “nomodeset” parameter to the kernel parameters you’re telling the kernel to just use a low(er) res screen, or whatever the hardware happens to default to, and to let the graphics driver take care of it.
If one combination of removing rhgb or adding nomodeset works for you, use it. It’s only graphical and should not impact the boot process (but of course, a fully booted system with a blank screen is of little use unless it’s headless)
If that is what works for you the simplest way to make the addition permanent is to use grubby. sudo grubby --update-kernel=ALL --args=" nomodeset "
This makes the changes in every location required (/etc/default/grub, /etc/kernel/cmdline, /boot/grub2/grub.cfg, and the kernel .conf files in /boot/loader/entries/) and does not require using the grub2-mkconfig command.
If you choose to remove the rhgb argument it can be done similarly. sudo grubby --update-kernel=ALL --remove-args="rhgb" Personally I remove both args "rhgb quiet".
Removing those args means that there will be some text scrolling on the screen during boot, but I prefer that to having the screen display nothing but the spinning circle while booting.
I have never used grubby before but thanks for bringing that up as I knew there was probably another way to accomplish the same thing. I just took a quick look a the man page for grubby…
That is probably not the root cause.
If you have time could you please try the following:
If I am not mistaken the cpu
has also an iGPU (driver: amdgpu?)
try booting with this changes:
add rhgb, remove nomodeset and append ,amdgpu to rd.driver.blacklist =>> rd.driver.blacklist=nouveau,nova_core,amdgpu
leave modprobe.blacklist as it is.
Does the system start successfully with these changes?