From owner-freebsd-hackers  Wed Sep  6 17:38: 3 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from etinc.com (et-gw.etinc.com [207.252.1.2])
	by hub.freebsd.org (Postfix) with ESMTP id CBDD437B422
	for <hackers@freebsd.org>; Wed,  6 Sep 2000 17:38:01 -0700 (PDT)
Received: from dbsys (dbsys.etinc.com [207.252.1.18])
	by etinc.com (8.9.3/8.9.3) with SMTP id UAA28088
	for <hackers@freebsd.org>; Wed, 6 Sep 2000 20:38:39 -0400 (EDT)
Message-Id: <200009070038.UAA28088@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Wed, 06 Sep 2000 20:38:08 -0400
To: hackers@freebsd.org
From: Dennis <dennis@etinc.com>
Subject: dc driver issues
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

With freebsd 4.1, I have 2 "problems" with the dc driver. Im using a 4 port
DLINK card in this test:

1) It always give me a "device timeout" on first startup. It seems to work
ok though. The de driver (oppositely) gives me an "enabled" on the
connected ports on startup.

2). It numbers the ports in the opposite order expected. Bottom to top. Is
there a simple patch to correct this...or is this a system or MB issue? the
MB is an Intel ATX, pretty standard stuff.

any ideas?

Dennis


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