public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Micha Feigin <michf@post.tau.ac.il>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc2-mm4 + alps locks input in X (alps not identifying correctly)
Date: Tue, 28 Sep 2004 05:46:22 +0200	[thread overview]
Message-ID: <20040928034622.GA3158@luna.mooo.com> (raw)
In-Reply-To: <m3wtyf792x.fsf@telia.com>

On Mon, Sep 27, 2004 at 10:25:42PM +0200, Peter Osterlund wrote:
> James Oakley <joakley@solutioninc.com> writes:
> 
> > On Monday 27 September 2004 4:27 pm, Micha Feigin wrote:
> > > I tried both with mm4 with the already included alps patch and with
> > > bk11 and bk13 with the patch manually applied. In both cases when
> > > starting X with the alps driver input is completely dead in X, both
> > > mouse and keyboard, including sysrq keys and num-lock/caps-lock.
> > 
> > I had this problem when I accidentally used the event device for my keyboard 
> > instead of the touchpad. It didn't help that every alps XF86Config example 
> > out there points to event1, which is my keyboard.
> > 

Thanks that solved the problem, no more lockups.

> > cat /proc/bus/input/devices to see which event device to use.
> 
> Or better yet, use the auto-dev feature, which should work if you have
> a new enough X driver and kernel patch.
> 

auto-dev doesn't work for me and I don't have time to check it
out. While poking around I did find another problem though.

There is also a kernel problem, to summarize, the touchpad is
identifying itself differently then with previous kernels and thus
isn't recognized at all by the kernel.

I don't know how much effect it actually has since some initialization
is also done through X.

The main problem I found:

Under 2.6.9-rc2-mm4 in alps.c under function alps_get_model, for the
call to ps2_command with PSMOUSE_CMD_GETINFO (the E6 report output) the
output is 00 00 14 instead of 00 00 64 like it was before and what is
expected, so the touchpad isn't recognized at all as an alps. (I can't
figure out whats causing the difference or how the return value is
received at all, and I don't have any more time to dig further into it).

Second problem is that hardware tapping is disabled by default
(I found no way to enable it externally) which in my case causes most
taps to be interpreted as double clicks instead of single clicks.

After fixing both things and X to use the right device things finally
work again.

> -- 
> Peter Osterlund - petero2@telia.com
> http://w1.894.telia.com/~u89404340
> -
> 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/
>  
>  +++++++++++++++++++++++++++++++++++++++++++
>  This Mail Was Scanned By Mail-seCure System
>  at the Tel-Aviv University CC.
> 

  reply	other threads:[~2004-09-28  2:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 19:27 2.6.9-rc2-mm4 + alps locks input in X Micha Feigin
2004-09-27 19:04 ` James Oakley
2004-09-27 20:25   ` Peter Osterlund
2004-09-28  3:46     ` Micha Feigin [this message]
2004-09-28  6:23       ` 2.6.9-rc2-mm4 + alps locks input in X (alps not identifying correctly) Dmitry Torokhov

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=20040928034622.GA3158@luna.mooo.com \
    --to=michf@post.tau.ac.il \
    --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