[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lp0 on fire - escputil anyone?



On Wed, Apr 28, 2004 at 04:29:31PM +1000, Tim Connors wrote:
> Richard Lyons <richard@the-place.net> said on Wed, 28 Apr 2004 01:26:35 +0200:
> > On Tuesday 27 April 2004 18:37, Tim Connors wrote:
> > > Richard Lyons <richard@the-place.net> said on Tue, 27 Apr 2004 
> > 17:12:09 +0200:
> > [...]
> > > > Back in command line, everything except ink level seems to work.
> > > > 'escputil -i' says it needs a raw device, and 'escputil -i -r
> > > > /dev/lp0' says 'Cannot read from /dev/lp0: Invalid argument' --
> > > > same as GUI.
> > [...]
> > > You need to set up bidirectional communication on your parallel port
> > > - I think it is a kernel compile option (my old crappy bios also has
> > > several options on the parallel port question, one of which is the
> > > bidirectional option -- try those).
> > 
> > I hadn't thought of the bios.  I'll look tomorrow.  Thanks
> 
> I don't promise anyhting - Linux usually ignores the BIOS (but maybe
> the BIOS sets up the ports, and Linux wont reset them later, using the
> defaults).
> 
> Now that I look closer, I don't see anything in my config (such as
> options in my modutils directory) that would be setting bidirectional
> communication...

Are you speaking of the CONFIG_PARPORT_1284 option (for EPP, ECP and
status readback)?  I think it is used if the kernel is compiled and the
device supports it.

> 
> -- 
> TimC -- http://astronomy.swin.edu.au/staff/tconnors/
> FORTRAN is a good example of a language which is easier to parse
> using ad hoc techniques.                -- D. Gries
> 

-- 
Chris Harris <charris@rtcmarketing.com>
-------------------------------------------
GNU/Linux --- The best things in life are free.



Reply to: