Problems with SMC EtherPower II

Problems with SMC EtherPower II

Post by Richard van der Hof » Sat, 28 Aug 1999 04:00:00



I recently upgraded my kernel to 2.2.10 (from 2.0.36), and since doing
so, I have been unable to get my Etherpower II working.  If anybody
has any suggestions where I go from here, I would be most grateful!

I'm using version 1.06 of the driver, and am trying to connect it to a
10baseT link; to this end I am using the options
  debug=6 options=4 full_duplex=0
to the module.

The card appears to be correctly detected at startup:

$ dmesg
...
epic100.c:v1.06 2/10/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/
epic100.html
eth0: SMSC EPIC/100 83c170 at 0xe800, IRQ 11, 00:e0:29:33:f3:b6.
eth0: EEPROM contents
 e000 3329 b6f3 1b00 001d 1c08 10b8 a015 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
 0010 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 4d53 3943 3334 4232
 5854 2020 0000 0000 0200 0200 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
eth0: MII transceiver #3 control 3000 status 7809.
eth0:  Autonegotiation advertising 01e1 link partner 0001.
eth0: Setting half-duplex based on MII xcvr 3 register read of 0001.
eth0: epic_open() ioaddr e800 IRQ 11 status 0512 half-duplex.
...

eth0: Media monitor tick, Tx status 00000000.
eth0: Other registers are IntMask 13bf IntStatus 248000 RxStatus ffff007f.
eth0: Media monitor tick, Tx status 00000000.
eth0: Other registers are IntMask 13bf IntStatus 248000 RxStatus ffff007f.
...

However I find that no packets are received transmitted without
error.  The following error occurs on packet transmission:
  eth0: Transmit error, Tx status 00007000.

epic-diag reports the following:

richards:epic# ./epic-diag -a
Found SMC83C170 EPIC/100 card #1 at 0xe800.
The EPIC/100 chip appears to be active, so some registers will not be read.
To see all register values use the '-f' flag.
EPIC chip registers at 0xe800
 0x000: 00000008 00248040 000013bf 00000512 0000001d 00000060 00000000 00000000
 0x020: 00000000 00000000 00000000 0000ffff 00000650 00000021 00000016 00003c60
 0x040: 0000e000 00003329 0000b6f3 00001b00 0000ffff 0000ffff 0000ffff 0000ffff
 0x060: 0000000c ******** ******** ******** 00003c79 00003000 ******** ********
 0x080: ******** 00fff820 ******** ******** ******** ******** ******** ********
 0x0A0: ******** ffff087f ******** ******** ffff0bff ******** ******** ********
 0x0C0: ******** 00fffad0 ******** ******** ******** ******** ******** 00fff900
 0x0E0: ******** ******** ******** ******** ******** ******** ******** ********
  Interrupt sources are pending.
   Tx chain done indication.
   Rx status valid indication.
  Transmitter: slot time 512 bits, half-duplex mode.
   Last transmit FAILED!!, 16 collisions.

richards:epic# ./epic-diag -e
Found SMC83C170 EPIC/100 card #1 at 0xe800.
EEPROM contents:
  e000 3329 b6f3 1b00 001d 1c08 10b8 a015
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0010 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 4d53 3943 3334 4232
  5854 2020 0000 0000 0200 0200 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
 The word-wide EEPROM checksum is 0x2a8e.
Parsing the EEPROM of a EPIC/100:
 Station Address 00:E0:29:33:F3:B6.
 Board name 'SMC9432BTX  ', revision 182.
 Calculated checksum is 00.
richards:epic# ./epic-diag -m
Found SMC83C170 EPIC/100 card #1 at 0xe800.
 MII PHY found at address 3.
 MII PHY #3 transceiver registers:
   1000 782d 0181 4401 01e1 0021 0000 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0040 0018 ffff ffff ffff ffff ffff ffff
   ffff ffff ffff 003e ffff 0040 0000 1dc4.
 MII PHY #3 transceiver registers:
   1000 782d 0181 4401 01e1 0021 0000 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0040 0018 ffff ffff ffff ffff ffff ffff
   ffff ffff ffff 003e ffff 0040 0000 1dc4.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:51:--:--:--, model 0 rev. 1.
   Vendor/Part: Quality Semiconductor (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0021: 10baseT.
   Negotiation did not complete.

I've tried installing the driver both as a module and built in to the
kernel, but the effect seems much ther same.

--

Jesus College, Cambridge, England | http://www.jesus.cam.ac.uk/~rav21
-----------------------------------------------------------------------

 
 
 

Problems with SMC EtherPower II

Post by Richard van der Hof » Sat, 28 Aug 1999 04:00:00



>Try forcing it to 100Mbps (or 10Mbps: whichever
> your hub is capable of) instead of allowing it to attempt to figure it out for
> itself.

Yeah, I wondered about this myself, but couldn't figure out how to do
it - I set it to 10Mbps in the DOS configuration utility, but that
doesn't seem to do much.  Is there another method?

--

Jesus College, Cambridge, England | http://www.jesus.cam.ac.uk/~rav21
-----------------------------------------------------------------------

 
 
 

Problems with SMC EtherPower II

Post by Richard van der Hof » Tue, 31 Aug 1999 04:00:00


I recently posted about my problems getting my Etrherpower II working,
but unfortunately didn't get very far - this is basically a plea to
say, if anyone has any suggestions, I'd be most grateful!

I haven't repeated the diagnostics outputs in the uinterest of
bandwidth, but the symptoms are (essentially) that the card is
detected correctly, but no packets are sent or received.

TIA

--

Jesus College, Cambridge, England | http://www.jesus.cam.ac.uk/~rav21
-----------------------------------------------------------------------

 
 
 

Problems with SMC EtherPower II

Post by S » Fri, 03 Sep 1999 04:00:00


Not sure if this is related to your problem or not, but I had a hell of a
time with my EtherPower II card.  It took me forever to figure out that I
had to shut the machine off (and unplug it from the wall) if I switched
between windoze and linux.  


says...

Quote:> I recently upgraded my kernel to 2.2.10 (from 2.0.36), and since doing
> so, I have been unable to get my Etherpower II working.  If anybody
> has any suggestions where I go from here, I would be most grateful!

> I'm using version 1.06 of the driver, and am trying to connect it to a
> 10baseT link; to this end I am using the options
>   debug=6 options=4 full_duplex=0
> to the module.

> The card appears to be correctly detected at startup:

> $ dmesg
> ...
> epic100.c:v1.06 2/10/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/
> epic100.html
> eth0: SMSC EPIC/100 83c170 at 0xe800, IRQ 11, 00:e0:29:33:f3:b6.
> eth0: EEPROM contents
>  e000 3329 b6f3 1b00 001d 1c08 10b8 a015 0000 0000 0000 0000 0000 0000 0000 0000
>  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
>  0010 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 4d53 3943 3334 4232
>  5854 2020 0000 0000 0200 0200 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> eth0: MII transceiver #3 control 3000 status 7809.
> eth0:  Autonegotiation advertising 01e1 link partner 0001.
> eth0: Setting half-duplex based on MII xcvr 3 register read of 0001.
> eth0: epic_open() ioaddr e800 IRQ 11 status 0512 half-duplex.
> ...

> eth0: Media monitor tick, Tx status 00000000.
> eth0: Other registers are IntMask 13bf IntStatus 248000 RxStatus ffff007f.
> eth0: Media monitor tick, Tx status 00000000.
> eth0: Other registers are IntMask 13bf IntStatus 248000 RxStatus ffff007f.
> ...

> However I find that no packets are received transmitted without
> error.  The following error occurs on packet transmission:
>   eth0: Transmit error, Tx status 00007000.

> epic-diag reports the following:

> richards:epic# ./epic-diag -a
> Found SMC83C170 EPIC/100 card #1 at 0xe800.
> The EPIC/100 chip appears to be active, so some registers will not be read.
> To see all register values use the '-f' flag.
> EPIC chip registers at 0xe800

 
 
 

Problems with SMC EtherPower II

Post by Richard van der Hof » Mon, 06 Sep 1999 04:00:00



> Not sure if this is related to your problem or not, but I had a hell of a
> time with my EtherPower II card.  It took me forever to figure out that I
> had to shut the machine off (and unplug it from the wall) if I switched
> between windoze and linux.  

Hmmm... that must be a bit of a pain.  Sadly it doesn't seems to help
here, but thanks anyway.

--

Jesus College, Cambridge, England | http://www.jesus.cam.ac.uk/~rav21
-----------------------------------------------------------------------

 
 
 

Problems with SMC EtherPower II

Post by Richard van der Hof » Tue, 28 Sep 1999 04:00:00



> Run 'mii-diag' to check the link state..
>   http://cesdis.gsfc.nasa.gov/linux/diag/index.html

Right - sorry about the delay (I've been away); here it is:

wallace:rav21$ ~/src/epic/mii-diag -v

Using the default interface 'eth0'.
 MII PHY #3 transceiver registers:
   1000 782d 0181 4401 01e1 0021 0000 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0040 0018 ffff ffff ffff ffff ffff ffff
   ffff ffff ffff 003e ffff 0040 0000 1dc4.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner is generating 10baseT link beat.
 MII PHY #3 transceiver registers:
   1000 782d 0181 4401 01e1 0021 0000 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0040 0018 ffff ffff ffff ffff ffff ffff
   ffff ffff ffff 003e ffff 0040 0000 1dc4.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:51:--:--:--, model 0 rev. 1.
   Vendor/Part: Quality Semiconductor (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0021: 10baseT.
   Negotiation did not complete.

It looks as though the link is ok, but the auto-negotiation is getting
confused.

--

Jesus College, Cambridge, England | http://www.jesus.cam.ac.uk/~rav21
-----------------------------------------------------------------------