From owner-freebsd-hackers Sun Jan 7 7:53:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DF65B37B6B2 for ; Sun, 7 Jan 2001 07:52:58 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f07Fqf728078; Sun, 7 Jan 2001 10:52:42 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 7 Jan 2001 10:52:41 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kazutaka YOKOTA Cc: hackers@freebsd.org, John Polstra Subject: Re: KVM switch vs. FreeBSD psm driver (Solved!) In-Reply-To: <200101071136.UAA24356@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Jan 2001, Kazutaka YOKOTA wrote: > I guess your KVM switch won't let the kernel talk to the keyboard, if > the switch wasn't pointed to the FreeBSD box. > > Remove the flags 0x1 from atkbd in your kernel config file. This flag > makes atkbd fail, if it doesn't detect a keyboard. Without the flag, > atkbd will install regardless of the absence of the keyboard. > > In RELENG_2 and RELENG_3, this flag wasn't specified to atkbd by > default. In RELENG_4, the flag was added to GENERIC so that syscons will > use a USB keyboard, if any, when there is no AT keyboard. So, question: is there a reason why we can't enable both the USB keyboard and a native PS/2 keyboard with syscons? It seems that I frequently find myself in a position where I'd like to plug in a keyboard, or switch KVM choices to a machine, and discover myself with no access to the hardware console, and I know at least one person who uses FreeBSD in production and finds this to be a serious impediment (as it requires the system to be rebooted to regain console access, and when you have 8 machines per KVM, and you boot them all, switching back and forth to catch each probe is effectively impossible). Presumably our syscons is intended to select on source of I/O and use it, but it might be worth considering a change here. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message