Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!rjf001!hpftc!teemc!ka3ovk!tgate!zardoz!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!usc!bbn!oliveb!amdahl!pacbell!belltec!lance From: lance@belltec.UUCP (Lance Norskog) Newsgroups: comp.unix.i386 Subject: Re: Ethernet boards for ISC 386/ix Summary: interrupt lines Message-ID: <391@belltec.UUCP> Date: 11 Aug 89 01:14:50 GMT References: <1423@hydra.gatech.EDU> Distribution: usa Organization: Bell Technologies, Fremont, CA Lines: 33 In article <1423@hydra.gatech.EDU>, gb7@prism.gatech.EDU (Joe Bradley) writes: > > The only other potential problem is that the ISC sysadm script for > configuring host based TCP/IP wants to set an IRQ of 3 to 7 for this > board. Well, all of those are taken in my present configuration, and > the board will support IRQ 2. Thus, I edited the sysadm script to allow > me to set an IRQ of 2 (and of course set the board likewise). Assuming > that's not causing a problem, then I guess I have to conclude the board > just plain won't work in my machine because the clock rate is too high. > Interrupt 2 on the card is interrupt 9 in the operating system, so you want to sysadm with 9 and then set the WD interrupt jumper at the left-hand end (interrupt 2). The WD driver in Streamlined TCP figures out if this is the problem and prints out a message on the console, I don't know if the 386/ix driver does. The motherboard mhz is not the problem, the Dell machine should clock the bus somewhere between 6-10mhz and the WD should work fine. I think the WD cards come with a disk that has a diagnostic on it; did you run that? The device driver for the WD board should do a complete check on the card when the system comes up (the one in Streamlined TCP does). You can test the digital and analog signal path at various points and make sure the shared memory works. The WD driver in 386/ix was written by Western Digital, and is available in source form from them, if all else fails. Lance Norskog Sales Engineer Streamlined Networks 415-659-1450