PCI is PNP as a rule, assuming you have a motherboard that conforms to PCI 2.1. If
you have a quality motherboard and PCI interface, you should never, never have to
mess with interrupts, in hardware nor Linux.
And, unlike ISA, PCI can =share= interrupts. (yeah, I know it's radical) This is
why Winders works. The fact they are both on 11 is not a warning sign. Have you
updated the microcode on your motherboard? It's not made in Guatemala is it? PCI
2.1? If so, it's probably the Intel cards.
I have 2 3C905's on my Mandrake 7.0-2 firewall and they work flawlessly. You can
get the latest driver here:
http://support.3com.com/infodeli/tools/nic/linux.htm
Be sure you get a 3C905B, not the 3C905, which is an older flavor. I think the C
model only adds remote admin. The 3C980 & 990 add on-board processing.
I almost bought Intel. (whew) Your time is worth more than $50/card.
--
Carl A. Cook
quantumATaugustmailDOTcom
Sign the petition at http://www.libranet.com/petition.html
Help bring us more Linux Drivers
Jeremy Kersenbrock wrote:
> I found out why my eepro100 won't work, but I can't seem to fix it.
>
> Even though my nic is not in the slot next to AGP, my AGP card and nic both
> have IRQ11. I have no idea why it still works in windows. It doesn't even
> show up as a conflict in the device manager list. But if I click on
> resources for both cards, they both have IRQ11.
>
> I have my BIOS set for "NO PnP OS". The nic is jumerless (of course), and I
> can't change the IRQ in windows. The DOS setup program that came with the nic
> won't run on my machine (it proclaims that the card has not been installed in
> the machine. I hate DOS.) Any ideas on changing the IRQ?
>
> Also, I found another problem. I don't know if it is related to the IRQ
> problem or not. When I try to manually load my eepro100 module, I get the
> message "eepro100.o: eepro100.o: No such file or device". The eepro100.o
> module is in the appropriate subdirectory of /lib/modules. What's this all
> about?
>
> I'm trying to learn something, so I appreciate any suggestions,
> but I think I'll be looking for a different nic (a 3com 3c905-TX; I've heard
> that they're the best). 3+ weeks of trying to get this piece of junk to work is
> more than enough.
>
> Jeremy
S/MIME Cryptographic Signature
