I don't know if there's a way to stop this, but it's normal, whenever I use my Parallel port zip drive, I have similar problems.
Ken On Sunday 02 December 2001 01:20 pm, you wrote: > I have an HP postsript laser (2100M) on a parallel intfc. > > [alane ~]$ uname -a > FreeBSD wwweasel.geeksrus.net 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Sun Oct > 28 04:44:34 EST 2001 > [EMAIL PROTECTED]:/usr/src-4.4-RELEASE/sys/compile/WWWEASEL i386 > > [alane ~]$ grep -i parallel /var/run/dmesg.boot > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 > > When I print a document that is heavy in graphics, it's large. > Multi-megabytes. That's expected 'cause postscript is verbose. > > But what surprises me is that copying that data to the parallel intfc burns > up an incredible amount of CPU. Until the document is printed, there's a > steady bg buzz of ~10% CPU use, with periods of 50% and even 100% CPU > utilization by the 'parallel'[1] process. The load is sufficient that it > locks out the mouse on X (interrupt blocking?). > > Anyone care to comment? Does this sound normal? Is there a way to reduce > the amount of CPU needed to drive the parallel port? > > Notes: > [1] /usr/local/libexec/cups/backend/parallel is the device interface using > by the print/cups package. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
