BIOS Update caused bazzite to no longer boot
Hardware: ROG Ally X
My ROG Ally X undersent some Windows Updates and one just so happened to be a BIOS update. I've known something like this would happen eventually as my bazzite boot launcher broke a few months back and I was given a bandaid solution until it would envitably break again, and now here we are. Usually my Ally boots straight into Bazzite and then from there I have a Non-Steam game shortcut that takes me into Windows, but when my Ally finished the BIOS update it launched into grub instead of straight into Bazzite. At first I didn't think anything of it because before I had to do the bandaid fix, seeing grub when I turned on my device was not uncommon. So I pressed enter and instead of booting into Bazzite I was met with the message shown in the picture. If anyone could help me understand what exactly this message means, or point me in the direction of how to fix it it'd be greatly appreciated.
Another note, I thought maybe my Bazzite bootloader was broken again so I checked it out and it looks fine so I don't believe it to be an issue with that again. Although I did mention it in the post in case it could have any bearing to the problem at hand. Again, thanks in advance.
My ROG Ally X undersent some Windows Updates and one just so happened to be a BIOS update. I've known something like this would happen eventually as my bazzite boot launcher broke a few months back and I was given a bandaid solution until it would envitably break again, and now here we are. Usually my Ally boots straight into Bazzite and then from there I have a Non-Steam game shortcut that takes me into Windows, but when my Ally finished the BIOS update it launched into grub instead of straight into Bazzite. At first I didn't think anything of it because before I had to do the bandaid fix, seeing grub when I turned on my device was not uncommon. So I pressed enter and instead of booting into Bazzite I was met with the message shown in the picture. If anyone could help me understand what exactly this message means, or point me in the direction of how to fix it it'd be greatly appreciated.
Another note, I thought maybe my Bazzite bootloader was broken again so I checked it out and it looks fine so I don't believe it to be an issue with that again. Although I did mention it in the post in case it could have any bearing to the problem at hand. Again, thanks in advance.
