From owner-freebsd-hackers Sat Nov 25 11:03:56 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA13911 for hackers-outgoing; Sat, 25 Nov 1995 11:03:56 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA13905 ; Sat, 25 Nov 1995 11:03:52 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA30226; Sun, 26 Nov 1995 06:01:55 +1100 Date: Sun, 26 Nov 1995 06:01:55 +1100 From: Bruce Evans Message-Id: <199511251901.GAA30226@godzilla.zeta.org.au> To: bde@zeta.org.au, stesin@elvisti.kiev.ua Subject: Re: Probing KBD. Cc: hackers@freebsd.org, sos@freebsd.org Sender: owner-hackers@freebsd.org Precedence: bulk >: The probe is supposed to time out after 5 seconds, but it has well-known >: bugs that somehow haven't been fixed in either 2.1 or -current. After >: timing out after 5 seconds, it executes an endless loop. >: The keyboard is only initialized at probe time, so it may not work if >: it is plugged in later. > I have a proposal of a simple change to a console driver, > inspired with what I have seen on BSDI: > if it can't probe the keyboard, it then happily shouts > something like -- "Hey, there isn't a keyboard here! I'm now > acting as a black-box router!" -- to the console, > and goes on booting. syscons is supposed to print "scprobe: keyboard won't accept reset command" and continue, but because of the bug it rarely prints this (never if there is a keyboard attached). The keyboard should be initialized after every console switch in case X owned the keyboard and messed up something, e.g., the keyboard repeat rate. Bruce