![]() ![]() ![]() Installing openSUSE 12.3 did result with a new option in NVRAM, but, trying to add or edit options using efibootmgr either on my fedora 17 install or the new openSUSE install fails. I also have an ASUS UEFI bios, and, I'm having the same problems with efibootmgr that you are. Strangely my /sys/firmware/efi/ folder do have 'efivars' and 'vars' subfolders even before modprobe and they contain non-empty 'files'. Output of 'lsmod' still shows the module is not being loaded afterwards. But this command also does not work either. Even a simple reorder instruction also does not work, such as:Ĭhecking related articles on archwiki, efibootmgr's manpage and README, they all say I need to 'modprobe efivars' first. I have tried the commands with combination of other options as well, but to no avail. Output of 'efibootmgr -v' remains unchanged. However, it does not seem to have any effect at all. # efibootmgr -c -d /dev/sda -p 1 -L "clover" -l '\EFI\CLOVER\CLOVERX64.efi' So, I figure I have to use the 'efibootmgr' command to tell the EFI boot manager that I have a new bootloader. I was originally hoping my Asus UEFI BIOS firmware would then automatically detect the new bootloader and list it as a new boot option when I press F8 during POST, but it does not work that way. I have manually copied the required Clover folder into ~]# ls /boot/efi/EFI/ At the moment, it only has 'fedora' Grub2 bootloader. I have ESP (EFI System Partition) already being created by F19 Anaconda installer on my /dev/sda1. I want to try Clover EFI bootloader to multiboot my PC into a Mac partition. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |