archive mirror
 help / color / mirror / Atom feed
From: Eric Altendorf <>
	swsusp-devel <>
Subject: Hotplug USB mouse bugs in 2.4+swsusp
Date: Fri, 11 Jul 2003 09:16:13 -0700	[thread overview]
Message-ID: <> (raw)

I'm not sure if this is a general kernel issue, a hotplug issue, a USB 
issue, or a swsusp issue, so I'm hoping for guidance here.

I'm running 2.4.21 (+ latest ACPI, toshiba ACPI, and swsusp pre14) and 
to get my USB mouse working at all with swsusp I had to use hotplug.  
However, I'm having a number of problems.

The mouse, under normal operation at times of heavy CPU or disk usage, 
will be spontaneously lost.  No messages are issued.  Physically 
unplugging and re-plugging the mouse restores it.

No matter what I've tried, after switching to using hotplug 
(previously I had been using the 2.5 kernel w/o the hotplug daemon), 
I have been unable to get the internal pointer multiplexed into 
/dev/input/mice.  USB mouse shows up under /dev/input/mice and 
internal pointer shows up under /dev/psaux only.

After suspend & resume, USB mouse is gone.  Physically replugging it 
doesn't help.  /etc/init.d/hotplug restart  fixes it.

Any ideas?  /proc cats, dmesgs, .configs, etc, available upon request.

Thanks much!


             reply	other threads:[~2003-07-14 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 16:16 Eric Altendorf [this message]
2003-07-14 18:52 ` [Swsusp-devel] " Nigel Cunningham
2003-07-14 20:01 ` Vojtech Pavlik

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Hotplug USB mouse bugs in 2.4+swsusp' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).