From owner-freebsd-isp@FreeBSD.ORG Tue Jun 15 00:29:14 2004 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F77E16A4CE for ; Tue, 15 Jun 2004 00:29:14 +0000 (GMT) Received: from wjv.com (user38.net339.fl.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id E370F43D54 for ; Tue, 15 Jun 2004 00:29:13 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.12.11) with ESMTP id i5F0SfLB006546; Mon, 14 Jun 2004 20:28:42 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.12.11/Submit) id i5F0SfBZ006545; Mon, 14 Jun 2004 20:28:41 -0400 (EDT) (envelope-from bv) Date: Mon, 14 Jun 2004 20:28:41 -0400 From: Bill Vermillion To: John Brooks Message-ID: <20040615002841.GA6509@wjv.com> References: <049320BD-BA63-11D8-B2DF-000A95CCF8C4@san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on bilver.wjv.com cc: freebsd-isp@freebsd.org Subject: Re: Console dead X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bv@wjv.com List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 00:29:14 -0000 Knocking over a stack of dishes on the heat sink John Brooks wondered out loud about: > I did a cvsup update, then a buildworld from 4.9 to 4.10 > on a remote box. Now the console keyboard is unresponsive > after completing the boot sequences. Early in the boot > sequence the keyboard functions normally. The box can be > accessed via ssh. Anybody come across this behavior before? I've seen this in the far past - back in the 2.x or early 3.x days. I don't remember the exact flag I used but it was one of the options you will find in LINT under the area labeled # options of atkbd. The BIOS on one of the machine I had then did not detect a keyboard and thus set the keyboard to the serial port, but I haven't used this option for about 5 years. Bill -- Bill Vermillion - bv @ wjv . com