From: Wiktor <victorjan@poczta.onet.pl>
To: dtor_core@ameritech.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: AT keyboard dead on 2.6
Date: Fri, 21 Jan 2005 20:07:51 +0100 [thread overview]
Message-ID: <41F15307.4030009@poczta.onet.pl> (raw)
In-Reply-To: <d120d500050121074831087013@mail.gmail.com>
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? Any other ideas?
(I use the newest gcc-3.3 if it matters.)
next prev parent reply other threads:[~2005-01-21 19:04 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 [this message]
2005-01-21 19:38 ` Dmitry Torokhov
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=41F15307.4030009@poczta.onet.pl \
--to=victorjan@poczta.onet.pl \
--cc=dtor_core@ameritech.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