Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

Why don't you try and let us know? Archboot installer is always WIP. There is never a fully finished and completely working install script. The more feedback we get, the better Archboot gets.

Archboot built-in grub2-uefi install support is not fully tested by many users since most of them install grub2-uefi manually by following the wiki using chroot (this is true of AIF based Archiso which does not include grub2 support).

ok, so I did a fresh install and erased Windows 7 completely from my harddrive. I did auto format ext4 with gpt support and chose grub2-efi-x86_64. Everything installed fine and grub2 was successfully installed, too. But after a reboot I ended up with a black screen and a blinking cursor on the top left corner. Arch didn't boot up. When hitting F8 on startup I can choose GRUB2 from the menu but that only leads to this black screen.

So I installed Windows 7 again and erased the harddrive completely. But now I still have that GRUB2 entry in the list when I hit F8 or enter the UEFI-Bios of my Asus P8P67. Is there anything I can do to get rid of that entry?

thanksAndreas

It's not that Archboot is doing anything wrong. I get it to create a fully functional 'grub.efi' but ASUS motherboards have their own unique way of booting into UEFI. I haven't found a way to boot directly from the drive I installed Arch Linux to. Basically you have to copy 'grub.efi' to 'shellx64.efi' and put 'shellx64.efi' onto the top level (not a subdirectory) of ANY FAT formatted partition on ANY device. Then boot into the BIOS setup, choose Advanced Mode, select Exit, then choose "Launch EFI shell from filesystem device".

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

KairiTech wrote:

It's not that Archboot is doing anything wrong. I get it to create a fully functional 'grub.efi' but ASUS motherboards have their own unique way of booting into UEFI. I haven't found a way to boot directly from the drive I installed Arch Linux to. Basically you have to copy 'grub.efi' to 'shellx64.efi' and put 'shellx64.efi' onto the top level (not a subdirectory) of ANY FAT formatted partition on ANY device. Then boot into the BIOS setup, choose Advanced Mode, select Exit, then choose "Launch EFI shell from filesystem device".

thanks for this explanation. Unfortunately I'm not that experienced in manually formatting drives and copying files here. And since Windows 7, Fedora 16 and Ubuntu install a pure UEFI system that boots without me having to copy anything maybe one of the next releases of archboot will do the trick anytime soon?(and please don't tell me that Arch might not be the right OS for me if I don't want to get my hands dirty here. I'm using Arch for more than 2 years now and have learned a lot when it comes to configuring my system like: mpd, alpine, awesome-wm, iptables, you name it...) I might as well stick with grub-legacy which does the job for me just fine.

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

Kodama wrote:

KairiTech wrote:

It's not that Archboot is doing anything wrong. I get it to create a fully functional 'grub.efi' but ASUS motherboards have their own unique way of booting into UEFI. I haven't found a way to boot directly from the drive I installed Arch Linux to. Basically you have to copy 'grub.efi' to 'shellx64.efi' and put 'shellx64.efi' onto the top level (not a subdirectory) of ANY FAT formatted partition on ANY device. Then boot into the BIOS setup, choose Advanced Mode, select Exit, then choose "Launch EFI shell from filesystem device".

thanks for this explanation. Unfortunately I'm not that experienced in manually formatting drives and copying files here. And since Windows 7, Fedora 16 and Ubuntu install a pure UEFI system that boots without me having to copy anything maybe one of the next releases of archboot will do the trick anytime soon?(and please don't tell me that Arch might not be the right OS for me if I don't want to get my hands dirty here. I'm using Arch for more than 2 years now and have learned a lot when it comes to configuring my system like: mpd, alpine, awesome-wm, iptables, you name it...) I might as well stick with grub-legacy which does the job for me just fine.

GreetsAndreas

Actually I'm hoping ASUS fixes their boot code to look for /boot/efi/efi/grub/grub.efi (which seems to be the "standard" place to locate it) and boot from there instead of having to rename and relocate it.

Look here for a better explanation of how I got my pure UEFI boot to work.

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

KairiTech wrote:

[

Actually I'm hoping ASUS fixes their boot code to look for /boot/efi/efi/grub/grub.efi (which seems to be the "standard" place to locate it) and boot from there instead of having to rename and relocate it.

Look here for a better explanation of how I got my pure UEFI boot to work.

How will ASUS do this? Through a Bios-Update maybe? (Just updatet my Bios to latest Version 2103 from 2011/12/14 because they promised improved memory compatibility and system stability.

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

Kodama wrote:

KairiTech wrote:

[

Actually I'm hoping ASUS fixes their boot code to look for /boot/efi/efi/grub/grub.efi (which seems to be the "standard" place to locate it) and boot from there instead of having to rename and relocate it.

Look here for a better explanation of how I got my pure UEFI boot to work.

How will ASUS do this? Through a Bios-Update maybe? (Just updatet my Bios to latest Version 2103 from 2011/12/14 because they promised improved memory compatibility and system stability.

I'm hoping so yes but the most recent update for my M5A99X EVO didn't change anything.

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

Hi there, perhaps someone can help me with this.

I have a Asus UX31 ultrabook.

Whenever I try to boot Archiso either from a USB stick or a CD via USB-DVD drive in UEFI mode, I get to the grub selection menu, where I can choose 32/64 bit and which kernel I wish to boot. But as soon as I make a selection, the screen goes blank. It still seems to continue loading though. As the DVD drive or usb stick still blinks, signalling IO activity.

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

KairiTech wrote:

Kodama wrote:

KairiTech wrote:

[

Actually I'm hoping ASUS fixes their boot code to look for /boot/efi/efi/grub/grub.efi (which seems to be the "standard" place to locate it) and boot from there instead of having to rename and relocate it.

Look here for a better explanation of how I got my pure UEFI boot to work.

How will ASUS do this? Through a Bios-Update maybe? (Just updatet my Bios to latest Version 2103 from 2011/12/14 because they promised improved memory compatibility and system stability.

I'm hoping so yes but the most recent update for my M5A99X EVO didn't change anything.

You can look here for a brilliantly simple way of installing a pure UEFI system using archboot. Not only does it show up in my boot menu it also gets set as the default so I can boot directly from the drive I installed Arch to. There is no old fashioned BIOS support though which is just fine with me but I think archboot spends a lot of effort trying to include BIOS support. I was able to modify the original script to include installing on a LUKS encrypted RAID array that I split into two LVM2 volumes. One for root and one for my data. That way I only enter the passphrase once to open the array and not once for root and again for my data.

WARNING!!! After the first boot of the newly installed system when I updated the kernel my /etc/mdadm.conf was repalced by a new default version and I lost my RAID configuration and could not boot after the update.

I had to re-install everything and remember to execute

madam --examine --scan > /etc/mdadm.conf

then update the kernel a second time BEFORE I rebooted so my boot image would contain my RAID configuration or my system would be toast.

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

How report bugs here from the archboot?

ok: in my machine a Celeron 430 @ 1.8GH w 1.5GR sismirage3d graphic, sis900 ethernet (the 2k11-R6 ang lower use the 8136too module for inthernet)the initrd64.img not finish from boot and freeze the sistem, the only way is a hard rebootbut the initrd.img (the i686) work perfectly

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

Jristz wrote:

How report bugs here from the archboot?

ok: in my machine a Celeron 430 @ 1.8GH w 1.5GR sismirage3d graphic, sis900 ethernet (the 2k11-R6 ang lower use the 8136too module for inthernet)the initrd64.img not finish from boot and freeze the sistem, the only way is a hard rebootbut the initrd.img (the i686) work perfectly

If initrd doesn't finish you probably have not enough memory in the machine, 320MB could be enough, 512MB has to boot.Is your celeron already a 64bit CPU?

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

tpowa wrote:

Jristz wrote:

How report bugs here from the archboot?

ok: in my machine a Celeron 430 @ 1.8GH w 1.5GR sismirage3d graphic, sis900 ethernet (the 2k11-R2 and upper use the 8136too module for inthernet)the initrd64.img not finish from boot and freeze the sistem, the only way is a hard rebootbut the initrd.img (the i686) work perfectly

If initrd doesn't finish you probably have not enough memory in the machine, 320MB could be enough, 512MB has to boot.Is your celeron already a 64bit CPU?

I Actualy using a 64Bit Arch Instalation (installed from a archiso>2011-R6)and My sistem have 1.5 Giga-Ram

finily the intrd never finish (I wait 10 minutes, and the cdroom/reader stop after 10 second befor the las dot in initrd64.......) but if i pointin the vmlinux64 alongide the initrd (32bit) can boot (obviously unable to load modules because the diferent in vmlinuz an initrd arch...but boot)

Re: 2011.11-1 archboot "2k11-R7" ISO hybrid image released

Kodama wrote:

Did you chance anything about the grub2 UEFI procedure in ASUS boards, so it'll do the trick this time?

No mobo/vendor specific workarounds currently. Actually the uefi code was just re-organized so that other UEFI bootloaders (apart from grub2) can be added later if needed. This change will be visible only for those who hack into archboot scripts and not to the normal user. Only visible change you might notice is the use of grub-mkstandalone to create (UEFISYS)/efi/arch/grub_standalone.efi . The shellx64.efi workaround is actually a path for the shell binary that the firmware launches. The new iso contains uefi shell from which you can use bcfg https://wiki.archlinux.org/index.php/Un … rface#bcfg to create a boot entry (if efibootmgr'e entry fails) for grubx64.efi .