Boot hangs after started gdm.service -gnome display manager
I installed virtual box (not sure if it's related but more info the better I find) and after I reset my pc, it hangs at the above title. I can reset into an earlier snapshot but virtual box isn't installed. Any ideas what could fix this?
7 Replies
I'm in bazzite 40 ostree: 1
Rather than bazzite 41 ostree 0.
Has anyone got any ideas?
Load into Bazzite 40 Then and pin it as you have a working Bazzite which you want to be able to load back to whenever needed with
sudo ostree admin pin 1 then you can confirm that it's pinned with you run rpm-ostree status .
Then do an rpm-ostree reset to unlayer virtualbox and other packages and update to Bazzite 41 without Virtualbox installed and see if you get your issue or not. If you have no problems then the issue might be Virtualbox. If you have boot issues then the issue might be Bazzite 41 in general rather than Virtualbox.
If all looks good then you can try and layer virtualbox again and see what happensThanks for your help here. So I've followed your guide up to rpm-ostree reset. It's now got changes queued for next boot. After this reboot, can I just clarify that I'll then need to update to Bazzite 41 after this reset?
After the reboot, it booted straight in and system information reckons it's already Bazzite 41
cool. so your system is updated and working fine without virtualbox. Now try and install virtualbox again and see if it still works
So far it looks like virtualbox or some other package that was layered was causing your issue.
So Virtualbox has now install, It's not working but I got it installed. When I go to launch a VM I'm met with a kernel driver not installed error. Running the suggested command throws me all sorts of errors
/sbin/vboxconfig
rm: cannot remove '/sbin/rcvboxdrv': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxdrv': File exists
./routines.sh: line 165: /lib/systemd/system/vboxdrv.service: Read-only file system
rm: cannot remove '/sbin/rcvboxballoonctrl-service': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxballoonctrl-service': File exists
./routines.sh: line 165: /lib/systemd/system/vboxballoonctrl-service.service: Read-only file system
rm: cannot remove '/sbin/rcvboxautostart-service': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxautostart-service': File exists
./routines.sh: line 165: /lib/systemd/system/vboxautostart-service.service: Read-only file system
rm: cannot remove '/sbin/rcvboxweb-service': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxweb-service': File exists
./routines.sh: line 165: /lib/systemd/system/vboxweb-service.service: Read-only file system
ln: failed to create symbolic link '/sbin/vboxconfig': Read-only file system
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-6.11.6-303.bazzite.fc41.x86_64
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-6.11.6-303.bazzite.fc41.x86_64
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Which I've been running it as root
So then you might want to boot back to bazzite 40. Then run
rpm-ostree rollback (this will make Bazzite 40 your default boot). Then turn off autoupdates with ujust toggle-updates else your system will auto update to Bazzite 41 and break again. Hopefully someone will figure out how to get virtualbox working on Bazzite/Fedora atomic 41 in the future.
Note that if you turn off auto updates, you'll want to manually run flatpak update from time to time to upgrade your flatpaksFair, appreciate your help