[[ I've added these answers as
http://cesdis.gsfc.nasa.gov/linux/misc/faq.html#ne2000
http://cesdis.gsfc.nasa.gov/linux/misc/faq.html#pci-irq
]]
On Wed, 6 Jan 1999, Wes wrote:
> From: Wes <[EMAIL PROTECTED]>
> I've been useing the same NIC cards and getting the same problem. Does
> anyone have any info on these cards? Could they be part of the problem?
> > From: kristof kowalski <[EMAIL PROTECTED]>
> > Subject: nic collisions
> >i have a realtek8029 (ne2000 pci compliant) card. it worked fine in a
> >machine i have, i then moved it to another pci based system and ever
> >since then it has started getting network collisions on that port. my
> >guess is the resource settings on the card. this card is a simple 10bT
> >card with nothing special on there.
> >
> >the only difference since the move of the card is, i have have switched
> >from a coaxial based setup to a twisted pair one. could it be that the
> >actual port is dead?
> >
> >the nic could also be set to full duplex somehow. is there an option to
> >disable this option, or somehow at least check under linux. i've seen
> >this to be the problem in many a setups in my time. since the hub is
> >only a simple half duplex entity.
There was no method in the original NE2000 to set full duplex (FD).
The NE2000 cards that support FD do so by loading the duplex setting from
the EEPROM at power-up time. FD is always disabled when using a 10base2
connection.
There was no software setting in the original NE2000 for the transceiver type.
Most NE2000 cards support 10baseT and "other", switching transceivers based
on the 10baseT link beat. If there are two other transceiver connections
(e.g. AUI and BNC), the active one is selected by an EEPROM bit.
There was no method in the original NE2000 to read or write the EEPROM.
Thus there is no standard way to find or change either of the above
settings.
There was no software setting in the original NE2000 for IRQ or IOAddr.
Once again, modern ISA chips put these into the EEPROM. PCI cards have
their IO address and IRQ line set by the PCI BIOS.
> >anyhow. i wanted to know how to set the interrupt and io settings for
> >the card. i do an ifconfig eth0 irq 10 and it says that it's not
> >supported. i check the /proc/pci resources and it always has it as
> >interupt 5. i have pasted this on.
You can only change this in the PCI BIOS setup. While you can overwrite the
PCI IRQ reporting register on the board, that won't change the
interrupt-to-IRQ steering logic on the motherboard.
Donald Becker [EMAIL PROTECTED]
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771
301-286-0882 http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
