Help needed w/ NFS/QIC

[Randy Jarrett WA4MEI]

In article <42700017 at osiris.cso.uiuc.edu> dpgerdes at osiris.cso.uiuc.edu writes:
++>
++>
++>
++>   I have V/386 3.0e.1, which is running Wollongong TCP and NFS for
++>Streams.  I also have an Everex 60Meg tape unit.  Either of these
++>alone works just fine, but when installed together, I get various problems.
++>If I install the Beta QIC driver from uPort, it gets a Panic as soon as
++>it tries to init the Qic driver (at least it looks that way), while alone it
++>works fine.  If I use the EV driver that came with the system, it boots
++>fine, and I can use the tape drive for a while, but as soon as I do anything
++>across the net, the next time I access the tape unit it either fails (no
++>such device I beleive)  or crashes the system.  This also seems to happen
++>if I try to access it after the system has been running over night (no
++>one using it).
++>    The TCP is configured for the Exelan 503 card using the internal 
++>transceiver (thin-net) and is configured as follows:
++>	intvec 5
++>	Base I/O: 0x310
++>	Major device 58
++>    The Everex is configured:
++>	Intvec 3 
++>	Base I/O 300
++>	Major device 22
++>
++>    The machine is a compaq 386/25 model 300.  There is only one serial
++>port on the machine and I have it disabled, as I have a logitech mouse
++>driver on intvec 4.
++>    Yes the jumpers are set correctly.  If anyone has any ideas what 
++>might be wrong, I would be greatly appreciative.
++>
++>
++>    I also have a problem with rlogin.  It frequently terminates connections
++>at random.  Wollongong has acknowledged the problem but refuses to correct
++>it because they have dropped all support for uPort products.
++>    Rlogin also has the undesirable feature of leaving passwords in a 
++>file '/tmp/netlgnlog'.  Again Wollongong will not provide a fix or a work
++>around other than telling me not to use rlogin.


I had a similar problem with V/AT 2.4.  The tape drive worked ok by itself
and the inteligent serial board worked ok alone but together the system
barfed.  The problem turned out to be a file in the linkkit/cf directory
called ifile.  It was linked to ifile.text3 and when both drivers were
linked into the kernel it needed 4 text segments so I linked the ifile.text4
to ifile and re-made the kernel and everything worked.


-- 
Randy Jarrett  WA4MEI 
UUCP  ...!gatech!wa4mei!rsj        | US SNAIL: P.O. Box 941217
PHONE +1 404 493 9017		   |           Atlanta, GA 30341-0217