From: Gene Heskett <gene.heskett@verizon.net>
To: linux-usb-devel@lists.sourceforge.net, <linux-kernel@vger.kernel.org>
Subject: usblp suddenly has mental problems
Date: Fri, 15 Aug 2003 19:45:33 -0400 [thread overview]
Message-ID: <200308151945.33976.gene.heskett@verizon.net> (raw)
Greetings;
This is regardless of the kernel booted to. I've now tried
2.4.22-rc2, 2.4.21, and 2.4.20. And we all know that 2.6.0-test3-mm2
is still broken.
Summary:
Cups from mozilla's accessing its web page (localhost:631) can print a
test page just fine to either printer. I've got 2 Epson usb printers
plugged in, really I do!
*Any* other attempt to get ink on the paper, regardless of the method,
down to and including 'lpr filename', gets me about the right amount
of paper spit out for the job, but instead of the text, it is covered
from bleed to bleed in all 4 sides with a flat, even medium grey,
about twice as bright as a kodak 18% card. I've now got about 35
such sheets in the bin from trying to print a letter, composed
originally in kwrite. The first attempt from the kwrite print menu
worked, but even that hasn't worked in about an hour now. But the
cups test page is still fine.
ATM I'm back on a 2.4.2-rc2 boot, the printer has been turned off to
recycle it several times without effecting this, and I'm out of hair.
Hell, I've even re-installed cups-1.1.19! I eventually sent the
letter off by email, which will not be near as effective as ink.
This lashup has worked flawlessly for several months.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
reply other threads:[~2003-08-15 23:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308151945.33976.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).