From: Greg KH <greg@kroah.com>
To: Daniel Robbins <drobbins@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-bk9 QA testing: firewire good, USB printing dead
Date: Fri, 27 Feb 2004 18:10:41 -0800 [thread overview]
Message-ID: <20040228021040.GA14836@kroah.com> (raw)
In-Reply-To: <1077933682.14653.23.camel@wave.gentoo.org>
On Fri, Feb 27, 2004 at 07:01:22PM -0700, Daniel Robbins wrote:
> However, 2.6.3-bk9's USB printing support appears to be dead. I can't
> get it to work reliably. Tested on Epson Stylus Photo 960 and a Brother
> Laser printer. catting files to /dev/usb/lp? tends to fail (process will
> get "stuck") and printer data stops flowing. This is on an Athlon XP
> (NForce2) system using the on-board USB. The official 2.6.3 release
> works fine. I'd expect these USB printing death symptoms to be easily
> reproducable on quite a few systems -- the problems hit me in the first
> few seconds of print testing. If they end up being more elusive, I can
> try to dig up more info for anyone who's interested in trying to isolate
> the problem.
Yes, I am. Do you get any error messages in your syslog when the
printer hangs?
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-28 2:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 2:01 2.6.3-bk9 QA testing: firewire good, USB printing dead Daniel Robbins
2004-02-28 2:10 ` Greg KH [this message]
2004-02-28 2:57 ` Daniel Robbins
2004-02-28 3:39 ` Kevin P. Fleming
2004-02-28 6:44 ` Greg KH
2004-02-28 21:22 ` Mike
2004-02-29 9:51 ` Jens Axboe
2004-03-01 7:43 ` [PATCH] " Barry K. Nathan
2004-03-01 8:02 ` Jens Axboe
2004-03-02 3:01 ` Mike
2004-03-02 13:09 ` Paulo Marques
2004-03-02 15:18 ` firewire good, USB printing fixed, CD-ROM block device IO errors near end of media Daniel Robbins
2004-03-02 19:26 ` [PATCH] Re: 2.6.3-bk9 QA testing: firewire good, USB printing dead Greg KH
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=20040228021040.GA14836@kroah.com \
--to=greg@kroah.com \
--cc=drobbins@gentoo.org \
--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