From owner-freebsd-questions@FreeBSD.ORG Wed Jun 18 08:39:03 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37F5D37B407; Wed, 18 Jun 2003 08:39:03 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 739F243F3F; Wed, 18 Jun 2003 08:39:01 -0700 (PDT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) by srv1.cosmo-project.de (8.12.9/8.12.9) with ESMTP id h5IFcvhR030187 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Wed, 18 Jun 2003 17:38:59 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.9/8.12.9) with ESMTP id h5IFcuRp099465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Jun 2003 17:38:56 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.9/8.12.9) with ESMTP id h5IFctoT006900; Wed, 18 Jun 2003 17:38:55 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.9/8.12.9/Submit) id h5IFcsb3006899; Wed, 18 Jun 2003 17:38:54 +0200 (CEST) Date: Wed, 18 Jun 2003 17:38:54 +0200 From: Bernd Walter To: "Thomas T. Veldhouse" Message-ID: <20030618153853.GO3626@cicely12.cicely.de> References: <00c201c3359f$016f4f10$d037630a@dh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00c201c3359f$016f4f10$d037630a@dh.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.1-CURRENT alpha User-Agent: Mutt/1.5.4i cc: FreeBSD-Current cc: FreeBSD-Questions Subject: Re: Problem with USB ulpt0 and CUPS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 15:39:03 -0000 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