On Mon, 2009-03-09 at 10:53 -0400, Alan Stern wrote: > On Mon, 9 Mar 2009, Maxim Levitsky wrote: > > > Sorry, sorry, sorry. > > > > is was the CONFIG_USB_EHCI_TT_NEWSCHED that did it. > > I confused both options, without the above option printer works > > flawlessly. > > Is your printer connected directly to the computer, or does it go > through a hub? (If it is connected directly then EHCI_TT_NEWSCHED > should not affect it at all.) > > If it does go through a hub, does it behave better when you attach it > directly? > > Alan Stern > No, it is connected directly. Just tried 'bad' driver, and firmware upload failed Do you mean that CONFIG_USB_EHCI_TT_NEWSCHED doesn't affect the driver at all when no hub is presented? Btw, at least according to lsusb -t, there are no internal hubs in the printer. But it can be a coincidence, it seems that with 'bad' driver printer works 'better' to as it failed back few days ago much more often, maybe cable is bad, don't know, but according to the web these printers 1018/1020.. have usb problems, there is even a readme for that in foo2zjz I try to use the 'good' driver (without CONFIG_USB_EHCI_TT_NEWSCHED) for some time. Best regards, Maxim Levitsky -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
