[arch-releng] archiso boot fail from cdrom (Was [PATCH 1/3] [syslinux-iso] ....

Gerardo Exequiel Pozzi vmlinuz386 at yahoo.com.ar
Sat Jun 26 20:24:02 EDT 2010

  On 06/26/2010 08:14 PM, Thomas Bächler wrote:
> Am 27.06.2010 00:46, schrieb Gerardo Exequiel Pozzi:
>>>> I tested on real machine and booting from cdrom works OK.
>>> And also tested under Virtualbox and also works fine booting from
>>> cdrom (iso).
>>> So if you testwas on qemu, I guess that something is wrong with new
>>> cdrom_id (there are several changes) and qemu.
> Yes, I tested on qemu. A simple udev rule like this one in the initramfs
> will also do the trick:
> ACTION=="add|change", SUBSYSTEM=="block", KERNEL=="sr*", GOTO="cdboot_start"
> GOTO="cdboot_end"
> LABEL="cdboot_start"
> IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
> ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
> SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
> ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*",
> SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"
> LABEL="cdboot_end"
Looks good for temporary solution, I sent an email to Kay (udev author) 
about problem with cdrom_id. So we need to wait for response.

> About memdisk: It works fine on 64 Bit, but not on 32:
> http://bsfh.ath.cx/memdisk_32.png
> Appending vmalloc=256M to the kernel command line fixes that, but it is
> apparently not without side effects - should be good enough for the ISO
> though.
Wheel seems that depends on amount of RAM (in inverse, yeah), for example:
Works OK under 32 bit 512MB RAM and no vmalloc.
vmalloc= is needed if machine have >~ 800M of RAM. (I guess related to 
LOWMEM area defined at 32 bits).

Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1

More information about the arch-releng mailing list