From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Roel Aaij <roel.aaij@gmail.com>
Cc: linux-input@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Problems with Elantech touchpad in 3.18-rc2
Date: Thu, 30 Oct 2014 11:03:31 -0700 [thread overview]
Message-ID: <20141030180331.GF36444@dtor-ws> (raw)
In-Reply-To: <545271E1.30306@gmail.com>
Hi Roel,
On Thu, Oct 30, 2014 at 06:14:09PM +0100, Roel Aaij wrote:
> Dear kernel input developers,
>
> While trying out 3.18-rc2, I noticed that the Elantech touchpad on my
> laptop didn't work as intended anymore. Mouse movement and tapping one
> finger worked, but scrolling and two finger tapping did not. X.org also
> didn't recognise the touchpad as a synaptics touchpad anymore.
>
> After googling around I found that i8042.nomux=0 brought it back to normal.
>
> My laptop is a Clevo model W650SH with a keyboard and a touchpad attached,
> and no touchschreen. Some output of dmesg is listed at the bottom, and the
> result of dmidecode is attached.
Argh, so quick search shows that there might be quite a few clones of
W650SH floating around, and I wonder if any of W650SF/W650SJ/W670SJQ/
W650SR/W650SZ exhibit the same behavior.
We might need to revert the nomux back to the original setting, although
I really do not want to do this: in my opinion it is better to have
touchpad revert to basic mode on affected laptops and work on
re-enabling MUX on them instead of having touchpad/keyboard completely
hosed from the get-go.
Linus, any guidance here? Can we live with such regression?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-10-30 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 17:14 Problems with Elantech touchpad in 3.18-rc2 Roel Aaij
2014-10-30 18:03 ` Dmitry Torokhov [this message]
2014-10-30 19:06 ` Linus Torvalds
2014-10-30 19:25 ` Dmitry Torokhov
2014-10-31 16:24 ` Dmitry Torokhov
2014-10-31 17:30 ` Pavel Machek
2014-10-31 17:35 ` 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=20141030180331.GF36444@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=roel.aaij@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).