public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@gnu.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 keyboard not working
Date: Thu, 18 Dec 2003 01:00:53 -0500	[thread overview]
Message-ID: <20031218060053.GA645@gnu.org> (raw)

Hi,

Halfway between having uncompressed the kernel and starting init, the console
starts to scroll "atkbd.c: Unknown key pressed", mentioning key code 0 (IIRC),
even though no keys are pressed at all.  After a while, the scrolling stops,
but the keyboard still doesn't work.  2.4 works fine on the same hardware.

Hardware is an Intel SE7505VB2 board with dual 2.40GHz Xeon processors,
and a Logitech PS/2 "Internet keyboard."

Ideas?


thanks,
Lennert

             reply	other threads:[~2003-12-18  6:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18  6:00 Lennert Buytenhek [this message]
2003-12-18  7:31 ` 2.6.0 keyboard not working Zwane Mwaikambo
2003-12-18  7:55   ` John Dee
2003-12-18 14:54   ` Lennert Buytenhek
2003-12-18 15:04     ` Lennert Buytenhek
2003-12-18 16:30       ` Zwane Mwaikambo
2003-12-18 17:32         ` Sebastian Benoit
2003-12-18 18:21         ` Lennert Buytenhek
2003-12-18 18:36           ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031218060053.GA645@gnu.org \
    --to=buytenh@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox