It's actually not just suspend/resume that's the problem. Just
disconnecting and reconnecting the mouse causes X to ignore the device
for the duration. My guess is that X gives up on the device once it
returns a read error.
I'm back to using the boot protocol driver in 2.2.13. Even though it
doesn't support the scroll wheel, at least I can disconnect and
reinsert the mouse without fear.
Lincoln
Dunlap, Randy writes:
> Hi,
>
> > From: Lincoln Stein [mailto:[EMAIL PROTECTED]]
> >
> > The subject line says it all. When I suspend/resume with a USB
> > mouse, the mouse device gets detached from /dev/input/mouse0 and
> > reattached to /dev/input/mouse1. Needless to say, this confuses X
> > tremendously.
>
> This seems to say to me that the input module isn't told about
> the disconnect (from the suspend), so the resume (=> connect)
> allocates another input/mouseN.
>
> [snip log]
>
> > I'm using standard APM. Oddly enough, the old development USB driver
> > in the 2.2.14 kernel worked quite well across suspend/resume. I got
> > greedy and wanted to use the scroll wheel in the intellimouse!
>
> Is use of the scroll wheel documented somewhere?
>
> ~Randy
--
========================================================================
Lincoln D. Stein Cold Spring Harbor Laboratory
[EMAIL PROTECTED] Cold Spring Harbor, NY
========================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
