I have the same problem, caused by flashing the wrongly named uboot image from USB drive. Saw the loading happen then no console, and no blue light. (Oh how i miss the blue light )

I won't take up space here, a complete description is on plugpbx.org at: http://forums.plugpbx.org/index.php/topic,298.0.html

I've tried with Windows 7 and then with Ubuntu 11.10, but running the script (runme.exe or runme.php) to reflash, gives an error:

brett@eeeBox:~/sheevaplug-installer-v1.0/uboot/openocd/config$ openocd -f sheevaplug.cfg -c init -c sheevaplug_reflash_uboot -c exit
Open On-Chip Debugger 0.5.0 (2011-08-26-10:27)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
sheevaplug_load_uboot
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
  feroceon.cpu mww address data [count]
mww ['phys'] address value [count]
Runtime Error: sheevaplug.cfg:34:
in procedure 'sheevaplug_reflash_uboot'
in procedure 'sheevaplug_init' called at file "sheevaplug.cfg", line 106
in procedure 'mww' called at file "sheevaplug.cfg", line 34

Any ideas on what might be up with the sheevaplug.cfg file?