From owner-freebsd-stable Tue Sep 5 11:23:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 0AEF537B43F for ; Tue, 5 Sep 2000 11:23:20 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e85IN5L48142; Tue, 5 Sep 2000 11:23:13 -0700 (PDT) Date: Tue, 5 Sep 2000 11:23:05 -0700 (PDT) From: Doug White To: simond@irrelevant.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with installing 4.1-RELEASE In-Reply-To: <20000902204907.A5182@irrelevant.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Sep 2000 simond@irrelevant.org wrote: > Hiya, is there any reason why "flags 0x1" got added to the atkbd0 line > somewhere between 4.0 and 4.1? I'm asking as when I was trying to install > 4.1-RELEASE it wasn't recognising the keyboard, installing with 4.0-RELEASE > worked, after which I tried cvsuping to 4.1-STABLE which still didn't work. I believe this is to facilitate USB keyboards. From the atkbd man page: bit 0 (FAIL_IF_NO_KBD) By default the atkbd driver will install even if a keyboard is not actually connected to the system. This option prevents the driver from being installed in this situation. If the atkbd driver loads it will become the default keyboard even if a USB keyboard is present. If your keyboard controller is busted then you can try removing the flag. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message