On Wed, Feb 09, 2000 at 01:06:36PM -0800, Quinn Weaver wrote:
> On Wed, 9 Feb 2000, Quinn Weaver wrote:
> 
> > Aha!
> > 
> > 20:43:37 New SrvLog started at Tue Feb  8 20:43:37 2000
> > 
> > 20:43:37 Resource limit on data size are set to 2147483647
> > 
> > 20:43:37 Server etext 0x813fa03, edata 0x81878b0
> > 20:43:37 No RvmType selected!
> > 
> > That looks like a memory-mapping problem to me.  I'm not sure what
> > "No RvmType selected" means, though.
> > 
> > [...]
> > 
> > I'll bet that's the problem.  I'll try re-running rdsinit and see what
> > happens.
> 
> O.K., I re-did rdsinit with the same values, except that I entered a
> starting address of 0x50000000 for memory-mapped RVM.  Again, codasrv
> starts without complaint, but then silently dies.  (It doesn't even leave
> a zombie for debugging).  It writes this message in /vice/srv/SrvLog:
> 
> 13:00:10 New SrvLog started at Wed Feb  9 13:00:10 2000
> 
> 13:00:10 Resource limit on data size are set to 2147483647
> 
> 13:00:10 Server etext 0x813fa03, edata 0x81878b0
> 13:00:10 No RvmType selected!

Ok, I've figured it out, you've left out the -rvm at the beginning of
/vice/srv.conf

it should look like:

-rvm <logdevice> <datadevice> <rvmsize>
^^^^

Otherwise this stuff is not passed on the codasrv by the startserver
script.

> This is pretty clearly the cause of the TCP/IP error on the Windows
> client, if not the "cannot open /dev/cfs0" error on the Linux client.
> What is going on?  Surely I'm missing something obvious. ;)

Do you have a kernel module, and does it load successfully? Having
/dev/cfs0 says nothing.

 Check if the kernel module can be loaded.
    modprobe coda

 Check for kernel messages.
    dmesg

 Check for zombie venus processes.
    ps auxwww | grep venus

Jan