> > > > Any suggestions? Is this a known problem or am I missing out on something > > .. ? > > Looks to me like a corrupted ramdisk image. I hope you unmounted the > ramdisk first before you downloaded the image to your board.
I've unmounted the ramdisk before download. I've also tried to generate new ramdisks on two other machines in case something was wrong on my local machine. Same result. I'm really puzzled here. I've even tried to e2fsck -v ramdisk.img and it returns with 0. The ramdisk always mounts fine locally but still fails on target. At one occasion though, I got linux booted. I then tried to run the large binary(approx. 1.2 Mb) that causes the problem and then linux produced a long list of these messages: attempt to access beyond end of device 01:00: rw=0, want=436207627, limit=4096 attempt to access beyond end of device 01:00: rw=0, want=1649098578, limit=4096 and then it stops with "bus error" (not linux, but loading of the binary). Linux still ran after this. Christer _______________________________________________ http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm http://www.arm.linux.org.uk/armlinux/mailinglists.php Please visit the above addresses for information on this list.
