> >I'm trying to fix the interrupt-driven lp now, but can't quite see what's
> >wrong.
>
> It would be nice to know if Anthony could print fine using the 2.0.33 lp
> driver __interrupt__ driven and __not__ polled to understand if its
> printer has hardware problems (I suppose he was using the 2.0.33 lp driver
> in the past as default and so polled). Anthony, in order to use interrupt
> with the 2.0.33 lp driver you need a program called tunelp and then run:
>
> tunelp /dev/lp1 -i 7
>
I grabbed tunelp and rebooted into 2.0.32 (never used 2.0.33) and while lp
was polling printing worked fine but turning on the interrupt handling
produced the same one character per page output as using interrupt
handling as 2.1.92+.
When I first began to use devel kernels at 2.1.58 or so I used the same
options as in the parport.txt file, which enables interrupts, and printing
worked.
-= Anthony DeStefano =- PGP key available from destefano@usa.net
<destefano@usa.net> with subject "get pgp key"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu