Printing to a network photosmart printer
Louis LeBlanc
freebsd at keyslapper.org
Tue Jun 8 21:15:16 PDT 2004
On 06/08/04 05:46 PM, Warren Block sat at the `puter and typed:
> On Tue, 8 Jun 2004, Louis LeBlanc wrote:
>
> >> See /usr/ports/print/hpijs.
> >
> > This certainly claims to work. I'm not understanding something
> > though. I'm trying to set it up through /etc/printcap as described,
> > but I still get the same problem after restarting lpd.
> >
> > I've downloaded the ppd, done the edits as recommended, and the
> > /etc/printcap entry is as follows:
> >
> >
> > Here's where I'm not sure: The command I added to the ppd file is:
> > *FoomaticRIPPostPipe: "| rlpr -Plp at printer"
> >
> > Now, I changed this under the assumption that the queue on the printer
> > is named lp. The machine is reachable (and pingable) at the dns name
> > "printer" so I'm sure that part is correct.
>
> HP JetDirects use "raw" for the queue name. Here is your printcap with
> some suggested changes:
>
> > lp|HP PSC 2510:\
> :lp=:\
> > :rm=printer:\
> :rp=raw:\
> > :if=/usr/local/bin/foomatic-rip:\
> > :af=/usr/local/etc/cups/ppd/HP-PSC_2500-hpijs.ppd:\
> > :sd=/var/spool/lpd/lp:\
> :mx#0:\
> > :sh:
>
> (Your if= and af= might be wrong; don't know.)
Thank you *very* much for your help Warren. It turned out something
was still wrong. I tried the CUPS install, and apparently found
something right, because I managed to get a test page printed from the
web interface to CUPS. Looked pretty darn good actually.
The printcap file was automatically generated from the web management
input (http://localhost:631) which was pretty easy. The only thing in
the printcap other than comments was
lp|lp:rm=keyslapper.org:rp=lp:
Once I got cups-lpr installed, it works fine. Now the tricky part is
remembering the path to the cups version. I can live with that.
Thanks again.
Lou
--
Louis LeBlanc leblanc at keyslapper.org
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org Ô¿Ô¬
Horner's Five Thumb Postulate:
Experience varies directly with equipment ruined.
More information about the freebsd-questions
mailing list