You are not logged in.
i mounted the iso and copied it to a fat32 formatted usb
when i boot i chose uefi: usb disk
then i get an error message : "No loader found. Configuration files in \loader\entries\*.conf are needed."
i have a SSD formatted with GPT and a UEFI motherboard (Latest BIOS version)
Last edited by Heema (2012-10-31 20:51:04)
Offline
Offline
tried "Just replace older [USB]/EFI/boot/bootx64.efi with /usr/lib/gummiboot/gummibootx64.efi of gummiboot-efi-7 pkg."
it didnt work
Offline
sure, because replace with the same file, you have already version 7.
Offline
sure, because replace with the same file, you have already version 7.
Yes, Archboot iso already has gummiboot-efi-7, I meant that for Archiso release 2012.10.06 which has gummiboot-efi-6. Even with gummiboot v7 the problem does not seem to be solved. The issue seems to be present in all Asus machines.
Can you guys try refind-efi ? If that works atleast we will know if the problem is specific to gummiboot.
Offline
Thanks for the suggestions, btw my motherboard is a gigabyte GA-Z77X-UD5H-WB
i tried getting the file "\usr\lib\refind\refindx64.efi" from "refind-efi-0.4.6-1-any.pkg.tar.xz" and renaming it and replacing it with[USB]/EFI/boot/bootx64.efi
it booted fine but it only saw my windows efi entries there wasn't an entry for the usb arch install
P.S: i just build my new pc and installed windows first then will dual boot with arch ( windows is just for playing games )
Last edited by Heema (2012-10-31 16:17:50)
Offline
Finally got it working, thanks to https://bugs.archlinux.org/task/31894
here is how i did it:
- download refind-efi-0.4.6-1-any.pkg.tar.xz from https://www.archlinux.org/packages/extr … /download/
- Extract the file "\usr\lib\refind\refindx64.efi" and renaming it to bootx64.efi
- Replacing it with [USB]/EFI/boot/bootx64.efi
- Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
- Add this to it
textonly
scanfor manual
menuentry Arch {
loader \boot\vmlinuz_x86_64
initrd \boot\initramfs_x86_64.img
options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
}
Offline
Finally got it working, thanks to https://bugs.archlinux.org/task/31894
here is how i did it:
- download refind-efi-0.4.6-1-any.pkg.tar.xz from https://www.archlinux.org/packages/extr … /download/
- Extract the file "\usr\lib\refind\refindx64.efi" and renaming it to bootx64.efi
- Replacing it with [USB]/EFI/boot/bootx64.efi
- Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
- Add this to ittextonly scanfor manual menuentry Arch { loader \boot\vmlinuz_x86_64 initrd \boot\initramfs_x86_64.img options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64" }
I'm trying to do the same thing, but I'm stuck.
As I understand the above, what you want to do is:
Replace the OLD file "bootx64.efi" in the directory "[USB]/EFI/boot/" with the NEW file "bootx64.efi" that you just extracted and renamed from "\usr\lib\refind\refindx64.efi".
Then make a NEW file named "refind.conf" in "[USB]/EFI/boot/" containing the listed stuff.
My sticking point is that the USB drive is read-only, and "cp" and "mv" and so forth refuse to change any files. I'm probably missing something obvious to experienced Linux hackers, but I'm very new at such hacking. So I'd appreciate any advice on how to move forward.
Thanks!
Alan
Offline
My sticking point is that the USB drive is read-only, and "cp" and "mv" and so forth refuse to change any files. I'm probably missing something obvious to experienced Linux hackers, but I'm very new at such hacking. So I'd appreciate any advice on how to move forward.
Chances are your USB drive is not mounted read-only, but that you need root access to write to it. I don't know what sort of system you're using to access the drive, but logging in as root or using "sudo" before each command (as in "sudo nano /boot/efi/EFI/boot/refind.conf" to edit the file with nano) should work.
If the drive really is mounted read-only, you should be able to fix it by using an explicit "rw" mount option, as in:
mount -o remount,rw /dev/sda1 /boot/efi
Omit the "remount," part if it's not currently mounted, and change the mount point as necessary.
Finally, you can do this from another OS, if you're more comfortable with something else.
Offline
Chances are your USB drive is not mounted read-only, but that you need root access to write to it. I don't know what sort of system you're using to access the drive, but logging in as root or using "sudo" before each command (as in "sudo nano /boot/efi/EFI/boot/refind.conf" to edit the file with nano) should work.
I'm running things in a recent Fedora 17 installation, mostly as root.
If the drive really is mounted read-only, you should be able to fix it by using an explicit "rw" mount option, as in:
mount -o remount,rw /dev/sda1 /boot/efi
Omit the "remount," part if it's not currently mounted, and change the mount point as necessary.
Turns out it WAS mounted as read-only. I had to repartition the whole stick as FAT32, then make a FAT32 filesystem on it. I had used it for other things prior to this. Now I can write to it.
Earlier today someone posted his method of getting stuff to work with a UEFI bios, and I'm working my way through it. I've learned quite a bit already. I'm stuck at one point, though, and will soon post on that thread ( https://bbs.archlinux.org/viewtopic.php?id=151773 ) what I've done so far.
Finally, you can do this from another OS, if you're more comfortable with something else.
You mean like I've been doing with Fedora? If not something like Fedora, what did you have in mind?
Thanks for your help!
Alan
Offline
Finally, you can do this from another OS, if you're more comfortable with something else.
You mean like I've been doing with Fedora? If not something like Fedora, what did you have in mind?
Windows, OS X, OS/2, DOS, BeOS, FreeBSD, NetBSD, OpenBSD, etc.
Offline
AlanF00 wrote:Finally, you can do this from another OS, if you're more comfortable with something else.
You mean like I've been doing with Fedora? If not something like Fedora, what did you have in mind?
Windows, OS X, OS/2, DOS, BeOS, FreeBSD, NetBSD, OpenBSD, etc.
Ah, I see. Well, the computer on which I'm running Fedora and trying to install ArchLinux is dedicated to playing with Linux and has no other OS's. The computer on which I'm typing this post is running Windows 7.
Both of these computers have new ASUS UEFI motherboards and Intel processors, so to move forward with anything but standard distros I'm going to have to thoroughly understand UEFI installation issues. My main goal here is not to install some Linux distro, but to come to know what I'm doing.
Eventually I'd like to become knowledgeable enough to run ONLY Linux on my machines.
Alan
Offline