System update causing issue?

Hey there. I saw there was an update to install from Bazzite. Everytime I restart now, I get to this menu and if I don't have a keyboard to select "Bazzite 42 ostree:1", the first option goes through and gives me a black screen with an underscore. Please assist. Thank you.
No description
9 Replies
Cilantro Limewire
Cold boot into bootloader by mashing volume up, then select bazzite boot disk, then you can use Dpad and A in grub menu to boot to 41 Then go into desktop mode, and use Bazzite rebase helper: brh rebase stable (or testing, whatever you’re not on rn)
antheas
antheas2w ago
just update again and be patient
Zeth Windwrecker
Zeth WindwreckerOP2w ago
Is it okay if after I restart, Bazzite boots back into a black screen with just an Underscore?
antheas
antheas2w ago
just wait for 5 min sometimes it happens if that doesnt work, use a keyboard to select the first one and then update second one*
Zeth Windwrecker
Zeth WindwreckerOP2w ago
Cool. Thanks. Sorry, a lot of this is new to me. Hey dude, I tried this. It gave me the option to choose between Windows and Fedora, but that's it.
Cilantro Limewire
Choose fedora, then you should see that same grub menu but this time you can use your controller in it. Reason being the ally only initializes the controller driver at that stage if in bios, so this is a workaround unless you wanna plug a keyboard in I had a similar issue with the black screen, rebased twice and got clear of it. Let it sit black for awhile too and couldn’t seem to get a keyboard recognized. YMMV but that’s how I got back on the path
Zeth Windwrecker
Zeth WindwreckerOP2w ago
Ahhh okay, now I see. I think I've rebased to the test build. I've successfully restarted without going into the grub menu again. Thanks for your help, folks. Hopefully things go well from here.
Cilantro Limewire
Right on, now if you rebase to stable you should be solid on 42 in case you’d prefer. My assumption is the leap from 41>42 with standard update process left some conflicting configs or scripts that prevented a full container mount and launch, but rebasing removes those potential conflicts fully
Zeth Windwrecker
Zeth WindwreckerOP2w ago
I just rebased to 42. Looks like everything is working as it should. Thanks a lot for your help!

Did you find this page helpful?