[tulip] I can't make multiple tulips work properly.

[Andy Stewart]

Hi everyone,

The motherboard's automatic configuration of the PCI interrupts was somehow
making choices which caused this error.  By manually overriding those settings,
I was able to get 2 Tulip based NICs to work in my system with kernel rev 2.2.18
and v0.92t of the driver.

Thanks for the help!

Andy

-- 
Andy Stewart, Founder         -o)  | I predict that today will be remembered  
Worcester Linux Users' Group   /\  | until tomorrow!                          
Worcester, MA, USA            _\_v |                                          
http://www.wlug.org                |

Donald Becker wrote:
> 
> On Mon, 15 Jan 2001, root wrote:
> 
> > I am using the 0.92t tulip driver loaded as a kernel module.  I have
> > tried this experiment with kernel revs 2.2.14 and 2.2.18 with similar
> > results.
> >
> > 1) Install one Linksys card (tulip-diag reports it as a Digital DC21041
> > Tulip).  Works great.  Call this eth0.
> >
> > 2) Install 2nd Linksys card (tulip-diag reports this as an ADMtek AL985
> > Centaur-P but I call it a Linksys LNE100TX v4.1).  This one is eth1.
> >
> > 3) 2nd Linksys card eth1 works great...but eth0 stopped working.  Here
> > is an excerpt from /var/log/messages:
> >
> > Jan 15 18:06:50 firewall kernel: eth0: 21041 media switched to 10baseT.
> > Jan 15 18:06:52 firewall kernel: eth0: 21041 transmit timed out, status
> > fc678057
> 
> Hmmm, looks like a simple IRQ problem.  The chip is raising an
> interrupt, but it isn't getting through the system.
> 
> Check /proc/interrupts to confirm.
> 
> > I can't fathom what I might have done wrong.  Any help or suggestions
> > would be greatly appreciated.
> 
> Adding another card moved the interrupt assignments around.
> 
> Donald Becker                           becker@scyld.com
> Scyld Computing Corporation             http://www.scyld.com
> 410 Severn Ave. Suite 210               Second Generation Beowulf Clusters
> Annapolis MD 21403                      410-990-9993