Why not just get yourself an OpenRD Client?

It looks like the packager did not update the upper level README.txt to mention that the config files are now in the directory  .../sheevaplug-installer-v1.0/uboot/uboot-env/

Maybe Rabeeh could update the README.txt and explain how to use the config files and repackage it as 1.01?

Did you also build the modules that go with the kernel and install them?

kilowatt why do you have two ext2load lines?  In my example I use only one and it works fine in reality.

kilowatt, are you saying the information at http://plugcomputer.org/plugwiki/index.php/U-Boot_Quick_Reference is incorrect ?

You need rootdelay=10 . This should give it 10 seconds to spin up.
See my reply to another of your questions at http://plugcomputer.org/plugforum/index.php?topic=532.msg3226#msg3226 to see this in context.

This is what I use to boot from a HDD in an external USB enclosure.


For reference my HDD  is partitioned as follows :

Disk /dev/sda: 40.0 GB, 40007761920 bytes
64 heads, 32 sectors/track, 38154 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          32       32752   83  Linux
/dev/sda2              33       38154    39036928    5  Extended
/dev/sda5              33       37432    38297584   83  Linux
/dev/sda6           37433       38154      739312   82  Linux swap / Solaris

Partition sizes are in MB

sda1 is formatted ext2
sda5 is formatted ext3

no, because you can always load the modules later using modprobe.

You may have 256 bit inodes.  You want to try the -i flag for 128 bit.  That is use -i 128 when formatting and see if you can then boot.

It is still there.

You do not need to move to 64 bit architecture to fix this.

Having worked on y2k issues I heard the exact same thing from nay sayers.  There is plenty of time for this to be fixed before 2038 and the changes have gone into some systems already. Embedded systems for which dates matter will be updated before then.

Many systems do not use dates at all and are irrelevant in this case.

You are making the assumption that the date is being stored as one 32 bit number.  Easy enough to store it as two 32 bit values. Just a matter of the correct algorithm for storage and retrieval.

Thank you for the response.  256 I node support would be good.  By the way what are the uboot ext2 commands?

prafulla, the impression I have is that to boot from an USB drive it has to be formatted as FAT.   Is that correct or does u-boot support booting from a drive formatted as ext2, ext3 or ext4?