Hi,

Hmm, rootpath looks good but what about root? Cause there's your mtdblock
probably coming from. As far as I understood, this gets passed from u-boot
to kernel. What version of u-boot you're running? What flags did you set on
compiling?

Regards

Yves

Gesendet von meinem Windows Phone
------------------------------
Von: Hai Nguyen Dang
Gesendet: Donnerstag, 9. Juni 2011 16:53
An: Yves Jeanrenaud
Betreff: Re: Re: Sheevaplug with new kernel 2.6.39

Hi Yves,
Thanks for your message.

These are uBoot environment variables from printenv

==============================
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0
(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
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
netmask=255.255.255.0
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000
(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw
ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
run_diag=no
ipaddr=192.168.10.2
serverip=192.168.10.10
filesize=73e1c
fileaddr=2000000
ethaddr=F0:AD:4E:00:0D:5C
arcNumber=2678
bootargs_console=console=ttyS0,115200
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /uImage; ext2load usb 0:1
0x01100000 /uInitrd
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm
0x00800000 0x01100000
stdin=serial
stdout=serial
stderr=serial
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
==============================

Thanks and rgds,
Dang Hai

On Thu, Jun 9, 2011 at 8:54 PM, Yves Jeanrenaud
<yves.jeanren...@gmail.com>wrote:

> Hi,
>
> What are does printenv say in u-boot?
>
> Regards
>
> Yves
>
> Gesendet von meinem Windows Phone Von: Arnaud Patard
> Gesendet: Donnerstag, 9. Juni 2011 15:06
> An: Hai Nguyen Dang
> Cc: Debian ARM
> Betreff: Re: Sheevaplug with new kernel 2.6.39
> Hai Nguyen Dang <dangha...@gmail.com> writes:
>
> > Hi All,
>
> Hi,
>
> > I tried to compile and upgraded my Sheevaplug from kernel 2.6.38 to
> 2.6.39
> > with my own compiled kernel, however I always got the mount root problem
> as
> > below.
> >
> > This is a part of uBoot messages before kernel panic and hang, my
> SheevaPlug
> > boots from USB normally with kernel 2.6.38 (I tried to compile the kernel
> > 2.6.39 many times, the last time I used kirkwood_defconfig without
> changes
> > as my kernel configuration but it doesn't work).
> >
> > ========================================
> > usb 1-1: new high speed USB device number 2 using orion-ehci
> > ata2: SATA link down (SStatus 0 SControl F300)
> > Root-NFS: no NFS server address
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > VFS: Cannot open root device "(null)" or unknown-block(2,0)
> > Please append a correct "root=" boot option; here are the available
> > partitions:
> > 1f00            1024 mtdblock0  (driver?)
> > 1f01            4096 mtdblock1  (driver?)
> > 1f02          519168 mtdblock2  (driver?)
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(2,0)
>
> Can you please provide your kernel command line ? Are you booting with
> an initrd ?
> If you're booting without initrd, from the part of the log, an usb
> devices seems to be detected but not yet probed. Maybe you're missing a
> rootwait in your kernel command line or missing usb mass storage support
> in your kernel ?
>
> Regards,
> Arnaud
>
>
> --
> To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/8739jjma9h....@lebrac.rtp-net.org
>

Reply via email to