[lkml]   [1996]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Printer on fire - I feel like an idiot

> (Marko Siladin) wrote on 18.11.96 in <>:
> > > Seriously, it's for unknown errors - off line is reported when the
> > > printer is off-line, out of paper is reported when the printer is out
> > > of paper, on fire is reported when the kernel doesn't know.
I've had a Panasonic and a couple Epson(!) printers, and never has a Linux
kernel reported offline as anything other than "on fire". Repeatedly
"on fire". Spamming-the-logfile-repeatedly "on fire".

> > But the problem is that my printer was - off-line and that the driver
> > did not detect that. Now I understand that there are many printers out
> In that case, the best explanation is probably that either your printer
> does something wrong with the signals, or your printer cable is not quite
> wired right.
Two different cables, though both are generic-cheapo.

> There *is* a definition on how to handle the different signals on that
> parallel port. All parties should conform to it, or confusion will result
> - as happened in your case.
Perhaps. But then again, there are "definitions" (such as PostScript) which
are incomplete or inaccurate without reading between the lines and knowing
what really happens...

Does anyone get an "offline" status (presumably from lpq or lpc stat after
the printer's been offline when lpd wanted to feed it something) from a
printer which is merely offline, without kernel patches?


Disclaimer: Do not taunt Happy Fun God.

 \ /
  Last update: 2005-03-22 13:38    [W:0.035 / U:1.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site