From: Andrew Walrond <andrew@walrond.org>
To: DervishD <raul@pleyades.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Weird problems with printer using USB
Date: Mon, 5 Jan 2004 21:25:23 +0000 [thread overview]
Message-ID: <200401052125.23985.andrew@walrond.org> (raw)
In-Reply-To: <20040105202936.GE15884@DervishD>
On Monday 05 Jan 2004 8:29 pm, DervishD wrote:
>
> The cable is OK, I've tested with two cables and with a USB
> memory stick and all works ok. Seems like the printer doesn't like to
> have both the parallel cable and the USB cable plugged at the same
> time, but sometimes it worked, so... The final cause seems to be the
> size of the file I want to print. The larger, the more chances to
> fail. I'll try a new cable tomorrow, probably, but I'll give a newer
> kernel a try.
>
Well yes; both cables I tried worked fine with other devices, but with the
printer (Laserjet 2400) the attenuation was obviously too much. With a 4ft
cable, everything works fine.
Same error messages, and same symtoms, in that the bigger the file, the more
likely the problem was to occur. Once the error had happened, the printer
needed to be power-cycled before more prints would work.
I spent a week before xmas trying all latest kernels and Gregs latest usb
patches, to no avail.
Let me know how it turns out :)
Andrew Walrond
next prev parent reply other threads:[~2004-01-05 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 19:24 Weird problems with printer using USB DervishD
2004-01-05 19:45 ` Greg KH
2004-01-05 20:25 ` DervishD
2004-01-06 14:01 ` Paulo Marques
2004-01-07 11:03 ` DervishD
2004-01-05 19:46 ` Martin Hicks
2004-01-05 20:27 ` DervishD
2004-01-05 19:50 ` Andrew Walrond
2004-01-05 20:29 ` DervishD
2004-01-05 21:25 ` Andrew Walrond [this message]
2004-01-07 11:02 ` DervishD
[not found] ` <mailman.1073332322.31520.linux-kernel2news@redhat.com>
2004-01-06 16:14 ` Pete Zaitcev
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=200401052125.23985.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@pleyades.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