RE: [Ltib] RE: Linux 2.6.34 for FDI board and NFS issue

[Daniel Widyanto]

Hi Jorge,

Mike's suggestion is correct. The LPC32xx ethernet driver needs ethaddr from 
the bootargs. For Linux-2.6.27.8, the 'ethaddr' is stored in SPI EEPROM. For 
Linux-2.6.34, the 'ethaddr' is stored in u-boot environment.

From your boot log, it seems like the 'ethaddr' is not set properly:
---------------------------------------------------
Kernel command line: console=ttyTX0,115200n8 root=/dev/nfs rw 
nfsroot=192.168.100.84:/tftpboot/rootfs,wsize=1500,rsize=1500 ethadd
r=${ethaddr} ip=dhcp init=/sbin/init
---------------------------------------------------

Regards,
-daniel

> -----Original Message-----
> From: address@hidden [mailto:ltib-
> address@hidden On Behalf Of Mike Nelson
> Sent: Wednesday, September 29, 2010 6:51 AM
> To: Kevin Wells
> Cc: address@hidden
> Subject: Re: [Ltib] RE: Linux 2.6.34 for FDI board and NFS issue
> 
> Kevin:
> 
> I have been told by others on this list that for 2.6.34 the bootargs
> need an additional argument, ethaddr.  For example:
> 
> bootargs=console=ttyS0,115200n81 root=/dev/mtdblock4 rw
> rootfstype=jffs2 ip=dhcp init=/sbin/init ethaddr="xx:xx:xx:xx:xx:xx"
> 
> Where xx:xx:xx:xx:xx:xx in the Ethernet MAC or hardware address, not
> the IP address.
> 
> Regards:
> 
> Mike Nelson, http://michaeltnelson.com
> mobile: 1-650-291-7343
> office: 1-650-257-7565