You are not logged in.
I've installed Arch on my system. The partition table looks like this:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 96M 0 part /boot
├─sda2 8:2 0 100G 0 part /
├─sda3 8:3 0 11.4G 0 part [SWAP]
├─sda4 8:4 0 100G 0 part
└─sda5 8:5 0 720G 0 part
sr0 11:0 1 1024M 0 rom
sda1 is the EFI partition
sda2 is the parition on which I've installed Arch
sda3 is swap space
sda4 is the parition on which I intend to install Windows
sda5 is my personal data partition.
I'm not quite familiar with the whole UEFI thing so I followed a tutorial which asked me to mount the EFI partition at /mnt/boot during installation. My system boots just right.
I wanted to know if it is the right thing to do.
Also, how do I go about installing Windows 10 now?
In my BIOS, secure boot is enabled by default so I had to create an entry for Arch in the boot order.
My system boots from that EFI entry for arch, not from the hard drive.
Will installing Windows interfere with this EFI entry of Arch?
The final result I want is a Windows entry added to the GRUB menu which shows up after I boot to that EFI entry for Arch.
[SOLVED]: It is automatically taken care of, Grub is not disturbed.
Last edited by anukul (2016-04-27 04:14:04)
Offline
In my BIOS, secure boot is enabled by default so I had to create an entry for Arch in the boot order.
My system boots from that EFI entry for arch, not from the hard drive.
This makes no sense at all. I'm not sure what you're trying to say here.
Will installing Windows interfere with this EFI entry of Arch?
It will likely set itself as the default loader, at least. It may even remove the NVRAM entry for Arch. If that happens, you'll need to use an install disk to get back into Arch and set up the bootloader again.
Offline
I'm not quite familiar with the whole UEFI thing so I followed a tutorial which asked me to mount the EFI partition at /mnt/boot during installation. My system boots just right.
I wanted to know if it is the right thing to do.
Yes, this is the recommended approach as outlined in the Beginner's Guide.
It will likely set itself as the default loader, at least. It may even remove the NVRAM entry for Arch. If that happens, you'll need to use an install disk to get back into Arch and set up the bootloader again.
Alternatively, run this command from your Windows system with administrator permissions:
bcdedit /set {bootmgr} path \EFI\BOOT\BOOTx64.EFIFor 32-bit systems, replace "BOOTX64.EFI" with "BOOTIA32.EFI"
https://wiki.archlinux.org/index.php/Un … boot_order
This presumes that your bootloader has installed the .efi loader to the default loader location (this is true for both GRUB and systemd-boot).
EDIT: Actually, I think GRUB only does that if you specify the "--removable" flag in the `grub-install` command.
For GRUB, try:
bcdedit /set {bootmgr} path \EFI\arch\grub64.efiLast edited by Head_on_a_Stick (2016-04-24 14:44:59)
Jin, Jîyan, Azadî
Offline
anukul wrote:In my BIOS, secure boot is enabled by default so I had to create an entry for Arch in the boot order.
My system boots from that EFI entry for arch, not from the hard drive.This makes no sense at all. I'm not sure what you're trying to say here.
anukul wrote:Will installing Windows interfere with this EFI entry of Arch?
It will likely set itself as the default loader, at least. It may even remove the NVRAM entry for Arch. If that happens, you'll need to use an install disk to get back into Arch and set up the bootloader again.
See, there is an option to boot from the hard drive, right? It doesn't boot Arch through that.
I had to create a separate option for it by going under the Secure Boot section in the BIOS and choosing some "grub*.efi" file for Arch which was created after I installed the bootloader. I'm not sure if this is the standard procedure on all laptops, but atleast on my Acer laptop, it is.
Offline
Post
$ efibootmgr -vdo it good first, it will be faster than do it twice the saint ![]()
Offline
See, there is an option to boot from the hard drive, right? It doesn't boot Arch through that.
I had to create a separate option for it by going under the Secure Boot section in the BIOS and choosing some "grub*.efi" file for Arch which was created after I installed the bootloader. I'm not sure if this is the standard procedure on all laptops, but atleast on my Acer laptop, it is.
OK, I see what you're saying now. You're still booting from the hard drive, just not from the default loader of the hard drive. Yes, this is the normal way, but it's usually done during the installation of the bootloader.
Offline
Post
$ efibootmgr -v
Boot0000* Arch HD(1,GPT,e0f121d3-c336-4c9b-a46b-aeb59a2348dc,0x800,0x30000)/File(\EFI\Arch\grubx64.efi)
Boot0001* USB HDD: KingstonDataTraveler G3 PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(3,0)/HD(1,MBR,0x62,0xac,0x14000)RC
Boot0002* HDD: WDC WD10JPVX-22JC3T0 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,e0f121d3-c336-4c9b-a46b-aeb59a2348dc,0x800,0x30000)RC
Boot0003* GRUB PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,e0f121d3-c336-4c9b-a46b-aeb59a2348dc,0x800,0x30000)/File(\grub\x86_64-efi\grub.efi)A01 ..
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RCMy laptop shipped with Linpus Linux but I deleted its partition and the EFI partition (using `cfdisk`) while installing Arch. However, it still boots to Linpus Linux's splash screen in the default loader (using the boot entry of the HDD), so I tried one more time to format the EFI partition and install grub again (due to which you might be seeing the two different entries `Arch` and `GRUB`).
Can you guys please tell me how to clean the EFI partition, possibly reset it in some way such that it only contains information of the current Arch install and nothing else?
I see Linpus's entry in BOOTX64.conf also.
Also, which .efi file should I use to boot to Arch? There are several, and more than one seems to work.
Last edited by anukul (2016-04-24 15:36:29)
Offline
My laptop shipped with Linpus Linux but I deleted its partition and the EFI partition (using `cfdisk`) while installing Arch. However, it still boots to Linpus Linux's splash screen [...] Can you guys please tell me how to clean the EFI partition, possibly reset it in some way such that it only contains information of the current Arch install and nothing else?
There are two separate factors here: the contents of the ESP (which holds the bootloader binaries and configuration files) and the motherboard NVRAM entries (seen in the `efibootmgr` output) -- the latter control which bootloader binary is started.
You have wiped the Linpus bootloader but the NVRAM entry is still there, I think it is Boot0003
So try:
# efibootmgr -b 0003 -Bto delete that NVRAM entry.
which .efi file should I use to boot to Arch? There are several, and more than one seems to work.
If you are booting with GRUB, you should use $ESP/EFI/Arch/grub64.efi
EDIT: Also, that is not the *full* output of `efibootmgr -v`
Please read https://bbs.archlinux.org/viewtopic.php?id=57855
Last edited by Head_on_a_Stick (2016-04-24 15:37:29)
Jin, Jîyan, Azadî
Offline
Okay, I've removed the junk entries from efibootmgr, but booting from the HDD entry still brings me to Linpus's screen. If I proceed, however, it gives me 'Error 15: File not found`.
As for the output, I think it is complete. Here is a screenshot: http://imgur.com/z8xm62G
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0002,2001,2002,2003
Boot0001* Arch PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,e0f121d3-c336-4c9b-a46b-aeb59a2348dc,0x800,0x30000)/File(\EFI\Arch\grubx64.efi)A01 ..
Boot0002* HDD: WDC WD10JPVX-22JC3T0 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,e0f121d3-c336-4c9b-a46b-aeb59a2348dc,0x800,0x30000)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RCOffline
From your booted Arch system, please post the full output of:
# bootctlJin, Jîyan, Azadî
Offline
Failed to read EFI variable LoaderDevicePartUUID: No such file or directory
System:
Firmware: n/a (n/a)
Secure Boot: disabled
Setup Mode: setup
Loader:
Product: n/a
Partition: n/a
File: └─n/a
Boot Loader Binaries:
ESP: /dev/disk/by-partuuid/e0f121d3-c336-4c9b-a46b-aeb59a2348dc
systemd-boot not installed in ESP.
File: └─/EFI/Boot/BOOTIA32.efi
File: └─/EFI/Boot/BOOTX64.efi
Boot Loader Entries in EFI Variables:
Title: Arch
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/e0f121d3-c336-4c9b-a46b-aeb59a2348dc
File: └─/EFI/Arch/grubx64.efiOffline
Is "CSM" or "Legacy" mode disabled in your firmware options?
Jin, Jîyan, Azadî
Offline
IIRC there were two options: UEFI and Legacy. I've chosen UEFI. It was also the default setting.
Offline
If grub was chosen, then try to chroot into the installation and repeat the grub installation once the ESP is mounted.
do it good first, it will be faster than do it twice the saint ![]()
Offline
Thanks, it was pretty straightforward. A Windows entry was created in the GRUB by itself and another option to boot directly to Windows in the BIOS.
Offline
[Solved] ? ![]()
do it good first, it will be faster than do it twice the saint ![]()
Offline