What NIC do you have? Some modules don't need io= entries to work (e.g., the
various 3Com modules, which won't work even with a correct io= option),
while others (most notably ne.o) do.
If you do need an io= entry, there's no good way to figure out the value in
Linux. Your two options are:
1. Get the configuration program for the NIC and run it. (They are usually
DOS based and can be run using FreeDOS or DR-DOS.) Or, if the card uses
jumpers, check the jumper settings against the documentation. This will tell
you both the io and the irq settings.
2. Use brute force. Keep changing the io= line until you get a hit. Try
0x240 through 0x360, incrementing by 20. Be aware that some NICs use
"software" io values way out of this range -- you won't get those by guessing.
One other thing to watch for is an irq conflict. Older NICs (actually, EVERY
isa NIC I've even installed) come out of the box set for irq=3, which
conflicts with /dev/ttyS1 . They need to be moved (via jumpers or the config
utility) to a free irq, usually 9, 10, or 11 (depending on what else is in
your system). pci NICs I've used don't have this problem; the pci stuff in
the BIOS handles both irq and ioport assignment quite well.
At 03:18 PM 1/19/00 +0100, James (Jim) Hatridge wrote:
>Paint me dumb but I can't figure out which ioport my network card is on.
>When it probes for my ethercard at 0x0300 it does not find it. Ioports
>does not show 0300, which one should I be using? Thanks! BTW, I'm using
>SuSE 5.2 and my system has two printer ports.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
