Hello Everyone!
I’m a new user to Fedora, I recently did a system upgrade to Fedora 40 via CLI.
But I’m stuck while booting, after selecting the Fedora 40 from grub it is stuck TOC BLOCK ERROR. This is for my HDD but I’ve installed fedora on my SSD. This used to happen on Fedora 38 & 39.
Attaching screenshots for reference, my keyboard works when stick TOC BLOCK error screen. Need help with either get this to working or rolling back to Fedora 39 
My keyboard work while I’m stuck on TOC BLOCK error message screen.
This seems to be referring to a windows file system problem
that the linux kernel detected.
Try booting into windows and checking its file systems.
Also make sure to turn off windows fast boot.
No idea why you posted the video of your keyboard.
Regardless of this being windows issue on my HDD, my system works with Fedora39.
When I’m booting into Fedora39 I see this error message blink twice and move ahead to the encyption password screen.
When trying with Fedora40, it blinks twice and gets stuck on the screen.
I shared a gif of my keyboard to show that they keyboard is working while I’m stuck on the screen.
I’m not able to find a solution to get past this.
The info i posted is from my web searches to understand your issue.
I have no direct experience of this problem.
I would assume that f39 with the same kernel as f40 uses will also see the same problem.
All I can suggest is you try to fix the windows file systems and see if that works. I take it you have not tried to do this?
Even without my HDD plugged in I’m stuck on a blank screen.
I am not running Fedora on my SSD
I’m trying to find the Post where @computersavvy helped me troubleshoot a dual-boot issue, it was this same behavior. fastboot was the issue.
If the OP is having other issues related to F40, with a black screen, this is a different problem.
I note in your posts that you have the 6.9.7 kernel for both f39 & f40.
Can you boot properly with the f39 kernels?
This might be nvidia related. Potentially the nvidia drivers may have gotten corrupted by a quick reboot after performing the update or by a similar known issue when doing the system-upgrade going from f39 to f40.
Could you please boot into whichever kernel works then run dnf list installed \*nvidia\* and post the result so we may see the status.
Also, as already noted, if you are dual booting with windows and have a windows partition being mounted at boot time it is necessary that you disable fast boot within windows to allow fedora to mount that windows file system.
Hey Jeff,
Yes you’re correct F39 kernels are working & F40 is failing.
I was able to launch F40 with following commands nomodeset plymouth.enable=0
But this was starting in 4:3 and low resolution. I tried installing driver there but that didn’t work.
Please find the requested information below.
prithvi@fedoranator:~$ dnf list installed \*nvidia\*
Installed Packages
akmod-nvidia.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.9.7-100.fc39.x86_64.x86_64 3:550.90.07-1.fc40 @@commandline
kmod-nvidia-6.9.7-200.fc40.x86_64.x86_64 3:550.90.07-1.fc40 @@commandline
nvidia-modprobe.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
nvidia-persistenced.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
My fastboot is disabled
Added f40
You are missing the nvidia-gpu-firmware package which is usually required.
sudo dnf install nvidia-gpu-firmware followed by a reboot should work.
Hey Jeff,
Thanks for the suggestion, I tried this on F39 and tried to launch F40.
Still facing the same issue.
This is the the video after selecting F40 from grub.
prithvi@fedoranator:~$ dnf list installed \*nvidia\*
Installed Packages
akmod-nvidia.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.9.7-100.fc39.x86_64.x86_64 3:550.90.07-1.fc40 @@commandline
kmod-nvidia-6.9.7-200.fc40.x86_64.x86_64 3:550.90.07-1.fc40 @@commandline
nvidia-gpu-firmware.noarch 20240610-1.fc40 @updates
nvidia-modprobe.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
nvidia-persistenced.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64 3:550.90.07-1.fc40 @rpmfusion-nonfree-nvidia-driver
The image is not necessary and is in fact redundant since you posted the text shown on that screen.
I am not understanding this.
Have you, since upgrading to f40, tried the following.
sudo dnf reinstall shim\* grub2\*
Your error seems like something that may have possibly already been fixed but not updated on your system.
Should I be running these commands on F39?
sudo dnf reinstall shim\* grub2\*
sudo dnf install nvidia-gpu-firmware
Update: I ran above commands in F39, still cannot login into F40 (with & without nomodeset plymouth.enable=0)
Is there a way I can simply rollback to F39 & do a fresh installation F40? Or maybe reinstallation F40?
Hello Everyone,
Latest update, system boots with nomodeset plymouth.enable=0 & everything is working absolutely fine.
Only problem is that without nomodeset plymouth.enable=0 i get stuck, with the commands it gives me CLI to type the password and proceed.
My display resolution & refresh rate is fixed.
Please help me fix the initial encryption password screen
Also, I would like to appreciate @computersavvy & @hamrheadcorvette for helping me out!
adding nomodeset under boot options, works for me!
