linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roey Katz <roey@sdf.lonestar.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
Date: Thu, 13 Jan 2005 03:19:21 +0000 (UTC)	[thread overview]
Message-ID: <Pine.NEB.4.61.0501130315500.11711@sdf.lonestar.org> (raw)
In-Reply-To: <200501110239.33260.dtor_core@ameritech.net>

Dmitry,

I have placed the results of the patched 2.6.9-rc2-bk2 kernel at the 
following address:

   http://roey.freeshell.org/mystuff/kernel/*-20050112

As expected, the system was unresponsive to keyboard input.
Regarding your mouse question:
How do I test the mouse if they keyboard does not work (is there some 
way to output the contents of /dev/psaux on startup? I'm not sure anymore 
what file the mouse data appears in, too)

- Roey


On Tue, 11 Jan 2005, Dmitry Torokhov wrote:

> Date: Tue, 11 Jan 2005 02:39:33 -0500
> From: Dmitry Torokhov <dtor_core@ameritech.net>
> To: linux-kernel@vger.kernel.org
> Cc: Roey Katz <roey@sdf.lonestar.org>
> Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
> 
> On Sunday 09 January 2005 08:09 pm, Roey Katz wrote:
>> OK, I moved that input/serio line to be just above the line mentioning
>> "input".  Rebooted;  still got this error.  See all the -2.6.9-rc2-bk3
>> logs on my web site (http://roey.freeshell.org/mystuff/kernel/) for
>> details. I will follow up with psmouse disabled if you want.
>>
>
> I just don't see anything wrong with it... oh well...
>
> Ok, I have cut out everything but input changes from -rc2-bk3, could you
> pleasde try appying the patch below to -rc2. If it does not work it will
> prove that the input code is to blame and we'll start reverting changes
> one by one to find out the one that broke the keyboard.
>
> Make you are booting with log_buf_len=131072 as some of your logs are
> short. And be sure hit keyboard couple of times after the mox finished
> booting (single user mode preferably).
>
> Btw, does your mouse work?
>
>>
>> Roey
>> PS: just changing a Makefile makes a difference?
>>
> This particular chane make keyboard controller initialization code run later
> in the startup sequence, but apparently it had no visible effect.
>
> -- 
> Dmitry
>
>

  reply	other threads:[~2005-01-13  3:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-01  8:27 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup Roey Katz
2005-01-01 21:31 ` Dmitry Torokhov
2005-01-02  6:28   ` Roey Katz
2005-01-02  6:52     ` Dmitry Torokhov
2005-01-02  6:59       ` Roey Katz
2005-01-03  2:53       ` Roey Katz
2005-01-03  3:06         ` Dmitry Torokhov
2005-01-03  5:37           ` Roey Katz
2005-01-03  6:23             ` Dmitry Torokhov
2005-01-03 13:21               ` Roey Katz
2005-01-03 16:35                 ` Dmitry Torokhov
2005-01-03 16:54                   ` Roey Katz
2005-01-04  5:49                   ` Roey Katz
2005-01-04  6:17                     ` Dmitry Torokhov
2005-01-04  6:26                       ` Roey Katz
2005-01-06  4:16                       ` Dmitry Torokhov
2005-01-06  4:29                         ` Roey Katz
2005-01-07  4:06                         ` Roey Katz
2005-01-07  5:45                           ` Dmitry Torokhov
2005-01-07 13:37                             ` Roey Katz
2005-01-07 15:20                               ` Dmitry Torokhov
2005-01-09  5:14                                 ` Roey Katz
2005-01-09  5:35                                   ` Dmitry Torokhov
2005-01-09 14:24                                     ` Roey Katz
2005-01-09 16:02                                       ` Dmitry Torokhov
2005-01-10  1:09                                         ` Roey Katz
2005-01-11  7:39                                           ` Dmitry Torokhov
2005-01-13  3:19                                             ` Roey Katz [this message]
2005-01-13  3:42                                               ` Dmitry Torokhov
2005-01-14 23:06                                                 ` Matthew Harrell
2005-01-15  0:29                                                   ` Matthew Harrell
2005-01-15  1:31                                                   ` Dmitry Torokhov
2005-01-15  2:28                                                     ` Matthew Harrell
2005-01-15  2:58                                                     ` Matthew Harrell
2005-01-15  3:57                                                       ` Dmitry Torokhov
2005-01-17 19:56                                                     ` Vojtech Pavlik
2005-01-17 19:58                                                       ` Matthew Harrell
2005-01-17 20:03                                                         ` Vojtech Pavlik
2005-01-15  7:23                                                 ` Roey Katz
2005-02-12 17:50                                                 ` Roey Katz
2005-02-13  6:45                                                   ` Dmitry Torokhov
2005-03-03 13:26                                                     ` Roey Katz
2005-01-03  3:03       ` Roey Katz
2005-01-15 11:05 Marco Cipullo
2005-01-15 17:42 ` Dmitry Torokhov
2005-01-15 18:02   ` marco

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=Pine.NEB.4.61.0501130315500.11711@sdf.lonestar.org \
    --to=roey@sdf.lonestar.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;
as well as URLs for NNTP newsgroup(s).