From owner-freebsd-current Mon Aug 31 15:08:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12679 for freebsd-current-outgoing; Mon, 31 Aug 1998 15:08:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12672; Mon, 31 Aug 1998 15:08:14 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id PAA18113; Mon, 31 Aug 1998 15:07:04 -0700 (MST) From: "Chad R. Larson" Message-Id: <199808312207.PAA18113@freebie.dcfinc.com> Subject: Re: Looking for feedback on xl (3c905/3c905B) driver To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Mon, 31 Aug 1998 15:07:03 -0700 (MST) Cc: chad@dcfinc.com, stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199808291923.PAA01095@skynet.ctr.columbia.edu> from Bill Paul at "Aug 29, 98 03:23:48 pm" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay people, it's been some time since I put the xl0 driver in > -current and -stable. I need to know if people are having problems > with the driver or not. So far I've gotten startlingly little > feedback. This either means that it's working so well that nobody has > had any trouble with it, or you guys are all just slackers and are too > lazy to speak up. Well, this was interesting. Bill talked me into trying to build his driver into my kernel. But first (taking baby steps) I cvsup'd -stable again, and rebuilt the world. Then I build a new kernel. Just to make sure that if anything broke, I wouldn't be blaming Bill. Glorioski! No network! The new kernel, supped as of Aug 25, no longer saw my vx0 device. In fact, it didn't even probe for it. The date on ../sys/pci/if_vx_pci.c is Aug 24th. Coincidence? So my choice was to try to fall back to a prior kernel and figure out what got broken, or to march onward. I chose the latter. I edited my kernel config file to change "device vx0" to "device xl0", edited /etc/rc.conf to change "vx" references to "xl". Then rebuilt the kernel and rebooted. As you can tell, I'm back on the net. But has anyone chased down what happened to the vx driver? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message