Dual boot OpenSuse 12.2 with Windows 8 on UEFI: Boot Menu for Opensuse not created

English Install/Boot/Login
1

I installed old OpenSuse 12.2 from the install DVD I was having. I had planned to upgrade it to 13.1 later- after installation. :wink:
It booted in **ELILO **and not GRUB
I had disabled Secure-Boot beforehand.
During installation in the partitioning menu I created separate ext4 partition and mounted it as '/’ and created swap partition.
For boot/efi I selected existing ‘Windows EFI Partition’ "without formatting it". It showed error for not formatting **boot/efi **which I ignored.

However it didn’t create entry to boot into OpenSuse.

I managed to boot into OpenSuse by pressing F12 (select boot device) option. It showed entry for OpenSuse present on hard drive. I’m posting through opensuse which got installed.

My system Acer V3-571G Laptop

2

The same thing happened when I installed Ubuntu 13.04. But then I had not disabled SecureBoot, which I disabled later and used Boot-Repair to solve the problem.

3

Are you asking a question or simply provide information?

Why not 12.3?

I had planned to upgrade it to 13.1 later- after installation.

Jumping over release during update is usually not recommended.

4

ok. Before upgrading is there a way to add openSUSE to boot menu

5

Could you show output of “efibootmgr -v” in tags code?

6

[size=3]akash@linux-iioq:~> sudo /usr/sbin/efibootmgr -v BootCurrent: 0004 Timeout: 0 seconds BootOrder: 0002,0004,0003,0001,0000 Boot0000* ATAPI CDROM: HL-DT-ST DVDRAM GT70N ACPI(a0341d0,0)PCI(1f,2)03120a00020000000000CD-ROM(1,112ca,21b5ce)RC Boot0001* HDD: HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC Boot0002* Windows Boot Manager HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}…6… Boot0003* HDD: HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC Boot0004* opensuse HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\opensuse\grubx64.efi)
[/size]

7 
akash@linux-iioq:~> sudo /usr/sbin/efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0004,0003,0001,0000
Boot0000* ATAPI CDROM: HL-DT-ST DVDRAM GT70N    ACPI(a0341d0,0)PCI(1f,2)03120a00020000000000CD-ROM(1,112ca,21b5ce)RC
Boot0001* HDD:  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC
Boot0002* Windows Boot Manager  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................
Boot0003* HDD:  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC
Boot0004* opensuse      HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\opensuse\grubx64.efi)
8 
akash@linux-iioq:~> sudo /usr/sbin/efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0004,0003,0001,0000
Boot0000* ATAPI CDROM: HL-DT-ST DVDRAM GT70N    ACPI(a0341d0,0)PCI(1f,2)03120a00020000000000CD-ROM(1,112ca,21b5ce)RC
Boot0001* HDD:  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC
Boot0002* Windows Boot Manager  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................
Boot0003* HDD:  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC
Boot0004* opensuse      HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\opensuse\grubx64.efi)

Looks more clear

9

Either Windows is hard coded for booting your system, or your system is using what is in “/boot/efi/EFI/Boot” for booting, and ignoring the NVRAM settings. Or at least it looks as if it is one of those.

In Windows, try:


bcdedit /set {bootmgr} path \EFI\opensuse\grubx64.efi

You will need to run that command from an Administrator command prompt.

Post back about what happens. If that does not help, then we can try something else.

10

Either Windows is hard coded for booting your system, or your system is using what is in “/boot/efi/EFI/Boot” for booting, and ignoring the NVRAM settings. Or at least it looks as if it is one of those.

In Windows, try:

bcdedit /set {bootmgr} path \EFI\opensuse\grubx64.efi

You will need to run that command from an Administrator command prompt.

By editing BCD \EFI\opensuse\grubx64.efi would load, so would windows boot?

vish_99 The same thing happened when I installed Ubuntu 13.04. But then I had not disabled SecureBoot, which I disabled later and used Boot-Repair to solve the problem.

I didn’t had to edit bcd then. And I hope so Boot-Repair will not work for repairing openSUSE.

I don’t know how GRUB works. Can you explain how GRUB will load windows bootloader

11

On EFI grub2 will simply launch bootmgfw.efi as EFI application.

12

lol!It works