I’m using the KDE spin of Fedora. After the last update for 39, my computer starts up to the grub menu, but then I lose my display. (My monitor connection fails after the grub screen.) I tried choosing earlier kernel versions, but that doesn’t do anything. I have a MSI Ventus GeForce RTX 3060.
What can I do to fix this? I’m clueless at this point.
When you have one of the newer nvidia GPUs as yours is, then simplest fix is to install the nvidia drivers from the rpmfusion repo.
You should be able to log in to the command line by using ctrl-alt-F3 and do the following.
dnf repolist should show if you have enabled the rpmfusion-nonfree-nvidia-driver repo.
If you have done so then the command sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda would install the driver. Wait about 5 minutes after the install completes then reboot.
If you have secure boot enabled then you will need to follow the steps in the secure boot link at Howto - RPM Fusion to enable signing the modules and using them with secure boot. Once those steps are completed then the command sudo akmods --force --rebuild should redo the module so another boot would then load it.
Thanks, but my problem is that I can’t get past the grub menu. Once I choose an option, I lose my display, so I can’t get into the terminal to make any changes. This is the last thing I see before the computer stops working with my monitor:
Additionally, the ‘c’ command-line option doesn’t actually do anything. I just get errors trying to use it:
From that grub menu have you tried any of the older kernels or the rescue kernel for booting? It is quite possible that one of the older kernels will boot and repairs can be made.
I see the 6.9.4 & 6.9.6 kernels and assume the highlighted one is 6.9.7 though it is not readable.
Yes, the grub command line is very limited in what it can do. It is, after all, only the boot loader and not an OS. The commands I gave were intended to be used after logging in.
This is not helpful. Does it boot or not? what actually happens? Does it also go to the grub command line or?
If it goes past the grub menu (your first image) and you can boot to an older kernel, even if the screen stays blank then it may be possible to get to a command line login as I suggested with ctrl-alt-F3
Yes. I have tried them all, to no avail. The display cuts out after choosing any of the kernel options provided.
When I turn on the computer, it boots up to the grub screen (what is in the first image). Then, after choosing any of the kernel options, I lose my monitor connection. The computer is still on, but it’s no longer communicating with my monitor. It’s as if the graphics card is no longer recognized.
The second image is the command line I’m able to get to from that grub menu. However, when I enter anything in (see image), it only produces errors. This is probably because it is limited in what it can do and doesn’t work as a Linux terminal.
My problem is that it does not go past the grub menu. ctrl+alt+F3 does not work for me, either.
Can you confirm that you were able to boot into any of the previous kernels (6.9.4 and 6.9.6) in the past, and it is only after the last update that you are unable to?
Yes. This issue started after the last update to 39.
For a start, please edit the grub menu entry with e, then:
rhgb quiet, in order to change booting to verbose mode. Boot with the modified boot entry, and tell us what you see.Just to clarify: you were already on F39, and did a regular update, or did you do a system upgrade (from F39 to F40 or from F38 to F39 maybe)? How did you do the update: via Discover or via terminal (dnf)?
<Ctrl-Alt F3> do <Caps Lock> or <Num Lock> lights respond (indicating the kernel is alive)?sudo dnf install inxi, then inxi -Fzxx and paste the output as pre-formatted text (using the </> button from the top line of the text entry panel).You may have a mass storage failure. If quick fixes fail, you should verify that the storage device is working properly (older devices that are nearing end-of-life often fail under the added stress of an update). If you can boot a Live USB system you should be able get the S.M.A.R.T data for the system drive. Gnome Disks has that as an option, not sure if it is available in KDE GUI sessions, but you can install smartmontoools (command-line).
I was on 39 and did a standard update for 39.
He’s what I see:
I can delete that entry, but how do I save that change before rebooting so it can take effect?
Thank you, but none of this is possible since I cannot get past the grub menu. My computer is somewhat new (~ 2 years).
The change is just for the current boot. Press “b” to boot and with luck you will see some useful error message.
The grub menu is not relevant when booting the a Live USB. You will need to disable secure boot if it is enabled and use appropriate (system dependent) function key to get to the option that will boot the USB key.
Typing b will just put a b on the screen in edit mode. My only options appear to be Tab to see a list of possible entries, Ctrl+x to boot (which doesn’t save anything and continues, giving me the same result of no monitor display), Ctrl+c for a minimal grub command line, and Esc to discard the edits and return to the grub menu.
Sorry, it has been a while since I needed to edit the command-line in grub (I always configure grub without rhgb quiet when installing Fedora). should boot with the current (edited) command line. The edit applies only to the current boot, so if the screen goes blank the issue occurs early in the boot process.
I think I can boot from a USB stick if I change it in the bios. However, I’m wondering if there’s something I can put on it to help fix this issue. I know nothing of my options.
It may also be of interest to note that I cannot access the rescue mode either.
