From owner-freebsd-hackers  Thu Sep 12 10:49:34 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA18814
          for hackers-outgoing; Thu, 12 Sep 1996 10:49:34 -0700 (PDT)
Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18809;
          Thu, 12 Sep 1996 10:49:32 -0700 (PDT)
Received: from impulse.csl.sri.com (impulse.csl.sri.com [130.107.15.11]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id KAA26715; Thu, 12 Sep 1996 10:49:01 -0700 (PDT)
Received: from impulse.csl.sri.com (localhost [127.0.0.1]) by impulse.csl.sri.com (8.7.3/8.7.3) with ESMTP id KAA02137; Thu, 12 Sep 1996 10:46:38 -0700 (PDT)
Message-Id: <199609121746.KAA02137@impulse.csl.sri.com>
To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org
Subject: 2.2-960801-SNAP--Problem with SMC 10/100 card and SMC 100mb `tiger hub'
Date: Thu, 12 Sep 1996 10:46:38 -0700
From: Fred Gilham <gilham@csl.sri.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I've noticed that running the 2.2-960801 snap causes the de driver to
fail to link up to the 100mb SMC tiger hub that we're experimenting
with.  It always reports

de0: enabling 10baseT port

and then gives timeout errors.

However, the de driver in 2.1.5R works with this setup (I was
able to establish communication with an ultrasparc at 100mb just
fine).

I actually ran both versions on the same system to eliminate the
possibility of hardware differences causing the problem.

If whoever looks at this wants any more information please contact me.

-Fred Gilham    gilham@csl.sri.com