All of lore.kernel.org
 help / color / mirror / Atom feed
* [U-Boot] Root-Filesystem ober NFS doesn't work... --> Kernel panic
@ 2009-10-19 16:59 Michael Schmid
  2009-10-19 18:01 ` Wolfgang Denk
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Schmid @ 2009-10-19 16:59 UTC (permalink / raw)
  To: u-boot

Hi!

I'm trying to get root-filesystem over NFS running. I'm a bit confused about all the new stuff and I don't know where I shall  start  searching for the problem :-(

I have:
Board: Artila M501 board with AT91RM9200
U-Boot: 1.1.2
Linux: 2.6
Flash: 16MB
SDRAM: 64MB

My U-Boot configuration is:

***  START ***
baudrate=115200
ethaddr=00:13:48:00:77:b5
rootpath=/opt/arm
lel=1
initrd=0x20800000,8192000 ramdisk_size=15360 root=/dev/ram0 rw
loader=tftp 21000000 m501_64M.alf
mtdparts=phys_mapped_flash:128k(loader)ro,128k(reserved)ro,1408k(linux)ro,2560(ramdisk)ro,-(userdisk)
filesize=3A3
netmask=255.255.255.0
bootcmd=bootm 10040000 101a0000
kernel=tftp 21000000 M501K;erase 10040000 1019ffff;cp.b 21000000 10040000 $(filesize)
skernel=loadb 21000000;erase 10040000 1019ffff;cp.b 21000000 10040000 $(filesize)
ramdisk=tftp 21000000 M501R;erase 101a0000 1041ffff;cp.b 21000000 101a0000 $(filesize)
sramdisk=loadb 21000000;erase 101a0000 1041ffff;cp.b 21000000 101a0000 $(filesize)
ipaddr=192.168.2.196
bootdelay=1
bargs=setenv bootargs mem=64M console=$(console),115200 initrd=0x20800000,8192000 ramdisk_size=15360 root=/dev/ram0 rw mtdparts=phys_mapped_flash:128k(loader)ro,128k(env)ro,1408k(linux)ro,2560k(ramdisk)ro,-(userdisk)
serverip=192.168.2.40
console=ttyS0
gateway=192.168.2.1
bootargs=root=/dev/nfs rw nfsroot=192.168.2.40:/opt/arm ip=192.168.2.196:192.168.2.40:192.168.2.254:255.255.255.0:michael-laptop::off console=ttyS0,115200
bootm=10040000 - 101a0000
stdin=serial
stdout=serial
stderr=serial
*** END ***

If I start my Board, the kernel boots and it looks fine until I get a kernel panic --> See the attached textfile!


Do you have any hints what the problems might be. I'm pretty sure that the NFS-Server works fine, but I'm not sure 100% (How can I find out if it works? Any Idea?).

Thanks!
Michael



-- 
GRATIS f?r alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
-------------- next part --------------
Uncompressing Linux............................................................................................... done, booting the kernel.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [U-Boot] Root-Filesystem ober NFS doesn't work... --> Kernel panic
  2009-10-19 16:59 [U-Boot] Root-Filesystem ober NFS doesn't work... --> Kernel panic Michael Schmid
@ 2009-10-19 18:01 ` Wolfgang Denk
  0 siblings, 0 replies; 2+ messages in thread
From: Wolfgang Denk @ 2009-10-19 18:01 UTC (permalink / raw)
  To: u-boot

Dear "Michael Schmid",

In message <20091019165934.319480@gmx.net> you wrote:
>
> I'm trying to get root-filesystem over NFS running. I'm a bit
> confused about all the new stuff and I don't know where I shall start
> searching for the problem :-(
>
> I have:
> Board: Artila M501 board with AT91RM9200
> U-Boot: 1.1.2

more than 4.5 years old!

> Linux: 2.6

2.6.14 according to your log => 4 years old

...
> bootcmd=bootm 10040000 101a0000

This setting means you are trying to boot with a ramdisk. If you want
to boot with root file system over NFS, you MUST NOT pass a ramdiska
ddress, i. e. you must not use two arguments to the "bootm" command.

> bootargs=root=/dev/nfs rw nfsroot=192.168.2.40:/opt/arm ip=192.168.2.196:192.168.2.40:192.168.2.254:255.255.255.0:michael-laptop::off console=ttyS0,115200

I don't think you want to assign the host name "michael-laptop" to
your target board (but this is no really critical at this moment yet).

> bootm=10040000 - 101a0000

This setting is completely bogus. It has no meaning. Delete it.

>  Linux version 2.6.14-M5 (Alan at ace-yang) (gcc version 3.3.2) #837 Tue 
> Aug 14 14:14:03 CST 2007
>  CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
>  Machine: Artila M501 SOM
...
>  RAMDISK: Compressed image found at block 0
>  VFS: Mounted root (ext2 filesystem).

Here you can see that the kernel mounts the ramdisk image which you
provided.

>  VFS: Cannot open root device "nfs" or unknown-block(0,255)
>  Please append a correct "root=" boot option
>  Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,255)

...and then it gets confused. 

> Do you have any hints what the problems might be. I'm pretty sure
> that the NFS-Server works fine, but I'm not sure 100% (How can I find
> out if it works? Any Idea?).

Well, just mount the root file system from another host?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
An armed society is a polite society.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-10-19 18:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-19 16:59 [U-Boot] Root-Filesystem ober NFS doesn't work... --> Kernel panic Michael Schmid
2009-10-19 18:01 ` Wolfgang Denk

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.