• State
  • Locked Locked
  • Replies 17 replies
  • Subscribers 102 subscribers
  • Views 2031 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM8168 can't mount rootfs from NFS?

xiang ***
Intellectual 260 points
Other Parts Discussed in Thread: PMP

I did as that the documents say, and  console output as below:(rootfs : nfs  come from the vc3 examlpe folder)

 Using DaVinci EMAC device
TFTP from server 192.168.1.2; our IP address is 192.168.1.3
Filename 'uImage'.
Load address: 0x81000000
Loading: T #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################
done
Bytes transferred = 2190004 (216ab4 hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37-rc3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2189940 Bytes = 2.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37-rc3 (xcaids@xcaids-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Tue Mar 29 17:16:12 CST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
bootconsole [earlycon0] enabled
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 29364
Kernel command line: console=ttyO2,115200n8 rw mem=166M earlyprintk vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=192.168.1.2:/home/xcaids/nfs ip=192.168.1.3:192.168.1.2:192.168.1.254::xcaids-desktop:eth0:off
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 116MB = 116MB total
Memory: 112596k/112596k available, 57388k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xca800000 - 0xf8000000   ( 728 MB)
    lowmem  : 0xc0000000 - 0xca600000   ( 166 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0035000   ( 180 kB)
      .text : 0xc0035000 - 0xc0428000   (4044 kB)
      .data : 0xc0428000 - 0xc0462c40   ( 236 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:400
GPMC revision 6.0
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_mux_init: Add partition: #1: core, flags: 0
_omap_mux_init_signal: Could not set signal i2c2_scl.i2c2_scl
_omap_mux_init_signal: Could not set signal i2c2_sda.i2c2_sda
NOR: Can't request GPMC CS
registered ti816x_vpss device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
ti816x_pcie: Invoking PCI BIOS...
ti816x_pcie: Setting up Host Controller...
ti816x_pcie: Register base mapped @0xca820000
ti816x_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev4.0 at 100 kHz
i2c_omap i2c_omap.2: bus 2 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0
Switched to NOHz mode on CPU #0
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
musb_hdrc: kernel must blacklist external hubs
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb_hdrc musb_hdrc.0: USB Host mode controller at ca80c000 using DMA, IRQ 18
musb_hdrc: kernel must blacklist external hubs
musb_hdrc musb_hdrc.1: MUSB HDRC host driver
musb_hdrc musb_hdrc.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb_hdrc musb_hdrc.1: USB Host mode controller at ca81e800 using DMA, IRQ 19
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
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) ?? 2001-2006 Red Hat, Inc.
msgmni has been set to 219
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap-hsuart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
omap-hsuart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap-hsuart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled, bootconsole disabled
console [ttyO2] enabled, bootconsole disabled
brd: module loaded
loop: module loaded
ahci ahci: forcing port_map 0x0 -> 0x3
ahci ahci: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi0 : ahci
scsi1 : ahci
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16
m25p80 spi1.0: found m25p05-nonjedec, expected w25x32
m25p80 spi1.0: m25p05-nonjedec (64 Kbytes)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
mtd: partition "U-Boot" extends beyond the end of device "spi_flash" -- size truncated to 0x10000
0x000000010000-0x000000012000 : "U-Boot Env"
mtd: partition "U-Boot Env" is out of reach -- disabled
0x000000000000-0x000000280000 : "Kernel"
mtd: partition "Kernel" extends beyond the end of device "spi_flash" -- size truncated to 0x10000
0x000000010000-0x000000010000 : "File System"
mtd: partition "File System" is out of reach -- disabled
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
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
i2c /dev entries driver
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
PSTATE 1f20000
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
1-0018 supply IOVDD not found, using dummy regulator
1-0018 supply DVDD not found, using dummy regulator
1-0018 supply AVDD not found, using dummy regulator
1-0018 supply DRVDD not found, using dummy regulator
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
emac-mii: probed
mdio_bus 1:01: DaVinci EMAC: mii bus found 31
ata2: SATA link down (SStatus 0 SControl 300)
ata1: SATA link down (SStatus 0 SControl 300)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
     device=eth0, addr=192.168.1.3, mask=255.255.255.0, gw=192.168.1.254,
     host=xcaids-desktop, domain=, nis-domain=(none),
     bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath=
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              64 mtdblock0  (driver?)
1f02              64 mtdblock2  (driver?)
1f04            2432 mtdblock4  (driver?)
1f05             128 mtdblock5  (driver?)
1f06            4352 mtdblock6  (driver?)
1f07          204928 mtdblock7  (driver?)
1f08           50304 mtdblock8  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c0043b34>] (dump_backtrace+0x0/0x110) from [<c031afb8>] (dump_stack+0x18/0x1c)
 r7:c6c12000 r6:00000000 r5:c002bb44 r4:c04632d0
[<c031afa0>] (dump_stack+0x0/0x1c) from [<c031b01c>] (panic+0x60/0x17c)
[<c031afbc>] (panic+0x0/0x17c) from [<c0009254>] (mount_block_root+0x1e0/0x220)
 r3:00000000 r2:00000000 r1:c6c23f58 r0:c03c2d0c
[<c0009074>] (mount_block_root+0x0/0x220) from [<c0009340>] (mount_root+0xac/0xcc)
[<c0009294>] (mount_root+0x0/0xcc) from [<c00094d0>] (prepare_namespace+0x170/0x1d4)
 r4:c0462ca4
[<c0009360>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/0x154)
 r5:c0008670 r4:c0462c40
[<c0008670>] (kernel_init+0x0/0x154) from [<c005e5c4>] (do_exit+0x0/0x5b8)
 r5:c0008670 r4:00000000

Please give me some help,thanks.

  • 0
    Guru 10685 points

    I just have ip=dhcp and it works fine. I have no idea without checking the documentation what your very long line means but I would get rid of everything after the ip=<ipaddress> and try that.

    Other things to check:

    -have you restarted your NFS server in order to re-read the exports file

    -more fundamentally, have you checked your NFS setup by trying to login to your NFS server from a machine that is not your TI dev board?

    Regards,

    Ralph

     

    P.S.

    Can I ask you was it much effort to port the VPSS driver module from the EZSDK kernel (v2.6.34) to the newer kernel you're using (presumably downloaded off kernel.org 2.6.37)? I know the EZSDK kernel has a reasonable number of patches on compared to the kernel.org v2.6.34. Thanks.

  • 0 in reply to _Ralph_
    Intellectual 260 points

    Thanks.

    I thought that my nfs server has no problem, because I had used the same setting and env to try the kernel 2.6.34 and 2.6.37,but the result is defferent:

    the kernel 2.6.34 can boot well from NFS,and outputs as below:

    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    IP-Config: Guessing netmask 255.255.255.0
    IP-Config: Complete:
         device=eth0, addr=192.168.1.3, mask=255.255.255.0, gw=192.168.1.254,
         host=DM86168, domain=, nis-domain=(none),
         bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath=
    Looking up port of RPC 100003/2 on 192.168.1.2
    PHY: 1:01 - Link is Up - 1000/Full
    Looking up port of RPC 100005/1 on 192.168.1.2
    VFS: Mounted root (nfs filesystem) on device 0:11.
    devtmpfs: mounted

    but kernel 2.6.37 can't:

    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    IP-Config: Guessing netmask 255.255.255.0
    IP-Config: Complete:
         device=eth0, addr=192.168.1.3, mask=255.255.255.0, gw=192.168.1.254,
         host=xcaids-desktop, domain=, nis-domain=(none),
         bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath=
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)

       

  • 0 in reply to xiang ***
    Guru 10685 points

    I can only suggest that you do not have your kernel configured correctly. Make sure that "ROOT_NFS" is set to "y" in your kernel config. This is located here:

         -> File systems                                                     │
      │       -> Network File Systems (NETWORK_FILESYSTEMS [=y])                │
      │         -> NFS client support (NFS_FS [=y])                            

    Regards,

    Ralph

  • 0
    Intellectual 320 points

    xiang *** said:
    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    IP-Config: Guessing netmask 255.255.255.0
    IP-Config: Complete:
         device=eth0, addr=192.168.1.3, mask=255.255.255.0, gw=192.168.1.254,
         host=xcaids-desktop, domain=, nis-domain=(none),
         bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath=
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)

    The phy is attached, but it isn't up when trying to mount nfs.

    Try added "rootdelay=1" (or more) to your bootparameters.

    You should see:

    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    IP-Config: Complete:
         device=eth0, addr=10.2.20.200, mask=255.0.0.0, gw=10.0.0.24,
         host=NetraTeod, domain=, nis-domain=(none),
         bootserver=10.2.20.100, rootserver=10.2.20.100, rootpath=
    Waiting 1sec before mounting root device...
    PHY: 1:01 - Link is Up - 100/Half
    VFS: Mounted root (nfs filesystem) on device 0:13.

  • 0 in reply to xiang ***
    TI__Expert 5290 points

    xiang *** said:
    Looking up port of RPC 100003/2 on 192.168.1.2
    PHY: 1:01 - Link is Up - 1000/Full

    Seems like you have a gigabit network in place. Would it be possible for you to try this on a 100Mbps network for now?

    Regards,

    Vaibhav

  • 0 in reply to Theo Debrouwere
    Intellectual 260 points
    I had printed something information during the booting about NFS, and the outputs is supprised and defferent from these two version kernels. kernel 2.6.37: eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013) IP-Config: Guessing netmask 255.255.255.0 IP-Config: Complete: device=eth0, addr=192.168.1.3, mask=255.255.255.0, gw=192.168.1.254, host=DM86168, domain=, nis-domain=(none), bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath= RPC: 1 call_start mount3 proc NULL (sync) RPC: 2 call_start rpcbind2 proc GETPORT (async) RPC: 1 remote rpcbind unreachable: -113 RPC: 3 call_start rpcbind2 proc GETPORT (async) RPC: 1 remote rpcbind unreachable: -113 RPC: 4 call_start rpcbind2 proc GETPORT (async) PHY: 1:01 - Link is Up - 1000/Full PHY: 1:01 - Link is Down RPC: 1 remote rpcbind unreachable: -113 RPC: 5 call_start rpcbind2 proc GETPORT (async) RPC: 1 remote rpcbind unreachable: -113 RPC: 6 call_start rpcbind2 proc GETPORT (async) PHY: 1:01 - Link is Up - 100/Full err : task->tk_status : 0 RPC: 7 call_start mount3 proc MOUNT (sync) err : task->tk_status : 0 RPC: 8 call_start nfs3 proc NULL (sync) RPC: 9 call_start rpcbind2 proc GETPORT (async) err : task->tk_status : 0 RPC: 10 call_start nfs3 proc FSINFO (sync) err : task->tk_status : 0 RPC: 11 call_start nfs3 proc PATHCONF (sync) err : task->tk_status : 0 RPC: 12 call_start nfs3 proc GETATTR (sync) kernel 2.6.34: IP-Config: Complete: device=eth0, addr=192.168.1.3, mask=255.255.255.0, gw=192.168.1.254, host=DM86168, domain=, nis-domain=(none), bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath= Looking up port of RPC 100003/2 on 192.168.1.2 RPC: 1 call_start rpcbind2 proc GETPORT (sync) PHY: 1:01 - Link is Up - 1000/Full Looking up port of RPC 100005/1 on 192.168.1.2 RPC: 2 call_start rpcbind2 proc GETPORT (sync) RPC: 3 call_start mount1 proc NULL (sync) RPC: 4 call_start mount1 proc MOUNT (sync) RPC: 5 call_start nfs2 proc NULL (sync) RPC: 6 call_start nfs2 proc STATFS (sync) RPC: 7 call_start nfs2 proc GETATTR (sync) RPC: 8 call_start nfs2 proc GETATTR (sync) RPC: 9 call_start nfs2 proc STATFS (sync) VFS: Mounted root (nfs filesystem) on device 0:11. RPC: 10 call_start nfs2 proc LOOKUP (sync) devtmpfs: mounted Freeing init memory: 164K RPC: 11 call_start nfs2 proc LOOKUP (sync) RPC: 12 call_start nfs2 proc LOOKUP (sync) please help me,thanks.
  • 0 in reply to xiang ***
    Intellectual 260 points
    I had printed something information during the booting about NFS, and the outputs is supprised and defferent from these two version kernels. kernel 2.6.37: RPC: 1 call_start mount3 proc NULL (sync) RPC: 2 call_start rpcbind2 proc GETPORT (async) RPC: 1 remote rpcbind unreachable: -113 RPC: 3 call_start rpcbind2 proc GETPORT (async) RPC: 1 remote rpcbind unreachable: -113 RPC: 4 call_start rpcbind2 proc GETPORT (async) PHY: 1:01 - Link is Up - 1000/Full PHY: 1:01 - Link is Down RPC: 1 remote rpcbind unreachable: -113 RPC: 5 call_start rpcbind2 proc GETPORT (async) RPC: 1 remote rpcbind unreachable: -113 RPC: 6 call_start rpcbind2 proc GETPORT (async) PHY: 1:01 - Link is Up - 100/Full err : task->tk_status : 0 RPC: 7 call_start mount3 proc MOUNT (sync) err : task->tk_status : 0 RPC: 8 call_start nfs3 proc NULL (sync) RPC: 9 call_start rpcbind2 proc GETPORT (async) err : task->tk_status : 0 RPC: 10 call_start nfs3 proc FSINFO (sync) err : task->tk_status : 0 RPC: 11 call_start nfs3 proc PATHCONF (sync) err : task->tk_status : 0 RPC: 12 call_start nfs3 proc GETATTR (sync) kernel 2.6.34: Looking up port of RPC 100003/2 on 192.168.1.2 RPC: 1 call_start rpcbind2 proc GETPORT (sync) PHY: 1:01 - Link is Up - 1000/Full Looking up port of RPC 100005/1 on 192.168.1.2 RPC: 2 call_start rpcbind2 proc GETPORT (sync) RPC: 3 call_start mount1 proc NULL (sync) RPC: 4 call_start mount1 proc MOUNT (sync) RPC: 5 call_start nfs2 proc NULL (sync) RPC: 6 call_start nfs2 proc STATFS (sync) RPC: 7 call_start nfs2 proc GETATTR (sync) RPC: 8 call_start nfs2 proc GETATTR (sync) RPC: 9 call_start nfs2 proc STATFS (sync) VFS: Mounted root (nfs filesystem) on device 0:11. RPC: 10 call_start nfs2 proc LOOKUP (sync) devtmpfs: mounted Freeing init memory: 164K RPC: 11 call_start nfs2 proc LOOKUP (sync) RPC: 12 call_start nfs2 proc LOOKUP (sync) please help me,thanks.
  • 0 in reply to xiang ***
    TI__Expert 5290 points

    Hi,

    In case you are still having this issue, please refer to http://e2e.ti.com/support/dsp/integra_dsparm/f/625/p/107894/381157.aspx#381157

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Bedia
    Expert 1100 points

    I'm booting 2.6.36+2.6.37 built from Arago PSP 04.00.00.09 via NFS and it works.  Here is the command line I'm passing in:

    Kernel command line: console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/home/hutch/downloads/Integra/rootfs mem=166M earlyprink vram=50M ti816xfb.vram=0:16M,1:16M,2:6M ip=192.168.1.1:192.168.1.5::255.255.255.0 noinitrd

    Regards,

    Brian


  • 0 in reply to hutchman
    Intellectual 260 points

    Thanks, my problem has solved , it can boot with NFS,  I found that my DHCP server had something wrong so I fixed it .

  • 0 in reply to hutchman
    TI__Expert 5290 points

    Brian,

    We have seen this issue crop up only on Gigabit networks. If you are using a 100Mbps network then the above bootargs will work fine.

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Bedia
    Expert 1100 points

    I was using a 1G Network switch and NFS was working fine!

     

    I received my daughter card with NOR flash on it yesterday and today when I fire up the board I think I see the 1G problem you guys have been talking about.  What used to work now doesn't .... now I'm getting messages like this (this is with bitbaked PSP04.00.00.09):

    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:02, id=282f013)
    Sending DHCP and RARP requests .
    PHY: 1:01 - Link is Up - 1000/Full
    ..... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:02, id=282f013)
    Sending DHCP and RARP requests .
    PHY: 1:01 - Link is Up - 1000/Full
    ..... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:02, id=282f013)
    Sending DHCP and RARP requests .
    PHY: 1:01 - Link is Up - 1000/Full
    ..... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, id=282f013)
    eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:02, id=282f013)
    Sending DHCP and RARP requests .
    PHY: 1:01 - Link is Up - 1000/Full
    ..... timed out!

    ... and it repeats forever.

     

    I'm off to find an old switch!

    Regards,

    Brian

     

     

  • 0 in reply to hutchman
    Expert 1100 points

    OK, I fixed my problem (it didn't have anything to do with the speed of the E-Switch).  I had to add 'eth0:off' to turn off the auto protocol stuff on my bootargs.  For some reason my previous bootargs worked without the daughter card but when I added it the board would get stuck trying to do dhcp.

    Regards,

    Brian

  • 0 in reply to hutchman
    Expert 1100 points

    ... here is what my bootargs look like now to do NFS:

    setenv bootargs 'console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/home/hutch/downloads/Integra/rootfs mem=166M earlyprink vram=50M ti816xfb.vram=0:16M,1:16M,2:6M ip=192.168.1.1:192.168.1.5::255.255.255.0::eth0:off noinitrd'

    Regards,

    Brian

  • 0 in reply to hutchman
    Guru 10685 points

    You need that to be "earlyprintk", not "earlyprink". I'm guessing you've got that due to a copy and paste from the TI "boot.cmd" supplied on the SD card which is also wrong.

    Ralph

  • 0 in reply to _Ralph_
    Expert 1100 points

    Oops.  I think it was just a copy paste.  Good eye!

    B

  • 0 in reply to hutchman
    Intellectual 700 points

    I am still experiencing this problem with the latest EZSDK.  NFSroot does not work with 1000baseT but is fine at 100baseT.  Are there any plans to investigage this problem further?