On Sun, 05 Mar 2006 13:13:16 +0100, Jan Rychter <[EMAIL PROTECTED]> wrote:
> BTW, if you google for "usblp0: failed reading printer status", you'll > see that a number of people have this problem. Most probably don't know > how and where to report it and just make do by power-cycling the printer. This a very clear example of dangers of googling for error messages. Same thing happens when they search for "ep0in: timeout". I can virtually guarantee that Helge's problem has nothing to do with yours. Timeouts when getting status are just that: timeouts. Firstly, there may be many reasons why this happens - all resulting in the same message. Secondly, they are somewhat normal and expected when working with 1020. It does not take too much for that thing to get boggled down and bust a few deadlines. In your case, the real problem is the -71. That is actually serious, mening that the printer is completely dead, not answering the low level requests (tokens). If you could catch a usbmon trace for the moment where the printer dies, it may be helpful. But you have to find it all by yourself. Try to engage the 1020 project. I try to work with Rick on 1020 issues, but it's not going well. See this for example: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174961 (Do not even think to mix this with your own bug - they are entirely different). -- Pete ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
