Public bug reported: Hi
Trying to start d-i from the netboot images at http://ports.ubuntu.com/ubuntu-ports/dists/jaunty/main/installer-armel/current/images/iop32x/netboot/ with these redboot commands: ip_address -l 192.168.0.106 -h 192.168.0.103 load -r -v -b 0x00800000 -m http /initrd load -r -v -b 0x00200000 -m http /vmlinux exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=1...@0xa0000000" the kernel starts but panics instead of starting d-i from initrd: RPC: Registered udp transport module. RPC: Registered tcp transport module. XScale DSP coprocessor detected. rtc-rs5c372 0-0032: setting system clock to 2009-03-26 18:07:31 UTC (1238090851) RAMDISK: Compressed image found at block 0 List of all partitions: 0800 244198584 sda driver: sd 0801 248976 sda1 0802 243947025 sda2 0810 244198584 sdb driver: sd 0811 248976 sdb1 0812 243947025 sdb2 1f00 256 mtdblock0 (driver?) 1f01 13312 mtdblock1 (driver?) 1f02 1408 mtdblock2 (driver?) 1f03 1152 mtdblock3 (driver?) 1f04 4 mtdblock4 (driver?) 1f05 128 mtdblock5 (driver?) No filesystem could mount root, tried: ext3 ext2 vfat fuseblk Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Dumping ftrace buffer: (ftrace buffer empty) I also tried without root=/dev/ram0 but it didn't work more than with it. Bye ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: arm -- [arm] iop32x panics instead of starting d-i from initrd https://bugs.launchpad.net/bugs/349104 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
