*BSD News Article 21017


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:5184 comp.os.386bsd.development:1217
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!pagesat!indirect.com!garbled
From: garbled@indirect.com (Tim Rightnour)
Subject: Re: Epson LQ printer - Can it be done?
Message-ID: <1993Sep17.212641.21561@indirect.com>
Organization: Internet Direct Inc. -- (602) 274-0100
References: <TONY.93Sep9182513@marge.apana.org.au> <1993Sep11.124630.22284@gmd.de> <279b1mINNjgb@bonnie.tcd-dresden.de>
Date: Fri, 17 Sep 1993 21:26:41 GMT
Lines: 29

>>|> It shows all the symptoms that I've seen discussed before: No port detected
>>|> unless the printer is unplugged (whether the printer is on or off), but \

>Please accept that this IS A BUG in *BSD, not in the cables. The bug has
>been introduced with pk 0.2.{3,4}. I can really exclude any other influences,
>since i've been working _all the time_ with my own (old) lp driver. The
>driver worked well till i upgraded to 0.2.4; the bundled lpt/lpa drivers
>generally fail to detect my printer. My lp driver sometimes fails to
>detect it. But, the more annoying thing: after the driver has detected
>a printer port, the system runs for some hours and then deselects the
>printer port. Yes, indeed, some{thing,one} is writing some byte to the
>printer port - it ain't the lp driver, though!
>
>I have no idea where to look for this...
>-- 

I kludged this bug by the following method.

a) unplug the printer from the PORT.  (the db25 at the card!)
b) reboot netbsd
c) login
d) plug in the printer (which should allready be on, and ready)
e) repeat for any time I wish to reboot.

I noticed that if you do not do this..  when booting, BSD does not
recognize the lpa0  and therefore the "device is not configured"