From: Kevin Fenzi <kevin-kernel@scrye.com>
To: linux-kernel@vger.kernel.org
Subject: psmouse as module with suspend/resume
Date: Thu, 15 Jul 2004 14:54:55 -0600 [thread overview]
Message-ID: <20040715205459.197177253D@voldemort.scrye.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings.
I am having a bit of an issue with psmouse and suspend/resume.
I am using the swsusp2, which is working great... (Thanks Nigel!)
However:
If I compile psmouse as a module and leave it in and suspend/resume
when the laptop comes back the mouse doesn't work at all.
If I compile psmouse as a module and unload before suspend, and reload
after resume, the mouse works for simple movement, but all the
advanced synaptics features no longer work. No tap for mouse button,
no scolling, etc.
If I compile psmouse in everything works after a suspend/resume cycle.
I would like to be able to compile psmouse as a module. Does anyone
see any reason the synaptics stuff wouldn't work after a
unload/reload?
Before a suspend/resume:
kernel: Synaptics Touchpad, model: 1
kernel: Firmware: 5.9
kernel: Sensor: 51
kernel: new absolute packet format
kernel: Touchpad has extended capability bits
kernel: -> 4 multi-buttons, i.e. besides standard buttons
kernel: -> multifinger detection
kernel: -> palm detection
kernel: input: SynPS/2 Synaptics TouchPad on isa0060/serio4
Afer a unload and reload:
kernel: Synaptics Touchpad, model: 1
kernel: Firmware: 5.9
kernel: Sensor: 51
kernel: new absolute packet format
kernel: Touchpad has extended capability bits
kernel: -> 4 multi-buttons, i.e. besides standard buttons
kernel: -> multifinger detection
kernel: -> palm detection
kernel: input: SynPS/2 Synaptics TouchPad on isa0060/serio4
So, it all looks the same there.
I wonder if it's not something with the input layer not reconnecting
right on reload with what the synaptics driver in X is expecting...
In the X log after a resume/reload:
(II) DevInputMice: ps2EnableDataReporting: succeeded
Synaptics DeviceOn called
(EE) xf86OpenSerial: Cannot open device /dev/input/event2
No such device.
(WW) Mouse0: cannot open input device
Any ideas?
Happy to provde more information on versions, etc...
thanks,
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFA9u8i3imCezTjY0ERAmWnAJ9uKMauJAfSMKgz9VBB6Z5o7/66vACffKg5
8Imj27a19cu4OtVuhaszXOM=
=6i7m
-----END PGP SIGNATURE-----
next reply other threads:[~2004-07-15 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 20:54 Kevin Fenzi [this message]
2004-07-16 5:58 ` psmouse as module with suspend/resume Dmitry Torokhov
[not found] ` <20040716164704.CFC1A43FF@voldemort.scrye.com>
2004-07-16 22:43 ` Dmitry Torokhov
2004-07-17 4:23 ` Nigel Cunningham
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=20040715205459.197177253D@voldemort.scrye.com \
--to=kevin-kernel@scrye.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