You forgot the list again...... You have a problem with your boot args - there must be some rubbish getting passed in Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs ip=dhcp nMPID hash table entries: 512 (order: 9, 8192 bytes) >From the output you sent the above is what the kernel is seeing - there is no >nfsroot path. It is possible that it is the terminal not wrapping the long lines - can you set that mode & try again. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com <http://www.trinityconvergence.com/>
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 10:56 To: Phil Quiney Subject: Re: RE: RE: I have a problem when use the NFS which use to mount the filesys ok it's this CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ) CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets Machine: DaVinci EVM Memory policy: ECC disabled, Data cache writeback DM6443 Built 1 zonelists Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs ip=dhcp nMPID hash table entries: 512 (order: 9, 8192 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: 120MB = 120MB total Memory: 119424KB available (1794K code, 394K data, 140K init) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok spawn_desched_task(00000000) desched cpu_callback 3/00000000 ksoftirqd started up. desched cpu_callback 2/00000000 desched thread 0 started up. NET: Registered protocol family 16 DaVinci: 71 gpio irqs Registering platform device 'serial8250.0'. Parent at platform Registering platform device 'musb_hdrc'. Parent at platform Registering platform device 'nand_davinci.0'. Parent at platform Registering platform device 'mmc.0'. Parent at platform DaVinci I2C DEBUG: 18:57:48 Jul 21 2008 Registering platform device 'i2c'. Parent at platform SCSI subsystem initialized Generic PHY: Registered new driver usbcore: registered new driver usbfs usbcore: registered new driver hub musb_hdrc: version 2.2a/db-0.4.8 [cppi-dma] [host] [debug=0] musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn) musb_hdrc: MHDRC RTL version 1.300 musb_hdrc: USB Host mode controller at c8000000 using DMA, IRQ 12 musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected VBUS_ERR squashfs: version 3.3 (2007/10/31) Phillip Lougher yaffs Jul 21 2008 18:57:23 Installing. watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec Registering platform device 'davinci_resizer.2'. Parent at platform Registering platform device 'davinci_previewer.2'. Parent at platform Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled Registering platform device 'serial8250'. Parent at platform ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A io scheduler noop registered io scheduler anticipatory registered loop: loaded (max 8 devices) i2c /dev entries driver elevator: using anticipatory as default io scheduler nand_davinci nand_davinci.0: Using 1-bit hardware ECC NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bi)Scanning device for bad blocks Creating 6 MTD partitions on "nand_davinci.0": 0x00020000-0x00050000 : "bootloader" 0x00050000-0x001d0000 : "core" 0x00200000-0x00800000 : "base" 0x00800000-0x01000000 : "scratch" 0x01000000-0x01200000 : "extra" 0x01200000-0x04000000 : "data" nand_davinci nand_davinci.0: hardware revision: 2.1 Registering platform device 'ti_davinci_emac'. Parent at platform TI DaVinci EMAC: MAC address is 00:0b:82:ff:ff:ff TI DaVinci EMAC Linux version updated 5.0 TI DaVinci EMAC: Installed 1 instances. netconsole: not configured, aborting Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice MUX: initialized KEYPAD Registering platform device 'gxv31xx_keypad.0'. Parent at platform Initialize 6x5 keypad for gxv31xx. mmc mmc.0: Supporting 4-bit mode mmc mmc.0: Using DMA mode NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 16384) NET: Registered protocol family 1 NET: Registered protocol family 17 Sending DHCP requests .., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.81.11 IP-Config: Complete: device=eth0, addr=192.168.81.11, mask=255.255.255.0, gw=192.168.81.1, host=192.168.81.11, domain=, nis-domain=(none), bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath= VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255) ________________________________ 2008-09-12 ________________________________ 发件人： Phil Quiney 发送时间： 2008-09-12 17:50:46 收件人： [EMAIL PROTECTED] 抄送： davinci-linux-open-source 主题： RE: RE: I have a problem when use the NFS which use to mount the filesys Hi, Please 'reply to all' to keep the list in the thread Can you post the complete output of the console rather than just the bit that fails. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com <http://www.trinityconvergence.com/> ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 10:40 To: Phil Quiney Subject: Re: RE: I have a problem when use the NFS which use to mount the filesys Hi now the problem is Sending DHCP requests .., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.81.11 IP-Config: Complete: device=eth0, addr=192.168.81.11, mask=255.255.255.0, gw=192.168.81.1, host=192.168.81.11, domain=, nis-domain=(none), bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath= VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255) ________________________________ 2008-09-12 ________________________________ 发件人： Phil Quiney 发送时间： 2008-09-12 15:11:56 收件人： [EMAIL PROTECTED] 抄送： davinci-linux-open-source 主题： RE: I have a problem when use the NFS which use to mount the filesys Hi, As Brad said, if this is your own kernel then can you rebuild it with the default options set. The kernel config requires 'CONFIG_ROOT_NFS=y' for this boot method to work. FYI I booted a DM355 with the following bootargs.... setenv bootargs 'mem=116M console=ttyS0,115200n8 noinitrd root=/dev/nfs rw nfsroot=172.18.1.34:/tftpboot/remote_fs/dm355_rootfsdir_nfs ip=dhcp' On the console the following appeared.... eth0: link down Sending DHCP requests ., OK IP-Config: Got DHCP answer from 172.18.0.254, my address is 172.18.128.92 IP-Config: Complete: device=eth0, addr=172.18.128.92, mask=255.255.0.0, gw=172.18.0.254, host=172.18.128.92, domain=trinity.local, nis-domain=(none), bootserver=172.18.0.254, rootserver=172.18.1.34, rootpath= Looking up port of RPC 100003/2 on 172.18.1.34 Looking up port of RPC 100005/1 on 172.18.1.34 VFS: Mounted root (nfs filesystem). Freeing init memory: 180K Can you also check the /var/log/messages file on the NFS host. You should see a message like... Sep 12 07:50:19 chrysler mountd[1989]: authenticated mount request from 172.18.128.92:800 for /tftpboot/remote_fs/dm355_rootfsdir_nfs (/tftpboot) You have of course made the directory available (in /etc/exports), started the nfs service & disabled the firewall (or otherwise allow NFS through). [EMAIL PROTECTED] ~]# cat /etc/exports /tftpboot *(rw,no_root_squash,sync) What happens if you try to mount the file system from the host....in my case that would be commands of the form... [EMAIL PROTECTED] ~]# mkdir /mnt/nfs [EMAIL PROTECTED] ~]# mount -t nfs localhost:/tftpboot/remote_fs/dm355_rootfsdir_nfs /mnt/nfs [EMAIL PROTECTED] ~]# ls /mnt/nfs bin dev etc lib mnt proc sbin sys usr boot home media opt root srv tmp var Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com <http://www.trinityconvergence.com/> ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brad Bitterman Sent: 12 September 2008 02:43 To: [EMAIL PROTECTED] Cc: davinci-linux-open-source Subject: Re: I have a problem when use the NFS which use to mount the filesys Did you build your own kernel? Seems like NFS is turned off in the kernel. - Brad On Sep 11, 2008, at 9:20 PM, [EMAIL PROTECTED] wrote: I have a problem when use the NFS which use to mount the filesys this problem is VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255) ________________________________ 2008-09-12 _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
