for ext2/3 based filesystems read the superblock to determine the last filesystem check.

see a few posts up. openocd does not find the plug because the usb identifier changed.

edit: user found it himself

you can check what is mounted by typing
in the booted linux system. Should show .

most likely you have not mounted the sdcard.

to boot from the sdcard you need the init the mmc system in u-boot (this is most important after a full system reset. after a normal reboot the mmc stays initialized).

So booting goes like

mmcinit
load a kernel from somewhere (nand, tftp, sdcard, ...)
load an initrd from somewhere
define bootargs including the rootfs
run the loaded kernel

i can't say the exact commands out of my head but the wiki should tell.

there are two ways to upgrade uboot. Either directly write to nand using jtag (you need this to recover from a bad uboot upgrade) or boot into uboot and then tftp the new binary.

Writing to nand using jtag is covered in the alpha installer. I haven't investigated how to prepare a fitting binary.

Compiling your own uboot and writing it using tftp goes like this.

to compile your uboot (based on uboot 1.1.4 + marvel patches + sd-card patches) follow thread http://plugcomputer.org/plugforum/index.php?topic=183.0

or search the thread there is a ready compiled binary attached.

to write using tftp

* setup tftp server in your network. place uboot.bin in tftp root folder.
* boot plug to uboot (hit key to prevent autoboot)
* set plug ip (setenv ipaddr 192.168.1.10) and tftp ip (setenv serverip 192.168.1.2)
* flash image from tftp (bubt u-boot.bin)
* reset plug (reset)

It looks like the cpuidle patch made it into mainline linux 2.6.31-rc4, no idea if it is already in earlier releases

the alpha installer will also upgrade the u-boot (introducing the possibility to boot from sdcard). This can also be done manualy. Unless you are interessted in a detailed understanding what happens, go for the installer.

the non marvell kernel have no access to the internal crypto engine.

add quotes.

looks like the last batch of sheevaplugs changed vendor and product id. Modified scripts-linux/openocd/config/interface/sheevaplug.cfg to

interface ft2232
ft2232_layout sheevaplug
ft2232_vid_pid 0x0403 0x6010
#ft2232_vid_pid 0x9e88 0x9e8f
#ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"
jtag_khz 2000

ordered june/11, received july/30. Looks like globalscale sends out a bunch the last days. But they still get the badge of "worst communiction" for not giving apox shipping dates (maybe not theirs fault) and not answering emails.

device naming might shift during detection phase (but as long as you don't add, move, change your devices it shouldn't). If you need to make sure that you always get the same devicenames you can add custom udev rules. Base those rules on a unique criteria of the usb-serial converter and add another alias (myserial01).

do you here a windows notification sound when the plug is connected?

Or boot a linux (live-cd) plug in and check with "lsusb" if the plug is connection to the host.