From owner-freebsd-questions@FreeBSD.ORG Tue Feb 7 01:49:07 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20BBB1065672 for ; Tue, 7 Feb 2012 01:49:07 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id BBBD18FC08 for ; Tue, 7 Feb 2012 01:49:06 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id B4EFA5C28; Tue, 7 Feb 2012 12:01:40 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id DBAD45C21; Tue, 7 Feb 2012 12:01:39 +1000 (EST) Message-ID: <4F308202.40605@herveybayaustralia.com.au> Date: Tue, 07 Feb 2012 11:44:34 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: jerry , "freebsd-questions@freebsd.org" References: <20120206163249.7d35337d@scorpio> In-Reply-To: <20120206163249.7d35337d@scorpio> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Debug Brother MFC-9560CDW failure to print X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "freebsd-questions@freebsd.org" List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2012 01:49:07 -0000 On 02/07/12 07:32, Jerry wrote: > OK Rock, if you think you can debug what is happening here, be my > guest. As shown in the subject line, this is a Brother MFC-9560CDW > printer. It works perfectly from Windows. Under FreeBSD, no so much. > When configured via CUPS 1.5.0, it will print a perfect test page. Now, > when I invoke the printer from an applications, only a blank page is > ejected. Most applications, offer both an LPR option as well as the > print to printer option. If I choose the LPR option, the document is > printed correctly. This is also true from the command line. > > I either print to LPR or I use Windows to print the document. I have > attached the PPD file along with a lot of other information. It is the > latest one from Brother that is used on Windows. There is no native PPD > file available for FreeBSD. However, in the past I have tried Linux PPDs > that worked fine on Linux but failed on FreeBSD. What I fail to > understand is why it is printing via LPR correctly but not via CUPS > although the CUPS test page does print correctly. When you say the test page prints correctly, is that the cups test page or the test page out of the printer? Put it this way: does it say "cups" on the page printed? Have you tried using foomatic? From what I read you could use pxlcolor filter. As I also understand it, using a windows ppd on anything other than windows (unless the manufacturer possibly made the programs with the same name- which is virtually never) will never work. You may _possibly_ have some success with Linux, but not likely. And your best bet is to forget the manufacturers stupid proprietary printer languages and stick with standards; ie. PCL, Postscript (which specifically is cups native language). If you need better quality (for, say, photos), then use gutenprint. Bottom line: I think you're chasing the wrong dog. I don't think it knows what you're talking about using BR-script3 and barfs. Switch to PCL6 and it will work I'm pretty sure. And ppd's won't mix and match- ppd's tell cups what to do, and cups then follows the scripts and spits the output; if it doesn't know what the scripts are it will not know what to do, and so far (I'm still going through it all) it looks like it is just sending something the printer has no idea at all what to do with and just spits paper out anyway.