06.09.2017 04:45, Patrick Shanahan пишет:

* Freek de Kruijf [09-05-17 17:27]:

...

At first I tried to install openSUSE Leap 42.3 with UEFI enabled in the BIOS. I was able to boot from an USB stick and installed it on the disk. However this system when booting only used the Windows boot system, so I never saw GRUB2. The Boot page in BIOS shows a list of devices to boot from, first the USB HDD, second the disk, third Windows Boot System, but with the USB device removed only Windows Boot System is used. Choosing Boot from Disk using the USB stick gives an error message, which I searched for with Google, but I did find, discussions, however not a solution.

After that I went for Legacy BIOS and now I get the GRUB2 boot screen, however without the possibility to boot Windows.

Changing back to UEFI in the BIOS gives me only Windows again. Changing to Legacy in BIOS gives me GRUB2 and only Leap. It is some kind of dual boot, but not the desired one.

Any suggestions?

There are a lot of systems where booting anything beyond (often, preinstalled) Windows is a challenge. The first step is to check whether boot entry is missing or it is ignored by firmware. Post "efibootmgr -v" output from any live Linux (booted in EFI mode), e.g. from openSUSE installation medium. As this post suggests, some Acer systems may require explicitly allowing execution of bootloader, even with Secure Boot disabled: http://p-s.co.nz/wordpress/dual-boot-ubuntu-16-04-on-win-10-acer-aspire-e15/ In the worst case the only solution is to hijack Windows bootloader. It is may also be also possible to switch Windows to legacy boot mode without reinstall.

I was successful using instructions here: https://en.opensuse.org/openSUSE:UEFI

you probably missed creating the openSUSE entry in the efi boot menu, re:

You are aware that openSUSE installer does exactly that, are not you?

# efibootmgr -c -L "openSUSE-alt" -l '\EFI\opensuse\grubx64.efi'

or something similar, mine is "openSUSE" rather than "openSUSE-alt"

and I can select windows from the grub boot menu.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op woensdag 6 september 2017 06:03:06 CEST schreef Andrei Borzenkov:

See also

https://forums.opensuse.org/showthread.php/524383-On-Acer-Aspire-ES-17-Bootl oader-doesn-t-start

https://forums.opensuse.org/showthread.php/523879-unable-to-dual-boot-window s-10-and-opensuse-leap-42-2?p=2817878#post2817878

This made me solve the problem. I now have UEFI (not secure), which boots using GRUB2 with a choice between 42.3 and Windows. I wonder whether it is possible on openSUSE during installation to change the same thing that bcdedit does on Windows. I got this idea after reading the UEFI page on the openSUSE wiki. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

06.09.2017 16:11, Freek de Kruijf пишет:

Op woensdag 6 september 2017 06:03:06 CEST schreef Andrei Borzenkov:

...

See also

https://forums.opensuse.org/showthread.php/524383-On-Acer-Aspire-ES-17-Bootl oader-doesn-t-start

https://forums.opensuse.org/showthread.php/523879-unable-to-dual-boot-window s-10-and-opensuse-leap-42-2?p=2817878#post2817878

This made me solve the problem. I now have UEFI (not secure), which boots using GRUB2 with a choice between 42.3 and Windows.

Could you post "efibootmgr -v" output?

I wonder whether it is possible on openSUSE during installation to change the same thing that bcdedit does on Windows. I got this idea after reading the UEFI page on the openSUSE wiki.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org