You are not logged in.
Does anyone else get a different md5sum than the one in md5sums.txt?
I tried redownloading the file, and also from a different mirror. But keep getting the same different md5sum: edf1dafc993e7200f34b178b51f26f89.
Offline
yes, i`ve the same md5...damaged iso on ftp
Last edited by KFe (2011-10-12 18:34:07)
Offline
Ack.
edf1dafc993e7200f34b178b51f26f89 <- actual .iso
f1f81f86d6fef5ef43f768762ec28e28 <- md5sum.txt
1000
Offline
Does anyone else get a different md5sum than the one in md5sums.txt?
I tried redownloading the file, and also from a different mirror. But keep getting the same different md5sum: edf1dafc993e7200f34b178b51f26f89.
Confirmed, yeah me too.
Offline
Tpowa:
Am wondering whether the archboot .iso can be installed via dd to a flash drive.......
I desire to produce a raid0 system that boots from a partition and loads root on second parttions using two devices. Doing such an arrangement in linux3.0 with grub fails to boot.
Can this approach work with your .iso?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Offline
Kari Tech:
Don't want a raid1 only a raid0 ....one boot partition on sdb1 ...one swap partition on sdc1...one root partition on arraymd0 on partition2 of the subject drives.
Linux doesn't boot it but kernel26 did well.
Cannot setup downloaded .iso to boot raid0 using the above arrangement. It fails with same error of major-minor number of root device. Happens whether using uuid or label or dev naming.
Hoping that this archboot is different!!!
EDIT: Does this .iso convert to flash drive with dd command?
Last edited by lilsirecho (2011-10-22 19:33:20)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
@tpowa: Please apply https://gist.github.com/1080899 to archboot git repo (ignore the MB vs MiB dialog info though).
Offline
Progress regarding parted MB vs MiB issue - https://lists.alioth.debian.org/piperma … 03959.html
Offline
==
Arch Linux (archboot creation tool) 2011.10-1, "2k11-R6" has been released.
. . .
Environment changes:
. . .
- added hypervisor kernel modules
==
IMHO, "hypervisor kernel modules" best read as "Hyper-V ( hv_ ) kernel modules".
See "Arch Linux: Hyper-V And archboot.iso"
http://vvm.blog.tut.by/2011/10/24/archl … hboot-iso/
P.S.
TO Tobias Powalowski (tpowa)
Big thanks!
Last edited by Victor Miasnikov (2011-10-27 07:16:25)
Offline
Success at last! Mostly...
I made the changes below to /arch/setup as suggested.
if [[ $(modprobe -q efivars) ]]; then
to
modprobe -q efivars
if [[ "$(lsmod | grep efivars)" ]]; then
Here is my partition scheme:
Model: ATA WDC WD2500KS-00M (scsi)
Disk /dev/sdd: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 211MB 210MB fat16 EFI System boot
2 211MB 289MB 78.6MB ext2 Linux filesystem
3 289MB 54.0GB 53.7GB ext4 Linux filesystem
4 54.0GB 250GB 196GB Linux filesystem
Here is how it's mounted and formatted:
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
/run on /run type tmpfs (rw,nosuid,nodev,mode=755,size=10M)
devpts on /dev/pts type devpts (rw)
shm on /dev/shm type tmpfs (rw,nosuid,nodev)
/dev/sdf1 on /mnt/USB type vfat (rw)
/dev/sdd3 on /tmp/install type ext4 (rw)
/dev/sdd2 on /tmp/install/boot type ext2 (rw)
/dev/sdd1 on /tmp/install/boot/efi type vfat (rw)
sysfs on /tmp/install/sys type sysfs (rw)
proc on /tmp/install/proc type proc (rw)
/dev on /tmp/install/dev type none (rw,bind)
When I get to the INSTALL BOOTLOADER option I get the "Setup detected that you are using x86_64 (64-bit) UEFI..." message and grub2-efi-x86_64 is installed, I get sent to parted but I just quit since I dont't need to change anything, then I get sent to the grub config but again I don't change anything.
Oddly enough, I then get prompted to select a bootloader to install and go through the same process outlined above a second time. I also just quit without changing anything and eventually get the "GRUB2 UEFI was successfully installed." message.
After I quit the installer I copy the grub.efi to shellx64.efi like so...
cp /tmp/install/boot/efi/efi/grub/grub.efi /tmp/install/boot/efi/shellx64.efi
...and when I use the "Launch EFI shell from filesystem device" from the Exit option of the advanced mode of the ASUS UEFI BIOS on my M5A99X EVO flashed to version 0705 I boot flawlessly into pure UEFI.
Archboot seem to be doing everything right but it looks like my motherboard can't tell. So maybe it's my motherboard that is the cause of my issue of not being able to boot directly from the hard drive because it is not recognized as a UEFI boot device. I only ever get a blank screen with an underscore blinking cursor at the top left.
I'll wait for some feedback before I try the above on my more complex config using Pure UEFI GPT SSD RAID system encryption with LUKS, LVM & GRUB2-EFI.
Offline
@KairiTech: The newly patched /arch/setup (in git) script will not take you parted anymore. It takes you to cgdisk instead and (I think so) only once during the setup. But detection of UEFISYS partition is a bit tricky and it is better fot the user to manually mount the partition at /boot/efi instead of relying on "GRUB2 UEFI" option in the setup script to do the job. Also efibootmgr seems to truncate paths while modifying the UEFI Runtime Variables so that migth be cause of the blank screen you get.
Offline
the.ridikulus.rat
So my question becomes "What is the difference between the USB used for the UEFI boot/install and hard drive Arch is installed to that allows the USB to be so easily detected as a UEFI boot device and the hard drive not?"
Offline
the.ridikulus.rat
So my question becomes "What is the difference between the USB used for the UEFI boot/install and hard drive Arch is installed to that allows the USB to be so easily detected as a UEFI boot device and the hard drive not?"
One is a "Removable device", the other is a non-removable device. The firmware can clearly differentiate between removable and non-removable devices and the UEFI spec allows that.
Offline
hi there,
I did a fresh install of Arch and chose auto partitioning with gpt support. The installation worked finde except when I chose grub2-uefi as bootloader. It gave me the message that grub2 was not installed properly and that I should fix that manually. I had the chance to see the config file but after reboot I got the same blank screen with a blinking cursor on the top left corner as mentioned above and Arch didn't boot.
Unfortunatley I'm not that experienced with Arch that I was able to chroot (never done this before) and fix it manually. Is there a chance that this will work in a next release? I have my troubles with the chroot and grub2 wiki. There are some parts that I don't fully understand and don't know exactly what to do. (and I want to get rid of my Windows 7 again and use Arch only^^)
Greets
Andreas
Last edited by Kodama (2011-11-05 09:48:00)
Offline
So I think I've finally figure out how to install and boot Arch in pure UEFI mode using Archboot.
1. Use unetbootin to create a UEFI bootable USB from archlinux-2011.10-1-archboot.iso
2. Make the change below to the /arch/setup script (I tried the https://gist.github.com/1080899 patch but still got sent to cdisk twice and it complained about efivars not being loaded properly and the DRIVE variable was empty so cfdisk requested a device name to work with. The GRUB2 install failed.)
=====================================
if [[ $(modprobe -q efivars) ]]; then
=====================================
to
========================================
modprobe -q efivars
if [[ "$(lsmod | grep efivars)" ]]; then
========================================
3. Mount the vfat partition on /boot/efi/
4. When the install is compete and you exit setup, copy /tmp/install/boot/efi/efi/grub/grub.efi to /tmp/install/boot/efi/shellx64.efi
5. Use the "Launch EFI shell from filesystem device" option from the Exit option of the advanced mode of the ASUS UEFI BIOS on my M5A99X EVO. (The boot is successful so clearly Archboot creates a fully functional grub.efi.)
This way of booting into pure UEFI however is likely specific to the ASUS implementation of UEFI so I'd be interested to know how to do this on other brands of motherboards. I suspect that there will eventually be a "standard" adopted among motherboard manufacturers but information on exactly how you are supposed to boot from a pure UEFI install is not easy to find.
I tried other location for grub.efi, shellx64.efi and even tried bootx64.efi (in a similar location as the one on the UEFI USB I used for the install) but couldn't get the drive I installed to to show up as UEFI bootable.
Since the drive with the install does not show up as UEFI bootable in my boot menu, and thus cannot be added to the boot priority list, I need to go to the BIOS setup each time as indicated above. Maybe a later version of the ASUS UEFI BIOS will change this. I have contacted their tech support and am awaiting a response. This (Posted:1/20/2011 12:32:00 PM) is the most I have found so far which confirms my "discovery."
Kind of like using a hand-cranked generator to provide the AC power to your UPS. Which begs the question "What will I have to do if I wanted to completely isolate several pure UEFI OS installs on seperate drives attached to the same motherboard?" Still though, ASUS is so way ahead of everybody else with this UEFI stuff.
[Edit] Decided to use separate low capacity USB flash drives to store the "shellx64.efi" for each install. Don't know if it was intended that UEFI would requires a physical "key" to boot into and isloate multiple installs on the same motherboard but now that I think about it it's a dammed good idea, security wise, when I add this to my system encryption strategy. I just copy shellx64.efi to the USB instead of to the UEFI System partition for the install.
Last edited by KairiTech (2011-11-10 17:34:15)
Offline
if [[ "$(lsmod | grep efivars)" ]]; then
could be written as
if lsmod | grep efivars &>/dev/null; then
Offline
http://www.linlap.com/wiki/hp+elitebook+8460p
On HP Laptops the default paths to the efi file are
EFI/BOOT/BOOTX64.EFI
EFI/Microsoft/BOOT/bootmgfw.efi
but I don't get it to start automatically..
tried that :
cp /boot/efi/efi/grub/grub.efi /boot/efi/efi/Microsoft/BOOT/bootmgfw.efi
(Don't know if the firmware is case sensitivity..) Any information ?
My EFI partion ( GPT, EF00) is on a USB Stick (mounted on /boot/efi), Harddisk has its own /boot partion also GPT
only select efi file with F9 works..
shell also works with F9
Changing the efibootmgr boot order don't work, the Laptop forget it.
efibootmgr --create --gpt --disk /dev/sdb --part 1 --write-signature --label "GRUB2" --loader "\\EFI\\grub\\grub.efi"
efibootmgr --bootorder XXXX,YYYY,ZZZZ
Amusingly bootnext is working. Could wirte a script for every shutdown to set bootnext at grub.
efibootmgr --bootnext XXXX
Maybe I can try to change the Bootorder with the efi shell ?
Don't know if the bios is buggy or efibootmgr..
Tested with BIOS revision: 68SCF Ver. F08. I will update to F.20 soon.
Keep Calm and Hack On
Offline
Fallback:
"Launch EFI shell from filesystem device" is likely an ASUS specific way to boot into a pure UEFI install. Seems like my ASUS looks or "Shellx64.efi" in the top level of all FAT partitions. That's why I can dump it onto a flash USB and boot from that into the install drive. It most likely will not work exactly the same with any other brand of motherboard/laptop.
You may have a similar boot option in your laptop's BIOS setup screen but there's no guarantee that the file should be named "Shellx64.efi" or that it should be in the same location as for my ASUS motherboard.
Look here for the "final" solution that worked for me...
Last edited by KairiTech (2011-11-15 16:29:16)
Offline
Hello everyone,
i'm having a problem installing archboot in uefi mode on my t420 notebook. What I did so far:
* create USB drive with fat32 filesystem and unpack there archboot iso. The system boot from USB - "UEFI only" mode, so far so good. But when it comes to Package Source a choose "CDROM, USBSTICK or OTHER SOURCE" and get first error:
No source media was autodetected, please switch to another VC and manually mount media under /src(...)
no problem, i thought i mounted the usb stick in /src everythink is in place. But then when i go to next step "Select Packages" i get and the bottom of the screen:
grep: /packages/core-x86_64/pkg/packages.txt No such file or directory
of course installation fails...
* i tried to follow a wiki tutor on creating usb stick https://wiki.archlinux.org/index.php/Ar … _ISO_Howto but there is no such folder "/core-x86_64/pkg" on archboot image i downloaded. The md5sum is edf1dafc993e7200f34b178b51f26f89 so image seems to be allright.
what is going on?
EDIT 1:
Installer is looking for archboot_packages_x86_64.tar, i created it from content of archboot_packages_x86_64.squashfs, but apperently it could find archboot_packages_x86_64.squashfs either. In dmesg I found:
FAT-fs (sdb): invalid media value (0xf3)
FAT-fs (sdb): Can't find a valid FAT filesystem
So how can I create valid filesystem??? I tried with diskpart on win7, and cfdisk on linux with partition type 0x0c
EDIT2:
I donloaded iso image again and recreated ubs stick, but i have stll the same problem
I did folowing:
# mount /dev/sdb1 /home
# mount -o loop /home/packages/archboot_packages_x86_64.squashfs /src
# /arch/quickinst media /mnt /src/pkg
but there is 7 error "failed retrieving file" for
linux-firmware-20110822-1-any
iana-etc=2.30-2-any
filesystem-2011.08-1-any
mkinitcpio-0.7.2-1-any
licenses-2.8-1-any
man-pages-3.32-1-any
pacman-mirrorlist-20110816-any
Last edited by pejotr (2011-11-16 09:39:07)
Offline
@pejotr
I have run into a similar problem this week while trying to install from the USB stick repo and not network while booting from UEFI. I found a solution that works, though I cannot guarantee it is bulletproof.
At boot, exit setup.
open /arch/setup in editor.
At line 282, comment out the umount command.
mount /dev/*usb* to /src
Run /arch/setup
It works for me, basically the script is unmounting any leftovers before trying to get its media, but fails to do so properly. The umount command in the script makes any manual attempt to work around the issue useless. Hope this helps!
Offline
@pejotr
open /arch/setup in editor.At line 282, comment out the umount command.
mount /dev/*usb* to /src
!
Could you give me a list of /dev/*usb* ?
And also a list of the /sys/block/*usb*
Thanks i'll add it on next version to fix this issue.
Offline
spoked wrote:@pejotr
open /arch/setup in editor.At line 282, comment out the umount command.
mount /dev/*usb* to /src
!Could you give me a list of /dev/*usb* ?
And also a list of the /sys/block/*usb*Thanks i'll add it on next version to fix this issue.
Well, it depends on the user. For me, it was /dev/sdb1 as /dev/sda in my main hdd. I guess it is better to check if something is already mounted to /src and leave it that way if it is the case. I don't get the point of the umount procedure in the script, if a user has mounted an additional drive before loading up /arch/setup, surely they have an idea of what's going on.
Offline
The umount is already removed from the next setup script.
What does /dev/*usb* show? I have no usbstick that makes such symlinks or nodes.
Offline
The umount is already removed from the next setup script.
What does /dev/*usb* show? I have no usbstick that makes such symlinks or nodes.
I'm sorry /dev/*usb* was just an abstraction of what your usb stick dev is such as /dev/sdb1 /dev/sdc1. A sort of "fill in the blank". It's my fault for using a non standard way of writing it. Could have been /dev/{PATH_TO_USB_STICK}
Offline