[eepro100] auto-negotiation | force fixed

[Frank Lenaerts]

--wxDdMuZNg1r63Hyj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

on Wed, Oct 30, 2002 at 10:42:40PM -0500, Donald Becker wrote about Re: [ee=
pro100] auto-negotiation | force fixed:
> On Wed, 30 Oct 2002, Frank Lenaerts wrote:
>=20
> > Each switch is a 3Com Office Connect (10/100Mbps). All hosts (A, B and
> > C) have 2 NICs: eth0 (indicated by 0) is a Myson MTD803 using the
> > fealnx driver
>=20
> Grrrmmmmm.  U

Are these cards that bad?

> As usual, I recommend
>   -  Checking for sleep mode

Sleep mode is not enabled.

> > Finally, I checked the interfaces (using myson-diag -m and
> > eepro100-diag -m -f).
>=20
> The following is very useful
>    mii-diag --watch
> You can usually get the same effect with the per-chip diags and "-mm".
>=20
> > --- begin myson ---
> > myson-diag.c:v1.00 5/15/2001 Donald Becker (becker@scyld.com)
> >  http://www.scyld.com/diag/index.html
> > Index #1: Found a Myson MTD803 adapter at 0xb800.
> >  Station address 00:02:44:63:00:02.
> >   Receive mode is 0x80f48e61: Normal unicast and hashed multicast.
> >  This device appears to be active, so some registers will not be read.
> >  To see all register values use the '-f' flag.
> >   No interrupt sources are pending (0000).
> >  MII PHY #32 transceiver registers:
> >    3000 786d 0302 d000 41e1 45e1 0000 0000
>=20
> Looks OK to me.
>=20
> >  Vendor ID is 00:c0:b4:--:--:--, model 0 rev. 0.
> >    Vendor/Part: ASIX (unknown type).
>=20
> Errkkk?  This transceiver ID was in the ASIX chip.
> That's very curious.  I'll have to check out that ID in libmii.c.
> This likely means that the vendor-specific registers are misinterpreted...
>=20
> >   TDK format vendor-specific registers 16..18 are 0x0602 0x0000 0x0000
> >       Link polarity is detected as normal.
> >      100baseTx Coding and scrambling is disabled!
> >       Auto-negotiation complete, 10Mbps half duplex.
> >       Rx link in fail state, PLL locked.
> >   10baseT loopback mode.
> >       No new link status events.
>=20
> Yup, ignore this message.

On the other hand, if I issue an mii-diag -w eth0 (the Myson NIC), I
get the following output. This could also be due to the fact that
vendor-specific registers are misinterpreted.

--- begin ---
Basic registers of MII PHY #0:  0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x0000: Auto-negotiation disabled, with
 Speed fixed at 10 mbps, half-duplex.
 Basic mode status register 0x0000 ... 0000.
   Link status: not established.
 Link partner information information is not exchanged when in fixed
 speed mode.=20
   End of basic transceiver informaion.

Monitoring the MII transceiver status.
11:40:22.522  Baseline value of MII BMSR (basic mode status register)
is 0000.
---  end  ---


--=20
lenaerts.frank@pandora.be

Those who do not understand Unix are condemned to reinvent it, poorly."
-- Henry Spencer


--wxDdMuZNg1r63Hyj
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE9wQnWuSr0q5/7NwcRAtZxAKCDjJqa2e6WXmUSx9BbM7yTxfI7awCfVkMW
hMV4D6TVvIoPDAArK+K1Luo=
=MBcM
-----END PGP SIGNATURE-----

--wxDdMuZNg1r63Hyj--