From: ulrik.debie-os@e2big.org
To: WangBiscuit <biscuit_2014@outlook.com>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: PROBLEM: ETPS/2 Elantech Touchpad dies after resume from suspend to RAM
Date: Mon, 26 Oct 2015 20:40:15 +0100 [thread overview]
Message-ID: <20151026194014.GA7442@lantern> (raw)
In-Reply-To: <BAY169-W27FC7ECF27DC8BAB44F081F7260@phx.gbl>
Hi,
Sorry, reaction will be slow these days, I'm rather busy.
So indeed your keyboard is also serio connected but that keeps on functioning
(and you're not using an usb keyboard).
Can you confirm that psmouse module is still loaded after the resume ? I see
no clear reason why the sysfs entry would be gone except when it is asked
to do a complete 'disconnect'. We could verify if elantech_disconnect is
called by adding a printk there for instance.
Would it be easy for you to apply a patch to the kernel and build ?
What happens if you rmmod psmouse and modprobe it again ? Does that also make
the mouse function again ? If that already gives you the mouse back, you can
add unload/modprobe the module as a workaround to your suspend/resume scripts.
When after resume the psmouse module is still present, I expect the problem
to be within the kernel and not gnome.
Best regards,
Ulrik
next prev parent reply other threads:[~2015-10-26 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 3:59 PROBLEM: ETPS/2 Elantech Touchpad dies after resume from suspend to RAM WBH
2015-10-19 14:53 ` Mike Mestnik
[not found] ` <20151022200616.GA11764@lantern>
[not found] ` <BAY169-W27FC7ECF27DC8BAB44F081F7260@phx.gbl>
2015-10-26 19:40 ` ulrik.debie-os [this message]
[not found] ` <BAY169-W817552DF4F9EC29EB3569CF7220@phx.gbl>
2015-10-27 2:25 ` WangBiscuit
-- strict thread matches above, loose matches on Subject: below --
2015-10-20 1:51 WangBiscuit
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=20151026194014.GA7442@lantern \
--to=ulrik.debie-os@e2big.org \
--cc=biscuit_2014@outlook.com \
--cc=dmitry.torokhov@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 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).