From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Wed, 11 Apr 2001 00:39:25 +0000 Subject: Re: rawhide hotplug broken Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > In case folks here are unaware, RedHat has been hacking > the hotplug srpm releases here for their rawhide releases > (and I assume their upcoming RH 7.1 release) doing such things > as removing the rc scripts from hotplug. It'd be interesting to know why that isn't being included. Despite what Trond said (in a separate email on this thread), it does more than just load modules; it also mounts "usbdevfs" at the _right_ time (before USB host controller modules load) to deal with some boot-time hotplugging ("cold-plugging") issues that come up in some configurations ... like the way RedHat 7.0 initialized USB, or the last 7.1 init scripts I saw did. Also, perhaps of more relevance to USB developers, "rc.usb" provides some simple USB diagnostics ("rc.usb status") and makes it easy to start, stop, and restart the USB subsystem. > On my linuxppc (running > Linux 2.4.4pre1, glibc 2.2.3 and the rawhide srpms), I find > that RedHat's modified hotplug doesn't work for loading the > usb print module when it sees my Epson 740i printer. ... Well, I did notice RedHat wasn't using current RPMs, but I don't think that'd be the whole problem. > I discovered last night that if I installed the latest > hotplug-2001_02_28 and usbutils-0.7-101 rpms on my machine > that the usb print module was loaded on boot or hotplugging > the Epson 740i printer. I also discovered that I had to have > usbutils installed for the hotplugging to work. Curious. Can you try debugging the script invocation to see why? I usually: (a) modify /sbin/hotplug to "env >/tmp/debug"; (b) insert the device, (c) modify a copy of that /tmp/debug file and turn it into a script that exports all variables (or at least the six used by USB hotplug :) and then does something like cd /etc/hotplug sh -x usb.agent Then there's copious debug output (save it to a log file) which can be examined ... in this case, to see why the "printer" driver listing in /lib/modules/.../modules.usbmap doesn't match. - Dave _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel