> From: [email protected] [mailto:[email protected]]
> I am seeing a strange keyboard related issue as well on a
> Thinkpad A20M. It seems if I walk away for say, 20 minutes,
> come back and try to input a password to KDE's screen saver,
> the FIRST keystroke I make is not recognized at all. All
> keystrokes after the first one register perfectly fine. This
> is on the laptop's built-in keyboard. I too am using ACPI. If
> I don't wait long enough it doesn't happen, so I do believe
> it has something to do with power management. I first noticed
> it in 2.5.61(first 2.5 kernel that would boot for me) and am
> currently running 2.5.63, where I still see it. I am not
> using modules.
>
> If anyone would like more info on this, please let me know.
I am seeing the same behavior under Windows on an IBM T20. This makes me
think it is not something the kernel is to blame for.
Regards -- Andy
I have the same problems with repeating keys when
running under battery vs AC power with the later 2.5.6x
kernels on an IBM T20. It goes away when i plug in
the AC adaptor or boot w/o acpi. The only other oddity
i've noticed is that i have to cntrl-alt-del TWICE
to get it to reboot, the first one does jack, but
i'm not blaming that on the kernel just yet ;p
-pee
Grover, Andrew wrote:
>>From: [email protected] [mailto:[email protected]]
>>I am seeing a strange keyboard related issue as well on a
>>Thinkpad A20M. It seems if I walk away for say, 20 minutes,
>>come back and try to input a password to KDE's screen saver,
>>the FIRST keystroke I make is not recognized at all. All
>>keystrokes after the first one register perfectly fine. This
>>is on the laptop's built-in keyboard. I too am using ACPI. If
>>I don't wait long enough it doesn't happen, so I do believe
>>it has something to do with power management. I first noticed
>>it in 2.5.61(first 2.5 kernel that would boot for me) and am
>>currently running 2.5.63, where I still see it. I am not
>>using modules.
>>
>>If anyone would like more info on this, please let me know.
>>
>>
>
>I am seeing the same behavior under Windows on an IBM T20. This makes me
>think it is not something the kernel is to blame for.
>
>Regards -- Andy
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>