From owner-freebsd-questions@FreeBSD.ORG Mon Sep 1 16:21:29 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 47E3E16A4BF for ; Mon, 1 Sep 2003 16:21:29 -0700 (PDT) Received: from ms-smtp-01.tampabay.rr.com (ms-smtp-01.tampabay.rr.com [65.32.1.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 501FB43FBF for ; Mon, 1 Sep 2003 16:21:28 -0700 (PDT) (envelope-from tbstep@tampabay.rr.com) Received: from 2416462hfc204.tampabay.rr.com (2416462hfc204.tampabay.rr.com [24.164.62.204])h81NLPS6028609 for ; Mon, 1 Sep 2003 19:21:27 -0400 (EDT) From: Todd Stephens To: questions@freebsd.org Date: Mon, 1 Sep 2003 19:16:59 -0400 User-Agent: KMail/1.5.3 References: <200309011743.18110.tbstep@tampabay.rr.com> In-Reply-To: <200309011743.18110.tbstep@tampabay.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309011916.59592.tbstep@tampabay.rr.com> Subject: Re: CUPS, foomatic-rip, 4.8 RELEASE (was: How to get CUPS to work) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 23:21:29 -0000 On Monday 01 September 2003 05:43 pm, Todd Stephens wrote: > I have been trying to get this setup to work as it does on my Linux > box. Has anyone gotten CUPS working using the foomatic-rip/gimp-print > method outlined on Linuxprinting.org? I have an Epson Stylus C82 at > /dev/lpt0. > > Everything seems to working properly with CUPS now; I have the CUPS > scheduler running, the printer is configured, but when I go to print > anything, I get the following message: > #lp -d EpsonC82 /etc/motd > request id is EpsonC82-4 (1 file(s)) > > Then nothing ever prints. I think CUPS is configured properly or I > would not have gotten that far, but maybe GS or gimp-print is not. > Does anyone have any experience with this? Looks like I got it. I guess it was the foomatic-rip that was breaking it. I installed the printer again using a different driver (one that for some reason did not show up the first time I tried) and it works now. -- Todd Stephens