--- Jan Rychter <[EMAIL PROTECTED]> wrote:
> >>>>> "Pete" == Pete Zaitcev <[EMAIL PROTECTED]> > writes: > Pete> On Sat, 11 Mar 2006 15:56:42 +0100, Jan > Rychter <[EMAIL PROTECTED]> > Pete> wrote: > >> I guess I need to print from Windows. Or get a > Mac... > > Pete> This is a good solution if it works for you. > Remember, it's all > Pete> in your hands. Nobody else can find and fix > your problem (most > Pete> certainly not without the data). > > I guess the above is a measure of my frustration and > a response to your > suggestion about the HP1200 being a crappy device. > The amount of time > that I have to spend on debugging (or helping debug) > problems with Linux > is increasing. I find that as years go by, more and > more drivers cause > problems. This is especially pronounced in case of > USB and FireWire -- I > can practically be sure that manupulating > peripherals connected to these > buses will eventually cause problems and lead to a > reboot. > > As an example, the host in question (the one with > printer problems) at > this moment has a process stuck in D state, trying > to print to the > printer that hangs. I typed 'lsusb', which now hangs > too. Power cycling > the printer does not help and I'm pretty sure I'll > have to reboot. Years > of experience taught me to be afraid of rmmoding > modules as well (and > for good measure, as an attempt to 'rmmod ehci_hcd' > has just resulted in > a stuck rmmod and a reboot). > > I realize that there are crappy cables and devices > that barely meet the > specs. Still, a Mac somehow manages not to crash and > burn and to to the > Right Thing. I'd gladly pick a USB implementation > many times slower and > burning a ton of CPU, but actually doing its job. > > Why is it that the Linux USB subsystem is so > fragile? > > --J. > > > > ------------------------------------------------------- > 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 > There are many printers that have internal timing problems non of which are ever ack'd by the printer manufacture. The driver for windows or Mac that they provide takes into consideration these internal problem. As I work for a large printer manufacture, I am aware of problems in some of the printers we produce. It generally comes down to internal priority issues in the printer. The internal usb controller has a higher then some time critical process and will cause that process to timeout if data is sent/received at a high data rate. When that process times out, the printer basically hangs for printing purposes. To work around these problems it becomes necessary to throttle the sending/receiving of data. It would be nice if the company I work for would provide this information so that we could handle these problem printers without having to experiment with data rates. Wish I could provide more data but am bound by an NDA but I hope this helps. Regards, John Carlson John Carlson <[EMAIL PROTECTED]> __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- 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