H@Ichi 
Zthat reads a lot like it isn't endorsed :p not that it doesn't work ^^
EI would take HikariKnight's advice seriously though, they are a maintainer
EIf anything they say contradicts what I suggest, please assume they are correct and I am wrong
Hthe ostree portion of grub does a few things that is not standard and is incompatible with other bootloaders (ex: systemd-boot) and will break
not sure if the ostree part of grub is upstreamed so that it is available in other distros as i have not checked that. but if it is not upstreamed yet then a grub update on a non ostree system can break your boot entry for your ostree system
not sure if the ostree part of grub is upstreamed so that it is available in other distros as i have not checked that. but if it is not upstreamed yet then a grub update on a non ostree system can break your boot entry for your ostree system
Hyoure free to try but dont be surprised if it blows up in your face 
Ayou can always do multiple efi partitions
Zohhh gotcha! makes a ton of sense...
Athats true its very easy for the boot entry to break
Ethis should have been what I put at the end of my suggestions lol
Hthis is what i do, my work laptop has 2 efi partitions, 1 for ostree grub and 1 for windows (windows is there for compatibility for some onsite work for other companies than the main one i work at)
CFor a while I had a triple boot arrangement with Windows and PopOS on the same drive and EFI partition, then a different arrangement with Windows, two copies of Bazzite, and two EFI partitions
CBoth worked, but I wouldn't necessarily recommend either
Zhuh, that makes sense! is there a guide somewhere?
Hif one exists it should be in https://universal-blue.discourse.group/docs
Planting the flag for the next generation Linux desktop
VApologies for replying to a post from months ago, but if fix-screenshare has been removed for the gnome release (it does not function still as of the 25th of February), does that mean the fix it is providing does not function on Gnome at all?
VIf so, I wish that could have been better communicated, as it's a rather critical omission that people should be aware of before installing the Gnome version of Bazzite.
VIt is not warned in the documentation anywhere that the command doesn't function in Gnome. I think it's rather unfair to the end user to have a particular command not function without explanation, forcing them to track down a single discord post from months ago to be aware of this.
VIf my tone conveys any rudeness, I apologize. I am frustrated.
©The UEFI-BIOS only recognizes the first ESP on a drive, but you can have more than one drive with each their own ESP...
Adunno about that, probably varies per manufacturer
Ai think for the legion go doing multiple efi partitions works
©Thats what i understood from the UEFI specs...
Hrather the spec specifies it should only aknowledge the first ESP
most uefi implementations dont follow that spec
most uefi implementations dont follow that spec
©if they don't follow specs, nothing to be said ofcourse 
Aall i know is that I have 1 partition, the legion go forgets my efi entries exist when I update the bios
Abut everyone that did 2 is ok
©When you update your BIOS ofcourse all UEFI-VARS in the CMOS also get deleted...thats logical...
Ano
Awhen you have a potato bios that happens
Aproper bios also have a built in secure boot key tool
Aso nice
Aand bios update from usb drive
©
those keys are totally different topic...Athe spec lists the minimum
©Anyhow....stay safe and use 1 ESP per drive... 
Ayeah well heres the thing: the legion go only has one drive
Aand forgets the efi entries
Aso you need 2 efi partitions
©then try dual booting on your own risk...as it is not supported...like they say...
Aalso, unlike a proper bios it doesnt let you pick an efi image to boot from
Aso you have to do the live cd game
©@antheas forgetting efi entries....is what in your definition?
The boot menu entries you see or the files inside the ESP?
The boot menu entries you see or the files inside the ESP?
Asure so heres the thing about the legion go
Ait only automatically picks up the xboot64 entry on an efi partition
Ayou have to add the others with efibootmgr
Aand it forgets them every bios update
Aso you can only have 1 image per efi partition
©Thats most likely because your device doesnt use secureboot
Ai use secure boot