On Tue, 2005-11-22 at 16:51 -0500, Alan Stern wrote: > On Tue, 22 Nov 2005, Steve Bangert wrote: > > > Ok, here's the two raw text files sent directly to the device node, > > this one a repost of the non-working printer: > > > > ddb97300 1765765675 S Bi:003:02 -115 8192 < > > ddb97800 1765766313 S Bo:003:01 -115 9 = 31313131 31313131 0a > > ddb97300 1765767176 C Bi:003:02 0 0 > > ddb97800 1765767181 C Bo:003:01 0 9 > > > ddb97300 1787606680 S Bi:003:02 -115 8192 < > > ddb97800 1787607293 S Bo:003:01 -115 17 = 31313131 31313131 31313131 > > 31313131 0a > > ddb97300 1787608643 C Bi:003:02 0 0 > > ddb97800 1787608648 C Bo:003:01 0 17 > > > > > and here's of the same two files on a _working_ printer > > > > de154200 2248153721 S Bi:003:02 -115 8192 < > > de154200 2248155385 C Bi:003:02 0 0 > > d3e62100 2248168752 S Bo:003:01 -115 9 = 31313131 31313131 0a > > d3e62100 2248169374 C Bo:003:01 0 9 > > > de154200 2269831979 S Bi:003:02 -115 8192 < > > d3e62100 2269832840 S Bo:003:01 -115 17 = 31313131 31313131 31313131 > > 31313131 0a > > de154200 2269833877 C Bi:003:02 0 0 > > d3e62100 2269833882 C Bo:003:01 0 17 > > > Presumably the two lines of text got printed out as the second trace > ended. I hate to say it, but these two traces are essentially the same. > > > and here's a repost of the same files through cups on a non-working > > printer: > > > same files through cups on a working printer: > > These two are basically the same also, although there are some apparent > differences. A data block of size 3819 in the first trace was sent in the > second as three blocks of size 963, 2136, and 720. Likewise, a block of > size 4347 was sent instead as two blocks of size 4096 and 251. However > the way the data gets divided up into blocks shouldn't matter to the > printer. > > 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. Steve ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&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
