I upgraded to coda-5.3.5 and when I try to start venus I get
the message

16:26:08 Kernel version ioctl failed (Inappropriate ioctl for device)!
16:26:08 2.3 or later kernels require an updated kernel module!
16:26:08 Initial LRDB allocation
16:26:08 Getting Root Volume information...
16:26:38 Venus starting...
16:26:53 fatal error -- vsgent::Connect: (0) failed (-2004)
16:26:53 RecovTerminate: clean shutdown

In a previous message I wrote:
 > >   Because it failed on every machine, on one machine I installed
 > > coda-5.3.4 (I was running coda-5.3.3)
 > > and starting venus still fails, this time with the message in
 > > the console file:
 > > B scan (5400, 129603) (25, 75, 4)
 > > 18:10:26 fatal error -- CacheFile::ResetContainer: open failed (2)
 > > 18:10:26 RecovTerminate: clean shutdown
 > > Assertion failed: 0, file "fso_cachefile.cc", line 132

and Jan replied
 > The layout of /usr/coda/venus.cache changed between 5.3.5 and 5.3.6,
 > which is probably the cause of this error message.

   But I did not write that I had upgraded to 5.3.6.  I wrote that I had
upgraded to 5.3.4.  Today I upgraded to 5.3.5 from 5.3.4.  I did not
upgrade to 5.3.6 because some other users have reported errors using
Linux Red Hat.
   Now then, using version 5.3.5 of coda, the console file says

16:26:38 Venus starting...
16:26:53 fatal error -- vsgent::Connect: (0) failed (-2004)
16:26:53 RecovTerminate: clean shutdown
Assertion failed: 0, file "comm.cc", line 2707
Sleeping forever.  You may use gdb to attach to process 20467.

Jan asked, what are the contents of /vice/db/VSGDB.  The answer is
the following
E0000100 caravius
E0000101 torbato
E0000102 supercfd
E0000111 caravius torbato
E0000112 caravius supercfd
E0000121 caravius torbato supercfd

The cmon command shows that the server on the computer "caravius"
is running.
The venus error message occured when running on computer called
"torbato" which happens also to be a replica server.

I have been installing alot of software into coda, so it would be
very, very valuable to be able to solve this problem.  I have been
using two replica servers and I have been making backups, so I thought
I was safe in using Coda, but if I cannot get the client to run,
I'm stuck.

Here is another experiment.  The version of coda is 5.3.5.  The
computer does not have a server, only a client.  When start venus
I get the following error message

16:43:05 Kernel version ioctl failed (Inappropriate ioctl for device)!
16:43:05 2.3 or later kernels require an updated kernel module!
16:43:05 Initial LRDB allocation
16:43:05 Getting Root Volume information...
16:43:35 Venus starting...
16:43:50 fatal error -- vsgent::Connect: (0) failed (-2004)
16:43:51 RecovTerminate: clean shutdown

The error message is the same.  There is the same strange message about
  Kernel version ioctl failed (Inappropriate ioctl for device)!
  2.3 or later kernels require an updated kernel module!
when in fact I am using kernel 2.2.13.  The file says
/usr/coda/etc/console
Coda Venus, version 5.3.5
[some text deleted]
16:43:05 Initial LRDB allocation
16:43:05 Getting Root Volume information...
16:43:35 Venus starting...
16:43:50 fatal error -- vsgent::Connect: (0) failed (-2004)
16:43:51 RecovTerminate: clean shutdown
Assertion failed: 0, file "comm.cc", line 2707

The same error as on the other computer concerning line 2707
of comm.cc.

This second test is a computer that is not a server, so there
is no file /vice/db/VSGDB.

I ran the command
   venus-setup caravius,torbato,supercfd 1015461
on all the machines.  I checked that the venus-setup command
was from the 5.3.5 distribuition.