On Wed, 23 Nov 2005, Steve Bangert wrote:
> > These traces show that the same data is getting sent to the printer in the
> > same way each time. So there's nothing wrong with the printing procedure
> > itself. Whatever is going wrong must happen earlier, during the device
> > detection and setup. Do you think you can trace that?
>
> I think I'll need some help with that, haven't found any documentation
> on recording usbmon traces at boot. Thanks for all your help so far.
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.
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
