From owner-freebsd-current Wed Nov 27 23:46:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA11153 for current-outgoing; Wed, 27 Nov 1996 23:46:41 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA11148 for ; Wed, 27 Nov 1996 23:46:39 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id AAA13604; Thu, 28 Nov 1996 00:46:33 -0700 (MST) Date: Thu, 28 Nov 1996 00:46:33 -0700 (MST) Message-Id: <199611280746.AAA13604@rocky.mt.sri.com> From: Nate Williams To: Peter Mutsaers Cc: freebsd-current@freebsd.org Subject: Re: Will userconfig work soon again? In-Reply-To: <87682qpuff.fsf@plm.xs4all.nl> References: <87682qpuff.fsf@plm.xs4all.nl> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I want to try to get my PCI NE2000 clone to work properly, but by > default it is not probed well (it does work in other OSses). Thus I > rely on userconfig to get it to work. It doesn't work at the moment > however. Should I try an older version of the kernel (which one) or > will userconfig work again shortly? UserConfig works now, but on *some hardware* (my boxes don't show the problem with the -current code) once you use it then you can't use the keyboard anymore. I've got a box that's connected to the ethernet, so I used UserConfig to get the ethernet configured correctly, then remotely logged in and rebooted it. Once I rebooted normally (w/out using UserConfig) the keyboard worked fine. Yeah, I know it's a kludge, but it worked. :) Nate