On Wed, 23 Nov 2005, Steve Bangert wrote: > > What happens if you move or rename the usblp.ko driver module, so that > > it's not available at boot time? You could then insmod it later on. > > Normally the file is found in > > > > /lib/modules/<linux-version>/kernel/drivers/usb/class > > > > It may turn out when you do this that the printer just starts working, or > > you may encounter the same problem as before. If you do then you'll be > > in a good position to use usbmon. > > Here's a usbmon trace when i insmod the printer driver, the printer > works fine at this time.
> So far i have been unable to produce a non-working printer condition > using this procedure and thus no trace so far, i suspect that i may > never be able to capture a trace under these conditions, do you know of > a way to start usbmon before /sbin/modprobe runs at system boot? That > seems to be the only time the printer fails to work. If worse comes to worst and we never find an answer, at least you know now how to prevent the problem from occurring... :-) What if instead of delaying usblp.ko, you delay the host controller driver (uhci-hcd.ko)? At this point it's not clear whether the key is having the printer on when the computer boots or having the printer on when the USB host controller initializes. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
