I've been fighting the same problems as have been reported here (on an eSATA plug, FWIW), but using the old installer package.
What I have learnt:
If the /etc/init.d/rcS script reads 3 mtd partitions, this command:
mount -t ubifs ubi0:rootfs /mnt/target
mounts the uImage partition when we want it to mount the rootfs partition. It then gives messages like:
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
**** Erasing all flash
ubiformat: mtd1 (nand), size 4194304 bytes (4.0 MiB), 32 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
**** Copying root filesystem. This will take few minutes
tar: write error: No space left on device.................................]
in the mtdpartitions
environment variable, despite the note "If using kernel >= 2.6.30 then replace orion_nand with orion_mtd". This solution has been mentioned here several times.
I am also
seeing exactly the same crash as Patrick, starting with Unable to handle kernel NULL pointer dereference at virtual address 00000018
. However, I am using a kernel that I (cross) compiled. And yet the error seems to be identical.
My first thoughts were that the kernel I created was faulty. I am relieved to finds myself at the same end point, but via a different route.
I have downloaded the installer v1.01 from the publicly posted link, and found it to be unreadable (although tar -xvzf sheevaplug-installer-v1.01.tar.gz
extracts partially, as Patrick reported).
@mgillespie - I am willing to try out your as-yet-unpublished installer. Will PM you imminently.
Edited to add:
Having run the same old installer that I have been using for the past couple of months, I then manually applied the kernel that I had compiled, and everything looks good and proper.
So the conclusion is that there is something in the installer process that is tripping up the (various, different) kernels that we have been working with?