Messages in this thread | | | Date | Tue, 12 Sep 2006 16:24:19 +0200 (CEST) | From | Piotr Gluszenia Slawinski <> | Subject | Re: thinkpad 360Cs keyboard problem |
| |
On Tue, 12 Sep 2006, Dmitry Torokhov wrote:
> On 9/11/06, Piotr Gluszenia Slawinski <curious@zjeby.dyndns.org> wrote: >> well, certainly 2.6.18 issue... > > Are you saying that it works on 2.6.17 and is broken on 2.6.18?
no, it works on 2.4.20. i didn't tried yet with other 2.6.x versions.
btw. now i compiled 2.4.33.3 using gcc 3.4.6 , and even though i used 486 in cpu type resulting binary requires TSC+ from cpu :o (now recompiling with gcc-2.95.3 , and config_notsc and it seems to boot up)
however weird behaviour aswell, because stops just after init... no matter wheter i use init=/bin/bash or regular init. it reports mounting root fs (ext2), then freeing unused kernel mem (52k) and stops .
when i press keys i see output like it should be , so at least keyboard work :)
with 2.6.18-rc5 it boots just fine, but ofcourse keyboard is broken.
>> 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.
so wrong keys reported - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |