From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Wed, 07 Mar 2001 03:38:31 +0000 Subject: Re: "Cold"-plugging my printer 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 So what did the "sh -x" invocation tell you about exactly why the USB agent did nothing when it contemplated loading "printer"? We know the result is wrong. We don't know why, but the answer is surely in that part of your "sh -x" output. - Dave ----- Original Message ----- From: "Pete Toscano" To: "David Brownell" Cc: Sent: Tuesday, March 06, 2001 7:09 PM Subject: Re: "Cold"-plugging my printer This is weird... (Not a good sign, eh? =) I tried what you said. I rebooted into single-user mode and ran "sh -x /etc/..." Errrr, oops. I just realized that I ran /etc/init.d/hotplug start (which, in turn, ran /etc/hotplug/usb.rc start). After, when I ran lsof, I noticed that the printer module was indeed loaded. Being a little surprised by this, I ran hotplug stop and then start and this time, a lot more debugging was printed out (all that USB setup info) and the printer module was not loaded. I tried it again and the same thing happened. pete On Tue, 06 Mar 2001, David Brownell wrote: > Or there could be something wrong in the boot-time init code, so that > a bit of shell script debugging is in order on your system. Maybe you > can boot in single-user mode and "sh -x /etc/hotplug/usb.rc start" to > watch what it's doing wrong! (Called by "/etc/rc.d/init.d/hotplug start", > as Greg suggested.) _______________________________________________ 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