Kyle A. Holder wrote:
> 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.
Theoretically, that driver will work fine. Read up on it here
ftp://aiedownload.intel.com/df-support/2896/ENG/e100.txt
and see if your adapter is listed. Be sure to check the board-id
against what's stamped on your board! That driver is version 2.1.15:
http://downloadfinder2.intel.com/scripts-df/Detail_Desc.asp?ProductID=62&DwnldID=2896
If someone built _that_ e100.c source from Intel against Dachstein,
then you should be able to use that one. Did they Charles?
But in general, people build the eepro100.o scyld linux networking driver,
which works great for my pro100+ pci adapters. But you have pro100+ Management.
And that's differnt. The scyld driver is here:
http://www.scyld.com/network/eepro100.html
Because your pro100+ Management uses the usual 82558 controller,
I'm guessing it will run fine with the eepro100.o also.
Now as far as IRQ's go, network cards have historically taken
IRQ 10. Because the PCI cards get interrupts before the ISA
cards do, then let the Pro100+ have IRQ 10. Load it's module second,
as suggested so that it becomes eth1. Let it autonegotiate
speed and duplex.
3c509.o
eepro100.o
For the 3c509B, the 3c509.o is the right driver, and it's
described here:
http://www.scyld.com/network/3c509.html
As Brian mentioned, use the 3c5x9cfg.exe dos utility
and force the card to these settings:
IRQ 11,
0x310 (the pro100+ will take 0x300),
PNP=no,
Speed=auto line speed,
Duplex=auto-negotiate,
Tranceiver Type=RJ-45 connector.
It's often a good idea to force the RJ-45, but then again,
you said you had a TPO, and O means "only" :) You can pick
other addresses, but 0x310 or 0x320 are resonable settings.
Dont' choose 0x2F8, 0x370, 0x3C8, or 0x3F8. Once you set
those and the utility burns them into the EEPROM, you won't
need any command line switches next to 3c509.o, simply
3c509.o
eepro100.o
or
3c509.o
e100.o
should suffice :)
Once you force the 3com to irq 11, then go into the
mainboard bios and tell it irq11 is reserved for legacy
ISA cards if possible.
Should work if you don't have it figured already.
> 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.
Flash the mainboard if there's a newer BIOS for it after you back
up the current BIOS.
> 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.
The PNP subsystem on VX mainboards was new and a little.... iffy.
Good Luck!
Matthew
-------------------------------------------------------
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
