I just did a dnf system-upgrade process to F37 from F36. No problems reported during the upgrade process but when the process was finished and the system tried to reboot into F37 the system comes up and indicates it is booting on kernel 6.2.12-200.fc37 the system fails to wake up the monitor for the login screen. The same look I see a lot after the system sleeps over night. The monitor light just flashes and never wakes up. I can boot back into the f36 kernel 6.2.12-100.fc36.
Apr 28 16:45:20 odyssey systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 28 16:45:20 odyssey systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Don’t really know what that means. Any help on how to trouble or fix would be appreciated!
Thanks
The NVIDIA drivers from RPM Fusion were installed and working before dnf system-upgrade. Do I have to re-install these drivers after upgrade?
When I boot on the F36 kernel the NVIDIA drivers work.
However I do see errors about nouveau in journalctl. I’m using 530.41.03.
(computersavvy ) That would have to be from the f36 kernel where the NVIDIA drivers are working:
[root@odyssey: ~ ]
SU: # dnf list installed 'kmod-nvidia-*'
Installed Packages
kmod-nvidia-6.2.11-100.fc36.x86_64.x86_64 3:530.41.03-1.fc36 @@commandline
kmod-nvidia-6.2.12-100.fc36.x86_64.x86_64 3:530.41.03-1.fc36 @@commandline
kmod-nvidia-6.2.12-200.fc37.x86_64.x86_64 3:530.41.03-1.fc37 @@commandline
[root@odyssey: ~ ]
SU: #
and installed kernels:
[root@odyssey: ~ ]
SU: # dnf list installed kernel
Installed Packages
kernel.x86_64 6.2.11-100.fc36 @updates
kernel.x86_64 6.2.12-100.fc36 @updates
kernel.x86_64 6.2.12-200.fc37 @updates
[root@odyssey: ~ ]
SU: #
The whole journalctl from that boot is massive! Most messages I don’t ever recall seeing in a normal boot process, but this the first time I have tried Fedora 37
One might try rebuilding the nvidia modules for the new kernel sudo dnf remove kmod-nvidia-6.2.12-200.fc37.x86_64 sudo akmods --kernels 6.2.12-200.fc37.x86_64
should remove the driver that does not load and build the new driver.
After the prompt returns wait another minute just for certainty then reboot to the 37 kernel and it should work.
If not then let us know exactly what you see during the boot.
You can watch the kernel messages during boot by opening the grub menu and editing the grub entry command line that begins with linux to remove the rhgb quiet part of the line and it will scroll the messages on screen during boot. When it stops and the boot fails the last messages should provide a clue as to why.
[root@odyssey: ~ ]
SU: # dnf remove kmod-nvidia-6.2.12-200.fc37.x86_64.x86_64
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
kmod-nvidia-6.2.12-200.fc37.x86_64
x86_64 3:530.41.03-1.fc37 @@commandline 41 M
Transaction Summary
================================================================================
Remove 1 Package
Freed space: 41 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : kmod-nvidia-6.2.12-200.fc37.x86_64-3:530.41.03-1.fc3 1/1
Running scriptlet: kmod-nvidia-6.2.12-200.fc37.x86_64-3:530.41.03-1.fc3 1/1
Verifying : kmod-nvidia-6.2.12-200.fc37.x86_64-3:530.41.03-1.fc3 1/1
Removed:
kmod-nvidia-6.2.12-200.fc37.x86_64-3:530.41.03-1.fc37.x86_64
Complete!
[root@odyssey: ~ ]
SU: # akmods --kernels 6.2.12-200.fc37.x86_64.x86_64
Could not find files needed to compile modules for 6.2.12-200.fc37.x86_64.x86_64
Are the development files for kernel 6.2.12-200.fc37.x86_64.x86_64 or the appropriate kernel-devel package installed?
[root@odyssey: ~ ]
SU: #
It looks like the modules aren’t there. How do I get the modules?
Sorry, my last post was premature. I was rushing to get to my grandsons soccer game. What you suggested solved my problem when I actually followed your instructions. I now can boot to the f37 kernel so all is well.