On Wed, 2005-11-23 at 10:54 -0500, Alan Stern wrote: > 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.
Here's a usbmon trace when i insmod the printer driver, the printer works fine at this time. dc3d9a00 3212138081 S Co:003:00 s 01 0b 0000 0000 0000 0 dc3d9a00 3212139822 C Co:003:00 0 0 dc3d9a00 3212139939 S Ci:003:00 s a1 00 0000 0000 03ff 1023 < dc3d9a00 3212141819 C Ci:003:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 dc3d9a00 3212141968 S Ci:003:00 s a1 01 0000 0000 0001 1 < dc3d9a00 3212142819 C Ci:003:00 0 1 = 18 d3f6e500 3212294992 S Bi:003:02 -115 8192 < dc3d9d00 3212295141 S Ci:003:00 s a1 00 0000 0000 03ff 1023 < d3f6e500 3212296796 C Bi:003:02 0 0 dc3d9d00 3212297811 C Ci:003:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 d3f6e500 3220781493 S Bi:003:02 -115 8192 < dc3d9d00 3220781649 S Ci:003:00 s a1 00 0000 0000 03ff 1023 < d3f6e500 3220783424 C Bi:003:02 0 0 dc3d9d00 3220784438 C Ci:003:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 d3f6e500 3220817200 S Bi:003:02 -115 8192 < d3f6e500 3220817412 C Bi:003:02 -2 0 d3f6e500 3277341929 S Bi:003:02 -115 8192 < d3f6e500 3277343279 C Bi:003:02 0 0 d3f6e500 3303234088 S Bi:003:02 -115 8192 < d3f6e500 3303236087 C Bi:003:02 0 0 dd4b7e80 3303263204 S Bo:003:01 -115 17 = 31313131 31313131 31313131 31313131 0a dd4b7e80 3303264076 C Bo:003:01 0 17 > 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. Steve ------------------------------------------------------- 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
