It's a very stupid error. In the exports file, I've put a space between the IP and the arguments so the rw wasn't enable. The nfs directory was mount in read only mode.
Sorry for the time you loose. -----Message d'origine----- De : ptxdist-boun...@pengutronix.de [mailto:ptxdist-boun...@pengutronix.de] De la part de Yannick Granger Envoyé : mercredi 25 février 2009 15:48 À : Juergen Beisert Objet : Re: [ptxdist] nfs boot problem > > /tftpboot/nfsroot is a link to > > /home/yannickG/OSELAS.BSP-Phytec-phyCORE-9/platform-phyCORE-i.MX27/root > > This is a huge security hole and your NFS server ignore the link! > This is the reason, why it does not work. I'm using until months this configuration with ADS platform without any problem. I did the changin /etc/exports and in uboot conf file. And I obtain the same mistake. ---------------------------------------------------------------------------------------------- Hit any key to stop autoboot: 0 Image Name: Linux-2.6.27-ptx-mxc3 Created: 2009-02-25 9:09:49 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1966952 Bytes = 1.9 MB Load Address: a0008000 Entry Point: a0008000 OK commandline: console=ttymxc0,115200 ip=192.168.87.51:192.168.87.21:192.168.87.252:255.255.255.0::: root=/dev/nfs nfsroot=192.168.87.21:/home/yannickG/OSELAS.BSP-Phytec-phyCORE-9/platform-phyCORE-i.MX27/root/,v3,tcp mtdparts=physmap-flash.0:256k(uboot)ro,128k(ubootenv),2M(kernel),-(root);mxc_nand:256k(uboot)ro,128k(ubootenv),2M(kernel),-(root) arch_number: 1551 Starting kernel ... Uncompressing Linux............................................................................................................................... done, booting the kernel. Linux version 2.6.27-ptx-mxc3 (yann...@yannickportable) (gcc version 4.3.2 (OSELAS.Toolchain-1.99.2) ) #2 PREEMPT Wed Feb 25 10:09:43 CET 2009 CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177 Machine: phyCORE-i.MX27 Revision 020 Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: console=ttymxc0,115200 ip=192.168.87.51:192.168.87.21:192.168.87.252:255.255.255.0::: root=/dev/nfs nfsroot=192.168.87.21:/home/yannickG/OSELAS.BSP-Phytec-phyCORE-9/platform-phyCORE-i.MX27/root/,v3,tcp mtdparts=physmap-flash.0:256k(uboot)ro,128k(ubootenv),2M(kernel),-(root);mxc_nand:256k(uboot)ro,128k(ubootenv),2M(kernel),-(root) MXC GPIO hardware MXC IRQ initialized PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 125696KB available (3696K code, 247K data, 108K init) Calibrating delay loop... 199.06 BogoMIPS (lpj=995328) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 288 bytes NET: Registered protocol family 16 SCSI subsystem initialized CSPI: mxc_spi-0 probed usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb mc13783 Rev 3.3 FinVer 0 detected Device spi0.0 probed PMIC Power successfully probed NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NET: Registered protocol family 1 i.MX cpu freq change driver v0.1 Regulator error? Ignore this message ;-) JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. fuse init (API version 7.9) msgmni has been set to 245 io scheduler noop registered (default) i.MX Framebuffer driver Console: switching to colour frame buffer device 30x40 Serial: IMX driver imx-uart.0: ttymxc0 at MMIO 0x1000a000 (irq = 20) is a IMX console [ttymxc0] enabled imx-uart.1: ttymxc1 at MMIO 0x1000b000 (irq = 19) is a IMX imx-uart.2: ttymxc2 at MMIO 0x1000c000 (irq = 18) is a IMX vcan: Virtual CAN interface driver CAN netdevice library sja1000 CAN netdevice driver sja1000 sja1000.0: sja1000 device registered (base_addr=0xc885a000, irq=211) FEC ENET Version 0.2 fec: PHY @ 0x0, ID 0x00221613 -- KS8721BL eth0: ethernet 00:50:c2:5e:00:6c Linux video capture interface: v2.00 usbcore: registered new interface driver uvcvideo USB Video Class driver (v0.1.0) Driver 'sd' needs updating - please use bus_type methods physmap platform flash device: 02000000 at c0000000 physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method Using auto-unlock on power-up/resume cfi_cmdset_0001: Erase suspend on write enabled 4 cmdlinepart partitions found on MTD device physmap-flash.0 Creating 4 MTD partitions on "physmap-flash.0": 0x00000000-0x00040000 : "uboot" 0x00040000-0x00060000 : "ubootenv" 0x00060000-0x00260000 : "kernel" 0x00260000-0x02000000 : "root" MXC MTD nand Driver NAND device: Manufacturer ID: 0x20, Chip ID: 0x36 (ST Micro NAND 64MiB 1,8V 8-bit) Scanning device for bad blocks RedBoot partition parsing not available 4 cmdlinepart partitions found on MTD device mxc_nand Creating 4 MTD partitions on "mxc_nand": 0x00000000-0x00040000 : "uboot" 0x00040000-0x00060000 : "ubootenv" 0x00060000-0x00260000 : "kernel" 0x00260000-0x04000000 : "root" mxc-ehci mxc-ehci.1: initializing i.MX USB Controller ULPI Vendor ID 0x4cc Product ID 0x1504 mxc-ehci mxc-ehci.1: Freescale On-Chip EHCI Host Controller mxc-ehci mxc-ehci.1: new USB bus registered, assigned bus number 1 mxc-ehci mxc-ehci.1: irq 55, io mem 0x10024400 mxc-ehci mxc-ehci.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice rtc-pcf8563 1-0051: chip found, driver version 0.4.3 rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc0 at24 1-0052: 4096 byte at24 EEPROM (writable) Driver for 1-wire Dallas network protocol. Serial: MXC OWire driver PMIC Audio driver loading... VPU initialized i.MX mmc driver usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.17. Probing i.MX DAM unit Probing i.MX SSI unit 0 Probing i.MX SSI unit 1 mc13783_enable called ALSA device list: #0: MXC Freescale with PMIC oprofile: using timer interrupt. TCP cubic registered NET: Registered protocol family 17 can: controller area network core (rev 20071116 abi 8) NET: Registered protocol family 29 can: raw protocol (rev 20071116) RPC: Registered udp transport module. RPC: Registered tcp transport module. input: mxc_ts as /devices/virtual/input/input0 mxc input touchscreen loaded rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable. rtc-pcf8563 1-0051: retrieved date/time is not valid. rtc-pcf8563 1-0051: hctosys: invalid date/time eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. IP-Config: Complete: device=eth0, addr=192.168.87.51, mask=255.255.255.0, gw=192.168.87.252, host=192.168.87.51, domain=, nis-domain=(none), bootserver=192.168.87.21, rootserver=192.168.87.21, rootpath= Looking up port of RPC 100003/3 on 192.168.87.21 Looking up port of RPC 100005/3 on 192.168.87.21 VFS: Mounted root (nfs filesystem). Freeing init memory: 108K Warning: unable to open an initial console. -----Message d'origine----- De : Juergen Beisert [mailto:j...@pengutronix.de] Envoyé : mercredi 25 février 2009 15:38 À : ptxdist@pengutronix.de Cc : Yannick Granger Objet : Re: [ptxdist] nfs boot problem Yannick, On Mittwoch, 25. Februar 2009, Yannick Granger wrote: > I'm trying to boot the phycore038 with nfs mode, but here is my error. > I'm using a fresh new Gentoo Installation with kernel nfs V3 V4 support. Now and here: > /tftpboot/nfsroot is a link to > /home/yannickG/OSELAS.BSP-Phytec-phyCORE-9/platform-phyCORE-i.MX27/root This is a huge security hole and your NFS server ignore the link! This is the reason, why it does not work. Regards, Juergen -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ | -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de