Release Engineering

Tasklist

FS#33730 - Problems with current (Februar) ISO

Attached to Project: Release Engineering
Opened by Jens Adam (byte) - Tuesday, 05 February 2013, 20:40 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 06 February 2013, 00:48 GMT
Task Type Bug Report
Category ArchISO
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I read https://mailman.archlinux.org/pipermail/arch-releng/2013-February/003103.html but the steps with 'sys' and 'nohave64' (CoreDuo laptop, so 32-bit) didn't work.
I'm using a 2 GB USB stick with a 500 MB VFAT partition for Arch, set up after https://projects.archlinux.org/archiso.git/tree/docs/README.transfer -> "PC-BIOS (MBR)"

Booting (32-bit via local QEMU and 64-bit on another computer) finally worked - with the mentioned manual steps 'sys' and '(no)have64' to get to the menu - after I copied the *.c32 files from my local (i686) /usr/lib/syslinux over to the flash drive.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Wednesday, 06 February 2013, 00:48 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Tuesday, 05 February 2013, 20:55 GMT
The Feburary ISO still uses syslinux 4.06 -- the mailing list post you cite isn't relevant.
Comment by Jens Adam (byte) - Tuesday, 05 February 2013, 21:06 GMT
Ah, ok.
So the problem was using 'extlinux -i ...' from syslinux [testing] with the 4.06 ISO files.
Simple dd transfer should be unaffected as well.
Thanks.

Loading...