>From the Ethernet-HOWTO
3.6. Problems with 3Com cards
Problem: The 3c503 picks IRQ N, but this is needed for some other
device which needs IRQ N. (eg. CD ROM driver, modem, etc.) Can this
be fixed without compiling this into the kernel?
Solution: The 3c503 driver probes for a free IRQ line in the order {5,
9/2, 3, 4}, and it should pick a line which isn't being used. The
driver chooses when the card is ifconfig'ed into operation.
If you are using a modular driver, you can use module parameters to
set various things, including the IRQ value.
The following selects IRQ9, base location 0x300, <ignored value>, and
if_port #1 (the external transceiver).
io=0x300 irq=9 xcvr=1
Alternately, if the driver is compiled into the kernel, you can set
the same values at boot by passing parameters via LILO.
LILO: linux ether=9,0x300,0,1,eth0
The following selects IRQ3, probes for the base location, <ignored
value>, and the default if_port #0 (the internal transceiver)
LILO: linux ether=3,0,0,0,eth0
Problem: 3c503: configured interrupt X invalid, will use autoIRQ.
Reason: The 3c503 card can only use one of IRQ{5, 2/9, 3, 4} (These
are the only lines that are connected to the card.) If you pass in an
IRQ value that is not in the above set, you will get the above
message. Usually, specifying an interrupt value for the 3c503 is not
necessary. The 3c503 will autoIRQ when it gets ifconfig'ed, and pick
one of IRQ{5, 2/9, 3, 4}.
Solution: Use one of the valid IRQs listed above, or enable autoIRQ by
not specifying the IRQ line at all.
Problem: The supplied 3c503 drivers don't use the AUI (thicknet) port.
How does one choose it over the default thinnet port?
Solution: The 3c503 AUI port can be selected at boot-time for in-
kernel drivers, and at module insertion for modular drivers. The
selection is overloaded onto the low bit of the currently-unused
dev->rmem_start variable, so a boot-time parameter of:
LILO: linux ether=0,0,0,1,eth0
should work for in-kernel drivers.
To specify the AUI port when loading as a module, just append xcvr=1
to the module options line along with your i/o and irq values.
3.7. FAQs Not Specific to Any Card.
3.7.1. Ethercard is Not Detected at Boot.
The usual reason for this is that people are using a kernel that does
not have support for their particular card built in. For a modular
kernel, it usually means that the required module has not been
requested for loading, or that an I/O address needs to be specified as
a module option.
If you are using a modular based kernel, such as those installed by
most of the linux distributions, then try and use the configuration
utility for the distribution to select the module for your card. For
ISA cards, it is a good idea to determine the I/O address of the card
and add it as an option (e.g. io=0x340) if the configuration utility
asks for any options. If there is no configuration utility, then you
will have to add the correct module name (and options) to
/etc/conf.modules -- see man modprobe for more details.
........
information in /usr/doc/HOWTO.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
<[EMAIL PROTECTED]> Roberto Magana. Escuela de Fisica UCR.
(The Physics Dept. University of Costa Rica.)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
