On 12.10.2012, at 08:52, Marcus Schäfer wrote:
Hi,
On the second boot, it stops here: ******************************************************************************** (...) your system time is not correct: Sat Jan 1 00:04:26 UTC 2000 setting system time to: Sun Aug 19 00:00:00 UTC 2012 [ 8.152404] alua: device handler registered [ 8.178344] emc: device handler registered [ 8.204162] hp_sw: device handler registered [ 8.230651] rdac: device handler registered Creating device nodes with udev [ 8.319793] udevd[90]: starting version 182 mount: devpts is already mounted or /dev/pts busy devpts is already mounted on /dev/pts Boot logging started on /dev/ttyO2(/dev/console) at Sun Aug 19 02:00:05 2012 Waiting for device /dev/0 to appear: ..............................Could not find /dev/0. Want me to fall back to /dev/disk/by-id/mmc-00000_0x770b5bf2-part2? (Y/n) ********************************************************************************
And I cannot answer to the last line to continue.
It may be due to the kernel cmd line: root=0 loader=uboot disk=/dev/disk/by-id/mmc-00000_0x770b5bf2 resume=openSUSE-Factory-ARM-JeOS-beagle console=ttyO2 vram=16M
I'm actually getting the exact same behavior on a Calxeda Highbank machine. So I'm quite sure it's something busted in the boot.scr generation (which is in uboot-setup.tgz):
Hmm, no this is on the second boot thus the result of mkinitrd plays a role here. imho this is not related to the kiwi image
Oh it definitely is, because the boot.script is busted: setenv ramdisk initrd setenv kernel uImage setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" printenv kerneladdr || setenv kerneladdr ${kernel_addr_r} printenv ramdiskaddr|| setenv ramdiskaddr ${ramdisk_addr_r} setenv bootcmd "ext2load scsi 0:1 ${kerneladdr} uImage; ext2load scsi 0:1 ${ramdiskaddr} initrd; bootm ${kerneladdr} ${ramdiskaddr} ${fdt_addr}" setenv bootargs root=0 loader=uboot disk=/dev/disk/by-id/ata-VM0500EBQHB_91NST05UT resume=openSUSE-12.2-ARM-JeOS-highbank console=ttyAMA0; boot The question is just whether our uboot setup scripts are wrong or whether kiwi calls them incorrectly :). Have you changed / fixed anything in that area recently? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org