olimex-sam9-l9260: can't boot over nfs.

Ghostie · **Joined:** Wed Feb 17, 2010 12:32 pm **Posts:** 4

hi,

i compiled atbootstrap, u-boot and linuxkernel from vanilla sources (2.6.32.7) on my own because i need ubifs support. u-boot workes fine. it can ping hosts on the network after setenv ethaddr and ipaddr.

but if i try to boot the kernel over nfs (i used this args: console=ttyS0,115200 mtdparts=atmel_nand:128k(bootstrap),512k(uboot),256k(ubootenv),3200k(kernel),60M@4M(rootfs),-(userfs) ubi.mtd=rootfs ubi.mtd=userfs root=/dev/nfs nfsroot=172.16.0.78:/exports/nfsroot-cc9cjsnand ip=172.16.0.191:172.16.0.78:172.16.0.251:255.255.255.0::eth0:) it doesn't find the nfs server:

Code:

MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:26:3c:00:00:01)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
...
TCP cubic registered
NET: Registered protocol family 17
IP-Config: Complete:
     device=eth0, addr=172.16.0.191, mask=255.255.255.0, gw=172.16.0.251,
     host=172.16.0.191, domain=, nis-domain=(none),
     bootserver=172.16.0.78, rootserver=172.16.0.78, rootpath=
Looking up port of RPC 100003/2 on 172.16.0.78
eth0: link up (100/Full)
rpcbind: server 172.16.0.78 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 172.16.0.78
rpcbind: server 172.16.0.78 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
Root-NFS: Server returned error -5 while mounting /exports/nfsroot-cc9cjsnand
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

other linux boxes can mount the nfs-share. u-boot can ping the nfs server quite before booting the kernel.

if i run tcpdump on the nfs server i can see the ping from uboot, but i can't see any further packets from the linuxkernel.

i'll selected "Olimex SAM9-L9260 board" in "Atmel AT91 System-on-Chip --->" and also the networkcard.

does anyone know what i did wrong?

koan · **Posted:** Wed Feb 17, 2010 3:27 pm

Ghostie wrote:

other linux boxes can mount the nfs-share. u-boot can ping the nfs server quite before booting the kernel.

if i run tcpdump on the nfs server i can see the ping from uboot, but i can't see any further packets from the linuxkernel.

i'll selected "Olimex SAM9-L9260 board" in "Atmel AT91 System-on-Chip --->" and also the networkcard.

does anyone know what i did wrong?

Which board are you using ?

If you have triple-checked the NFS server configuration, I guess you are facing to problems with your ethernet on target-side verify PHY settings ([Generic PHY] sounds wrong) and ethernet too.

falingtrea · **Posted:** Wed Feb 17, 2010 8:49 pm

I have a RFS on my linux box at exported directory /nfs_tssroot. the bootcmd I use for this is:

bootargs=mem=64M root=/dev/nfs_tsroot nfsroot=192.168.2.2:/nfs_tsroot ip=192.168.2.1 console=ttyS0,115200'

So maybe your root should be /dev/exports/nfsroot-cc9cjsnand ?

Ghostie · **Joined:** Wed Feb 17, 2010 12:32 pm **Posts:** 4

my board is "olimex-SAM9-L9260": http://www.olimex.com/dev/sam9-L9260.html

maybe the boot parameters aren't "good", but they're working with the original olimex kernel (and the nfs-server also!). but i can't use this kernel because it doesn't support ubifs.

generic_phy or ethernet are no problem i think. the card get's detected and configured as you can see in kernel output. it even detect's the link. the card is included via CONFIG_MACB=y.

but i will try the bootargs from koan and i will try disabling generic_phy and ethernet tomorrow.

koan · **Posted:** Thu Feb 18, 2010 9:46 am

Ghostie wrote:

my board is "olimex-SAM9-L9260": http://www.olimex.com/dev/sam9-L9260.html

maybe the boot parameters aren't "good", but they're working with the original olimex kernel (and the nfs-server also!). but i can't use this kernel because it doesn't support ubifs.

This may well be the problem: who modified the new kernel vanilla sources (2.6.32.7) adding the patch required by the platform you are using (SAM9-L9260)?
Please post dmesg of the working kernel too.

Ghostie · **Joined:** Wed Feb 17, 2010 12:32 pm **Posts:** 4

like i wrote: it is vanilla kernel without any patches. this board is "directly supported".

i solved the problem: the patch on the olimex page worked also with the new kernel version.

thanks.

koan · **Posted:** Thu Feb 18, 2010 10:51 am

Just for reference that may help others. could you tell us what was the problem?

Ghostie · **Joined:** Wed Feb 17, 2010 12:32 pm **Posts:** 4

hmmm... the problem:

vanilla kernel sources didn't manage the macb phy on the olimex board without patching the kernel with patches from the olimex webpage.

the confusing thing is that current vanilla kernel sources are supporting this board (you can choose exactly this board in menuconfig), but the networkdriver don't work without patch.

trontheim · **Joined:** Wed Aug 31, 2011 2:30 pm **Posts:** 7

Hi,
perhaps this is long resolved. here my 2 cents worth as a newbie:
I could not get the board to successfully boot off the JSFF2 file system in the Dataflash. In fact I could not successfully load the dataflash, in spite of following the instructions in the SAM9-L9260 development board Users Manual, Restoring the on-board root filesystem.
I managed to get it to boot without "Kernel Panic" (whatever that is!) by using the file system described under "Running with another root filesystem" off a USB formatted as ext. 3.
I'm having issues with Samba and the Olimex board, and uploading a redboot ROM monitor. I'm beginning to think the Olimex boards are defective.

olimex-sam9-l9260: can't boot over nfs.

Who is online