Re: LP0 on fire
Verifique mau contato no cabo ou teste com outro cabo. Fabiano. Em 29/08/05, Juaci Carvalho[EMAIL PROTECTED] escreveu: Ola pessoal... Instalei debian no meu servidor, fiz todas as configuracoes, mas quando fui imprimir deu a mensagem LP0 on fire. Alguem sabe dizer o que pode estar acontecendo? Grato pela atenção. Juaci Carvalho. ___ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Abraços, Fabiano
LP0 on fire
Ola pessoal... Instalei debian no meu servidor, fiz todas as configuracoes, mas quando fui imprimir deu a mensagem LP0 on fire. Alguem sabe dizer o que pode estar acontecendo? Grato pela atenção. Juaci Carvalho. ___ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lp0 on fire - Epson Stylus Color 480 with Woody and Knoppix and CUPS
Hello folks. My logs are showing lp0 to be on fire. This is an Epson Stylus Color 480. It behaved oddly last time I printed something - a few weeks back. It was a fairly large print job, which it refused to touch only to print the lot out the next time I booted. Thereafter it refused to print anything. I'm using Woody. After googling lots and playing some, and getting nowhere, I decided to do a knoppix hd install on a spare hard drive, to see if I could rule a printer hardware problem out. Sadly the hardware problem possibility now seems to be ruled in, as the logs in the knoppix install agree that lp0 is on fire. I left the printer disconnected for a while to see if the problem would clear, but it didn't. I'll perhaps leave the cable out overnight, just on the off-chance. When I fiddle with the CUPS admin routine through my browser I can sometimes get the printer to clear its throat and shuffle its shoulders (which it also still does when I switch it on) but then it falls silent. It won't print anything. The jobs are queued, and the parallel port claims to be busy (trying again in thirty seconds). When I cancel the jobs and switch the printer off and on through admin the printer is shown to be idle - but it still won't print. tunelp /dev/lp0 gives the IRQ as -1, which seemed odd to me, but as polling is being used perhaps this is right? The cable looks okay. Both ends are attached to something, one of which is the printer. I wondered initially whether it was perhaps simply out of ink, but Escputil won't run - when I try to do anything at all, declaring the raw device, Escputil hangs. Somewhere I came across ps aux | grep root and then kill -9 anything odd and printer-related: there was stuff to kill, but it never solved the problem. So: Does the fact that the problem occurs with two different installs mean that it is definitely hardware related, or is there another possibility? I wish I had another machine or another printer or even another printer cable so that I could narrow things down a bit. I'll probably end up buying a cable then a printer and then discover the motherboard is beginning to fail or something. I'm using the latest 2.4.18-1-k6 kernel image on the Woody, although I doubt it matters. Any advice please? lpinfo -v -l gives the following: network socket network http network ipp network lpd direct epson:/dev/lp0 direct parallel:/dev/lp0 serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS1?baud=115200 serial serial:/dev/ttyS2?baud=115200 serial serial:/dev/ttyS3?baud=115200 direct usb:/dev/usb/lp0 direct usb:/dev/usb/lp1 direct usb:/dev/usb/lp2 direct usb:/dev/usb/lp3 direct usb:/dev/usb/lp4 direct usb:/dev/usb/lp5 direct usb:/dev/usb/lp6 direct usb:/dev/usb/lp7 direct usb:/dev/usb/lp8 direct usb:/dev/usb/lp9 direct usb:/dev/usb/lp10 direct usb:/dev/usb/lp11 direct usb:/dev/usb/lp12 direct usb:/dev/usb/lp13 direct usb:/dev/usb/lp14 direct usb:/dev/usb/lp15 Geoff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
On Fri, Mar 07, 2003 at 05:20:09PM +1100, John Griffiths wrote: Yes, you are using a retarded email client and inserting this huge disclaimer bullshit which is all one one line. You asked for that one :-) Wow, you're in a charming mood today dude. Well, it's not particularly nice, but those stupid email disclaimer things are just fucking annoying. It doesn't even have a proper '^-- $' sig delimiter on it, so I can't have mutt simply hide it for me. I'm sure I could come up with a procmail hack that would strip it, but really, should I have to? -rob (who has better things to be doing than ranting on d-u;) -- Rob Weir [EMAIL PROTECTED]http://ertius.org/ pgp0.pgp Description: PGP signature
Re: kernel: lp0 on fire ????
On Thu, Mar 06, 2003 at 07:06:04PM +, Shri Shrikumar wrote: Mar 6 14:24:35 server kernel: lp0 on fire What does this mean - I can confirm that there is no actual fire as of yet but it does have me worried - any thoughts ? You just became the umpteenth victim of an extremely long running linux joke. When your printer is turned off, and the computer tries to check the port that printer is attached to, it reads a normally impossible state (I think it's ready and No paper simultaneously). Since it's not possible to be ready and not have paper if you're a printer, the kernel spits back an equally unlikely scenario (the printer's screaming, it must be on fire). You're in on the joke now, enjoy it. -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system pgp0.pgp Description: PGP signature
Re: kernel: lp0 on fire ????
On Thursday 06 March 2003 11:02 pm, Rob Weir wrote: On Fri, Mar 07, 2003 at 05:20:09PM +1100, John Griffiths wrote: Yes, you are using a retarded email client and inserting this huge disclaimer bullshit which is all one one line. You asked for that one :-) Wow, you're in a charming mood today dude. Well, it's not particularly nice, but those stupid email disclaimer things are just fucking annoying. It doesn't even have a proper '^-- $' sig delimiter on it, so I can't have mutt simply hide it for me. I'm sure I could come up with a procmail hack that would strip it, but really, should I have to? I agree they are annoying and useless. Anyone who sends sensitive information in email deserves the consquences if it gets intercepted. Encryption? Whut's that? However yelling at the sender does no good, they have no control over it. The disclaimers are appended at the server. -- ~ Carla Schroder www.tuxcomputing.com this message brought to you by Libranet 2.7 and Kmail ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
On Thursday 06 March 2003 23:16, Mark L. Kahnt wrote: And if there is lots of heat, light and smoke, get the fire extinguisher - it is not *totally* impossible for printers to catch fire. Old, very fast line printers could catch fire if the paper jamed while the printer still wanted to spit out paper. If this is the reason for implementation is another case. -- Svenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
On Thursday 06 March 2003 20:57, Carla Schroder wrote: A Google search for lp0 on fire turns up several hits: http://216.239.37.100/search?q=cache:bcjVD8F2zJUC:www.kalamazoolinux.org/ma ilarchive/0006/msg00188.html+lp0+on+firehl=enie=UTF-8 Apparently this is an old and honorable Unix humor tradition. Well, according to this orther google search : http://groups.google.com/groups?hl=enlr=ie=UTF-8selm=linux.kernel.200208092200.RAA34736%40tomcat.admin.navo.hpc.milrnum=5 it is more likely to be here for a historical than for a funny reason. Must have been great to work with computers back then :-). Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
On Fri, 2003-03-07 at 13:04, Svenn Are Bjerkem wrote: On Thursday 06 March 2003 23:16, Mark L. Kahnt wrote: And if there is lots of heat, light and smoke, get the fire extinguisher - it is not *totally* impossible for printers to catch fire. Old, very fast line printers could catch fire if the paper jamed while the printer still wanted to spit out paper. If this is the reason for implementation is another case. -- Svenn I haven't seen the fire, but I have seen burnt printers from problems like that, or early laser printers where the fusing element picked up loose dust and not totally cleared jammed papers. Hey - modern life - cell phone in a holder on one hip, fire extinguisher on the other ;) -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: kernel: lp0 on fire ????
On Thursday 06 March 2003 11:06 am, Shri Shrikumar wrote: Hi All, I got this very interesting logcheck email with this line Mar 6 14:24:35 server kernel: lp0 on fire What does this mean - I can confirm that there is no actual fire as of yet but it does have me worried - any thoughts ? Shri A Google search for lp0 on fire turns up several hits: http://216.239.37.100/search?q=cache:bcjVD8F2zJUC:www.kalamazoolinux.org/mailarchive/0006/msg00188.html+lp0+on+firehl=enie=UTF-8 Apparently this is an old and honorable Unix humor tradition. `lp0 on fire' is a age-old UNIX joke. It was in the earliest kernels of UNIX. Linux is just trying to conform ;) 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. -- ~ Carla Schroder www.tuxcomputing.com this message brought to you by Libranet 2.7 and Kmail ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
Quoting Shri Shrikumar [EMAIL PROTECTED]: Hi All, I got this very interesting logcheck email with this line Mar 6 14:24:35 server kernel: lp0 on fire What does this mean - I can confirm that there is no actual fire as of yet but it does have me worried - any thoughts ? Ahh, geek humor. It means that the parallel port status bits were set to a pattern that the printer driver doesn't understand. If it is was momentary, ignore. If there was a real problem, fix it and ignore. If you have something besides a printer on the parallel port, you have a configuration problem. Perhaps alias lp0 off in /etc/modules.conf or somewhere in the /etc/modutils/ tree. HTH, Jeffrey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: kernel: lp0 on fire ????
On Thu, 2003-03-06 at 22:10, Narins, Josh wrote: Quoting Shri Shrikumar [EMAIL PROTECTED]: Hi All, I got this very interesting logcheck email with this line Mar 6 14:24:35 server kernel: lp0 on fire What does this mean - I can confirm that there is no actual fire as of yet but it does have me worried - any thoughts ? Ahh, geek humor. It means that the parallel port status bits were set to a pattern that the printer driver doesn't understand. If it is was momentary, ignore. If there was a real problem, fix it and ignore. If you have something besides a printer on the parallel port, you have a configuration problem. Perhaps alias lp0 off in /etc/modules.conf or somewhere in the /etc/modutils/ tree. I set my printer ablaze, and did not get this message. Am I doing something wrong? I guess you forgot to install the firealarm package. Shri -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
On Thu, Mar 06, 2003 at 05:10:13PM -0500, Narins, Josh wrote: I set my printer ablaze, and did not get this message. Am I doing something wrong? yes: arson hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
Yes, you are using a retarded email client and inserting this huge disclaimer bullshit which is all one one line. You asked for that one :-) Wow, you're in a charming mood today dude. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: lp0 on fire ????
On Fri, Mar 07, 2003 at 05:20:09PM +1100, John Griffiths wrote: Yes, you are using a retarded email client and inserting this huge disclaimer bullshit which is all one one line. You asked for that one :-) Wow, you're in a charming mood today dude. I see your mailer does not respect Mail-Followup-To: ... apparently it strips emoticons as well? Note for the terminally clueless: IT WAS A JOKE. THE POST IT REPLIED TO WAS A JOKE. HUMOR CAN BE FUN; TRY IT OUT. -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] Avoid gunfire in the bathroom tonight. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lp0 on fire
David Raeker-Jordan [EMAIL PROTECTED] wrote: I was printing a rather large label job from a local debian machine to a remote debian machine that has an old dot matrix printer attached to it. After about 10 minutes of printing to the remote printer, the message lp0 on fire popped up on the remote machine's terminal and the printer stopped for a minute or so. The printer then continued, but the lp0 on fire message keeps coming up every several minutes along with the corresponding pause in printing. I did not find a similar message on the local machine. Aha, haven't seen that error message for a while :) Install doc-linux-html or doc-linux-text and have a look at the Linux FAQ for this one. Here's a quote: 8.3 lp1 on fire This is a joke/traditional error message indicating that some sort of error is being reported by your printer, but that the error status isn't a valid one. It may be that you have some kind of I/O or IRQ conflict - check your cards' settings. Some people report that they get this message when their printer is switched off. Hopefully it isn't really on fire ... In newer kernels this message reads lp1 reported invalid error status (on fire, eh?). Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: lp0 on fire
On Fri, Jun 15, 2001 at 05:13:13PM +0100, Colin Watson wrote: In newer kernels this message reads lp1 reported invalid error status (on fire, eh?). that should read 'older newer kernels' or something. It means 2.2.x. (in 2.4.x people returned to sanity and put it back) -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: I suggest a new strategy, Artoo: let the Wookie win. -- C3P0 pgpCUFEuQ4Y29.pgp Description: PGP signature
Re: lp0 on fire
John R Lenton [EMAIL PROTECTED] wrote: On Fri, Jun 15, 2001 at 05:13:13PM +0100, Colin Watson wrote: In newer kernels this message reads lp1 reported invalid error status (on fire, eh?). that should read 'older newer kernels' or something. It means 2.2.x. (in 2.4.x people returned to sanity and put it back) Do let the FAQ maintainer know, then. According to the feedback section, his address is Robert Kiesling [EMAIL PROTECTED]. -- Colin Watson [EMAIL PROTECTED]
Re: lp0 on fire
On Sat, Jun 16, 2001 at 10:41:07AM +0100, Colin Watson wrote: Do let the FAQ maintainer know, then. According to the feedback section, his address is Robert Kiesling [EMAIL PROTECTED]. I'll wait for 2.4.7 :/ -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: It is through symbols that man consciously or unconsciously lives, works and has his being. -- Thomas Carlyle pgpvBMJYs3rZb.pgp Description: PGP signature
lp0 on fire
I was printing a rather large label job from a local debian machine to a remote debian machine that has an old dot matrix printer attached to it. After about 10 minutes of printing to the remote printer, the message lp0 on fire popped up on the remote machine's terminal and the printer stopped for a minute or so. The printer then continued, but the lp0 on fire message keeps coming up every several minutes along with the corresponding pause in printing. I did not find a similar message on the local machine. I do not recall this message when I would attach the dot matrix printer to the local debian machine and use the printer as a local printer. Any ideas what is happening? BTW, the print job came out fine. -- David Raeker-Jordan mailto:[EMAIL PROTECTED] Harrisburg, PA, USA
Re: lp0 on fire
* David Raeker-Jordan ([EMAIL PROTECTED]) spake thusly: I was printing a rather large label job from a local debian machine to a remote debian machine that has an old dot matrix printer attached to it. After about 10 minutes of printing to the remote printer, the message lp0 on fire popped up on the remote machine's terminal and the printer stopped for a minute or so. The printer then continued, but the lp0 on fire message keeps coming up every several minutes along with the corresponding pause in printing. I did not find a similar message on the local machine. I do not recall this message when I would attach the dot matrix printer to the local debian machine and use the printer as a local printer. Any ideas what is happening? BTW, the print job came out fine. There used to be [very] big and [very] noisy line printers that used 132-column tractor-fed paper. They usually lived in a separate room, together with stacks of paper. Sometimes paper would get stuck, printer would be hitting the same spot, heating it up until it caught fire. That's where the error message comes from. It means there's some kind of printer error, but since printers usually aren't smart enough to report back what exactly went wrong, it doesn't know WTF happened. Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) http://www.bmrb.wisc.edu/descript/gpgkey.dmaziuk.ascii -- GnuPG 1.0.4 public key I'm going to exit now since you don't want me to replace the printcap. If you change your mind later, run -- magicfilter config script
Re: lp0 on fire
On Fri, 15 Jun 2001 11:51:57 EDT, David wrote: I was printing a rather large label job from a local debian machine to a remote debian machine that has an old dot matrix printer attached to it. After about 10 minutes of printing to the remote printer, the message lp0 on fire popped up on the remote machine's terminal and the printer stopped for a minute or so. The printer then continued, but the lp0 on fire message keeps coming up every several minutes along with the corresponding pause in printing. I did not find a similar message on the local machine. I do not recall this message when I would attach the dot matrix printer to the local debian machine and use the printer as a local printer. Any ideas what is happening? BTW, the print job came out fine. I get this message whenever my Epson Stylus Pro 850 has any error, such as out of ink, out of paper, overheating, etc. My other printer, an Epson dot-matrix printer causes these messages on very hot days and during very big print runs, but seldom fails to complete the print job. I assume that lp0 on fire is how lpd reports any error message from the printer. I could be wrong though - anyone got more/better info? It does get one's attention quite efficiently. --ptw It sure does get ones attention though. -- Paul T. Wright [EMAIL PROTECTED] -currently seeking employment-
