From owner-freebsd-stable Sat Feb 10 21:17:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 823CB37B401 for ; Sat, 10 Feb 2001 21:17:19 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:kXgT2bHH5CiqEn7jhV4AiLceBqo1A5KF@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.11.0/3.7Wpl2) with ESMTP id f1B5HFM09886; Sun, 11 Feb 2001 14:17:15 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:llZCEv6SmL5SkTEyrAlOfED54NnR9Rm7@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id OAA06084; Sun, 11 Feb 2001 14:25:08 +0900 (JST) Message-Id: <200102110525.OAA06084@zodiac.mech.utsunomiya-u.ac.jp> To: Matt Dillon Cc: Warner Losh , Jesper Skriver , Robert , freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: uh oh - after 4 -> 4.2 cvsup, no keyboard. any ideas? In-reply-to: Your message of "Sat, 10 Feb 2001 20:46:54 PST." <200102110446.f1B4ksR29654@earth.backplane.com> References: <20010204112503.E71706@skriver.dk> <200102110424.f1B4OVW18984@harmony.village.org> <200102110446.f1B4ksR29654@earth.backplane.com> Date: Sun, 11 Feb 2001 14:25:07 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's probably the stupid USB keyboard mod, which disables the standard > keyboard when no keyboard is attached during boot, unless you specify > flags 0x1 for the keyboard controller, even if no USB keyboard is found. No, this is not true. Syscons uses whatever keyboard that is available at boot. If both the AT keyboard and the USB keyboard are attached and detected, the one which are detected first will be used; and that is the AT keyboard. Without the flags 0x1, the AT keyboard driver will ALWAYS install, even if an AT keyboard is not attached. This has been the default behavior since FreeBSD 1.X, because there are systems (mostly servers) to which people want to attach the keyboard only when necessary. (I still don't recommend hot plugging the AT keyboard. But, many people want it...) This behavior creats problems for those who wants to use the USB keyboard which is fully capable of hot plugging/unplugging, because syscons will always use the AT keyboard driver even when the AT keyboard is not present. The flags 0x1 will instruct the AT keyboard driver to fail when an AT keyboard is not available. This way, together with the flags 0x100 for syscons, syscons will detect and use the USB keyboard when it's plugged. If no keyboard is attached to the system at boot time, syscons will have no input device. And this is creating another problem for those who wants to hot-plug the AT keyboard... Because the keyboard is not attached at boot time, the AT keyboard driver Those people should REMOVE the flags 0x1 from the AT keyboard driver. This flag have been in existance for a long time, but it only made default since 4.1-RELEASE (see GENERIC rev 1.245.2.5). > I don't mind having USB keyboard detection in there, but it should not go > and disable the main keyboard if the main keyboard doesn't happen to be > plugged in. No, as I wrote the above, the USB keyboard driver does not disable the AT keyboard driver. Kazu > This is like the fifth person who has gotten smacked by that. It's > *really* annoying to have all of one's rack mount machines suddenly > stop accepting a keyboard being plugged in after an upgrade. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message