On Tue, Feb 22, 2000 at 08:24:41AM -0600, 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.
The PCI spec requires that drivers be able to daisy chain (share)
interrupts. So this should not be a problem. You might want to look at the
source for the AGP card driver and make sure that it is either not using
the interrupt or chaining properly. (I am assuming you have X working
properly.)
->
-> 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?
When you boot to DOS, do you boot to real mode (no memory manager, like
emm386.sys)? If so, that may be your problem.
->
-> 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
--
-- C^2
No windows were crashed in the making of this email.
Looking for fine software and/or web pages?
http://w3.trib.com/~ccurley
