You are not logged in.
I have made a bootable usbkey with the archlinux-2012.09.07-dual.iso
file but having tried to boot it, both on an Inspiron 530s and also a
Samsung Q35 netbook, there is a blue "graphics" screen but it does not
stop and offer me the choice of i686 or x86_64 but carries straight on
to boot to the normal prompt. So I can't choose which architecture to
use for the install.
Does anyone know a workaround to be able to get to choose which of 32
or 64 bit to boot for the install? Or is there a problem with this new
install media on some hardware?
I have done quit a bit of reading but not seen this issue mentioned in
any of the arch wiki or other google searches.
Thanks
Last edited by mcloaked (2012-09-16 10:10:19)
Mike C
Offline
The fact that the usb stick doesn't work on two different machines is interesting, and make me think it's more a problem with the usb stick than with your hardware. Did you check the md5 or sha1 checksums after you downloaded the iso? How did you copy it to the usb stick? Can you try copying it again?
Offline
Which method/software did you use to prepare the USB stick?
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
The fact that the usb stick doesn't work on two different machines is interesting, and make me think it's more a problem with the usb stick than with your hardware. Did you check the md5 or sha1 checksums after you downloaded the iso? How did you copy it to the usb stick? Can you try copying it again?
Yes I checked the sha1sum after download.
Mike C
Offline
Which method/software did you use to prepare the USB stick?
I used unetbootin - which I have used many times to prepare things like PartedMagic for example. The unetbootin run seemed to prepare the isbkey without issue.
Mike C
Offline
DSpider wrote:Which method/software did you use to prepare the USB stick?
I used unetbootin - which I have used many times to prepare things like PartedMagic for example. The unetbootin run seemed to prepare the isbkey without issue.
I have been told on the arch general list that unetbootin breaks the image! As it is late here I will try to the dd method tomorrow and see if that works - and report back once I have tried that.
Mike C
Offline
EDIT: Too late
This shouldn't be possible unless the iso, usb-stick or written data has been flawed in some way during processing...
There's zero reason to use unetbootin for things like these; use dd to write the iso to usb and check both the iso and the written data to the usb-stick afterwards.
I've made a shell-function which I use, that automates the above and which you're free to use also:
Usage:
$ iso2usb <file> <drive>
iso2usb() {
md2=$(md5sum $1 | cut -d " " -f 1)
sudo dd if=$1 of=$2 2>/dev/null
md1=$(sudo dd if=$2 count=$(( $(stat -c %s $1) / 512 )) 2>/dev/null | md5sum | cut -d " " -f 1)
if [ $md1 != $md2 ] ;then
echo FAILED!
else
echo OK!
fi
}
Last edited by mhertz (2012-09-15 21:46:27)
Offline
EDIT: Too late
This shouldn't be possible unless the iso, usb-stick or written data has been flawed in some way during processing...
There's zero reason to use unetbootin for things like these; use dd to write the iso to usb and check both the iso and the written data to the usb-stick afterwards.
I've made a shell-function which I use, that automates the above and which you're free to use also:
Usage:
$ iso2usb <file> <drive>
iso2usb() { md2=$(md5sum $1 | cut -d " " -f 1) sudo dd if=$1 of=$2 2>/dev/null md1=$(sudo dd if=$2 count=$(( $(stat -c %s $1) / 512 )) 2>/dev/null | md5sum | cut -d " " -f 1) if [ $md1 != $md2 ] ;then echo FAILED! else echo OK! fi }
OK I tried with the dd method and it works perfectly... I will check back on the wiki and edit to ensure that a comment is included that the unetbootin method does not work.
Thank you for the shell function - which I will use though I changed it so that the drive only needs defining as an argument as "sdX" and added in the /dev/ prefix in the function as per:
iso2usb() {
md2=$(md5sum $1 | cut -d " " -f 1)
sudo dd if=$1 of=/dev/$2 2>/dev/null
md1=$(sudo dd if=/dev/$2 count=$(( $(stat -c %s $1) / 512 )) 2>/dev/null | md5sum | cut -d " " -f 1)
if [ $md1 != $md2 ] ;then
echo FAILED!
else
echo OK!
fi
}
Thank you for the help.
Mike C
Offline
I have edited the wiki at https://wiki.archlinux.org/index.php/US … UNetbootin to include a warning about unetbootin for the dual architecture install isos.
Last edited by mcloaked (2012-09-16 10:16:46)
Mike C
Offline
Fucking Unetbootin... It was removed at least three times already from the wiki. It's a piece of shit.
It's way too intrusive. It installs its own version of the bootloader, a crappy syslinux.cfg, and doesn't give a shit about labels.
Unetbootin is totally NOT recommended for Arch Linux and it should be removed from the wiki.
Use something else.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Just out of interest, is there a recommended method for use on a Windows machine?
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
I don't know about recommended however I just tested Win32 Disk Image aka Image Writer for Windows:
https://launchpad.net/win32-image-writer
And it handles the Arch Linux ISO with no issues (that I've noticed anyways).
Offline
I don't know about recommended however I just tested Win32 Disk Image aka Image Writer for Windows:
https://launchpad.net/win32-image-writer
And it handles the Arch Linux ISO with no issues (that I've noticed anyways).
If you prefer the commandline, try dd for windows or windd
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline