You are not logged in.
Pages: 1
Hi,
I created the bootable usb media using following command :
dd bs=4M if=archlinux-2017.10.01-x86_64.iso of=/dev/sdb && sync
In the boot menu of my laptop there is two option is shown corresponding to the usb, one is with UEFI : device name and another is simply the device name. Booting with the non UEFI option works fine.
But If I choose UEFI boot option then a menu shown like the following :
Arch Linux archiso x86_64 UEFI CD
UEFI shell x86_64 v1
UEFI shell x86_64 v2
EFI default bootloader
Reboot Into Firmware Interface
Selecting the first option "Arch Linux archiso x86_64 UEFI CD" leads me to a blank screen with nothing happening afterwards.
How can I boot in UEFI mode?
Please help.
Thanks
Offline
Does your hardware support UEFI? Can you boot into one of the UEFI shells? Have you disabled legacy compatibility in the BIOS? Is secure boot enabled or disabled? What UEFI firmware do you have? Is this a dual boot machine? Does any existing OS boot UEFI?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Does your hardware support UEFI? Can you boot into one of the UEFI shells? Have you disabled legacy compatibility in the BIOS? Is secure boot enabled or disabled? What UEFI firmware do you have? Is this a dual boot machine? Does any existing OS boot UEFI?
I created 2 more bootable usb using dd. Luckily 3rd usb successfully booted into uefi. So as per my experience, 1st usb drive shows uefi boot option but shows blank screen afterwards. 2nd usb device does not even show the uefi option. 3rd iab device successfully boots into uefi. I am currently installing arch linux using tje 3rd device. I have no idea what is going on. Whatever my system is, end result should have been same for three cases as I am using same dd command.
Offline
Arch Linux archiso x86_64 UEFI CD
that "CD" option may be the problem here. When you succesfully boot into the live environment, what's the option you choose?
Offline
rasr11 wrote:Arch Linux archiso x86_64 UEFI CD
that "CD" option may be the problem here. When you succesfully boot into the live environment, what's the option you choose?
I successfully booted using 1st option - "Arch Linux archiso x86_64 UEFI CD"
Offline
I've seen this with some of my USB sticks. I believe it has to do with something done to the USB sticks by something I've used them for prior to putting an ISO on them. Can you see any partition table difference in one that works and one that doesn't? A difference in the partition table type, label, partitions shown?
Simple and Open
Offline
If you rewrite the image with dd 2 or 3 times it should boot properly.
Last edited by Monkey_Mod (2017-12-02 05:59:29)
Offline
If you rewrite the image with dd 2 or 3 times it should boot properly.
Could you elaborate? Why should writing it multiple times make a difference?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Can you see any partition table difference in one that works and one that doesn't? A difference in the partition table type, label, partitions shown?
^ This.
If the USB stick had a GUID partition table before flashing the image then the backup tables may be preventing the ISO image from booting correctly.
If you have a Linux system available (or Win10 with the Linux Subsystem enabled) then this command should clear all traces and allow the Arch ISO image to be transferred correctly:
# sgdisk --zap-all /dev/sdX
Jin, Jîyan, Azadî
Offline
Pages: 1