All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: littlebat <dashing.meng@gmail.com>
Cc: linux-input@vger.kernel.org, seth.forshee@canonical.com
Subject: Re: Lenovo G360: ALPS Touchpad Recognized as "PS/2 Generic Mouse"
Date: Wed, 4 Jul 2012 22:20:09 -0500	[thread overview]
Message-ID: <20120705032009.GA8748@burratino> (raw)
In-Reply-To: <CAAT31jY5_P13xjybsYFm3oix0pjbbzRihCrjecQ+cXkrHhnrCQ@mail.gmail.com>

(dropping Debian bug from cc list)
Hi,

littlebat wrote:

>                                                               I report a
> kernel bug about ALPS touchpad to you.
>
> My lenovo G360 has an ALPS touchpad, show in Windows 7 Home Editition
> OEM in this laptop. Under Debian Squeeze or Ubuntu 12.04 LTS LiveCD in same
> laptop, the left and
> right key, single and double tap, tracking  of touchpad works well.
> But, there isn't touchpad tab in gnome mouse setting dialog, so I
> can't setup edge scrolling and disable touchpad on typing. xinput
> shows it is a "PS/2 Generic Mouse".
[...]
> Tell me If need more detail information.

Thanks.  Forgive me for being dense: can you spell this out a little
more for me?

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

Could you provide full "dmesg" output from booting a working and
non-working kernel?

Hope that helps,
Jonathan

  reply	other threads:[~2012-07-05  3:20 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 [this message]
2012-07-05  7:45   ` littlebat
2012-07-05 13:30     ` Seth Forshee
  -- 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=20120705032009.GA8748@burratino \
    --to=jrnieder@gmail.com \
    --cc=dashing.meng@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    /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.