Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!sco!belal
From: belal@sco.com (Bela Lubkin)
Newsgroups: biz.sco.opendesktop,comp.unix.sysv386
Subject: Re: Problems with network commands under ODT-VIEW
Keywords: odt, sco, unix, X11, network
Message-ID: <265.belal@sco.com>
Date: Mon, 10 Jun 91 18:08:07 GMT
References: <1991Jun4.071324.6701@bohra.cpg.oz.au>
Lines: 43

Dhiraj Sharma wrote that, essentially, his network access only works
when he is NOT displaying an X server on his console screen.  Several
replies have suggested that he is running out of streams buffers.

The behavior he described does not suggest streams problems.  Streams
problems would be more erratic.  This problem sounds more like a
hardware conflict between the video board and the ethernet board.

VGA display memory is usually mapped into the A0000-BFFFF range of
memory.  Most VGA boards also have ROM BIOS code in the Cxxxx or Dxxxx
ranges.  I don't think SCO's 3C503 driver actually uses shared memory,
but if it does, there could be a conflict there.

>serial    0x02f8-0x02ff       03      -1    unit=1 type=Standard nports=1 
>serial    0x03f8-0x03ff       04      -1    unit=0 type=Standard nports=1 
>tape      0x0338-0x033c       05      01    type=wangtek 
>floppy    0x03f2-0x03f7       06      02    unit=0 type=96ds15 
>parallel  0x03bc-0x03be       07      -1    unit=1 
>e3B       0x0300-0x0310       11      -1    type=3c503 addr=02:60:8c:0f:99:a5 
>adapter   0x0330-0x0332       13      05    type=ad ha=0 id=7 
>fpu       0x0000-0x0000       15      -1    type=80387 

A more likely cause is that the ethernet board is on interrupt 2.
[Vector 2 gets chained to the 2nd interrupt controller, coming in as
interrupt 9.  The driver then displays it in octal, i.e. 11, or
interrupt 1 on PIC 1.  You will also see it as interrupt 25 or 31
(interrupt 1 on PIC 3, decimal or octal)].  Some VGA boards take over
interrupt 2 for their own purposes, only when in graphics mode.  If the
VGA is driving the INT2 bus line low, the ethernet board probably won't
be able to generate interrupts.

So, Dhiraj, I suggest setting your 3C503 to a different interrupt.  The
3C503's interrupt is configured at boot time by the e3B driver.  You
need only change the number, relink the kernel and reboot.  Unfortunately,
your system is already using all of the possible interrupts for the
3C503.  You could put the tape drive on 2, in which case you could only
access tapes from a text screen -- that might be a less annoying
limitation.  Or you could disable one of the serial or parallel ports
and use its interrupt (3, 4 or 7).

Bela Lubkin  * *  //  filbo@deeptht.santa-cruz.ca.us  Not speaking for SCO...
     @     * *   //  belal@sco.com  ...ucbvax!ucscc!{deeptht!filbo,sco!belal}
R Pentomino  * \X/  Filbo @ Pyrzqxgl +1 408-476-4633 and XBBS +1 408-476-4945