Dunno nfs internal protcols, but

the directory nfs tries to mount is:
/tftpboot/xxx.xxx.xxx.xxx

where xxx.xxx.xxx.xxx is the ip # of the rio box
(and note leading slash - I do mean root)
 
 
 

Ian Pedersen wrote:

I am having trouble getting the RioPlay receiver code that I compiled to run on the Rio Receiver. I struggled for a while to find the correct toolchain and get an environment setup to compile the rioplay code, but I believe I am now on the right track. I setup a box with Debian Linux and installed Emdebian for an arm 2.95.2 cross-toolchain environment. I was then able to compile the RioPlay code without any problems. I replaced the './bin/rioplay' and './sbin/init' binaries within a working receiver.arf, but the Rio Receiver does not like it. It appears to go into an infinite loop. I traced the session with Ethereal and saw the following LOOKUP call being mode over and over with increasing XID value:NFS   V2 LOOKUP Call XID 0xa2200000
NFS   V2 LOOKUP Reply XID 0xa2200000
NFS   V2 LOOKUP Call XID 0xa3200000
NFS   V2 LOOKUP Reply XID 0xa3200000
NFS   V2 LOOKUP Call XID 0xa4200000
NFS   V2 LOOKUP Reply XID 0xa4200000
NFS   V2 LOOKUP Call XID 0xa5200000
NFS   V2 LOOKUP Reply XID 0xa5200000
...etc Does anyone have any ideas what I might be doing wrong? Ian