From owner-freebsd-questions  Fri May 15 07:56:10 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA07859
          for freebsd-questions-outgoing; Fri, 15 May 1998 07:56:10 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from ns.cityip.co.za (ns.cityip.co.za [196.25.223.140])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA07569
          for <questions@freebsd.org>; Fri, 15 May 1998 07:55:26 -0700 (PDT)
          (envelope-from wjv@cityip.co.za)
Received: from wjv by ns.cityip.co.za with local (Exim 1.82 #2)
	id 0yaLtF-0007H0-00; Fri, 15 May 1998 16:55:17 +0200
Subject: DEC 21140 NIC not auto-resetting
To: questions@FreeBSD.ORG
Date: Fri, 15 May 1998 16:55:17 +0200 (SAT)
X-PGP: ftp://ftp.cityip.co.za/users/wjv/pubkey.asc
X-URL: http://www.cityip.co.za/~wjv/
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E0yaLtF-0007H0-00@ns.cityip.co.za>
From: Johann Visagie <wjv@cityip.co.za>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I am currently testing the new Netgear FA310TX NIC (DEC 21140-AF chipset)
under 2.2.6-R.  I've got it connected to a Netgear fast ethernet switch.  The
switch is set to auto-sense the duplexing mode (though setting it to
full-duplex does not seem to change the problem I'm about to describe).

Using this configuration, the driver seems to initialise the card correctly.
The media is reported as "autoselect (100baseTX <full-duplex>)" by ifconfig.
If I force a line break (by pulling out a connector), the driver reports:

/kernel: de0: link down: cable problem?
/kernel: de0: autosense failed: cable problem?

ifconfig now reports the media type merely as "autoselect".

If I plug the cable back in, ifconfig once again reports the media type as
"autoselect (100baseTX <full-duplex>)" and the status as "active", BUT the
NIC is not functioning.  Only when I force an interface reset with "ifconfig
de0 down" does the driver report:

/kernel: de0: enabling Full Duplex 100baseTX port

If I then bring it back up with "ifconfig de0 up", everything works again.

So I tried things differently:  I forced the media detection with "ifconfig
de0 medial 100baseTX mediaopt full-duplex".  ifconfig now reports the media
correctly as "100baseTX <full-duplex> status: active".  I force a line break
and get the same error messages, but ifconfig now reports the interface
status as "no carrier".  If I plug the line back in, the status _stays_ at
"no carrier".  The only thing that seems to revive it then is setting the
media back to "autoselect", and _then_ bouncing the interface down and back
up.

Is this behaviour standard?

-- V

Johann Visagie | Email: wjv@CityIP.co.za | Tel: +27 21 419-7878

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message