You can install it through the website and that'll override the system version for now
You can install it through the website and that'll override the system version for now
Jhuh, weird. I swear it was working like a week ago
Kyeah, local install works
Kit was
Kthis got missed, we're just waiting for the fix to be approved and land in stable
Jah
Bis there a image for nvidia with game mode enable or a tutorial if i wanna give it a try?
VThere isn't, period. The drivers don't work with gamescope-session which is required for game mode.
VThis may change in a few year(s)
ZBtw dont update resolve
Zdev did a refactor and .desktop shortcuts dont work for now
Jlike this?
DWhen will the next Bazzite update be?
Ktoday
VWhat about tomorrow
Jdoesnt seem to work ;( oh well
Kprobably
VMadness!
DCould you mention some improvements?
J
DI would like to understand why the GRUB takes so long to start the system, and sometimes it doesn't start at all
VThat's not normal behaviour.
Kwe don't make grub, and given the number of other issues you've had I'd seriously start to consider hardware issues
Hgot a new usb, checked the hash and it matched and it still won't boot from ventoy
DLol
VEspecially intermittent issues like this.
POk, what is sus about it? Would you recommend against dual boot at this time? I think the issue has to do with the Ally's Bios option for Secure Boot. Everything worked great except this Bios setting, which is not discussed anywhere in the documentation.
If I leave Secure Boot Control enabled in Bios (and it's on by default), I get this screen when booting to Bazzite. However, the dpad is nonfunctional so I have no way of getting past this screen. All the buttons don't work, this screen forces me to reboot, go into Bios, and disable Secure Boot Control. Then it boots to Bazzite without a problem. Secure Boot Control is separate in Bios from Secure Boot itself being on or off; in my case Secure Boot has always been set to off, but Secure Boot Control was set to enabled by default and I had to turn it off.
Otherwise I did everything according to instructions.
If I leave Secure Boot Control enabled in Bios (and it's on by default), I get this screen when booting to Bazzite. However, the dpad is nonfunctional so I have no way of getting past this screen. All the buttons don't work, this screen forces me to reboot, go into Bios, and disable Secure Boot Control. Then it boots to Bazzite without a problem. Secure Boot Control is separate in Bios from Secure Boot itself being on or off; in my case Secure Boot has always been set to off, but Secure Boot Control was set to enabled by default and I had to turn it off.
Otherwise I did everything according to instructions.
KOk, what is sus about it?1: only one reporting a fundemental graphical issue our testers would have found
2: suddely broken Windows w/ issue that can't arise from mere dual booting
VDidn't the BSOD mention something BIOS related?
KYeah, ACPI issue
Kseriously fundemental problem
VOh yeah that's bad
Khence, reimaging Windows and trying again
PI guess my point is, I'm OK redoing the entire process but how do I handle the Bios setting I mentioned, do I turn it off before trying to install Bazzite? And is there anything else I need to do differently in my process? I'm just trying to understand why we would expect a different result if I repeat the process exactly the same.
Kbazzite can be installed w/ secure boot on
Kbut I wouldn't even touch that until you've confirmed windows works perfectly after reimaging
VI'm gonna say my piece and bet on SOME kind of hardware issue now, especially if Windows gives issues.
PHardware as in the Ally X or the Samsung SSD?
VI mean, I doubt it's the SSD if the BSOD is complaining about ACPI
Hdont have a usb to check ventoy with atm but the installer should have ventoy support. if not then its blindly tabbing to navigate the wrongly scaled installer 
PI think I'll return this Ally X tomorrow to Best Buy as planned, after I take out my SSD. Then on the new unit I'll put my SSD back in and see if Windows will boot, and if the graphics artifact still recurs. If there's still any issue I'll re-image the entire drive.
FSaw some workarounds potentially to get GeForceNow (Electron) to do 120FPS on linux. Something about modifying a few flags/settings in Chrome. Anyone ever try?
SI used ventoy (my ventoy version is 1.0.97) today with no issue
PDuring the install process Bazzite could not start up for the first time and was giving an error message about bad shim signature, which I understood had to do with Secure Boot, so I turned that off and then Bazzite finished installing and ran for the first time. I guess I'll have to pay extra close attention to that next time.
Kour installer uses Fedora's kernel, which is signed with Fedora's microsoft-approved key
Kthe only way to get that error is:
1: you messed up and didn't enroll the key after the installer finished
2: cosmic ray
1: you messed up and didn't enroll the key after the installer finished
2: cosmic ray
POK, now it's becoming clear where this went sideways. I watched Aru's video and in his install, he skips enrolling the key when shown the MOK option screen. I followed his video and clicked past it, and immediately got the shim error. I then went into Bios and disabled the Secure Boot Control, restarted, and Bazzite resumed installing and loaded successfully. I don't know how this causes an ACPI error but this is the clear point at which I fucked up (I've never used Linux before lol in case that wasn't clear). It's true that after I resized the drive, I never again booted into Windows, I went straight into booting the Bazzite USB and installing Bazzite. I did not boot Windows again till today when I got the ACPI error.
Hturning off secure boot would not cause the ACPI error as it is not related
Ksecure boot definitely has nothing to do with any of your problems
Kagain I don't even think it's worth the mental energy to figure this out, your issues are fundemental and I wouldn't do anything but re-install Windows right now and re-test
