I’ve just installed Fedora on my new laptop.
Before updating packages (and kernel), everything was fine. I’ve rebooted the PC several times with no problems.
After I’ve updated the packages, I can’t boot anymore with 6.4.7 kernel.
When I press ESC at boot and choose 6.2.9, the PC continues the boot process and asks me for the password to decrypt the volume.
Now, because I don’t know how to debug the problem, I need help, if possible!
Of course feel free to ask me everything on the hardware.
I really appreciate any help you can provide.
Yes, I already searched and found that article.
I don’t think it’s related to me.
I’ve tried to follow what those users did, but my results are inconclusive.
I don’t know exactly what to check.
I’d like to fix the problem with that!
Try to boot to 6.4.7. Wait for ~5 min and event with black screen try to switch to TTY - Ctrl+Alt+. If you get to a working TTY console - login using your user and password. If that works - try gather log data and find what is broken. Based on errors you will find, search internet or ask here more specific questions.
Was having the same problem. After removing rd.driver.pre=vfio-pci it worked again.
Get into boot menu, select entry with updated kernel version, hit ‘e’ in order to enter edit mode. At the end of end of kernel param line remove the ‘rd.driver.pre=vfio-pci’. Then boot it. If it boots, make change to kernel line permanent by removing the parameter from the GRUB_CMDLINE_LINUX= line in the /etc/default/grub config or using grubby. Then update grub to make change persistent. This workaround has to be reversed once the issue is fixed in kernel.
There is no magic command. Your problem seams a “popular one”. That thread contains some suggestions , please try what is most relevant in your case. As you did not share your HW details, there is nothing else I can help you with, apologies.
The problem is I’m upset because I waited a long time and … I’m stuck.
I’ve generated a file with ALL the specifications for my laptop.
I searched on Google, and I got something, I think. My laptop specifications
Apparently your post on pastebin was not made public. I cannot read it.
If you were to log in with the 6.2.9 kernel then run inxi -Fzxx and post that output here we could see the hardware and configs, including drivers, so we might have some idea of what is happening.
If you have an nvidia GPU then this might be related to an earlier noted problem where the password entry to unlock the disk was not displayed – It could, however, be entered blindly and still unlock the disk and continue.
That problem seemed to be related to NOT having the nvidia drivers installed (nouveau drivers in use), and once the nvidia drivers were installed the problem disappeared.
Just for further info,
Installing akmod-nvidia can be done, and yes it does install the latest kernel and the drivers for that kernel.
Once installed the user could boot to the 6.2.9 kernel then use the command akmods --kernels $(uname -r) --force to build the modules for the running 6.2.9 kernel. Once done, a reboot to the same kernel should load the drivers as long as secure boot is disabled.
In your case the nvidia 4070 gpu has no driver loaded at all.
That is a very new gpu and likely not yet supported by nouveau. I suspect that if you can get the nvidia drivers loaded the problem may disappear.
Install the drivers by first enabling the 3rd party repos in gnome software, then from the command line first use dnf list installed '*nvidia*' to confirm the nvidia-gpu-firmware package (and no other nvidia packages) is properly installed. If the system shows that package as any version other than the one below then upgrade that package before continuing.
# dnf list installed nvidia-gpu-firmware
nvidia-gpu-firmware.noarch 20230625-151.fc38 @updates
Then install the drivers with dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda to install the drivers and any necessary supporting packages.
Finally wait at least 5 minutes after that install completes then reboot and see if it will properly boot with the drivers loaded (disable secure boot if not already done during this boot)