LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Piotr Gluszenia Slawinski <curious@zjeby.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: thinkpad 360Cs keyboard problem
Date: Tue, 12 Sep 2006 21:43:15 -0400	[thread overview]
Message-ID: <200609122143.15814.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0609121950381.2685@Jerry.zjeby.dyndns.org>

On Tuesday 12 September 2006 17:21, Piotr Gluszenia Slawinski wrote:
> On Tue, 12 Sep 2006, Dmitry Torokhov wrote:
> 
> > On 9/12/06, Piotr Gluszenia Slawinski <curious@zjeby.dyndns.org> wrote:
> >>  On Tue, 12 Sep 2006, Dmitry Torokhov wrote:
> >> 
> >> >  On 9/11/06, Piotr Gluszenia Slawinski <curious@zjeby.dyndns.org> wrote:
> >> 
> >> > >   kernel boots up fine, but keyboard is totally messed up,
> >> > >   and locks up after some tries of use.
> >> > 
> >> >  Could you try describing the exact issues with the keyboard? Missing
> >> >  keypresses, wrong keys reported, etc?
> >>
> >>  with prink enabled it prints series of 'unknown scancode'
> >>  and keys are randomly messed up, and it changes, so like pressing b
> >>  results with n, then space, then nothing at all.
> >>  after some tries keyboard locks up completely.
> >> 
> >
> > Are you loading a custom keymap by any chance? Could I please see
> > dmesg with "i8042.debug log_buf_len=131072"?
> 
> no custom keymaps . init=/bin/bash :d
> uhm, i don't get what you mean by this dmesg syntax :o

These were kernel boot options. If you let the system boot normally
so that syslog is running I'd expect debug messages end somewhere
(like in /var/log/messages) so you could reboot and send me that file.

> i should probably attach serial conole and send you whole output,
> as now (as keyboard is unuseable) i can't scroll screen.
> 
> btw. serio: i8042 KBD port at 0x60,0x64 irq 1
> is found.
> also
> input: AT Raw Set 2 keyboard as /class/input/input1
> is reported
> 

It could be that it lies about being in raw mode and actually is in
translated mode.

-- 
Dmitry

  reply	other threads:[~2006-09-13  1:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10  0:13 swsusp problem curious
2006-09-10  9:33 ` Rafael J. Wysocki
2006-09-10 19:24   ` curious
2006-09-10 19:27     ` Pavel Machek
2006-09-10 19:39       ` Piotr Gluszenia Slawinski
2006-09-10 19:49         ` Pavel Machek
2006-09-10 19:59           ` Piotr Gluszenia Slawinski
2006-09-11  0:54           ` Dmitry Torokhov
2006-09-11  8:04             ` Pavel Machek
2006-09-12  0:12             ` thinkpad 360Cs keyboard problem Piotr Gluszenia Slawinski
2006-09-12 14:05               ` Dmitry Torokhov
2006-09-12 14:24                 ` Piotr Gluszenia Slawinski
2006-09-12 17:12                   ` Dmitry Torokhov
2006-09-12 21:21                     ` Piotr Gluszenia Slawinski
2006-09-13  1:43                       ` Dmitry Torokhov [this message]
2006-09-10  9:40 ` swsusp problem Pavel Machek
2006-09-10 19:36   ` Piotr Gluszenia Slawinski

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=200609122143.15814.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=curious@zjeby.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: thinkpad 360Cs keyboard problem' \
    /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

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).