Date: Wed, 18 Jun 2003 17:38:54 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: "Thomas T. Veldhouse" <veldy@veldy.net> Cc: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: Problem with USB ulpt0 and CUPS Message-ID: <20030618153853.GO3626@cicely12.cicely.de> In-Reply-To: <00c201c3359f$016f4f10$d037630a@dh.com> References: <00c201c3359f$016f4f10$d037630a@dh.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 18, 2003 at 08:39:12AM -0500, Thomas T. Veldhouse wrote: > I posted this in April and received no response. However, this has been an > ongoing issue since at least 2001 (where I found the first reference to this > trouble via Google). > > The problem seems to be that the FreeBSD USB LPT driver (even with no-reset) > is somehow dropping the first bits of the data stream, causing a page full > of trash to be printed prior to the actual print job. I have no verified > this problem with 5.1-RELEASE as well. > > ---- > > I have a machine that has been serving as a print server. That machine was > running CUPS and SAMBA over Linux. Now, it is running FreeBSD > 5.0-RELEASE-p7 with CUPS and SAMBA. I have a Lexmark Optra 312 laser > printer hooked up to the usb port, ulpt0 (no reset). When it was running > linux, everything ran perfectly. I allow the Windows client machines to use > their print drivers and send a raw stream through samba to cups for > printing. This configuration has worked fine. However, for reasons of my > own, I have put FreeBSD 5.0 on this machine. The same software > configuration exists for printing. Now, when I print most pages, I get an > extra page prefixing the job with two or three lines of printer commands > (i.e. resolution = 600, @PCL, etc). This seems to be caused by the FreeBSD > usb printer driver dropping a couple of characters at the beginning of the > command stream. This used to happen to me with FreeBSD 4.6 as well, which > is why that machine was running Linux in the first place. Has anybody seen > this strange behavior and is there a known fix for it? I can reproduce it localy with -current, but have no fix. I thought that I had found the reason a few days ago, but murphy teached me better :( There is a bug in signal handling, but that's not our problem here. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030618153853.GO3626>