1
0
mirror of https://git.FreeBSD.org/src.git synced 2025-01-28 16:43:09 +00:00

Added comments regarding 3Com PCMCIA cards:

- Multi-function ethernet/modem cards are not supported
- 3c589D is not supported
- Add advice on how to setup the driver to work with 3c589 cards.
- State how to select the network connector.
This commit is contained in:
Nate Williams 1997-03-08 20:04:20 +00:00
parent 870d983770
commit df3be16ec3
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=23544

View File

@ -1,4 +1,4 @@
Hardware Documentation Guide: $Id: hardware.hlp,v 1.22 1997/03/02 14:20:21 joerg Exp $
Hardware Documentation Guide: $Id: hardware.hlp,v 1.23 1997/03/07 16:39:28 jkh Exp $
Contents last changed: Jan 14th, 1997
@ -106,11 +106,10 @@ le0 300 5 dyn d0000 Digital Equipment EtherWorks
lnc0 280 10 n/a dyn Lance/PCnet cards
(Isolan, Novell NE2100, NE32-VL)
vx0 dyn dyn n/a dyn 3Com 3c59x / 3c9xx
ze0 300 5 dyn d8000 IBM/National Semiconductor
ze0 300 5 n/a d8000 IBM/National Semiconductor
PCMCIA Ethernet Controller
zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III
Ethernet Controller (but not
3C589D!)
zp0 300 10 n/a d8000 3Com 3c589 Etherlink III
PCMCIA Ethernet Controller (NOT 3c589D!)
--- End of table ---
@ -296,6 +295,50 @@ A: Use the UserConfig utility (see section 1.0) and disable the probing of
the devices that you will be using enabled in your kernel.
Q: FreeBSD claims to support the 3Com PCMCIA card, but my card isn't
recognized when it's plugged into my laptop.
A: There are a couple of possible problems. First of all, FreeBSD does
not support multi-function cards, so if you have a combo
ethernet/modem card, it won't work. Secondly, 3Com's most recent
version of the 3C589, the 'D' revision is not supported by the
GENERIC kernel. 3Com changed the card in a manner that we can no
longer support it in the default driver (* See below).
Assuming you have an older 3C589 card, then this card is
supported and will work in FreeBSD. The driver was written just like
all of the other drivers in FreeBSD, and depend on the card's own
configuration data stored in NVRAM to work. You must correctly
configure FreeBSD's driver to match the IRQ, port, and IOMEM stored
in NVRAM.
Unfortunately, the only program capable of reading them is the
3COM supplied DOS program. This program must be run on a absolutely
clean system (no other drivers must be running), and the program will
whine about CARD-Services not being found, but it will continue.
This is necessary to read the NVRAM values. You want to know the
IRQ, port, and IOMEM values (the latter is called the CIS tuple by
3COM). The first two can be set in the program, the third is
un-settable, and can only be read. Once you have these values, set
them in UserConfig and your card will be recognized.
* The D revision is supported in new PCMCIA generic code written for
FreeBSD, but there is little/no documentation written on how to set
it up yet. Hopefully in the next release of FreeBSD the new code
will be better supported, which will add support for almost all
PCMCIA cards.
Q: FreeBSD finds my PCMCIA network card, but no packets appear to
be sent even though it claims to be working.
A: Many PCMCIA cards have the ability to use either the 10-Base2 (BNC)
or 10-BaseT connectors for connecting to the network. The driver is
unable to 'auto-select' the correct connector, so you must tell it
which connector to use. In order to switch between the two
connectors, the link flags must be set. Depending on the model of
the card, '-link0 link1' or 'link0 -link1' will choose the correct
network connector. You can set these in sysinstall by using the
'Extra options to ifconfig:' field in the network setup screen.
Q: The system finds my ed network card, but I keep getting device
timeout errors.