From: Igor Murzov <intergalactic.anonymous@gmail.com>
To: linux-input@vger.kernel.org
Subject: [RFH] Lenovo Ideapad U455 touchpad not always works
Date: Mon, 30 Jan 2012 04:51:43 +0400 [thread overview]
Message-ID: <20120130045143.5d1be121@garik> (raw)
Hi, list.
I have a problem with my touchpad. It works fine, but not at every boot.
More specifically, AUX port not always initialized properly:
-----------------------------------------
i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12 # <-- this line is not always appear in dmesg output
-----------------------------------------
Here are two dmesg outputs:
http://paste.pro/5141560 <-- this time touchpad worked fine
http://paste.pro/5141561 <-- and this time touchpad was not working
I saw in the git logs that many laptops require some workaround to make
their touchpad work. I've tried i8042.notimeout, i8042.nomux and
i8042.noloop, but this didn't solve the issue. I wonder is there any way
to detect which options should I use to make touchpad work, other than
rebooting system countless number of times?
Output of lshw: http://paste.pro/5141562
-- Igor
reply other threads:[~2012-01-30 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120130045143.5d1be121@garik \
--to=intergalactic.anonymous@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