Booting not possible anymore
Hi! im running bazzite-nvidia, and when i wanted to just reboot my device since a game (dota 2) didnt want to launch for whatever reason, i now boot into a full blackscreen with no apparent progress. Im waiting already for around 6 minutes. this didnt happen before, and i couldnt even access grub. What are the things i may be able to do to revive the pc?
15 Replies
what i did find out as far as i am now, is:
- the kernel seemingly doesnt hang, when i just press the power button, fedoras splash pops up and shuts down.
so i assume its something related to the nvidia driver?
You have secureboot enabled?
Negative
I disabled it prior a long time ago, like at least a year now
Can you do ctrl+alt+f2
Also not, sadly. I iterated through all f keys to see if any of these work
Which is odd, to be honest.
On another matter, for some reason I can't even boot the iso properly anymore (1.0.1), its always stuck on dracut
Definitely weird given that I've been successfully using bazzite for about a week or so.
Did you upgrade your firmware or something? 🤔
Strange that it worked before and not anymore
Also not, I've didn't change anything on the hardware-side or uefi
does silverblue iso work for you?
Will check in a second
Haven't tested that one yet
Silverblue seems to be able to install, currently in the process of doing so
i now followed the readme (https://github.com/ublue-os/bazzite#gnome) to rebase, but i already have problems again
GitHub
GitHub - ublue-os/bazzite: Bazzite is an OCI image that serves as a...
Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers and living room home theater PCs. - GitHub - ublue-...
using this:
results into:
so i guess my next question is: how would i enable replacement?
nvm, had my old issue with my weird hostname, seems to run now.
lets see if that brings me back to bazzite
seems like im back up and running, nice.
@tsubajashi how did you resolve that? I had that error after multiple reboots and eventually tried a
rpm-ostree reset which led me to a different set of errorsi listed everything ive done here, it is kind of impractical how i did that since it resulted into a fresh system
For me this got fixed through a restart if I remember correctly
so it may just happen on any system using those in very rare instances