NSLU2-Linux
view · edit · print · history

HowTo.HPIJS History

Hide minor edits - Show changes to markup

December 13, 2013, at 04:37 AM by Benalua --
Changed line 99 from:

I've added my notes to the add a printer page but basically, I can only locally print with hpijs in conjunction with usblp since hplip is pretty much broken in terms of printing. It's still pretty good for scanning and status check. Ghostscript and foomatic-rip need to be fixed to be more optware compliant since a lot of things seem to refer to /usr still and this causes things not to work. You can edit /opt/bin/foomatic-rip to see what I mean. Also XPDF needs to be installed for adequate local printing and fixed. The generated PS files tend to scramble my printer. I actually had to download and build poppler instead to get things running.

to:

I've added my notes to the AddPrinter page but basically, I can only locally print with hpijs in conjunction with usblp since hplip is pretty much broken in terms of printing. It's still pretty good for scanning and status check. Ghostscript and foomatic-rip need to be fixed to be more optware compliant since a lot of things seem to refer to /usr still and this causes things not to work. You can edit /opt/bin/foomatic-rip to see what I mean. Also XPDF needs to be installed for adequate local printing and fixed. The generated PS files tend to scramble my printer. I actually had to download and build poppler instead to get things running.

December 13, 2013, at 04:34 AM by Benalua -- Added info to local printing and noted some optware deficiencies.
Changed lines 96-99 from:

Very helpful - seems to be working for me. I have just one question. I found the ppd for my specific printer (HP DeskJet? 5550) and I unpacked it and copied it to the appropriate models directory as instructed above. However, I'm not sure what I need to change to be able to use that as my default printer. The default hp990c seems to work OK so far, but I haven't tried printing anything terribly complex yet.

to:

Very helpful - seems to be working for me. I have just one question. I found the ppd for my specific printer (HP DeskJet? 5550) and I unpacked it and copied it to the appropriate models directory as instructed above. However, I'm not sure what I need to change to be able to use that as my default printer. The default hp990c seems to work OK so far, but I haven't tried printing anything terribly complex yet.


I've added my notes to the add a printer page but basically, I can only locally print with hpijs in conjunction with usblp since hplip is pretty much broken in terms of printing. It's still pretty good for scanning and status check. Ghostscript and foomatic-rip need to be fixed to be more optware compliant since a lot of things seem to refer to /usr still and this causes things not to work. You can edit /opt/bin/foomatic-rip to see what I mean. Also XPDF needs to be installed for adequate local printing and fixed. The generated PS files tend to scramble my printer. I actually had to download and build poppler instead to get things running.

August 05, 2008, at 07:44 PM by Mark Gauldin -- Question about changing default printer
Added lines 95-96:

Very helpful - seems to be working for me. I have just one question. I found the ppd for my specific printer (HP DeskJet? 5550) and I unpacked it and copied it to the appropriate models directory as instructed above. However, I'm not sure what I need to change to be able to use that as my default printer. The default hp990c seems to work OK so far, but I haven't tried printing anything terribly complex yet.

January 18, 2008, at 11:30 AM by Smasher -- my solution for foomatic-rip failed
Added lines 76-85:

found the error why foomatic-rip fails... in the file foomatic-gswrapper, that you have to download when following the original cups-howto from http://www.linux-foundation.org/en/OpenPrinting/Database/CUPSDocumentation

there is a line (number 43) '-sOutputFile=%stdout' : '-sOutputFile=/dev/fd/3');

change the /dev/fd/3 to /dev/null , its just for standard out...

and then 'chmod 777 /dev/null

it worked for me then..


September 14, 2007, at 08:01 PM by Marcelo -- HPIJS problem not solved yet.
Added line 76:

The update posted below is about a DIFFERENT problem. The above described one (foomatic-rip failed) is NOT solved yet:

September 06, 2007, at 09:59 AM by Dave Wardle -- \'/invalidfont in findfont\' problem solved?
Changed lines 78-79 from:
                    chmod 644 /opt/share/ghostscript/fonts
to:
                    chmod 644 /opt/share/ghostscript/fonts/*
September 06, 2007, at 09:54 AM by Dave Wardle -- \'/invalidfont in findfont\' error solved?
Changed lines 74-83 from:

why is that?

to:

why is that?


I'm also running Unslung V2.3R63-uNSLUng-6.8-beta, trying to print to an HP 1010 laserjet, and was getting the same problem as above i.e. foomatic-rip gives the error "/invalidfont in findfont". After several days of research I suspected the problem might have something to do with the permissions of the fonts in the fonts directory. I checked, and found that I had copied the fonts with only root permissions. If the fonts are in /opt/share/ghostscript/fonts then the following command should cure the problem

                    chmod 644 /opt/share/ghostscript/fonts

This gives read permissions to everyone. I can now print from Windows XP and Linux machines, directly to the CUPS server, without going via samba, and the 'Print test page' function works in the CUPS web interface. If you want to print directly to CUPS in Windows XP the following link tells you how

            http://www.owlfish.com/thoughts/winipp-cups-2003-07-20.html
August 27, 2007, at 03:43 PM by fcarolo -- formatting, reminder about mailing list
Changed lines 1-2 from:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions. Then I just grabbed my print driver (.ppd file) from linuxprinting.org, uploaded it through the cups web interface and added my printer. Everything prints fine so far (including PostScript? files), so either the below issues have been fixed or there is a significant difference in other people's systems.

to:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions. Then I just grabbed my print driver (.ppd file) from linuxprinting.org, uploaded it through the cups web interface and added my printer. Everything prints fine so far (including PostScript files), so either the below issues have been fixed or there is a significant difference in other people's systems.

Changed lines 20-21 from:
 #gunzip /opt/share/ppd/HP/HP-DeskJet?_3550-hpijs.ppd.gz
 #cp /opt/share/ppd/HP/HP-DeskJet?_3550-hpijs.ppd /opt/share/cups/model/
to:
 #gunzip /opt/share/ppd/HP/HP-DeskJet_3550-hpijs.ppd.gz
 #cp /opt/share/ppd/HP/HP-DeskJet_3550-hpijs.ppd /opt/share/cups/model/
Changed line 31 from:
  • For me copying the contents of /usr/local/share/ghostscript/fonts on my FreeBSD? box into /opt/share/ghostscript/fonts on the slug was good enough.
to:
  • For me copying the contents of /usr/local/share/ghostscript/fonts on my FreeBSD box into /opt/share/ghostscript/fonts on the slug was good enough.
Added lines 39-41:

Before posting questions to a wiki page, please remember that the MailingLists are the appropriate channels for such questions. Please use the nslu2-linux list.

Changed line 65 from:

The cupsd.conf's "LogLevel? debug" suggests a gs problem.

to:

The cupsd.conf's "LogLevel debug" suggests a gs problem.

Changed line 69 from:
 Process dying with "Possible error on renderer command line or PostScript? error. Check options.", exit stat: 3
to:
 Process dying with "Possible error on renderer command line or PostScript error. Check options.", exit stat: 3
August 26, 2007, at 02:43 PM by omr --
Changed lines 68-71 from:

Hi! I'm having the exact same problem. Has anyone came to a solution to this?

to:

Hi! I'm having the exact same problem. Has anyone came to a solution to this?


I've installed everything but when i try to print the test page from cups it says "/opt/lib/cups/filter/foomatic-rip failed" why is that?

June 25, 2007, at 01:26 AM by rph -- same problem
Changed lines 67-68 from:

to:

Hi! I'm having the exact same problem. Has anyone came to a solution to this?

June 05, 2007, at 09:29 PM by chriss -- hpijs
Added lines 56-66:

The packages perl-module-strict perl-module-posix perl-module-cwd don't exist and you don't need 'm. I guess someone (or something) picked 'm up from the first lines of the foomatic-rip script:

 use strict;
 use POSIX;
 use Cwd;

No, the problem is somewhere else. The script is compilable and executable. The cupsd.conf's "LogLevel? debug" suggests a gs problem.

 AFPL Ghostscript 8.50: Unrecoverable error, exit code 1
 renderer return value: 1
 renderer received signal: 1
 Process dying with "Possible error on renderer command line or PostScript? error. Check options.", exit stat: 3
May 05, 2007, at 01:07 AM by cyrxi --
Changed lines 1-2 from:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions. Then I just grabbed my print driver (.ppd file)from linuxprinting.org, uploaded it through the cups web interface and added my printer. Everything prints fine so far (including PostScript? files), so either the below issues have been fixed or there is a significant difference in other people's systems.

to:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions. Then I just grabbed my print driver (.ppd file) from linuxprinting.org, uploaded it through the cups web interface and added my printer. Everything prints fine so far (including PostScript? files), so either the below issues have been fixed or there is a significant difference in other people's systems.

May 05, 2007, at 01:06 AM by cyrxi --
Changed lines 1-2 from:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions.

to:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions. Then I just grabbed my print driver (.ppd file)from linuxprinting.org, uploaded it through the cups web interface and added my printer. Everything prints fine so far (including PostScript? files), so either the below issues have been fixed or there is a significant difference in other people's systems.

May 05, 2007, at 01:00 AM by cyrxi --
Added lines 1-6:

All I needed to do was "ipkg install hpijs" after following the first section on AddPrinter - i.e. I only installed cups and cups-doc and followed the post-installation instructions.

NOTES: I am running Unslung V2.3R63-uNSLUng-6.8-beta. I am not printing directly from the slug, but from another Linux box connected wirelessly.

    -cyrxi

_________________________________________________________________________

April 03, 2007, at 01:15 AM by greg -- add more comments claiming for help
Added line 49:

Actually, in unslung there is a package name perl-module-build (version 5.8.8) that once installed derives a number of modules, including strict, cwd among others, but foomatic-rip still fails. What I don't understand is that hpijs is available in the unslung repository, so it should work. Please, does anybody using Unslung had success on using hpijs? give a light.

April 03, 2007, at 12:33 AM by greg -- added more comments
Changed line 48 from:

Yeah... but there is too many dependencies to attend, including different libc6 versions and so... perhaps one day someone will port them to Unslung (any candidates?)

to:

Yeah... but there are too many dependencies to attend, including different libc6 versions and so... perhaps one day someone will port them to Unslung (any candidates?)

April 03, 2007, at 12:33 AM by greg -- Added more comments
Changed lines 46-49 from:

You can grab them from the openslug-bag feed. :-)

to:

You can grab them from the openslug-bag feed. :-)


Yeah... but there is too many dependencies to attend, including different libc6 versions and so... perhaps one day someone will port them to Unslung (any candidates?)


April 02, 2007, at 06:27 AM by Jan Alonzo -- added comment
Added line 46:

You can grab them from the openslug-bag feed. :-)

April 01, 2007, at 04:05 PM by greg -- Comments about unavailable \"perl-module-*\" packages
Added lines 42-45:

Fine, but there is still a showstopper problem, where to find all these perl-module-* ipks since ipkg states they do not exist (Unslung-6.8) even after a fresh "ipkg update"? Anyway, thanks for helping (though it is not working yet :-) )


April 01, 2007, at 03:37 AM by Jan Alonzo -- fix line break formatting
Changed lines 16-18 from:
  • If there is no existing PPD for your printer, you can copy the one you're using
  • in your Linux box or from the vendor's cd-rom.
to:
  • If there is no existing PPD for your printer, you can copy the one you're using in your Linux box or from the vendor's cd-rom.
April 01, 2007, at 03:31 AM by Jan Alonzo -- added other foomatic-rip dependencies
Deleted lines 2-11:

Help request


Please help! The below instructions doesn't work. Followed all the instructions, installed everything and created a new queue, which works fine for plain text and for remote client printer-native code (as if it was a raw quere), but it sinply refuses to print PS files, including the testpage in the cups printer page. It states: "/opt/lib/cups/filter/foomatic-rip failed" Installed packages: cups-1.2.7-3, ghostscript-8.50-2, hpijs-2.1.4-1, perl-5.8.8-13. Also installed all fonts from a working ghostscript installation in the indicated directory is any other package necessary? Could please provide more comprehensive instructions? Sorry for polluting the page.


Changed lines 8-9 from:
 #ipkg install perl
to:
 #ipkg install perl perl-module-strict perl-module-posix perl-module-cwd
 #ipkg install perl-io-handle perl-module-io perl-module-data-dumper
 #ipkg install perl-module-bytes perl-module-sigtrap
Changed line 13 from:
  • Gunzup it and copy it to /opt/share/cups/model/
to:
  • Gunzip it and copy it to /opt/share/cups/model/
Changed lines 16-18 from:
to:
  • If there is no existing PPD for your printer, you can copy the one you're using
  • in your Linux box or from the vendor's cd-rom.
Changed lines 31-42 from:
to:

Comments


Please help! The below instructions doesn't work. Followed all the instructions, installed everything and created a new queue, which works fine for plain text and for remote client printer-native code (as if it was a raw quere), but it sinply refuses to print PS files, including the testpage in the cups printer page. It states: "/opt/lib/cups/filter/foomatic-rip failed" Installed packages: cups-1.2.7-3, ghostscript-8.50-2, hpijs-2.1.4-1, perl-5.8.8-13. Also installed all fonts from a working ghostscript installation in the indicated directory is any other package necessary? Could please provide more comprehensive instructions? Sorry for polluting the page.


Make sure you have installed perl-module-strict as well and other dependencies. Added it to the instructions above.

January 19, 2007, at 01:07 PM by Greg -- Typo
Changed line 5 from:

Please help! This doesn't work. Followed all the instructions, installed everything and created a new queue, which works fine for plain text and for remote client printer-native code (as if it was a raw quere), but it sinply refuses to print PS files, including the testpage in the cups printer page. It states: "/opt/lib/cups/filter/foomatic-rip failed"

to:

Please help! The below instructions doesn't work. Followed all the instructions, installed everything and created a new queue, which works fine for plain text and for remote client printer-native code (as if it was a raw quere), but it sinply refuses to print PS files, including the testpage in the cups printer page. It states: "/opt/lib/cups/filter/foomatic-rip failed"

January 13, 2007, at 10:13 PM by Greg -- Request for help
Changed lines 6-11 from:

Installed packages cups: 1.2.7-3 ghostscript: 8.50-2 hpijs: 2.1.4-1 perl: 5.8.8-13 also installed all fonts from a working ghostscript installation in the indicated directory

to:

Installed packages: cups-1.2.7-3, ghostscript-8.50-2, hpijs-2.1.4-1, perl-5.8.8-13. Also installed all fonts from a working ghostscript installation in the indicated directory

January 13, 2007, at 10:12 PM by Greg --
Added line 4:

January 13, 2007, at 10:11 PM by Greg -- Request for help
Changed line 3 from:
to:

Help request

Changed lines 14-15 from:
to:

January 13, 2007, at 10:09 PM by Greg -- request for help
Added lines 3-15:

Please help! This doesn't work. Followed all the instructions, installed everything and created a new queue, which works fine for plain text and for remote client printer-native code (as if it was a raw quere), but it sinply refuses to print PS files, including the testpage in the cups printer page. It states: "/opt/lib/cups/filter/foomatic-rip failed" Installed packages cups: 1.2.7-3 ghostscript: 8.50-2 hpijs: 2.1.4-1 perl: 5.8.8-13 also installed all fonts from a working ghostscript installation in the indicated directory is any other package necessary? Could please provide more comprehensive instructions? Sorry for polluting the page.

August 12, 2006, at 11:52 AM by Ernst --
Changed lines 23-24 from:
  • You can probably get these from http://www.ghostscript.com somehow,
to:
  • You can probably get these from http://www.ghostscript.com somehow,
  • or download them from http://ftp.debian.org/debian/pool/main/g/gsfonts/gsfonts_8.14+v8.11+urw.orig.tar.gz
July 09, 2006, at 03:34 AM by Dan --
Changed lines 17-19 from:
 #ln -s  /opt/bin/gs /bin/gs
 #ln -s  /opt/bin/hpijs /bin/hpijs
to:
 #ln -s /opt/bin/gs /bin/gs
 #ln -s /opt/bin/hpijs /bin/hpijs
July 09, 2006, at 03:33 AM by Dan --
Changed lines 1-3 from:

Here's the steps I needed to take to get HPIJS and cups qorking properly.

  • Install these packages. hpijs should depend on perl because it includes foomatic-rip (a perl script) and at least one of hpijs or cups should require ghostscript.
to:

Here's the steps I needed to take to get HPIJS and cups working properly.

  • Install these packages. hpijs should depend on perl because it includes foomatic-rip (a perl script) and at hpijs and/or cups should require ghostscript.
Changed lines 8-10 from:
 #ipkg install perl 
 #ipkg install fontconfig (unsure if this is necessary)
to:
 #ipkg install perl
Changed line 15 from:
  • Create the following symlinks so that cups can find certain executables. There may be a way of altering the $PATH variable to avoid some of these:
to:
  • Create the following symlinks so that Cups can find certain executables:
Changed lines 21-22 from:
  • I found that there were no fonts in the ghostscript fonts directory (hint - see towards the bottom of gs -h output)
  • For me copying the contents of /usr/local/share/ghostscript/fonts on my FreeBSD? box into /opt/share/ghostscript/fonts on the slug was good enough.
to:
  • I found that there were no fonts in the ghostscript fonts directory
  • For me copying the contents of /usr/local/share/ghostscript/fonts on my FreeBSD? box into /opt/share/ghostscript/fonts on the slug was good enough.
Changed line 26 from:
  • Now add you printer in the normal manner.
to:
July 09, 2006, at 12:45 AM by Dan -- How to add an HPIJS printer
Added lines 1-27:

Here's the steps I needed to take to get HPIJS and cups qorking properly.

  • Install these packages. hpijs should depend on perl because it includes foomatic-rip (a perl script) and at least one of hpijs or cups should require ghostscript.
 #ipkg install hpijs
 #ipkg install cups-doc
 #ipkg install ghostscript
 #ipkg install perl 
 #ipkg install fontconfig (unsure if this is necessary)
  • Go to /opt/share/ppd/HP/ and find the ppd for your HP printer.
    • Gunzup it and copy it to /opt/share/cups/model/
 #gunzip /opt/share/ppd/HP/HP-DeskJet?_3550-hpijs.ppd.gz
 #cp /opt/share/ppd/HP/HP-DeskJet?_3550-hpijs.ppd /opt/share/cups/model/
  • Create the following symlinks so that cups can find certain executables. There may be a way of altering the $PATH variable to avoid some of these:
 #ln -s /opt/bin/foomatic-rip /opt/lib/cups/filter/foomatic-rip
 #ln -s  /opt/bin/gs /bin/gs
 #ln -s  /opt/bin/hpijs /bin/hpijs
  • Put some ghostscript fonts into /opt/share/ghostscript/fonts.
    • I found that there were no fonts in the ghostscript fonts directory (hint - see towards the bottom of gs -h output)
    • For me copying the contents of /usr/local/share/ghostscript/fonts on my FreeBSD? box into /opt/share/ghostscript/fonts on the slug was good enough.
    • You can probably get these from http://www.ghostscript.com somehow,
      • (Note to devs - perhaps there should be a gsfonts package?)
  • Now add you printer in the normal manner.
view · edit · print · history · Last edited by Benalua.
Based on work by Benalua, Mark Gauldin, Smasher, Marcelo, Dave Wardle, fcarolo, omr, rph, chriss, cyrxi, greg, Jan Alonzo, Greg, Ernst, and Dan.
Originally by Dan.
Page last modified on December 13, 2013, at 04:37 AM