Hi Vic,
I had the same issue with my FDI board trying to mount the rootfs with
NFS. I solved defining (in my own case)
uboot> setenv build_param 'setenv bootargs console=ttyTX0,115200n81
root=/dev/nfs rw
nfsroot=192.168.100.84:/home/jcastro/ltib/rootfs,wsize=1500,rsize=1500
ip=192.168.100.85
ethaddr=${ethaddr} init=/sbin/init'
and then
uboot> run build_param
uboot> saveenv
In this way I specify the ethaddr in the bootargs, which it seems to be
necesary to the LPC and newer kernel distributions. Also I take
specific care of the /etc/exports ensuring to have my direct roofs and
not a link to it (I don't know exacttly how or why but it make a
difference). I have it like:
/home/jcastro/ltib/rootfs
192.168.100.*(rw,no_root_squash,no_subtree_check,async)
I hope it can help you with this.
Regard.
Jorge Castro.
P.S.: Here is my complete uboot variables
baudrate=115200
ethaddr=00:1a:f1:00:00:00
bootcmd=tftpboot; bootm
bootfile=uImage
loadaddr=0x80100000
bootdelay=2
serverip=192.168.100.84
ipaddr=192.168.100.85
gatewayip=192.168.100.50
netmask=255.255.255.0
root=/dev/nfs
bootargs=console=ttyTX0,115200n81 root=/dev/nfs rw
nfsroot=192.168.100.84:/home/jcastro/ltib/rootfs,wsiz
e=1500,rsize=1500 ip=192.168.100.85 ethaddr=00:1a:f1:00:00:00
init=/sbin/init
stdin=serial
stdout=serial
stderr=serial
On 10/08/2010 10:21 AM, vic wrote:
Hi Kevin,
I'm not at my workbench but as far as I remember my nfsboot differs
from yours in that it has ... ea_ethaddr=$(ethaddr) instead of
ethaddr=$(ethaddr). Does that make a difference? I mean it works fine
in 2.6.27.8. Anyway, will confirm it in the morning.
Regards,
Vic
Hi Vic,
Check to make sure the 'ethaddr' parameter is passed on the command
line to your kernel.
Something like this:
console=ttyS0,115200n8 root=/dev/nfs rw
nfsroot=192.168.1.41:/home/usb10132/dev/ltib/rootfs ethaddr=${ethaddr}
ip=dhcp
thanks,
Kevin
> Subject: Re: Problem using 2.6.34 in EA 3250
>
> Hi Kevin,
>
> Now able to successfully compile 2.6.34 but when I boot the kernel
it's
> unable to configure eth0 as below. Booting with 2.6.37.8 remains
fine
> using
> same configuration. I'm using nfs mounted root file system.
>
> ...
> TCP cubic registered
> NET: Registered protocol family 17
> ssp-pl022 dev:ssp0: ARM PL022 driver, device ID: 0x00041022
> pl022: mapped registers from 0x20084000 to c4882000
> ads7846 spi0.0: touchscreen, irq 64
> input: ADS7846 Touchscreen as /class/input/input0
> CLCD: Embedded Artists 3.2 inch LCD hardware, QVGA portrait display
> Console: switching to colour frame buffer device 30x40
> VFP support v0.3: implementor 41 architecture 1 part 10 variant 9
rev 1
> rtc-lpc32xx rtc-lpc32xx: setting system clock to 2059-04-12
10:56:18 UTC
> (2817370578)
> IP-Config: Failed to open eth0
> IP-Config: No network devices available.
> Looking up port of RPC 100003/2 on 192.168.1.6
> rpcbind: server 192.168.1.6 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on 192.168.1.6
> rpcbind: server 192.168.1.6 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using
default
> Root-NFS: Server returned error -101 while mounting
/home/user/ltib/rootfs
> 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:
> 1f00 3200 mtdblock0 (driver?)
> 1f01 12800 mtdblock1 (driver?)
> 1f02 256 mtdblock2 (driver?)
> 1f03 4096 mtdblock3 (driver?)
> 1f04 110720 mtdblock4 (driver?)
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
> Backtrace:
> [] (dump_backtrace+0x0/0x108) from []
> (dump_stack+0x18/0x1c)
> r6:00000000 r5:c3c9a017 r4:c3c19f60
> [] (dump_stack+0x0/0x1c) from []
(panic+0x5c/0xf8)
> [] (panic+0x0/0xf8) from []
> (mount_block_root+0x1d4/0x21c)
> r3:00000000 r2:c3c18000 r1:c3c19f60 r0:c0356d6c
> [] (mount_block_root+0x0/0x21c) from []
> (mount_root+0xc4/0xfc)
> [] (mount_root+0x0/0xfc) from []
> (prepare_namespace+0x170/0x1d4)
> r5:c0022a08 r4:c03cb278
> [] (prepare_namespace+0x0/0x1d4) from []
> (kernel_init+0x11c/0x160)
> r5:00000000 r4:c03cb058
> [] (kernel_init+0x0/0x160) from []
(do_exit+0x0/0x684)
> r4:00000000
>
> Regards,
> Vic
>
>
> ----- Original Message -----
> From: "Vic"
> To: "Kevin Wells"
> Cc: "ltib mail"
> Sent: Thursday, October 07, 2010 9:49 PM
> Subject: Re: Problem using 2.6.34 in EA 3250
>
>
> > Hi Kevin,
> >
> > Question is, why only in 2.6.34? I'm fine compiling with
2.6.27.8. They
> > are both in GPP, right? It has always been my issue from the
start. it
> > always get stuck in this file. Apparently the url in the
installer
> script
> > URL:http://bitshrine.org/gpp/tc-fsl-x86lnx-armeabi-nptl-4.1.2-
> 3.i386.rpm.md5
> > is no longer a valid location.
> > Is there any other place I can manually retrieve the file?
> >
> > Thanks,
> > Vic
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Kevin Wells"
> > To: "Vic" ;
> > Sent: Thursday, October 07, 2010 6:10 PM
> > Subject: RE: Problem using 2.6.34 in EA 3250
> >
> >
> > Hi Vic,
> >
> >> ERROR: md5sum mismatch, re-naming
/opt/ltib/pkgs/linux-2.6.34.tar.bz2
> to
> >> /opt/ltib/pkgs/linux-2.6.34.tar.bz2.bad, please re-try
> >
> > It looks like some of your files in the ./opt/ltib/pkgs
> > directory are corrupt or incomplete. When you see these
> > messages, you can try to delete the files in that directory
> > with the similar names and try again, but it might be an
> > indication your network is having problems fetching them.
> >
> > Kevin
> >
> >
> >> -----Original Message-----
> >> From: Vic [mailto:address@hidden]
> >> Sent: Thursday, October 07, 2010 8:33 PM
> >> To: address@hidden
> >> Cc: Kevin Wells
> >> Subject: Re: Problem using 2.6.34 in EA 3250
> >>
> >> Hi Kevin,
> >>
> >> I think there is basic problem with installing 2.6.34
from the error
> >> trace
> >> I'm getting. It keeps on referring to a mismatch as
follows.
> >> ...
> >> Processing: kernel-2.6.34-lpc32xx
> >> ===================================
> >> Build path taken because: no prebuilt rpm,
> >> Testing network connectivity for gpp
> >> OK GPP: is available
> >> Try linux-2.6.34.tar.bz2 from the GPP
> >> ERROR: md5sum mismatch, re-naming
/opt/ltib/pkgs/linux-2.6.34.tar.bz2
> to
> >> /opt/ltib/pkgs/linux-2.6.34.tar.bz2.bad, please re-try
> >> Can't get: linux-2.6.34.tar.bz2 at ./ltib line 802.
> >>
> >>
> >> f_buildrpms() returned an error, exiting
> >> traceback:
> >> main:567
> >>
> >>
> >> Started: Thu Oct 7 19:55:17 2010
> >> Ended: Thu Oct 7 19:57:49 2010
> >> Elapsed: 152 seconds
> >>
> >> VERSION : 10.1.1
> >> CVS_VERSION : $Revision: 1.71 $ (Savannah)
> >> PLATFORM : ea3250
> >> GNUTARCH : arm
> >> TOOLCHAIN : tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm
> >> TOOLCHAIN_CFLAGS : -O2 -fsigned-char -mfloat-abi=softfp
-mfpu=vfp
> >>
> >> These packages failed to build:
> >> kernel-2.6.34-lpc32xx
> >>
> >> Build Failed
> >>
> >> Exiting on error or interrupt
> >>
> >> Regards,
> >> Vic
> >>
> >>
> >>
> >
> >
>
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib
--
Jorge A. Castro
Canam-Technology, Inc.
|