public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Dee <antitux@antitux.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 keyboard not working
Date: Thu, 18 Dec 2003 00:55:51 -0700	[thread overview]
Message-ID: <3FE15D87.6070401@antitux.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0312180230150.1710@montezuma.fsmlabs.com>

hrm. I was having the same problems with both my usb keyboard and mouse. 
i figure I just missed something.
haven't gotten around to looking too much into it though.
maybe in the morning.

Zwane Mwaikambo wrote:
> On Thu, 18 Dec 2003, Lennert Buytenhek wrote:
> 
> 
>>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?
> 
> 
> May we have a look at your .config?
> 
> ta,
> 	Zwane
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2003-12-18  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18  6:00 2.6.0 keyboard not working Lennert Buytenhek
2003-12-18  7:31 ` Zwane Mwaikambo
2003-12-18  7:55   ` John Dee [this message]
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=3FE15D87.6070401@antitux.net \
    --to=antitux@antitux.net \
    --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