Thanks to help from Gene Black.. The resolution to this particular problem was: IRQ conflict AMIBIOS ver 1.00.12.AX1T has in the Advanced Configuration the options of ISA IRQ 10 [Used/Free] and ISA IRQ 11 [Used/Free].. by default they were both set to "Used", which apparently left only IRQ 9 for both cards. The successful final configuration was to set ISA IRQ 10 to "Free" and ISA IRQ 11 to "Used" (because the CDROM drive wanted 11 but the cards would always snag 11 if it was "Free"..) I don't know what I would have done if I had wanted to run three NICs in that machine, but for now I don't have to worry about it. Having more fun tracking down a different problem now.. I'll post more on that when I run out of ideas or have more information/ a resolution. Thanks.. Meriwether > -----Original Message----- > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] > Sent: Monday, October 25, 1999 4:56 PM > To: [EMAIL PROTECTED] > Subject: Funky 2 NIC behavior > > > Here is the hardware: > Running RH6.0 on Gateway Pentium 90 with 72 meg ram.. > Machine has two NIC's, one tulip, and one epic100.. > > Scenario: > Both cards are working fine, but something (power outage, test to see if > I've gotten rid of the problem, etc.) forces a reboot, > when the system comes back up, the epic100 comes back up, but one of 3 > things happens with the tulip > a) it does not come back up > b) it says it comes back up, but won't talk to or listen to anything > > c) it comes back up and talks, but very slowly with lots of packet > loss.. > I then power back down. Remove the epic100 card, and power back up. > Tulip comes up fine, talks fine, power back down. > Put epic100 card back in, tulip and epic100 both work just fine... until > next time I have to reboot when the same thing happens again. > > Experimentations/investigations/supplemental info: > I found someone else with an epic100, and so I traded epic100's.. same > problem.. work-around still works the same.. > I think that the tulip worked successfully in another 2 NIC machine > before, > but I am not positive.. > Don't ask how much time and cursing it took to find that work-around! > > Anyone heard of this problem before? Solutions? Requests for further > details? > > thanks in advance.. > > Meriwether > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
