From owner-freebsd-questions Mon Oct 30 8:22: 4 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 706AB37B479 for ; Mon, 30 Oct 2000 08:22:01 -0800 (PST) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id QAA34586; Mon, 30 Oct 2000 16:21:45 GMT (envelope-from simond) Date: Mon, 30 Oct 2000 16:21:45 +0000 From: simond@irrelevant.org To: Jud Cc: freebsd-questions@freebsd.org Subject: Re: Newbie - Atkbd0 Not Recognized After Cvsup to 4.1-STABLE (was Problems with installing 4.1-RELEASE) Message-ID: <20001030162145.A33728@irrelevant.org> References: <3A000C8F@operamail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A000C8F@operamail.com>; from Jud@operamail.com on Mon, Oct 30, 2000 at 11:13:09AM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 30, 2000 at 11:13:09AM -0500, Jud wrote: > I've just had precisely the same experience Simon Dick describes below (in his > September 2 message to freebsd-stable) after I upgraded with cvsup from > 4.1-RELEASE to 4.1-STABLE. Interesting bit is that after I unloaded kernel > and successfully booted kernel.GENERIC, I tried compiling and installing the > GENERIC kernel as MYKERNEL, but got exactly the same result - normal boot gave > the "attach returned 6" message and hung a few lines later, while booting > kernel.GENERIC worked. > > I'm a newbie, having just installed FreeBSD as my first Unix about 5 weeks > ago. I'd very much appreciate help with the answers to 2 questions (and of > course suggestions as to additional information I can provide): > > 1. What's the meaning of/reason for "flags 0x1?" It sort of tells you in atkbd(4): bit 0 (FAIL_IF_NO_KBD) By default the 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. > 2. What should I do to avoid this particular problem in the future? Does the visual config editor allow the changing of this bit? I've not actually tried that (it only just occured to me). Someone mentioned that the problem may be caused by some BIOS setting related to USB keyboards, I still don't think it's good to enable this flag, it just makes it far harder for some people to install it :( -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message