From owner-freebsd-questions@FreeBSD.ORG Tue Apr 21 08:52:29 2009 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 3A35D106566B for ; Tue, 21 Apr 2009 08:52:29 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 977F48FC21 for ; Tue, 21 Apr 2009 08:52:28 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from vhoffman.lon.namesco.net (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.0) with ESMTP id n3L8rnTW099365 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 21 Apr 2009 09:53:50 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <49ED8949.3080102@unsane.co.uk> Date: Tue, 21 Apr 2009 09:52:25 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1 MIME-Version: 1.0 To: weif@weif.net References: <20090420145839.5D396A3DC7@maxine.cjones.org> <86fxg3gwny.fsf@nowhere.org> <20090420173603.8CF7EA3DC7@maxine.cjones.org> <9B2BDFC5F4D9083916FFE187@utd65257.utdallas.edu> <20090420192048.40290A3D2E@maxine.cjones.org> <62CFD48735EA944E20668C98@utd65257.utdallas.edu> <20090420223625.8847EA3DF2@maxine.cjones.org> In-Reply-To: <20090420223625.8847EA3DF2@maxine.cjones.org> X-Enigmail-Version: 0.96a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Paul Schmehl , freebsd-questions@freebsd.org Subject: Re: Can you ACTUALLY print from FreeBSD? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2009 08:52:29 -0000 On 20/4/09 23:36, Keith Seyffarth wrote: >> Googling that shows it to be a file shared with Windows boxes when you're >> running samba. I don't know if you set up samba or not, but I would ignore >> this error for now. It's likely unrelated to the printing problem that you're >> having. >> > > OK. Thanks. I guess. I was kind of hoping that figuring that out might > be the fix... > > >>>> Do you have the startup script: >>>> /usr/local/etc/rc.d/cupsd ? >>>> >>> yes >>> >>> >>>> If so, what is the output of /usr/local/etc/rc.d/cupsd status? >>>> >>> currently it's: >>> cupsd is running as pid 721. >>> >>> but I did start cups manually since my last reboot. >>> >>> >> Cupsd was started automatically on reboot by the script. So that part is >> working fine. >> > > after rebooting the machine, it's: > cupsd is not running. > > > > >> It appears the problem is the printer. Try changing the perms to 0777 for >> testing purposes. If you're able to print, the problem is permissions. You'll >> have to figure out what permissions you need to get it working. >> > > That doesn't help. I get the same behavior with the permissions set to > 0777. > > >> One person mentioned that you should be using the ugen device instead of >> /dev/ultp0. This thread might be relevant - >> http://foo2zjs.rkkda.com/forum/read.php?9,546,547 >> >> You might have to abandon using cupsd for this printer. >> > > Yeah. We may not be using this printer long anyway, since it is nearly > out of ink, and the ink will be $95. It would just be nice to be able > to demonstrate that printing is an option. > > Also, from what I've been seeing in my testing and so on since > Thursday, it looks like if you use CUPS at all, you can't use anything > else, since CUPS overwrites things like /etc/printcap with its own > settings frequently. And since I've been successfully using cups-pdf > for several months, I'd need a replacement for that. At least with > that, despite all the shortcomings of .pdf format, we can still get > stuff printed. Just not in our office. > > >> If so, this might be helpful: >> http://www.onlamp.com/pub/a/bsd/2004/07/08/FreeBSD_Basics.html?page=last >> > > I had read through that several times. It is one of several places > pointing out that the device has to be at ultp*, and if it's at ugen* > you likely have a problem... > > However the pkg-message for hplip says differently. I had to recompile without ulpt in the kernel to get my hp c3180 psc to work, but it prints (and scans) fine from freebsd now. read the output from pkg_info -xD hplip It has got full instructions on what needs doing. Recompiling the kernel isnt actually all that hard, and is detailed fully in the handbook. Actually to any devs who might be reading, is there any reason we have ulpt built in rather than as a module? Vince > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >