From owner-freebsd-current Fri Sep 17 6:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (Postfix) with ESMTP id 5B77714A08; Fri, 17 Sep 1999 06:22:35 -0700 (PDT) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id PAA21262; Fri, 17 Sep 1999 15:23:19 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199909171323.PAA21262@oskar.nanoteq.co.za> Subject: Re: Weird syscons keyboard behaviour In-Reply-To: <199909171245.OAA77092@freebsd.dk> from Soren Schmidt at "Sep 17, 99 02:45:08 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Fri, 17 Sep 1999 15:23:15 +0200 (SAT) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, mpp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Kazutaka YOKOTA wrote: > > > > It appears that if you hit the keyboard before (at the boot loader > > prompt or during the kernel is probing devices) or while the keyboard > > driver is being initialized, you may see the problem. > > Hmm I've seen the problem where on "loose" the input at the loader prompt > but it has always come back when syscons probes the keyboard. > > But I have also seen the other problem exactly two times, and the > keyboard hasn't been touched at all those two times... > I had written it of as a fluke in my screen/keyboard/mouse switchbox... > I've sometimes experienced the problem where my keyboard goes crazy .. e.g. when typing 'r' it types two "up-arrowa" on the screen. It's only weird characters ... I then have to press the reset button, because ctrl-alt-del doesn't work and plugging the keyboard out and in doesn't help. I've also thought it's something of the Itel 440-BX motherboard .. Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message