Multiple threads for continuing problems cause confusion for those attempting to assist.
It is always best to complete the solution for one problem before tackling another so the focus remains constant.
We cannot tell what changes made based on suggestions on the other thread might interfere or assist in solving this issue.
As asked on the other thread, when dealing with a grub issue it helps us to help you if you post the output from cat /etc/default/grub and cat /proc/cmdline so we can see if the changes made the the first was applied properly.
I did not consider this to really be the same problem, since even with a completely reverted GRUB file, this issue still occurs, although it started at the same time. As mentioned, I also made some software updates when the issue occurred, so while I think the two may have caused this problem in conjunction, for the sake of other users who might have encountered this problem after adjusting GRUB and making software updates at the same time, I made a separate thread. Still, I could be wrong about that diagnosis.
You mentioned an update, and I know the kernel was recently updated from 6.4.7 to 6.4.8. Did your update include that kernel update?
Where was virtualbox installed from? Oracle or rpmfusion? If from oracle then potentially the driver did not properly get updated to match the new kernel.
The same applies to the nvidia drivers – even when installed from rpmfusion.
Both drivers require to rebuild the kernel modules after the install completes and before the user reboots. If one does not wait adequate time after doing an update that involves either the drivers or the kernel then rebooting may interrupt the driver build and thus prevent a suitable driver build so they cannot be loaded properly.
To check the nvidia drivers one may use lsmod | grep nvidia. If that returns 4 or so lines of text showing the nvidia drivers then they are loading properly. If not then they are not loading.
One may force the system to rebuild the drivers by first removing the currently installed modules that might exist. This is done by using sudo dnf remove kmod-nvidia-$(uname -r). Following that the command sudo akmods --force --kernels $(uname -r) will rebuild and reinstall the modules for nvidia (actually it would rebuild all kernel modules that were originally built with an akmod-XXX package). The critical thing is that now one must wait until the command ps aux | grep kmod returns only one line to the screen with the grep command before rebooting.
If one installs VirtualBox from the rpmfusion repo this is the same way to recover. When installed from oracle the recovery is different since I think it uses dkms to build the kernel modules.
Both of those would be expected when the nvidia drivers did not load properly
The fix I gave should work as long as the nvidia packages are installed.
One can check that with dnf list installed '*nvidia*'
The output should look similar to this (except for all the kmod-nvidia packages)
Checking kmods exist for 6.4.9-200.fc38.x86_64 [ OK ]
Building and installing nvidia-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/nvidia/535.86.05-1-for-6.4.9-200.fc38.x86_64.failed.log for details
Building and installing v4l2loopback-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/v4l2loopback/0.12.7^20230503g2c9b670-1-for-6.4.9-200.fc38.x86_64.failed.log for details
Building and installing VirtualBox-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/VirtualBox/7.0.10-1-for-6.4.9-200.fc38.x86_64.failed.log for details
Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
'/usr/sbin/akmods --force' as root.
We can see that secure boot should not be interfering, but something is since the kmod-nvidia package is not being built locally.
Maybe try either a direct reinstall of akmod-nvidia sudo dnf reinstall akmod-nvidia to see if that works, or if that fails then one may remove akmod-nvidia and the remaining parts of the nvidia packages followed by a reinstall. sudo dnf remove '*nvidia*' --exclude nvidia-gpu-firmware sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda
Those two commands would manage that and should potentially install any missing dependencies as well. Something seems missing because the akmods command failed for VB, nvidia, & v4l2loopback as well. One may also need to use sudo dnf reinstall akmods
The rebuild status will be revealed when one runs dnf list installed kmod*
If that reveals that the kmod-nvidia-6.4.9-200.fc38.x86_64 package is installed then the reinstall and rebuild was successful. Remember that it may take several minutes after the install before that completes, ps aux | grep kmod will reveal several lines if the rebuild is in progress.
I added initcall_blacklist=simpledrm_platform_driver_init to one of the lines to try and fix a login screen issue, as mentioned in the linked topic. I’ve tried removing it to no effect, and it had worked previously, so I put it back.