Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Mar 1998 13:29:18 +0930
From:      Greg Lehey <grog@lemis.com>
To:        John Utz <utz@serv.net>
Cc:        questions@freebsd.org
Subject:   Re: lptcontrol -p is good!Re: why is ghostscript so slow now? did i miss a setting?
Message-ID:  <19980330132918.31846@freebie.lemis.com>
In-Reply-To: <Pine.BSI.3.95.980329180058.6756A-100000@itchy.serv.net>; from John Utz on Sun, Mar 29, 1998 at 07:18:25PM -0800
References:  <19980329163759.20841@freebie.lemis.com> <Pine.BSI.3.95.980329180058.6756A-100000@itchy.serv.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 29 March 1998 at 19:18:25 -0800, John Utz wrote:
> On Sun, 29 Mar 1998, Greg Lehey wrote:
>
>> On Sat, 28 March 1998 at 23:01:39 -0800, John Utz wrote:
>>>> On Sat, 28 March 1998 at 13:13:37 -0800, John Utz wrote:
>>>>> hi;
>>>>>
>>>>> vital stats:
>>>>>
>>>>> 2.2.6-980323-BETA
>>>>>
>>>>> fake pentium amd p5 kr-100 32 meg o ram
>>>>>
>>>>> canon bj200ex printer
>>>>>
>>>>> gs 2.6.2 or gs 5.1.0
>>>>>
>>>>> this setup was perfectly tolerable with ghostscript and apsfilter in 2.2.5
>>>>>
>>>>> now it takes an hour to print two pages!
>>>>>
>>>>> it seems like gs has become de-niced down to turtle speed, or something
>>>>>
>>>>>
>>>>> the print speed is normal if i dont use ghostscript or apsfilter. and if i
>>>>> do all the apsfilter stuff by hand it is still insanely slow, so the
>>>>> problem appears to be a gs/lpd hose up?
>>>>
>>>> What are you printing?  I don't know the bj200ex (bubble jet?), but if
>>>> you're printing complicated pictures, it could be that the printer is
>>>> taking that long to accept all the data you're sending it.  That's
>>>> particularly true for LaserJet 1 emulation.
>>>>
>>>> A couple of things to try:
>>>>
>>>> 1.  Convert to memory (i.e. just make an image for the printer) and
>>>>     see how long that takes.
>>>
>>>
>>> yah, i forgot to mention that in my first mail....i had actually
>>> converted the file 'by hand' via invoking ghostscript to just convert the
>>> file. that happens lickety split. actually getting the file printed is
>>> what takes so long.
>>
>> OK.  Printing the file has nothing to do with ghostscript.  I think
>> this has just shown that ghostscript is not the culprit.
>>
>>>> 2.  Convert a simple printed text.
>>>
>>> oh, epic bummer. :-( this *is* a text file. a 3 line .rhosts file.
>>
>> On two pages?
>>
>>> and it takes an hour to print. lpd sends the head across once every 8
>>> minutes or so on a single pass. this is pretty time consuming.
>>>
>>> this hardware setup has run with gs for a couple years now, this is sort
>>> of surprising.
>>
>> That's a good piece of information.  I suspect you might be running
>> into problems with interrupts.  If the line printer driver doesn't get
>> any interrupts, it transfers about one character per second.  That
>> sounds like what's happening to you.
>>
>> Before you go chasing the wrong problem, try this:
>>
>>  # lptcontrol -p
>>
>> If you're not using /dev/lpt0, use the -u option to describe which
>> unit *number* (1 or 2) you are using.  See the man page for further
>> details.
>>
>> This will turn the printer port on in polled mode.  The result should
>> be much faster if the interrupts are the problem.
>
> lptcontrol -p did the trick. i am putting it into my rc.local.
> 
> tnx mucho!

Well, that's only the first step.  This means that you have an
interrupt conflict somewhere.  You really should find out what it is.
There's a good chance that you have another device on irq 7 which is
also not working right.

> (note the subject line: this will get this searchable in the archive) 

Thanks!
Greg

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980330132918.31846>