From: Patrick Dreker <patrick@dreker.de>
To: Tim Waugh <twaugh@redhat.com>,
Michael Ben-Gershon <mybg@netvision.net.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lpr to HP laserjet stalls
Date: Tue, 4 Sep 2001 02:56:56 +0200 [thread overview]
Message-ID: <E15e4WO-0007uH-00@wintermute> (raw)
In-Reply-To: <3B93E289.7F121DE9@netvision.net.il> <20010903221142.J20060@redhat.com>
In-Reply-To: <20010903221142.J20060@redhat.com>
Am Montag 03 September 2001 23:11 schrieb Tim Waugh:
> On Mon, Sep 03, 2001 at 11:05:29PM +0300, Michael Ben-Gershon wrote:
> > It is intermittent, but very frequent. It is difficult to print more
> > than about 10 sheets without it happening sometime.
>
> Take a look at Documentation/parport.txt: see the 'Troubleshooting'
> section.
I had the same problem here with my Epson Stylus Color 600. I did not matter
whether I sent the output directly to the printer (cat file.txt > /dev/lp0)
or used cups or lpd. It just stuck in random places. Fiddling with parport
settings did not change anything.
In debugging the problem I found out that if one attaches an strace to the
stuck output process (strace -p pid) the output continues. The strace always
consisted of either write or read calls (can't remember right now, though
write seems more logical) the first of which after attaching with strace was
a request for 8192 Bytes which returned short with usually some 100 bytes.
All folowing calls had the full 8192 requested Bytes as return value.
All of this vanished, when I replaced all occurrences of /dev/lp0 in my
printer configuration by /dev/par0. I has been working flawlessly since then.
I have changed quite a bit on my system since that time, but using
/dev/printers/0 under devfs also works fine here.
> Tim.
> */
--
Patrick Dreker
---------------------------------------------------------------------
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
Alan Cox on linux-kernel@vger.kernel.org
next prev parent reply other threads:[~2001-09-04 1:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 20:05 lpr to HP laserjet stalls Michael Ben-Gershon
2001-09-03 21:11 ` Tim Waugh
2001-09-04 0:20 ` Horst von Brand
2001-09-04 8:36 ` Tim Waugh
2001-09-04 0:56 ` Patrick Dreker [this message]
2001-09-04 8:50 ` Tim Waugh
2001-09-04 12:07 ` Patrick Dreker
2001-09-04 11:05 ` Michael Ben-Gershon
[not found] ` <3B94B4E7.701C76FA@netvision.net.il>
[not found] ` <20010904121523.Q20060@redhat.com>
2001-09-04 11:21 ` Michael Ben-Gershon
2001-09-04 11:27 ` Tim Waugh
2001-09-04 13:22 ` Michael Ben-Gershon
2001-09-04 13:27 ` Tim Waugh
2001-09-04 13:41 ` Michael Ben-Gershon
2001-09-04 13:48 ` Tim Waugh
2001-09-04 21:17 ` Michael Ben-Gershon
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=E15e4WO-0007uH-00@wintermute \
--to=patrick@dreker.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mybg@netvision.net.il \
--cc=twaugh@redhat.com \
/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