Lost in boot, I think no EFI

English Install/Boot/Login
#21

In Yast, this is my disk config :

http://i.imgur.com/SdzjgKt.png
and the boot option :

http://i.imgur.com/PYcvLJJ.png

I really don’t know what to do, it’s frustrating.

#22

Hi
But what is you BIOS set to, UEFI or Legacy boot?

You have no efi entry for openSUSE in the last output… plus your slashes are in the wrong direction…


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

It’s in EFI, I’ve disabled fastboot.

What do you mean I’ve no EFI entry, sda6 is not an EFI partition ?

I’ve tried with the slash in both direction, it dosn’t boot…

#24 
linux-1urk:~ # efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0001* UEFI: SanDisk Cruzer Slice 1.26       PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(3,0)/HD(1,MBR,0x1b681c50,0x107c,0x1e84)..BO

One thing I notice is that my evibootmgr dosn’t “survive” a boot. Is it normal ? How can the system know where to boot if the variable is not present at boot ?

#25

No. But so far you did not show any evidence that “efibootmgr” is effective even before reboot. Copy-paste both “efibootmgr” command you used to set menu entry as well as “efibootmgr -v” after that and before reboot and their complete output.

#26

it is effective before boot, I’ve checked it many time before :

linux-1urk:~ # efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0001* UEFI: SanDisk Cruzer Slice 1.26       PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(3,0)/HD(1,MBR,0x1b681c50,0x107c,0x1e84)..BO
linux-1urk:~ # efibootmgr -c -d /dev/sda -p 6 -L "opensuse" -l "\\EFI\\opensuse\\grubx64.efi"
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0001* UEFI: SanDisk Cruzer Slice 1.26
Boot0000* opensuse
linux-1urk:~ # 
linux-1urk:~ # efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* opensuse      HD(6,GPT,b52565dc-fa51-43ff-832b-d77d2692b09b,0xc0fc000,0x59000)/File(\EFI\opensuse\grubx64.efi)
Boot0001* UEFI: SanDisk Cruzer Slice 1.26       PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(3,0)/HD(1,MBR,0x1b681c50,0x107c,0x1e84)..BO
linux-1urk:~ #

Now I’ll reboot (and boot via the USB key)and just enter efibootmgr -v.

edit : SanDisk is the USB stick I use.

#27

After reboot, I’ve this :

linux-1urk:~ # efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0001* UEFI: SanDisk Cruzer Slice 1.26       PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(4,0)/HD(1,MBR,0x1b681c50,0x107c,0x1e84)..BO

So yes, the command doesn’t survive the boot.

I’m searching the web where exactly this command try to write the boot order.

#28

I’m afraid this is something your firmware does and is outside of openSUSE control. What manufacturer and model of your system? Did you check if there is BIOS update?

Do you have \EFI\Microsoft\Boot\bootmgfw.efi file? Could you try to enter path to this file and check whether it sticks after reboot? Name it Windows or similar.

#29

I see your point. I don’t have Windows EFI anymore, it have been overwritten at some point.

It so frustrating that something that was working before just doesn’t work after a fresh install.

I’m not saying it’s not me the problem,but I understand the problem now, EFI, CSM, SecureBoot, but it just doesn’t work…

#30

OK, guys, I rage quit.

I’ve enough of this, I’ll start from the beginning. It’s just make no sense at all. Even to boot from the USB stick, sometime it work sometime it doesn’t not work. I change NOTHING, I try to boot, it doesn’t work, I reboot, it work.

I’ll try to boot on windows, erase all the linux related stuff and reinstall 42.3 from here.

Thanks a LOT for your help, I know it’s hard to help people online when you don’t have all the information !