did you apply any additional patches? What did you use as cross compiler chain (i had issues with gcc 4.5)
i use flipflips u-boot. No idea about the orginal u-boot

The process is actually pretty straight forward http://www.held-im-ruhestand.de/software/sheevaplug/Kernel

the guruplugs have the sd-card internally attached as an USB device.

if you are using a sd card as rootfs, there is no reason to keep /var/cache/apt in tmpfs. Check your etc/fstab

afaik all units have been opened to replace the PSU. If you open it (voiding your waranty) you will see that they broke out some plastic parts to make room for the psu.

no crossover needed. i have not seen any gigabit interface that does not implement auto mdix. I', not sure but imho its part of the gigabit standard

great idea!

the kernel is read correctly. AFAIK the uImage contains a header and a checksum, it matches otherwise it would not even try to start the kernel.

no, the gcc version. i had serious trouble with gcc 4.5 and kernels.

how did you compile the kernel? cross-compiler? and what version?

disregarding the mmcinit you should see the kernel starting up and spilling messages before it tries to mount the rootfs.

hey buy our new supersportscar it has a range of 200 mpg.

*sell cars*

oh, sorry it only has 10mpg, we changed the sign. If you are lucky we will release a new supersportscar in one year that will have the 200 mpg. If you are even luckier you can _buy_ an upgrade kit. Till then, just put your car on a trailer, you will get an infinite mpg range then.

that's squashing all ids. You can also try ugidd, but this needs to be run on the client, i wouldn't go this way. Either sync the ids or go for nfsv4

if they didn't change anything there are only the screws. 1cm low thread. So keep turning them, they will come out.

here are the hints: mmcinit and ext2load (but only on sheevaplug)

did you compile in serial console support into your kernel? Is the u-boot env variable console defined?