Edik Landaveri wrote: > Installing a desktop environment & unistalling other shouldn't have had to screw up your boot sector. I think what you did is inadvertdly changed your bios settings. If it was working before and after that no. Do you remember having played with the BIOS settings? You can disable EFI on the BIOS if you wish. Maybe that's how was installed and then you changed. Once in a while I have a similar issue which I pinpointed to be the same, so I go back && change it to defaults & it works. UEFI contains its own bootloader that is separate from the hard drive. This a "feature" of UEFI. On the old BIOS and MBR platform the BIOS would read the MBR and automatically boot a partition with the boot flag. On the new UEFI and GPT platform it will look for a default EFI loader or a custom EFI loader that has been registered into the EFI boot manager. It seems on UEFI updates (a.k.a. BIOS updates) the boot manager is wiped out. Fedora uses a custom-named EFI loader (grub.efi instead of bootx64.efi) so after a UEFI update it cannot find any OS to boot. Here's the differences between BIOS and UEFI: BIOS -> MBR -> GRUB UEFI -> EFI Boot Manager -> EFI Loader -> GRUB The EFI boot manager is not something that UEFI interfaces allow users to adjust so this is not something I can modify in the UEFI settings. The only way to configure the EFI boot manager is through the "efibootmgr" utility. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
