All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: littlebat <dashing.meng@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	linux-input@vger.kernel.org, 679750@bugs.debian.org
Subject: Re: Lenovo G360: ALPS Touchpad Recognized as "PS/2 Generic Mouse"
Date: Thu, 5 Jul 2012 08:30:36 -0500	[thread overview]
Message-ID: <20120705133036.GA28604@thinkpad-t410> (raw)
In-Reply-To: <20120705154545.8d7492cc.dashing.meng@gmail.com>

On Thu, Jul 05, 2012 at 03:45:45PM +0800, littlebat wrote:
> > Is the following summary correct?
> > 
> >  - 2.6.32.y (Debian squeeze) works well, using xinput or synclient to
> >    configure
> >  - 3.2.y (Ubuntu 12.04 LTS) sees a generic mouse, unconfigurable
> >  - 3.2.y (Debian squeeze-backports) is likewise unconfigurable
> >  - 3.4.4 (Debian experimental) is also unconfigurable
> 
> No, none of these four kernels can configure a full functional ALPS
> touchpad. Under all of these four kernels:
> 1, "synclient -l" shows "Couldn't find synaptics properties. No
> synaptics driver loaded? "
> 2, "xinput --list" shows it is a "PS/2 Generic Mouse"
> 3, "cat /proc/bus/input/devices" shows it is "N: Name="PS/2 Generic
> Mouse""
> 4, Can't find any string like "touchpad", "synaptics" in
> "/var/log/Xorg.0.log" 
> 5, There isn't touchpad tab in gnome mouse setting dialog, so I
> can't setup edge scrolling and disable touchpad on typing.

ALPS refuses to provide information about their touchpad protocols, so
any support we have for ALPS touchpads is based on reverse engineering
the protocol. It's likely that yours uses some version of the protocol
that isn't supported, in which case someone with access to the hardware
will need to do the reverse engineering work.

There's a slight chance that it uses a known protocol but just has an
unknown model signature. In that case the fix is easy, but it will
require some trial and error to see if that's the case.

> > Could you provide full "dmesg" output from booting a working and
> > non-working kernel?
> 
> The laptop isn't here, I will post full "dmesg" output under "3.4.4
> (Debian experimental)" kernel later.

When you send dmesg it would help if you could use a build with the
following line added to the top of drivers/input/mouse/alps.c, before
the includes.

 #define DEBUG

This will cause the model signature for your touchpad to be included in
the log.

Thanks,
Seth


  reply	other threads:[~2012-07-05 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05  2:58 Bug#679750: Lenovo G360: ALPS Touchpad Recognized as "PS/2 Generic Mouse" littlebat
2012-07-05  3:20 ` Jonathan Nieder
2012-07-05  7:45   ` littlebat
2012-07-05 13:30     ` Seth Forshee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-05  3:30 littlebat

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=20120705133036.GA28604@thinkpad-t410 \
    --to=seth.forshee@canonical.com \
    --cc=679750@bugs.debian.org \
    --cc=dashing.meng@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-input@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.