public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wiktor <victorjan@poczta.onet.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AT keyboard dead on 2.6
Date: Fri, 21 Jan 2005 14:38:56 -0500	[thread overview]
Message-ID: <d120d500050121113867c82596@mail.gmail.com> (raw)
In-Reply-To: <41F15307.4030009@poczta.onet.pl>

On Fri, 21 Jan 2005 20:07:51 +0100, Wiktor <victorjan@poczta.onet.pl> wrote:
> Dmitry Torokhov wrote:
> > Hi,
> >
> > What kernel version are you using? Have you tried 2.6.8.1? - it looks
> > like changes in 2.6.9-rc2-bk3 caused problems on some hardware.
> >
> 
> Hi,
> 
> it looks like 2.6.10 (which I was using) - serio ports are detected ok
> (both on 0x60,0x64, keyboard irq 1, aux irq 12), keyboard also (AT
> Keyboard Translated Set 2 on isa0060/serio) and nothing - while
> detection NumLock (set by BIOS) is turned off and keyboard is dead.
> Maybe someone would be so kind and compare keyboard driver
> hadrware-level parts and (possibly) post patch reversing any changes
> since 2.4?

Ahem, that would be the one wiping out entire input system...

> Any other ideas?

1. Try compiling psmouse as a module and not load it until keyboard
driver (atkbd) is loaded.

2. Try kernel 2.6.8.1 - it looks like changes in 2.6.9-rc2-bk3 are
causing trouble on some systems but I can't figure out the reason.

Also, if you change undef DEBUG to #define DEBUG in
drivers/input/serio/i8042.c, reboot with log_buf_size=131072 and send
me the full dmesg or kernel log I'd appreciate it.

Thanks!

-- 
Dmitry

  reply	other threads:[~2005-01-21 19:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 15:27 AT keyboard dead on 2.6 Wiktor
2005-01-21 15:48 ` Dmitry Torokhov
2005-01-21 19:07   ` Wiktor
2005-01-21 19:38     ` Dmitry Torokhov [this message]
2005-01-25 19:37       ` Wiktor
2005-01-28 14:31         ` Vojtech Pavlik
2005-01-28 14:46           ` Dmitry Torokhov
2005-01-28 18:41             ` Vojtech Pavlik
2005-01-28 19:22             ` Wiktor
2005-01-28 19:27               ` Dmitry Torokhov
2005-01-28 19:35                 ` Vojtech Pavlik
2005-01-29 20:32                   ` Wiktor
2005-01-28 19:49                 ` Wiktor
2005-01-28 19:53                   ` Dmitry Torokhov
2005-01-28 20:22                     ` Wiktor
2005-01-28 20:25                       ` Vojtech Pavlik
2005-01-28 20:05                   ` Vojtech Pavlik
2005-01-28 19:27               ` Vojtech Pavlik
2005-01-29 20:29                 ` Wiktor
2005-01-28 14:28 ` Vojtech Pavlik
2005-01-28 16:47   ` Christian
2005-01-28 19:39     ` Wiktor
2005-01-28 19:41       ` Vojtech Pavlik
2005-01-29 20:38         ` Wiktor

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=d120d500050121113867c82596@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=victorjan@poczta.onet.pl \
    /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