From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Awtrey Date: Thu, 29 Sep 2005 16:32:43 +0000 Subject: udev 070 and coldplugged usb mice Message-Id: <433C172B.5060301@idealcorp.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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