Thanks for the inputs,
We are still in the process of debugging the nfs mounting for our target board,
there were Tx clock and Rx clock pins in our board were different as compared to MPC8272ADS board and we configured PC_F2RXCLK and PC_F2TXCLK macro,s accordingly in \arch\ppc\8260_io\fcc_enet.c.
still nfs is not up.. same error " Root-NFS: Server returned error -5 while mounting /opt/montavista/pro/devkit/ppc//82xx/target" is comming up.
We verified " immr->im_cpmux.cmx_fcr = 0x2c0000" reg value both in bootloader and kernel, both are same but ethernet works in u-boot and does not work in kernel.
Please suggest how we can attack this problem.
Thanks
Manjunath AM
| Andre Haupt <haupt.andre@xxxxxx>
Sent by: linuxppc-embedded-bounces+manjunath.am=lntemsys.com@xxxxxxxxxx 01/24/2007 01:40 PM |
|
Scott Wood wrote:
> Andre Haupt wrote:
>> Also what seems a bit odd to me is that your dmesg shows no rootpath
>>
>> IP-Config: Complete:
>> device=eth1, addr=192.168.178.234, mask=255.255.255.0,
>> gw=192.168.178.47,
>> host=cashel, domain=, nis-domain=(none),
>> bootserver=192.168.178.110, rootserver=192.168.178.110, rootpath=
>>
>> On my system the complete root path is printed here.
>
> I don't think I've ever seen the root path printed there (with nfsroot
> otherwise working), so I don't think that's the problem... From
> looking at the code, it seems that the root path received from BOOTP
> is stored in a different variable than the path from the nfsroot boot
> option, and it's the former that gets printed there.
Ahh, ok. I am using BOOTP, so this has nothing to do with Manjunaths
problem. Thanks for clarification.
Best,
Andre
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@xxxxxxxxxx
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
