From owner-freebsd-questions  Mon Jul  3 12:36:25 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from ptavv.es.net (ptavv.es.net [198.128.4.29])
	by hub.freebsd.org (Postfix) with ESMTP id BB37537BDB6
	for <freebsd-questions@FreeBSD.ORG>; Mon,  3 Jul 2000 12:36:18 -0700 (PDT)
	(envelope-from oberman@ptavv.es.net)
Received: from ptavv.es.net (localhost [127.0.0.1])
	by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e63JaEn10033;
	Mon, 3 Jul 2000 12:36:14 -0700 (PDT)
Message-Id: <200007031936.e63JaEn10033@ptavv.es.net>
To: "Jonathan Belson" <jon@dookie.demon.co.uk>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: [Q] FreeBSD 4.0 and Xircom ethernet cards? 
In-reply-to: Your message of "Sun, 02 Jul 2000 00:07:37 BST."
             <000501bfe3b1$26522f20$03fea8c0@local> 
Date: Mon, 03 Jul 2000 12:36:14 -0700
From: "Kevin Oberman" <oberman@es.net>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> From: "Jonathan Belson" <jon@dookie.demon.co.uk>
> Date: Sun, 2 Jul 2000 00:07:37 +0100
> Sender: owner-freebsd-questions@FreeBSD.ORG
> 
> Hiya
> 
> 
> Has anyone managed to get Scott Mitchell's Xircom driver to work under
> 4.0-RELEASE?
> I tried the latest archive from his website (1.20 dated last year some time)
> but it wouldn't
> compile - it worked nicely under 3.4 though.

The problem is not just the driver, but the underlying structures
for PCCARD and driver support which changed with V4.0. The Xircom
(Dingo) driver does not and will not work in 4.0-Release. It has
worked in 4.0-Stable for about a month or two due to modifications to
both the driver and to other system components.

If you can't cvsup to STABLE, you will probably have to wait two weeks
until 4.1-Release is available and install that. (Jordan had posted
that July 15 is the target date for 4.1 and I am seeing MFCs starting
to hit as code is moved from CURRENT prior to STABLE rot release, so
it should be close to on time.)

FWIW, my Xircom has run just fine since the modifications to STABLE,
but it puts out TONS of debug messages that drove me nuts, so I edited
if_xe.c to $undef XE_DEBUG after the line where it is defined as
#define XE_DEBUG 2 
in /sys/dev/xe/if_xe.c.

That quiets it down to where I'd like it to be, but you might want to
wait to do this until you know it's running correctly.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634


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