Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

[Jiri Slaby]

On 3/9/07, Jiri Kosina <jikos@xxxxxxxx> wrote:
> On Fri, 9 Mar 2007, Jiri Kosina wrote:
>
> > If this is present also in vanilla and not only in -mm, could you please
> > try reverting commits 4237081e573b99a48991aa71364b0682c444651c and
> > d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the
> > situation gets any better?
>
> Hi Jiri,

Hi.

> or even better, does the patch below (against 2.6.21-rc3) fix the problem
> with your keyboard? I can see possibilities of report fields unaligned to
> the byte boundary, which this might be causing problems.

I'll try it all.

I don't know if this is related, but my notebook keyboard doesn't emit
numbers with numlock (not even directly Fn+blue number) anymore with
-rc3 (note that LED is flashing when numlock is on). I think -rc2
worked fine (I'm going to check this too). It's Asus M6R, similar
(except wi-fi) to for example yenya's model here:
http://www.fi.muni.cz/~kas/m6r/

thanks,
--
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/