[tulip] Problem with ADMtek Centaur-P

[Duane Clark]

Howdy,

I have a problem with my computer randomly locking up hard after a
recent kernel upgrade (to RH 7.3, kernel 2.4.18-18, compiled). For 
various reasons not important at the moment (I don't think) I suspect 
this to be due to the ethernet interface. So I figured I would try the 
latest tulip driver.

My computer has two ethernet cards. They both come up with the stock
tulip driver, but only the first comes up with the latest tulip driver.
I have confirmed that simply swapping the tulip.o file between the
versions (I saved the old one) alone determines whether the second card
comes up.

Here is a snip from dmesg with the stock tulip driver.

pci-scan.c:v1.11 8/31/2002  Donald Becker <becker@scyld.com>
http://www.scyld.com/linux/drivers.html
Linux Tulip driver version 0.9.15-pre11 (May 11, 2002)
PCI: Enabling device 00:0d.0 (0384 -> 0387)
PCI: Found IRQ 11 for device 00:0d.0
PCI: Sharing IRQ 11 with 00:09.1
PCI: Sharing IRQ 11 with 01:00.0
eth0: Lite-On PNIC-II rev 37 at 0xb800, 00:A0:CC:E5:4D:82, IRQ 11.
PCI: Enabling device 00:0e.0 (0014 -> 0017)
PCI: Assigned IRQ 10 for device 00:0e.0
PCI: Sharing IRQ 10 with 00:05.0
PCI: Sharing IRQ 10 with 00:07.0
PCI: Sharing IRQ 10 with 00:09.2
eth1: ADMtek Comet rev 17 at 0xb400, 00:20:78:04:1C:53, IRQ 10.

And here is the same section with the latest driver. Pretty much 
everything in dmesg prior to this point is identical.

pci-scan.c:v1.11 8/31/2002  Donald Becker <becker@scyld.com>
http://www.scyld.com/linux/drivers.html
tulip.c:v0.95f 11/17/2002  Written by Donald Becker <becker@scyld.com>
    http://www.scyld.com/network/tulip.html
    The PCI BIOS has not enabled the device at 0/104!  Updating PCI
command 0384->0386.
eth0: Lite-On LC82C115 PNIC-II rev 37 at 0xf8995000, 00:A0:CC:E5:4D:82,
IRQ 11.
PCI device 'ADMtek Centaur-P' was not assigned an IRQ.
It will not be activated.