From owner-freebsd-questions@FreeBSD.ORG Tue Apr 4 16:59:38 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF07C16A420 for ; Tue, 4 Apr 2006 16:59:38 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 318D543D62 for ; Tue, 4 Apr 2006 16:59:32 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.pgh.priv.collaborativefusion.com (vanquish.pgh.priv.collaborativefusion.com [192.168.2.61]) by wingspan with esmtp; Tue, 04 Apr 2006 12:59:31 -0400 id 00056416.4432A5F3.000112CF Date: Tue, 4 Apr 2006 12:59:31 -0400 From: Bill Moran To: "mike s. cojocea" Message-Id: <20060404125931.9888b305.wmoran@collaborativefusion.com> In-Reply-To: References: Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.0 (GTK+ 2.8.12; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Keyboard Issue on Dell 1850/FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2006 16:59:38 -0000 On Tue, 04 Apr 2006 16:54:21 +0000 "mike s. cojocea" wrote: > > I am working to install a FreeBSD 6.0 on a Dell 1850, with Dell Remote > Access Card. > > After the install is complete the keyboard no longer works. > > I can access the machine over SSH to do debugging. The /var/log/messages did > not show any error: > > %Apr 4 09:10:14 APPS01 kernel: atkbd0: Keyboard> irq 1 on atkbdc0 > Apr 4 09:10:14 APPS01 kernel: kbd0 at atkbd0 > > I tried it with FreeBSD 5.4 and it does the same thing. A Fedora Core 4 and > an RHEL 3 Linux did not have similar keyboard problem. > > Any help to figure this out is going to be greatly appreciated. We've been there and done that. In our case, building a custom kernel solved the problem - being sure to have the required USB devices in the kernel (note that DRAC keyboards are USB keyboards). You may be able to accomplish the same thing with some sort of modules or loader magic, but we wanted custom kernels anyway, so it wasn't a hassle. -- Bill Moran Collaborative Fusion Inc.