copying to the usb (especially if the usb is crap or bad) can corrupt the iso
copying to the usb (especially if the usb is crap or bad) can corrupt the iso
Hthe usb is fine as far as im aware
Ha faulty/slow usb is never reliable
H yeah this is what i got on the usb
Hyep
Hat least you dont need to redownload
JIs anyone experiencing not being able to change the Just Pefection extension?
ZThat reminds me this will be a thing in a future XD
KView gnome-shell-extension-just-perfection in the Fedora package repositories. gnome-shell-extension-just-perfection: GNOME Shell extension to change behavior and disable UI elements
KWatch F40 testing, when that hits Stable it'll be fixed
Kwe use the Fedora package
CYou 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
