Hi,

I am trying to install virtualogix linux on dm6437 dsp. I built the kernel on vmware appliance (fedora 7) then i tranferred the kernel through ccstudio(windows) onto the board. I am watching the traces on serial port(hyperterminal) of the board. I am getting rpc -101 error when the kernel is trying to boot the root file system. I know that the board is not able to reach the nfs share of fedora, but i am not able to figure out how can i overcome this problem. I have two ethernet adapters to my system, one for connecting to lan (internet) and other for connecting to the board. Here are the ips

Lan ethernet:143.205.129.195
other ethernet connecting to board: 169.254.200.148
fedora(vmware)ip : 192.168.195.128
board ip: i dont know the board ip, i am trying to assign the static ip in config file.

Here is the serial line trace:


Linux version 2.6.13-jaluna (root@localhost.localdomain) (gcc version 3.2.2) #1
Mon May 26 01:41:31 EDT 2008
TMS320DM643X port (C) VirtualLogix and others
Designed for the EVMDM6437 board, Spectrum Digital Inc.
CPU: C64x+ revision unknown core voltage 1.2V core number 0
Initializing kernel
Zone DMA start=0x87000000 size=0x1000000
disabling caching for 0x87000000 to 0x87ffffff
zone : 80287c08, size 4096
zone 0 start 32768, 8036e000 8028e000
zone : 80287d3c, size 28672
zone 1 start 28672, 8028e000 8028e000
zone : 80287e70, size 0
Built 1 zonelists
Kernel command line: console=ttyS0,115200 root=/dev/nfs rw nfsroot=192.168.195.1
28:/opt/linux_build_dir/linux-root,auto_uid \ip=192.168.195.127:::::eth0: video=
dm64xxfb:output=pal");
PID hash table entries: 1024 (order: 10, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory available: 127104k/128476k RAM, 0k/0k ROM (586k kernel code, 58k dat
Mount-cache hash table entries: 512
NET: Registered protocol family 16
eth0: EMAC driver version 0.12 IRQ=10 ZERO_COPY=ON
eth0: Ethernet addr=00:0e:99:02:93:5e PHY=MII
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
davincifb: Options "output=pal");"
DaVinci: Output on PAL in COMPOSITE format, Enabled windows: Video0 Video1 OSD0
OSD1
Setting Video0 size 720x576, position (0,0)
Setting Video1 size 720x576, position (0,0)
Setting OSD0 size 720x576, position (0,0)
Setting OSD1 size 720x576, position (0,0)
Setting Up Clocks for DM420 OSD
Console: switching to colour frame buffer device 90x36
fb0: dm_osd0_fb frame buffer device
fb1: dm_vid0_fb frame buffer device
fb2: dm_osd1_fb frame buffer device
fb3: dm_vid1_fb frame buffer device
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 7) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
Looking up port of RPC 100003/2 on 192.168.195.128
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.195.128
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get mountd port number from server, using default
RPC: sendmsg returned error 101
Root-NFS: Server returned error -101 while mounting /opt/linux_build_dir/linux-r
oot
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)