You are not logged in.
In my Acer laptop I have Windows 10 installed on /dev/sda4 and the ESP partition is /dev/sda2.
As described in the Beginner's Guide I installed Arch Linux on a newly created partition /dev/sda5 and swap /dev/sda6 with the Windows 10 created ESP /dev/sda2 as /boot.
As the bootloader I chose systemd-boot which is recommended by the guide if the motherboard is UEFI (which is)
I configured the /boot/loader/loader.conf as follows;
timeout 10
default arch
Created an entry for arch.conf at /boot/loader/entries/arch.conf as follows;
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sda5 rw
But after rebooting Windows 10 boots by default. Couldn't even see the bootloader menu. Also no option to select Linux Boot Loader in boot options. What am I doing wrong?
Note: Both fastboot(Windows 10) and secureboot (UEFI) are off.
Last edited by fmir864 (2016-02-24 17:02:53)
Offline
The firmware is probably loading the Windows bootmanager automatically.
Check the boot order with
#efibootmgr -v
Change the boot order with:
# efibootmgr -o xxxx,yyyy,zzzz
If the "Linux Boot Manager" (or so) is already first in the list, change the boot order from Windows as per https://wiki.archlinux.org/index.php/Un … boot_order
The command would be:
bcdedit /set {bootmgr} path \EFI\systemd\systemd-bootx64.efi
EDIT:
@yoshiserry: re-install systemd-boot, see https://wiki.archlinux.org/index.php/Sy … t#EFI_boot
Last edited by Head_on_a_Stick (2016-02-23 08:25:29)
Jin, Jîyan, Azadî
Offline
Moderator -- Split thread hijack to dustbin https://bbs.archlinux.org/viewtopic.php?id=209278
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I have seen weird UEFI implementations. On a Packard Bell laptop (I think they are the same as ACER) the UEFI automatically detect the Windows boot manager and put it first. To boot something other by default, you have to go in the firmware setting and select the hard disk as default boot device instead of Windows. As I understand booting from the hard disk really mean "respect the normal UEFI boot variables". I have found a lot of problems on the internet with UEFI's "that love Windows". One other trick is to rename the Windows boot manager as well as bootx64.efi (a copy of the Windows boot manager). You can still load Windows by launching the renamed file with your boot loader (Windows shouldn't be affected).
Last edited by olive (2016-02-23 21:26:30)
Offline
OK, I have tried the suggestion of @Head_on_a_Stick.
#efibootmgr -v
Returns all my boot options. It has Linux boot manager in the list but boot order didn't specify any thing about it.
So, I manually edited the boot order by
# efibootmgr -o 1003,1001,2001 and something.
But, the problem is same. Boot order is reverted back after an reboot.
So I tried the other suggestion.
bcdedit /enum firmware
Contains my Linux boot manager. So I ran
bcdedit /set {bootmgr} path \EFI\systemd\systemd-bootx64.efi
Thanks @Head_on_a_Stick this did solve my problem. Now I have a working dual boot of Windows 10 and Arch Linux
Offline
is it [Solved] ?
do it good first, it will be faster than do it twice the saint
Offline
Yes [Solved]..
Offline
Please mark you post solved then by prepending [Solved] to the post title
Offline
@phw Done.
Offline
Thanks
following this topic I've solved the same issue
the grub is put in last place and using efibootmgr the order is not changed at reboot
instead with bcdedit from windows all is ok
bye
Offline