Hi
Quentin,
There is a change in way of passing the MAC address in Ethernet driver between
2.6.27.8 & 2.6.34.
In 2.6.27.8 kernel, the ethernet driver MAC address was hardcoded in EA3250 platform
code (arch/arm/mach-lpc32xx/board-ea3250.c file).
But this is changed in 2.6.34 kernel. Now you need to pass the MAC address for
your Ethenet device in kernel command line.
Pass the MAC address in kernel command line as shown below:
ethaddr=<MAC address>
With
kind regards,
Giri
-----------------------------------------------------------------
Bangaragiri
G
BU-High
Performance Mixed Signal (BU-HPMS)
NXP
Semiconductors India Private Limited
Manyata
IT park , Nagawara Village, Bangalore, India - 560045
Tel:
+91-80-40247692, Fax: +91-80-40247855, Mobile: +91-9972583803
E-mail:
address@hidden
From: Quentin YANG
[mailto:address@hidden
Sent: 2010 Jul 19 8:18 AM
To: Bangaragiri G
Cc: address@hidden; Srinivas Bakki
Subject: Re: [Ltib] Phytec LPC32xx Board Failed to mount RFS after using
Kernel 2.6.34 ?
Hi Srinivas&Bangaragiri,
After restoring the default kernel config ' linux-2.6.34-phy3250.config ' and
enabled NFS client.
I am still having trouble to mount the Rootfs from linux NFS server.
In order to to ensure that I had the NFS server set up correctly and all
network connections are right.
I rebuilt with 'linux-2.6.27.8-phy3250.config', Phytec LPC3250 board could run
all the way to Linux console prompt ' address@hidden /]# ' without any
problems.
I've attached the logs, 'Linux Kernel Config' and 'LTIB make configuration'
that I used for your reference.
Thanks.
Regards,
Quentin
On Fri, Jul 16, 2010 at 4:38 PM, Quentin YANG <address@hidden> wrote:
Thanks very much. Giri.
Because of those annoying 'command-line' kernel config confirmation question
after exiting kernel config GUI, I must accidently typed 'no' for " [ ]
Enable POSIX file locking API " question,
so my kernel config GUI menu totally screwed up.
That's why I could not see <> NFS client support anymore.
I applied 'linux-2.6.34-phy3250.config', now things back on track.
Thanks and will post my update soon.
Regards,
Quentin
On Fri, Jul 16, 2010 at 4:07 PM, Bangaragiri G <address@hidden>
wrote:
Hi Quentin,
I can see that NFS support is
enabled in default PHYTEC 3250 configuration in LTIB GUI:
1. Execute ./ltib -c to get the LTIB
configuration
2. Enable the "Configure the
Kernel" option in GUI. This will provide the Kernel configuration GUI
before it builds the kernel.
3. In Kernel configuration GUI, you can
see " File Systems->NFS", enable the NFS options which are required
You can find the the kernel configuration file
created by LTIB in /ltib/config/platform/phy3250/linux-2.6.34-phy3250.config.
Regards,
Giri
-----------------------------------------------------------------
Bangaragiri G
BU-High Performance Mixed Signal (BU-HPMS)
NXP Semiconductors India Private Limited
Manyata IT park , Nagawara Village, Bangalore, India
- 560045
From:
Quentin YANG [mailto:address@hidden]
Sent: 2010 Jul 16 11:02 AM
To: Bangaragiri G; Srinivas Bakki
Cc: address@hidden
Subject: Re: [Ltib] Phytec LPC32xx Board Failed to mount RFS after using
Kernel 2.6.34 ?
Hi
Giri,
Thanks for asking me about my Phytec Board Adventure.
As recommended by Srinivas, I've been trying to get 2.6.34 running on Phytec
board.
Still not winning yet.
I am using LTIB tool to build the kernel. (Did not try using make command.)
One thing I learned was 'I have to use Tool Chain --
"tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm" in PATH
"/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi".
I failed kernel build after error message "cc1: error: invalid option
`abi=aapcs-linux' " when using Tool Chain --
"tc-nxp-lnx-arm-3.4.5-1.i386.rpm" in PATH "/opt/nxp/gcc-3.4.5-glibc-2.3.6/arm-linux-gnu"
( After googling error "cc1: error: invalid option
`abi=aapcs-linux'", it looks I have to disable 'eabi support' when using
Tool Chain -- "tc-nxp-lnx-arm-3.4.5-1.i386.rpm". which I did not do
further test. )
Anyway, I successfully compiled 2.6.34 kernel for Phytec board using Tool Chain
-- "tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm".
But for some reasons, which I am trying to find out, Phytec board could not
mount rootfs.
I ATTACHED THE PHYTEC BOARD SERIAL PRINT FOR YOUR REFERENCE.
I could not see following lines in kernel .config of 2.6.34, which is my main
worry now.
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
I tried to get 'CONFIG_ROOT_NFS=y' in LTIB kernel config GUI.
HELP SHOWS:
Symbol: ROOT_NFS
[=n]
Prompt: Root file system on
NFS
Defined at
fs/nfs/Kconfig:86
Depends on: NETWORK_FILESYSTEMS [=y] && NFS_FS
[=n]=y [=y] && IP_PNP [=y]
Location:
-> File
systems
-> Network File Systems
(NETWORK_FILESYSTEMS
[=y])
-> NFS client support
(NFS_FS [=n])
But in LTIB 2.6.34 Kernel config GUI, I only get this
--- Network File
Systems
< > SMB file system support (OBSOLETE, please
use CIFS)
< > Ceph distributed file system
(EXPERIMENTAL)
< > CIFS support (advanced network filesystem,
SMBFS successor)
< > NCP file system support (to mount NetWare
volumes)
< > Coda file system support (advanced network
fs)
< > Andrew File System support (AFS)
(EXPERIMENTAL)
I am bit lost what to do now.
Don't know WHERE TO SET "CONFIG_ROOT_NFS" in LTIB GUI.
I manually added above lines in .config, but they were always removed after
running './ltib'
Hope you can point me to the right direction.
Regards,
Quentin
On
Fri, Jul 16, 2010 at 2:29 PM, Bangaragiri G <address@hidden>
wrote:
Hi Quentin,
How are u building the kernel? Are uy trying to
build the kernel alone by using make command (in kernel tree)?
If you are trying to build the kernel by using
make command in kernel tree, please set the cross compilation tool chain path
in PATH variable.
Regards,
Giri
----------------------------------------------------------------
Bangaragiri G
Tel: +91-80-40247692, Fax: +91-80-40247855, Mobile:
+91-9972583803
E-mail: address@hidden
From:
ltib-bounces+bangaragiri.g=nxp.com@nongnu.org [mailto:ltib-bounces+bangaragiri.g=nxp.com@nongnu.org] On Behalf Of Quentin YANG
Sent: 2010 Jul 16 6:05 AM
To: address@hidden
Subject: [Ltib] How to skip command-line question based kernel
configuration when doing Kernel 2.6.34 configuration for Phytec LPC32xx board ?
Hi,
Regarding latest Linux Kernel configuration when chosing
"Kernel_2.6.34" for Phytec board.
WHY LTIB is STILL ASKING THE KERNEL CONFIGURATION in COMMAND-LINE after I've
finished all kernel configuratino in GUI?
Very time consuming to go through and answer each question.
Can anyone tell me how to skip these command-line questions AS SHOWN
BELOW? Thanks a lot.
.................................
Add support for standard UART3 (ARCH_LPC32XX_UART3_SELECT) [N/y/?] (NEW) n
Add support for standard UART4 (ARCH_LPC32XX_UART4_SELECT) [N/y/?] (NEW) n
Add support for standard UART5 (ARCH_LPC32XX_UART5_SELECT) [Y/n/?] (NEW) n
Add support for standard UART6 (ARCH_LPC32XX_UART6_SELECT) [N/y/?] (NEW) n
*
* High speed UARTS
*
Add support for high speed UART1 (ARCH_LPC32XX_HSUART1_SELECT) [N/y/?] (NEW) n
Add support for high speed UART2 (ARCH_LPC32XX_HSUART2_SELECT) [N/y/?] (NEW) n
Add support for high speed UART7 (ARCH_LPC32XX_HSUART7_SELECT) [N/y/?] (NEW) n
*
* LPC32XX chip components
*
Use IRAM for network buffers (ARCH_LPC32XX_IRAM_FOR_NET) [N/y/?] (NEW) n
Check to enable MII support or leave disabled for RMII support
(ARCH_LPC32XX_MII_SUPPORT) [N/y/?] (NEW) y
*
* Processor Type
*
*
* Processor Features
*
Support Thumb user binaries (ARM_THUMB) [Y/n/?] y
Disable I-Cache (I-bit) (CPU_ICACHE_DISABLE) [N/y/?] n
Disable D-Cache (C-bit) (CPU_DCACHE_DISABLE) [N/y/?] n
Force write through D-cache (CPU_DCACHE_WRITETHROUGH) [N/y/?] n
Round robin I and D cache replacement algorithm (CPU_CACHE_ROUND_ROBIN) [N/y/?]
n
*
* Kernel Features
*
Tickless System (Dynamic Ticks) (NO_HZ) [N/y/?] n
High Resolution Timer Support (HIGH_RES_TIMERS) [N/y/?] n
Memory split
> 1. 3G/1G user/kernel split (VMSPLIT_3G) (NEW)
2. 2G/2G user/kernel split (VMSPLIT_2G) (NEW)
3. 1G/3G user/kernel split (VMSPLIT_1G) (NEW)
............................................
Regards,
Quentin