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" 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. I am uploading ISOs that work to http://alberich.archlinux.org/misc/testiso/, they should be there in about an hour.