Re: PandaboardES NFS Issue

[Andrei]

I would like to mention that during the entire boot sequence, I do not see the ethernet lights flashing at all on the pandaboard, leading me to believe that the interface isn't up.


Any ideas please?


On Saturday, September 29, 2012 7:37:00 PM UTC-7, Andrei wrote:

Hi All,

I am having some issues using NFS as a file system and I would like your input.
I tried mounting the nfs share on another linux box with no issues.
1. Building the kernel.
I built the kernel and enabled NFS and booting from it as well as the smsc95xx driver to be compiled into the kernel rather than a module.


I am using U-boot to boot the zImage from the SDcard. The boot arguments for the kernel are as follows:
set bootargs console=ttyO2,115200n8 console=tty0 smsc95xx.macaddr=86:63:11:5e:60:86 root=/dev/nfs rw nfsroot=192.168.0.5:/panda_fs ip=192.168.0.12 rootdelay=2

I have pasted what seems to be the important bit of the boot output.

[    3.402679] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    3.412292] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.422760] hub 1-1:1.0: USB hub found
[    3.429290] hub 1-1:1.0: 5 ports detected
[    3.451416] mmc1: card claims to support voltages below the defined range. These will be ignored.
[    3.484100] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
[    3.493347] mmc1: new SDIO card at address 0001
[    3.719146] usb 1-1.1: new high-speed USB device number 3 using ehci-omap
[    3.844421] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.854034] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  123.258056] IP-Config: Guessing netmask 255.255.255.0
[  123.265777] IP-Config: Complete:
[  123.271392]      device=usb0, addr=192.168.0.12, mask=255.255.255.0, gw=255.255.255.255,
[  123.281982]      host=192.168.0.12, domain=, nis-domain=(none),
[  123.290557]      bootserver=255.255.255.255, rootserver=192.168.0.5, rootpath=
[  428.679992] VFS: Unable to mount root fs via NFS, trying floppy.
[  428.688964] VFS: Cannot open root device "nfs" or unknown-block(2,0)
[  428.697998] Please append a correct "root=" boot option; here are the available partitions:
[  428.711456] b300        15558144 mmcblk0  driver: mmcblk
[  428.719451]   b301           65536 mmcblk0p1 00000000-0000-0000-0000-000000000000
[  428.732208]   b302        15491072 mmcblk0p2 00000000-0000-0000-0000-000000000000
[  428.744995] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

If I set the bootargs ip to dhcp, the kernel output becomes
[  123.242462] Sending DHCP requests ...... timed out!
[  203.469940] IP-Config: Retrying forever (NFS root)...
[  203.478088] ADDRCONF(NETDEV_UP): usb0: link is not ready
[  323.508087] Sending DHCP requests ...... timed out!
[  398.969848] IP-Config: Retrying forever (NFS root)...

If I look in my router DHCP lease table, I do not see an entry for the mac address I specified. Also during the boot process, if I try to ping the address of the board, I do not get a reply

Any ideas would very much be appreciated.

Thanks.

[Nicolas Dechesne]

On Sun, Sep 30, 2012 at 4:37 AM, Andrei <adan...@andreisoft.com> wrote:
> [ 123.290557] bootserver=255.255.255.255, rootserver=192.168.0.5,

> rootpath=
> [ 428.679992] VFS: Unable to mount root fs via NFS, trying floppy.

your problem is because of ^^. you don't seem to have all the right
CONFIG to boot with NFS. not sure what you've done, but that's the
original error. the rest happens because of this error. are you sure
that you exported your folder from you server? You should first check
that you can mount your root fs using 'sudo mount -t nfs xxx'...

[Andrei]

I am not sure that is the problem, if I set the ip in bootargs to DHCP, on my router's DHCP table I should see a new IP being leased and I don't.

Moreover when I do set ip=dhcp that I see the following error " [  203.478088] ADDRCONF(NETDEV_UP): usb0: link is not ready. Leading me to believe that the interface isn't up.

When pandaboard attempts to obtain a new ip address over DHCP, should I not see the LEDs on the ethernet port flash? They currently don't.

I tried mounting the nfs by hand on a different system with no issues.

Thanks

[Sebastien Jan]

Did you try to use rootwait instead of rootdelay=2? maybe 2s is not enough for this interface to come up?

[Andrei]

I used the following kernel args:

mmc rescan;fatload mmc 0:1 0x80300000 zImage;set bootargs console=ttyO2,115200n8 console=tty0 smsc95xx.macaddr=86:63:11:5e:60:86 root=/dev/nfs rw nfsroot=192.168.0.5:/panda_fs ip=dhcp rootwait=1 nfsdebug=1;bootz 0x80300000

with the same log

[    3.155059] regulator_init_complete: VDAC: incomplete constraints, leaving on
[    3.165557] regulator_init_complete: VUSB: incomplete constraints, leaving on
[    3.175567] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    3.185882] ADDRCONF(NETDEV_UP): usb0: link is not ready
[    3.364562] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    3.374176] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.384674] hub 1-1:1.0: USB hub found
[    3.391174] hub 1-1:1.0: 5 ports detected
[    3.681182] usb 1-1.1: new high-speed USB device number 3 using ehci-omap
[    3.806304] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.815917] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  123.220031] Sending DHCP requests ...... timed out!
[  212.994354] IP-Config: Retrying forever (NFS root)...
[  213.002410] ADDRCONF(NETDEV_UP): usb0: link is not ready

[dmitry pervushin]

Andrei,

What kernel are you using? The interface name usb0 looks suspicious
(read: your kernel is old), 'cause newer kernels announce the interface
of smsc95xx as ethX but not as usbX.

> *[ 123.220031] Sending DHCP requests ...... timed out!
> [ 212.994354] IP-Config: Retrying forever (NFS root)...*
> *[ 213.002410] ADDRCONF(NETDEV_UP): usb0: link is not ready*

- Are you using proper cable?
- Do you have smsc95xx driver compiled into the kernel? (grep SMSC95XX
.config should show line "CONFIG_USB_NET_SMSC95XX=y")

> Moreover when I do set ip=dhcp that I see the following error "
> [ 203.478088] ADDRCONF(NETDEV_UP): usb0: link is not ready.
> Leading me to believe that the interface isn't up.

Yes, and this might happen by two reasons:
- no link (== bad cable)
- no driver (check the .config)

> When pandaboard attempts to obtain a new ip address over DHCP,
> should I not see the LEDs on the ethernet port flash? They
> currently don't.

Of course you should see green led flashing and orange led lighting.

> I tried mounting the nfs by hand on a different system with no
> issues.
>
> Thanks
> On Monday, October 1, 2012 4:18:30 AM UTC-7, ndec wrote:
>
> On Sun, Sep 30, 2012 at 4:37 AM, Andrei
> <adan...@andreisoft.com> wrote:
> > [ 123.290557] bootserver=255.255.255.255,
> rootserver=192.168.0.5,
> > rootpath=
> > [ 428.679992] VFS: Unable to mount root fs via NFS,
> trying floppy.
>
> your problem is because of ^^. you don't seem to have all
> the right
> CONFIG to boot with NFS. not sure what you've done, but
> that's the
> original error. the rest happens because of this error. are
> you sure
> that you exported your folder from you server? You should
> first check
> that you can mount your root fs using 'sudo mount -t nfs
> xxx'...
>

--
Sincerely yours,
dmitry pervushin

[Andrei]

You are completely correct, the kernel version I was using was old, I switched to 3.4 and everything worked correctly and the NFS was mounted.


Thanks Dmitry.

-Andrei