PCMCIA Driver for SMC 10/100 CardBus

[Donald Becker]

On Mon, 8 May 2000, Richard Atterer wrote:

> > > When did they send it? I'm asking because they seem to have changed
> > > the design of the card without also changing the name or model
> > > number. (The PCMCIA ID *has* changed, though.) v0.91g most definitely
> > > doesn't work with it, and IIRC neither does 0.91x.
> > 
> > Hmmm, probably a year or so ago.  I can't find the paperwork on it.
> > 
> > Load with debug=7 and send the output...
> 
> I bought mine around Christmas. It needs the following entry in config.opts:
> 
>     card "SMC EZ CardBus 10/100 PC Card"
>       manfid 0x01bf, 0x2220
>       bind "tulip"

OK, that is different.  The line I have on the update page
  http://www.scyld.com/network/index.html
is
  card "SMC EZ CardBus 10/100 Ethernet"  manfid 0x01bf, 0x2225  bind "tulip"

I'll have to add
  card "SMC EZ CardBus 10/100 Ethernet"  manfid 0x01bf, 0x2220  bind "tulip"

> I have managed to build the v0.92 driver - however, I had to make
> cb_shim.o manually. The following was logged with debug=7 when I
> inserted the card. (It was already connected to the 10Mbit network
> here when I did so.)

How did you build the driver?  The Makefile should build cb_shim
automatically, but only if it finds the PCMCIA include files.
I guess I need to add a search path...

> Note the "Failed to map PCI address 0x0 for device 'Digital DS21143
> Tulip'". What's the problem?

> May  8 16:24:03 elessar kernel: tulip.c:v0.92 4/17/2000  Written by Donald Becker <becker@scyld.com>
> May  8 16:24:03 elessar kernel:   http://www.scyld.com/network/tulip.html
> May  8 16:24:03 elessar kernel: Failed to map PCI address 0x0 for device 'Digital DS21143 Tulip'.

Hmmm, I don't know what is triggering this message.  It looks as if the
card exists in the PCI table at this point (is the CardBus code adding
it?), but hasn't been assigned resources.

> May  8 16:24:03 elessar kernel: Found a Digital DS21143 Tulip at 32/0 address 0xa00c0000->0xc4c58000 IRQ 10.
> May  8 16:24:03 elessar kernel: Digital DS21143 Tulip at 32/0 command 0x7.
> May  8 16:24:03 elessar kernel: eth0: Digital DS21143 Tulip rev 65 at 0xc4c58000, 00:E0:29:55:E1:12, IRQ 10.
> May  8 16:24:03 elessar kernel: eth0:  EEPROM default media type Autosense.
> May  8 16:24:03 elessar kernel: eth0:  MII interface PHY 0, setup/reset sequences 2/2 long, capabilities 02 08.
> May  8 16:24:03 elessar kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.

This is a MII card.  The only non-obvious attribute is that it has a
transceiver reset method.

> May  8 16:24:03 elessar kernel: eth0:  MII transceiver #1 config 3000 status 7809 advertising 00a1.
> May  8 16:24:03 elessar kernel: eth0:  Advertising 01e1 on PHY 1, previously advertising 00a1.

Hmmm, it powered up advertising only half duplex media types!?

> May  8 16:24:04 elessar kernel: eth0: No link beat on the MII interface, status 7809.

You don't have link beat.  Are you certain the cable is good, and the dongle
is connected?  (A common problem is a broken dongle.)

> May  8 16:26:00 elessar kernel: eth0: Transmit error, Tx status 7fffbc00.

No link beat.

It's faintly possible that this is caused by an incorrectly reset
transceiver.  But it really looks like you have a standard case of no
network connectino.

Donald Becker				becker@scyld.com
Scyld Computing Corporation
410 Severn Ave. Suite 210
Annapolis MD 21403


-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-tulip-request@beowulf.org