From: "hanasaki@gmail.com" <hanasaki@gmail.com>
To: LIST - Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Mouse no longer working : works in 4.18 : doesn't work in 4.18.5
Date: Fri, 7 Sep 2018 09:41:09 -0400 [thread overview]
Message-ID: <8a77c527-01af-3857-e4ad-30be18f94bd2@gmail.com> (raw)
Mouse worked fine in 4.18 however does not work in 4.18.5 Both kernels
were built with exactly the same .config file (copied from the 4.18
build dir to the un-tar'ed 4.18.5 directory to build)
Any input on root cause and fix / workaround is appreciated.
"Doesn't work" means : syslog and kernel show that:
1. the kernel finds the mouse
2. gpm finds the mouse and detects its protocol
3. mouse cursor does not move and buttons do not work
: not in gpm
: not in X
4. syslog and kernel .config are the same for both versions
Below is the output from syslog and dmesg.
Update : same issue in 4.18.6 @ 20180906
========= dmesg
6.925981] usbcore: registered new interface driver usbhid
[ 6.925982] usbhid: USB HID core driver
[ 6.927425] usbcore: registered new interface driver usbmouse
[ 6.942113] input: PixArt USB Optical Mouse as
/devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/0003:093A:2510.0001/input/input17
[ 6.942207] hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID
v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-10/input0
========= Syslog
Sep 6 23:26:22 russia /usr/sbin/gpm[2699]: *** info
[daemon/startup.c(131)]:
Sep 6 23:26:22 russia /usr/sbin/gpm[2699]: Started gpm successfully.
Entered daemon mode.
Sep 6 23:26:23 russia /usr/sbin/gpm[2699]: *** info [mice.c(2059)]:
Sep 6 23:26:23 russia /usr/sbin/gpm[2699]: Detected EXPS/2 protocol mouse.
TIA / Thanks.
reply other threads:[~2018-09-07 13:41 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=8a77c527-01af-3857-e4ad-30be18f94bd2@gmail.com \
--to=hanasaki@gmail.com \
--cc=linux-kernel@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
Powered by JetHome