Hi,
I've got a Sheevaplug and I'm using a 4GB SD card to hold the OS.
I followed the instructions at http://plugcomputer.org/plugforum/index.php?topic=1041.0 but my boot sequence halts with the lines:
rtc-mv rtc-mv: setting system clock to 2009-12-31 19:12:06 UTC (1262286726) Waiting 10sec before mounting root device... EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 179:1. Freeing init memory: 116K Warning: unable to open an initial console.
I've googled that warning message but I'm not finding anything that makes any sense to me.
Can anyone shed any light on what my problem is and where I can start debugging?
Thanks,
Graeme Hilton
PS My environment and uBoot version are attached below.
Marvell>> printenv baudrate=115200 loads_echo=0 ipaddr=10.4.50.165 serverip=10.4.50.5 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 console=a0000 e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; ethmtu=1500 mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host yuk_ethaddr=00:00:00:EE:51:81 nandEcc=1bit netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no ethact=egiga0 mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) ethaddr=00:62:81:a0:00:00 real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000 recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions); bootm 0x00800000 0x01100000 recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000 recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd arcNumber=2097 filesize=1CAE6D bootargs_nand=console=ttyS0,11200 rw root=/dev/mtdblock2 rootfstype=jffs2 bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootargs_sd=console=ttyS0,115200 ro root=/dev/mmcblkp01 rootdelay=1 bootcmd_sd=setenv bootargs $(bootards_sd); mmcinit; ext2load mmc 0 0x800000 /boot/uImage-2.6.30-sheevaplug; bootm 0x800000 bootargs_console=console=ttyS0,115200 bootargs_root=rw root=/dev/mmcblk0p1 rootdelay=10 rootfstype=ext2 bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_mmc; bootm 0x0800000 bootargs=console=ttyS0,115200 rw root=/dev/mmcblk0p1 rootdelay=10 rootfstype=ext2 bootcmd_mmc=mmcinit; ext2load mmc 0 0x800000 /boot/uImage-2.6.30-sheevaplug stdin=serial stdout=serial stderr=serial nandEnvBase=a0000 mainlineLinux=yes enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=3 disaMvPnp=no enaAutoRecovery=yes pcieTune=no
Environment size: 2492/131068 bytes Marvell>> version
U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19 Marvell>>
On 01/02/10 11:08, Somebody in the thread at some point said:
Hi -
Don't have a sheevaplug but -->
rtc-mv rtc-mv: setting system clock to 2009-12-31 19:12:06 UTC (1262286726) Waiting 10sec before mounting root device...
You don't have to do that. Use "rootwait" instead, it just waits until the root device appears (usually much sooner that 10s).
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 179:1. Freeing init memory: 116K Warning: unable to open an initial console.
You need some minimum goodies in /dev to get any joy.
Here's mine used with F11 on SD Card Boot.
-bash-4.0# ls -l /dev total 4 crw-r--r-- 1 root root 5, 1 Jan 1 01:04 console <=== !!! crw-r--r-- 1 root root 29, 0 Sep 25 2009 fb0 crw-rw-rw- 1 root root 10, 229 Sep 25 2009 fuse drwxr-xr-x 2 root root 4096 Nov 2 2009 input srw-rw-rw- 1 root root 0 Jan 1 1970 log brw-r--r-- 1 root root 7, 0 Sep 25 2009 loop brw-r--r-- 1 root root 179, 0 Sep 29 2009 mmcblk0 brw-r--r-- 1 root root 179, 1 Sep 25 2009 mmcblk0p1 brw-r--r-- 1 root root 179, 2 Sep 25 2009 mmcblk0p2 brw-r--r-- 1 root root 179, 3 Sep 25 2009 mmcblk0p3 brw-r--r-- 1 root root 179, 4 Sep 25 2009 mmcblk0p4 crw-rw-rw- 1 root root 1, 3 Jun 17 2009 null crw-r--r-- 1 root root 108, 0 Oct 28 2009 ppp crw-r--r-- 1 root root 5, 2 Jan 1 01:04 ptmx drwxr-xr-x 2 root root 0 Jan 1 01:00 pts brw-r--r-- 1 root root 1, 1 Sep 25 2009 ram crw-r--r-- 1 root root 1, 8 Sep 25 2009 random crw------- 1 root root 254, 0 Sep 25 2009 rtc drwxrwxrwt 2 root root 40 Jan 1 01:00 shm crw--w---- 1 root tty 204, 64 Jan 1 01:00 ttySAC0 crw------- 1 root root 207, 16 Jan 1 01:00 ttymxc0 crw-r--r-- 1 root root 207, 17 Sep 25 2009 ttymxc1 crw-rw-rw- 1 root root 207, 18 Sep 25 2009 ttymxc2 crw-r--r-- 1 root root 1, 9 Sep 25 2009 urandom crw-rw-rw- 1 root root 1, 5 Jun 17 2009 zero
bootargs_nand=console=ttyS0,11200 rw root=/dev/mtdblock2 rootfstype=jffs2
You mean 115200 here.
-Andy
2010/1/2 Andy Green andy@warmcat.com:
On 01/02/10 11:08, Somebody in the thread at some point said:
Hi -
Don't have a sheevaplug but -->
rtc-mv rtc-mv: setting system clock to 2009-12-31 19:12:06 UTC (1262286726) Waiting 10sec before mounting root device...
You don't have to do that. Use "rootwait" instead, it just waits until the root device appears (usually much sooner that 10s).
Thanks, I'll do that.
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 179:1. Freeing init memory: 116K Warning: unable to open an initial console.
You need some minimum goodies in /dev to get any joy.
Here's mine used with F11 on SD Card Boot.
-bash-4.0# ls -l /dev total 4 crw-r--r-- 1 root root 5, 1 Jan 1 01:04 console <=== !!!
This is the one. Thanks for that.
bootargs_nand=console=ttyS0,11200 rw root=/dev/mtdblock2 rootfstype=jffs2
You mean 115200 here.
I do, but this line isn't used in booting from the SD. I changed it anyway so it doesn't catch me out in future.
Thanks Andy; now to get the filesharing and printing up and running.
Graeme Hilton
On 01/02/10 11:57, Somebody in the thread at some point said:
Hi -
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 179:1.
Some advice from experience, ext2 will bite you sooner rather than later.
ext4 works great on SD Card partitions and it's really robust if you have the kernel commandline mount it ro, and add an fsck before remounting / rw, or use the Fedora initscripts if you're patient. If you went down cleanly then the fsck is over with in well under a second.
-Andy
On Sat, 2010-01-02 at 11:08 +0000, Graeme Hilton wrote:
Hi,
I've got a Sheevaplug and I'm using a 4GB SD card to hold the OS.
PS My environment and uBoot version are attached below.
Marvell>> printenv baudrate=115200 loads_echo=0 ipaddr=10.4.50.165 serverip=10.4.50.5 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 console=a0000 e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) CASset=min MALLOC_len=1
U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19 Marvell>>
There is a bug in Sheevaplug uboot 3.4.19 which corrupts the environment (see console=a0000 and following line above).
This is now fixed in 3.4.27, but two further issues have been found, and pingtoo has produced fixes -see http://plugcomputer.org/plugforum/index.php?topic=1134.31 . It appears that the best uboot is 3.4.27 as patched by pingtoo, available from http://plugcomputer.org/plugforum/index.php?action=dlattach;topic=1134.0;att... .
Beware though, and it applies not only to 3.4.27, but also 3.4.19 and 3.4.16 and probably earlier, that it appears there is a bug in the SDHC handling, and that uboot will not be able to handle offsets greater than 4Gb on the card; you should be safe with your 4Gb card of course.
Regards, Quentin Armitage
-
Andy Green -
Graeme Hilton -
Quentin Armitage