Thanks for replying. I've since gone back and taken 8390 out. At first, when things weren't working right, I tried putting it in there, thinking there was some sort of wierd dependancy or something. I've searched through Intel's site, and found out that I need to be using e100.o. So, I have since switched to that driver, and now, am having IRQ problems, as you have correctly pointed out. I am currently trying to figure out if it is possible for me to either disable the PNP on my motherboard, or if I have to get some kind of BIOS flash. I looked at the logs, and found that both cards were attempting to use IRQ 10. Bad news. Do you know if there is any command-line way to change the IRQ of the NICs, or does that *have* to be done through the BIOS? BTW, I'm using a P5I430VX-250 Explorer MB. Sometimes there are jumpers that can disable the PNP, but I'm not sure they're on this board.
Thanks again, Kyle -----Original Message----- From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 9:00 PM To: Kyle A. Holder; [EMAIL PROTECTED] Subject: Re: [leaf-user] Dachstein NIC Card Conflicts > P166/32 RAM > Dachstein (Kernel 2.2.19-3-LEAF) > Eth0: Intel PRO/100+ Management (PCI) > Eth1: 3COM 3C509B-TPO (ISA) > > Loaded modules on startup: > > pci-scan.o > 8390.o > eepro100.o > > 3c509.o > > All modules load correctly, and self-test correctly. However, the network > cards conflict with each other. <snip> First off, why are you loading the 8390 driver? That's not needed by either the eepro100 or the 3c509 driver, and while it shouldn't be causing any problems, you never know... Second, what I/O port and IRQ are you assigning the 3c509 card? Did you make sure to flag the IRQ as "used by ISA card" in the BIOS, so it won't get assigned to a PCI slot? Most Pentium systems of this era had some mechanism to register IRQ's used by ISA cards with the BIOS so they wouldn't be assigned to PCI slots...some would even allow you to manually assign IRQ's to particular PCI slots, which may be required in your situation. Also, pay particular attention to the messages output by the drivers when loaded (regarding I/O space & IRQ mapping), and you might want to check out /proc/interrupts, /proc/ioports, and /proc/pci, looking for potential conflicts... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
