https://bugzilla.novell.com/show_bug.cgi?id=855679 https://bugzilla.novell.com/show_bug.cgi?id=855679#c0 Summary: Copy bootloader .efi image to /EFI/BOOT/BOOTX64.EFI Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: moonfire.bogdan@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Some systems (like my HP Probook 4540s) don't use NVRAM entries for UEFI bootloaders, instead they search for /EFI/BOOT/BOOTX64.EFI. YaST does not update this file when the bootloader is installed or updated, it only relies on /EFI/opensuse/grubx64.efi and an entry in the NVRAM. So for these systems, if BOOTX64.EFI is not found, an error will be displayed on power up that no image was found, or if the file was created by a previous OS, it will try to load that OS's bootloader. After creating /EFI/opensuse and copying all the necessary files inside, YaST needs to create a copy of grubx64.efi (or shim.efi for secureboot) to /EFI/BOOT/BOOTX64.EFI. Reproducible: Always Steps to Reproduce: 1. Install openSUSE on UEFI based machine that ignores NVRAM entries. Actual Results: The system won't boot automatically, you need to manually specify what .efi file to use (here /EFI/opensuse/grubx64.efi) Expected Results: GRUB2 should load automatically on powerup. My laptop runs in UEFI mode, openSUSE was installed using /boot/efi, root, swap and /home partitions. GRUB-EFI was installed successfully and /EFI/opensuse/grubx64.efi was created. Secure boot and Fast boot are disabled. Manually booting the .efi file shows the GRUB menu and successfully loads the system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.