How to detect and set up a ISA NIC

[rov]

I have 2 ISA NICs in an old 486 comp so I can share my connection between my wonderful Linux maching and my family's Win 98 box that will never connect to the DSL connection consistently. So....

The ISA NICs aren't detected at startup, I don't know the card numbers (I bought them at a used parts store) and because of that don't know what drivers to use.

And then if anybody could tell me how to set them up after that....

BTW, there's nothing about ISA NICs out there in docs. It's all PCI stuff.

[Iceman]

You'll HAVE to determine what brand and model# of NIC's you have--or what chipset they use. After that it's simply a matter of configuring the card with a manufacturer supplied DOS utility.

There's plenty of info on ISA NIC's. Read the Ethernet HOW-TO for starters.

Good luck

[rov]

So basically, I'm screwed?!?!?!?!?!?!

I don't know the card #s, but I'll check on the cards. Isn't there a program to find the right modules like with PCI cards???

[rov]

Alright, I actually found numbers on the card itself. I'm going to try to set it up tommorow or something.

[DJ-dOoK]

Word of advice. If the ISA cards are NE2000 compatible, there should not be as much of a problem!

[fuzzy]

Originally posted by DJ-dOoK:
Word of advice. If the ISA cards are NE2000 compatible, there should not be as much of a problem!

Yeah, I have an old ISA NIC from an old 486 and it works just find. I think it's a D-Link 220? Really, though, it's an NE2000 compatible and it took only a few things to get it going. OVerall, relatively painless! http://www.linuxnewbie.org/ubb/smile.gif


------------------
I spy with my little eye something that begins with "W"... oops, it's gone now.

[mattmorrow]

Here are some tips for setting up your NIC:
1. Make sure you're using the right module.
Your distro vendor should have a hardware compatability matrix (that lists your card and the corresponding module).
If you can't find it, do a web search to see what module others have used for that card.
You can always try a few different modules. Remember that not all cards from the same manufacturer use the same module.
For example, the Netgear PCI card FA310tx uses tulip.o while their EA201c uses ne.o.
Initially, let the system try to determine the IRQ and base address. Ultimately, you may have to.
2. Test with a fully supported card first.
If you can beg, borrow or steal a fully supported card (like the 3Com 3c509) do it.
It should be automatically detected. Note all the configuration settings using things like:
linuxconf, ifconfig, dmesg output, contents of /etc/conf.modules (or modules.conf), contents of ifcfg-eth0 (script)
When you replace the card with your card (which is perhaps a lesser known brand), use those same settings.
You may have to program your board (see below).
For example, I used the settings from a borrowed 3Com 3c509c (IRQ 10, base address 0x0300) that was automatically detected.
I removed it and programmed my Netgear EA201c (NE2000 compatible) to use the same.
3. Program the card. If you just can't get it to detect your card, program the card using the manufacture's configuration utility (on diskette w/ card or go to their site), then use linuxconf (or some other techniques) to configure the exact same settings.
The two most important settings are the IRQ and Base Address. Make a note of all the settings you use.
Usually, you boot from a DOS floppy, then replace it with the card manufactures diskette and run the config program.
Boot the system and run linuxconf to configure it identically.
HTH, matt

[rov]

Well, I'm in luck, I guess. Both the cards are 3c059. But they're not detected. Maye I'm not using the right module. What module do they use??? I'll go check the NHF and see if I can fidn ti there.

How do I fidn the IRQ and Base ADress and such and make Linux detect the card??

[edit]
Well, don't I feel like an idiot. 3C059 is the module name. Ooops

[This message has been edited by rov (edited 07 November 2000).]