From owner-freebsd-questions  Sat Mar  3  4:31: 2 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from herakles.uci.kun.nl (herakles.uci.kun.nl [131.174.93.48])
	by hub.freebsd.org (Postfix) with ESMTP id 2A5FE37B721
	for <freebsd-questions@FreeBSD.ORG>; Sat,  3 Mar 2001 04:30:59 -0800 (PST)
	(envelope-from matijs@blender.org)
Received: from roswell (catv6124.extern.kun.nl [131.174.116.124])
 by mailserver.uci.kun.nl (PMDF V5.2-31 #42470)
 with SMTP id <0G9M00BQRG3HAM@mailserver.uci.kun.nl> for
 freebsd-questions@FreeBSD.ORG; Sat,  3 Mar 2001 13:30:54 +0100 (MET)
Date: Sat, 03 Mar 2001 13:30:52 +0100
From: Matijs <matijs@blender.org>
Subject: DEC Etherworks 2 problem
To: freebsd-questions@FreeBSD.ORG
Message-id: <BEEBLFKILIEFFGDOBMBEMELECAAA.matijs@blender.org>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi there,

I am trying to install FreeBSD 4.2 on a Compaq Pressario machine (486SX,
20MB memory, 250MB HD with a DE201 DEC Etherworks 2 NIC). The FreeBSD 4.2
supported hardware list says it's supported. However the driver doesn't show
up in the screen where you can resolve hardware conflict just before the
hardware probe.

I decided to try a FreeBSD 4.1.1 install. This time the driver (le0) was
present in the 'resolve hardware conflicts screen'. This time however, the
probe didn't find the NIC. After testing the NIC with DEC diaturbo software
and testing IRQ, I/O-address and memory settings it turned out the card was
not broken. (It had been working in a similar system under Windows 3.11 just
the day before)

My questions to you are:

- Is the DE201 DEC Etherworks 2 NIC no longer supported in FreeBSD 4.2?
- What could be the cause for the NIC not functioning under FreeBSD 4.1.1?
- Is there a workaround to manually add the driver to the kernel?

PS. a network install is the only option since the system doesn't have a
CDROM, nor is there room for one (Only one IDE controller).
PSS. I have been experimenting with the various settings, nothing helped.

Thanks in advance,

Matijs


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