Comment 47 for bug 35638

Have you looked into the hunch I posted quite a while ago? The cycling
timing may be due to the driver looking at the wrong status bit. If it
is looking at a bit which goes on & off to indicate status of the fuser
heater temperature, it would behave like it does -- random on and off
intervals as the fuser heater goes on and off to maintain temperature of
the roller. Maybe the driver looks at the fuser status, not the
printer-ready-to-receive-data status bit. When I use the parallel
port, the printer works fine. Parallel port doesn't have a fuser status
bit to confuse a driver, only a printer status bit. The problem is not
in the printer, but rather in a driver that looks at the wrong status, I
think. Perhaps Brother support can give you a document that details the
status information which the printer reports.

Stan Sokolow
==================
Till Kamppeter wrote:
> So then it seems that the problem is not caused by the "usblp" module
> but by a lowere level USB driver in the kernel or even by the hardware.
>
> Does
>
> lsusb
>
> and
>
> lsusb -vvv
>
> always give the same output? Or is there some cycling also there?
>
>