public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems with my parport (and printer)
Date: Sun, 28 Mar 2004 17:51:34 +0200	[thread overview]
Message-ID: <20040328155134.GG27362@lug-owl.de> (raw)
In-Reply-To: <20040325115131.GA12195@DervishD>

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

On Thu, 2004-03-25 12:51:31 +0100, DervishD <raul@pleyades.net>
wrote in message <20040325115131.GA12195@DervishD>:
>     Hi all :)
> 
>     I have a printer connected thru my parallel port, supported in
> the kernel by parport+parport_pc+lp:
> 
> kernel: parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
> kernel: parport0: Printer, Lexmark International Lexmark Optra E312
> kernel: lp0: using parport0 (interrupt-driven).
> kernel: lp0: console ready
> 
>     It works ok, BTW... The problem is that, when the printer is
> switched of and I try to print something, the print command just
> blocks, no error, no messages, nothing. I use a shell function to

First of all, if you want to do normal printing, you shouldn't switch on
LP console. From there on, all kernel debug output (as seen in
/var/log/kern.log and outputted with "dmesg") would be sent to the
printer, what isn't exactly what you want to have.

>     Why this operation doesn't fail? IMHO, it should fail with
> ENODEV, because parport can work (the parallel port is there...), but
> lp shouldn't (the printer is switched off...).

Another gotcha may be that your printer doesn't easily accept commands.
Many printers don't do that nowadays. Some are dumb GDI-Printerts
(Windows-only, that is...), some nees specific wake-up sequences.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-03-28 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 11:51 Problems with my parport (and printer) DervishD
2004-03-28 15:51 ` Jan-Benedict Glaw [this message]
2004-03-28 18:09   ` DervishD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040328155134.GG27362@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox