Hi birdman,
On the weekend I amended the bootcmd_mmc u-boot environment variable given her
http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html with an "usb start"
setenv bootcmd_mmc 'mmcinit; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd; usb start'but it does not mitigate the situation:
Last login: Sun Nov 21 16:51:42 2010
root@Share:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 746848 607824 101088 86% /
tmpfs 257788 0 257788 0% /lib/init/rw
udev 254952 76 254876 1% /dev
tmpfs 257788 0 257788 0% /dev/shm
/dev/mmcblk0p1 124743 22009 96078 19% /boot
root@Share:~# mount -a
root@Share:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 746848 607860 101052 86% /
tmpfs 257788 0 257788 0% /lib/init/rw
udev 254952 76 254876 1% /dev
tmpfs 257788 0 257788 0% /dev/shm
/dev/mmcblk0p1 124743 22009 96078 19% /boot
/dev/sda1 1922858352 1424940752 478382444 75% /mnt/sda1
But of course your hint was worthwhile a new try (in the meantime I also saw some of your post where you ran into a similar situation :-)
Thus I modified the u-boot variables as follows:
setenv bootargs_console 'console=ttyS0,115200 rootdelay=5'
setenv bootargs_mmc 'mmcinit; ext2load mmc 0:1 0x01100000 /uInitrd; ext2load mmc 0:1 0x00800000 /uImage'
setenv bootcmd_mmc 'setenv bootargs $(bootargs_console); run bootargs_mmc; bootm 0x00800000 0x01100000'
setenv bootcmd 'run bootcmd_mmc; run bootcmd_nand; run bootcmd_sd'And indeed, looks better, now :-)
BTW: as my plug's in the basement I always have to pick it up and bring it to my PC to have access to the u-boot environment.
So I though being lazy and considered the use of the sheeva-uboot-tools (
https://code.google.com/p/sheeva-uboot-tools/), dl them and compiled my own version.
However, though the sheeva-ubootenv-print worked OK, sheeva-ubootenv-save seem to have screwed the config, as another print claimed about CRC? errors and the plug didn't came after reboot. When I picked it up I could access u-boot, but it just had default settings. Luckily I had a backup at hand and could restore my previous settings, so got it working again (though there was another small intermezzo with the kernel complaining about an unknown Manufacturer ID, but I can't recall exactly how did overcome this ;-)
