From owner-freebsd-questions Fri May 16 04:12:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22591 for questions-outgoing; Fri, 16 May 1997 04:12:11 -0700 (PDT) Received: from localhost (poca33.capecod.net [205.230.13.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA22583 for ; Fri, 16 May 1997 04:12:04 -0700 (PDT) Received: (from crtb@localhost) by localhost (8.6.12/8.6.12) id XAA01698; Thu, 15 May 1997 23:31:19 -0400 Date: Thu, 15 May 1997 23:31:19 -0400 From: Chuck Message-Id: <199705160331.XAA01698@localhost> To: helbig@MX.BA-Stuttgart.De, proot@horton.iaces.com Subject: Re: Slow printer behavior Cc: crtb@capecod.net, questions@FreeBSD.ORG Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >In a previous message, Wolfgang Helbig said: >> > Running FreeBSD 2.2.0-RELEASE. >> > Problem: Printer (a Canon BJ200 Bubble-Jet) runs at normal speed about >> > half the time, but often excruciatingly slowly. Sometimes it will print an >> > entire page, pausing about ten seconds between passes across the paper. >> > And other times it goes at normal speed. I use apsfilter and >> > ghostscript 3.51 for most printing. >> > >> > This behavior just began about a month ago. I think of a bad connection >> > somewhere, with an ACK signal failing or something like that. Or is it >> > possible that the printer port interrupt can get turned off, and the >> > /dev/lpt driver fails to restore it? >> > >> > Wonder if anyone else has seen this happen. I'd be grateful to find out! >> >> Nope, I'm using the same printer, apsfilter, ghostscript 2.6.2 and -current >> and never seen anything like that. > >You might try setting your lpt port to polling instead of interrupt, and see >if that does anything. Polling should be more efficient that interrupts >anyway. I have a BJC-4100 on mine. > >You can put it in your config with: >device lpt0 at isa? port "IO_LPT1" tty Sounds interesting! I'll try it next kernel around. >Or set it via the command line with: > >lptcontrol -p -u 0 May solve the problem. Still, I'd like to know why the interrupt system seems to have failed. >Paul. > > >-- >Never attribute to malice that which is adequately explained by stupidity. > --Grant R. Gainey Thanks for the tips. Wonder why I never knew about lptcontrol :-]