can't boot after install, UEFI, GPT

Just got an Acer V3-575T-7008. Windows 10 is installed UEFI.
Installed leap 42.1 from DVD.
I thought I needed a separate EFI partition ( as opposed to the /dev/sda1 that came with windows 10 preconfigured computer)
So I created a FAT partition( /dev/sda8) and chose to mount /boot/efi there. I now understand EFI a “little” better I think.
So I moved /dev/sda8/EFI/boot to /dev/sda1/EFI/boot and /dev/sda8/EFI/opensuse to /dev/sda1/EFI/opensuse
Thought maybe I needed to set something in /etc/fstab but there is no entry for /boot/efi
restarted and it still goes into windows.

Using Installation Disk for Rescue System.


gdisk /dev/sda -l

/dev/sda1   efi system partition
/dev/sda2   Microsoft reserved part
/dev/sda3   Basic data partition
/dev/sda4   Basic data partition (recovery)
/dev/sda5   primary   (/swap)
/dev/sda6   primary   (/root)
/dev/sda7   primary    (/home)
/dev/sda8   primary


What do I need to do to get my install working? Thank you for your time, as always.

You only needed to move the “opensuse” directory. It was not necessary to also move the “boot” directory, though that should not hurt.

There should be an entry for “/boot/efi” in “/etc/fstab”, though it is not essential for booting if everything else is setup correctly. But if there is no entry for “/boot/efi”, then I worry that things are not setup correctly. If there is an entry, but it’s for the wrong EFI partition, then that’s not a serious problem. You can fix that later.

Boot your 13.2 install media to UEFI mode, and get a root command line.

Run the command:

# efibootmgr -v

If that lists an entry for “opensuse”, then you need to delete it (so you can add a new entry).

If the entry says something like

0002 opensuse some-string-that-may-be-hard-to-understand

then remove that with:

# efibootmgr -b 0002 -B

Now add a new entry, using:

# efibootmgr -c -d /dev/sda -p 1 -l "/EFI/opensuse/grubx64.efi" -L opensuse

Hmm, before running that command, make sure that the file “grubx64.efi” exists in that “opensuse” directory in the EFI partition.

That should give you a choice to boot opensuse. Turn off secure-boot in the BIOS before you try.

If you want to use secure-boot, then post back in this thread. It requires a slightly different setup, so it will be easier to do that once you have your system up and running.

And let us know how this works out.

For that last command that I gave, it would be better to use:

# efibootmgr -c -d /dev/sda -p 1 -l '\EFI\opensuse\grubx64.efi' -L opensuse

The arch linux documentation says that it will work either way. But I have only ever tried it with backslashes, so better to play it safe.

That change affects only one parameter of the command.

You could start with telling what does not work.

@nrickert I did like you asked, I deleted the first entry 0001 that was set for hd(1,8…)File(\EFI\opensuse\grubx64.efi)RC
I then created the entry like you said with the back slashes.
it changes the boot order to 0000 as the first, the entry I just created.

In BIOS I only have the option of Legacy or UEFI
if I choose UEFI it is set for secure boot with no option to change that ??

Booting from UEFI it just starts Windows even after our changes
Booting into Rescue and issuing


efibootmgr -v

shows that the changes did not persist. The First entry 0001 is back and the entry 0000 that I created is not there.

Booting from Legacy just waits and waits.

Well, it could be related to using secure boot as well; grubx64.efi is not signed. Check if you have \EFI\opensuse\shim.efi, if yes, try the same command but specifying this path.

I got it to boot. I hacked at it by moving /dev/sda1 /EFI/Microsoft/Boot/Bootmgfw.efi up a folder and moving and renaming the /EFI/opensuse/grubx64.efi to /EFI/Microsoft/Boot/Bootmgfw.efi

Thanks for your help…

Now on to the wireless card

Hi
Your better off to pop the file into the EFI Boot directory as bootx64.efi which is what I did for my MacBook and create an efi entry based on that (it also helps if the is a default disk entry that always comes first in the nvram…

I haven’t checked if efibootmgr persists after doing this, but I thought people should know:

in order to turn uefi on but secure boot off I had to go into BIOS and go to the security tab at the top, enter a bios password, then items became changeable on that security tab
as well as the secure boot on the boot tab. Found this out after installing latest kernel from Kernel:/stable/ (4.6). It’s not signed, so I needed secure boot off.

and this isn’t boot related but the wireless card is working from these instructions:
Post #22 is what I followed:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1520343

It is probably signed, but with a different key that secure-boot does not recognize.

In any case, you can use MokManager and related software to install your own key and sign the kernel yourself. Or just leave secure-boot off for now.