update(2) of Network/Sound conflict [FIXED!!]

[G.J.]

just after i sent that last msg.... it occurred to me to try one more
tactic.

it worked. at least it's a workaround if not the real fix.

i took the offending NIC(s) =] and put them in different slots.
lo and behold the PCI bus gave them new nics that didn't conflict with my
sound card!!

in fact, as you can see here, i got them both to be recognized.


eepro100.c:v0.99B 4/7/98 Donald Becker linux-eepro100@cesdis.gsfc.nasa.gov
eth0: Intel EtherExpress Pro 10/100 at 0x10e0, 00:A0:C9:EA:55:40, IRQ 9.
  Board assembly 710550-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eepro100.c:v0.99B 4/7/98 Donald Becker linux-eepro100@cesdis.gsfc.nasa.gov
3c59x.c:v0.99H-WOL 2/24/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth1: 3Com 3c905B Cyclone 100baseTx at 0x1000,  00:10:4b:0a:51:f1, IRQ 5
  8K byte-wide RAM 5:3 Rx:Tx split, Autonegotiate interface.
  MII transceiver found at address 24, status 7849.
  MII transceiver found at address 0, status 7849.
  Enabling bus-master transmits and whole-frame receives.

i know that the network code fully supports irq sharing, so my inclination
is to blame the driver(s) for the creative labs ensoniq 64D sound card.
(which, btw, i reported incorrectly as being PCI. it's not. it's ISA)

since the sound card was ISA, shouldn't my first attempt at fixing the
conflict (reserving the irq for legacy ISA devices in BIOS) have worked?

oh well. i'm happy cause i can listen to my Led Zeppelin AND so ssh!

--gareth


--
/*
 * Gareth Jenkins
 * Linux hacker, "Mr. Sensitive", armchair philosopher,
 * PERL lover, child of God
 *
 * http://endor.hsutx.edu/~locutus http://www.wtlug.org
 */