Re: printers

[Michael Ward Cole <colemw@home.com>]

Unfortunately,  I am not able to print a blessed thing.  I get device unknown on /dev/lp0, /dev/lp1 and /dev/lp2.  I have also tried the ttySn ports but that was on a 'wing and a prayer'.  I have tried echo "Hello "World" > /dev/lp0, lp1 and so on without success.  The problem then is in the device I would assume.  Or should I just not assume anything and try everything?  I don't care about the polling.  I just want little black dots on the white sheet of paper.  I have been working with an Epson Stylus Photo 750, a HP 695c and a Star NL-10(dmp).  I can't get any to work.   
Any thoughts and assistance would be helpfful.  
Thanks,
Michael

On Thu, Sep 20, 2001 at 09:38:51AM -0400, Stephen Gran wrote:
> Thus spake Michael Ward Cole:
> > Okay, Perhaps I need to reword this.  I am getting the instruction on bootup that my parports are identified as 0 and 1, but that I need to 'use procfs to enable interrupt-driven operation.'  I don't know what this means and really would appreciate someone directing me to some instructions on this matter.  Does it mean that I have to compile the kernel with this procfs.h included?  
> > Thanks,
> > Michael
> > 
> > 
> > On Wed, Sep 19, 2001 at 07:23:14AM -0400, Michael Ward Cole wrote:
> > > I have two parallel ports and have parport and parport-pc modules installed into linux 2.2.19pre17.  I get messages on boot up that the two ports are identified but it gives me an instruction to use procfs to enable interrupt-driven operation.  The only file procfs on my system is a header file.  What does this message mean and what am I suppose to do about it?  
> > > Thanks,
> > > Michael
> > > 
> As far as I can gather from your post, oyu're not having trouble
> printing, are you?  Interrupt-driven operation is something that some
> newer printers use for higher speeds.  Most older printers (and most new
> printers, AFAIK) use 'polling', a different method for the CPU to
> monitor the port.  It basicaly has to do with CPU usage and efficiency
> in making sure the right bits get to the right places.  If you're
> printing just fine, don't worry about it, IMHO.  If you've researched
> your printer, and it should be using interrupts, and you feel like
> recompiling your kernel to include procfs, go for it.  That is what the
> error message means.
> Good luck, 
> Steve
> 
> -- 
> :wq
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>