On Tue, 22 Feb 2000, you 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.
The 3c59x is also good and perhaps a bit more economical.
Yep, duplicates what I found--shared interrupts. Windows handles that with
some polling at non-maskable ISR time, at the cost of efficiency. Nothing
like getting a frame dropped because you have to blast the next wave of
monsters in Quake.
And of course the cards worked fine in some old Socket-7 machines without AGP
for the same reason. No AGP means IRQ 11 is not a problem for the network card.
It might be easier to move the interrupt for AGP, but I wasn't successful with
that strategy either. You might try.... xdosemu to run the interrupt setting
of the card in jumperless mode instead of plug N pray. I didn't have the
floppy on the cards.
In all fairness, I should mention that I have two machines using AGP and
eepro100. They came working from the manufacturer. I queried the manufacturer
and he doesn't know what made them work properly and others not. Perhaps
different lot numbers or revisions from Intel, or perhaps different Chipsets on
the Motherboard. The failures I had were with an Intel LX chipset board and
ATI RageIIC AGP, and the successes used Trident 3DImage 985 AGP and a Gigabyte
5AX Motherboard which utilizes an ALi Aladdin V Chipset. On the successes, the
eepro irq is 12.
Civileme
>
> Jeremy
