From: Anthony Awtrey <tony@idealcorp.com>
To: linux-hotplug@vger.kernel.org
Subject: udev 070 and coldplugged usb mice
Date: Thu, 29 Sep 2005 16:32:43 +0000 [thread overview]
Message-ID: <433C172B.5060301@idealcorp.com> (raw)
I have a tablet device with an internally connected usb mouse pointer
running Debian unstable. I'm using linux kernel version 2.6.13.2 and
Marco's debian unstable package udev-0.070-3. That udev package
conflicts out the hotplug package completely which may have done the
coldplugging correctly before.
Neither the usb driver for the mouse, nor the general PS/2 mousedev
driver load automatically at boot time. I've gotten around this by
running an ugly hack coldplug catchup script as the last run-level S script:
for i in /sys/bus/*/*/*/modalias
do
modprobe `cat $i`
done
modprobe mousedev
I see udevsynthesize is running during the udev init script and the
devices are showing up as expected under the /sys/bus/* directories even
when the usb modules don't loading automatically. Should udev
automatically load all drivers via udevsynthesize without some kind of
additional coldplugging hack? Or is this expected behaviour?
T
--
Anthony L. Awtrey
Chief Technology Officer
[T] 407.999.9870 x13
[F] 407.999.9850
I.D.E.A.L. Technology Corporation
http://www.idealcorp.com
"The Leader in Linux and Open Source Solutions"
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-09-29 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 16:32 Anthony Awtrey [this message]
2005-09-29 16:51 ` udev 070 and coldplugged usb mice Marco d'Itri
2005-09-29 17:17 ` Anthony Awtrey
2005-09-29 17:21 ` Marco d'Itri
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=433C172B.5060301@idealcorp.com \
--to=tony@idealcorp.com \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.