Sponsored Content
Operating Systems Solaris Printer (lpadmin) error - blank pages PS/PCL Post 302700299 by poyato on Thursday 13th of September 2012 08:26:00 AM
Old 09-13-2012
Printer (lpadmin) error - blank pages PS/PCL

Help!

I have to solve an urgent problem!

I have a Solaris 10 server, where I created a line of printing with the command
Code:
 # /usr/sbin/lpadmin -p IL_Printer -s pv24002 -v /dev/null -m netstandard_foomatic -A write -n /usr/lib/lp/model/ppd/system/foomatic/Canon/cnl66e1.ppd.gz -o dest=99.99.99.99 \
    -o protocol=tcp -o banner=never -u allow:all

I have a remote printer - Canon LBP6650 - the other side of the planet.
Everything works fine, but for some reason the prints started coming out garbled and / or blank.

I downloaded the original PPD driver on the Canon site (Europe) and still the problem persists.

Even creating the queue without any driver, in the most generic possible the problem persists:
Code:
 # lpadmin -p PT_Printer -v /dev/null -m netstandard_foomatic -o dest=99.99.99.99 -A none -o banner=never -o protocol=tcp -u allow:all

Moderator's Comments:
Mod Comment Please use code tags, not font settings.


I noticed that the printer has only as optional PostScript mode.
I thought the PCL, but the extension of the file is PDD instead of PPD.

The command below to install the driver of error:

Code:
# ppdmgr -a cnl665e1-pcl.pdd -w
ppdmgr: invalid PPD file: /impressora/cnl665e1-pcl.pdd


How, for the love of god, do I install a printer through a PCL file PDD?

Smilie

Last edited by jim mcnamara; 09-13-2012 at 09:38 AM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

PCL Font does not download to printer.

OS: HP-UX B.11.11 U Printer: HP 8150. I require a font to be downloaded to the printer and used. As documented the steps are: 1. Tell printer to accept font 2. Send the font to the printer 3. Make the font permanent 4. Select font for use or in PCL 1. <Esc>*c90D 2.... (0 Replies)
Discussion started by: mbb
0 Replies

2. Solaris

configuring printer using lpadmin

Can some one tell me how to configure the printer on solaris printer name = A printer server address : 172.21.19.6 (3 Replies)
Discussion started by: krishan
3 Replies

3. UNIX for Dummies Questions & Answers

Add printer with IP address with lpadmin

Hi all, I'm tryin' to add a network printer with lpadmin (I don't have access to admintool) to a Solarisbox but I don't exactly know where to use the IP address. The thing is that this printer exists already with another printQ but I don't see any printerserver declared with lpsystem -l although... (3 Replies)
Discussion started by: nulnul7
3 Replies

4. UNIX for Dummies Questions & Answers

Printer prints blank pages

Hello Everyone :) , I have this printer installed on the network which is an HP 1160. When sending a print job to the printer from SCO Unix 7.1 it prints one line of text and the rest of it comes up with blank pages. I have tried deleting the printer and recreating it; but I am getting... (6 Replies)
Discussion started by: George26
6 Replies

5. UNIX for Dummies Questions & Answers

Lpadmin and viewing printer settings

Hi - Dummy question #1.... We either use the Hewlett Packard HPPI too or LPADMIN command to setup out printers. Is there an LPADMIN command that will show you the default config of a particular printer. Ideally looking to see default font, CPI settings etc. Thanks. BravehearT1326 ... (1 Reply)
Discussion started by: BravehearT1326
1 Replies

6. Red Hat

Red hat 5. - PCL Printer

I need to setup a HP 4000 PCL printer - it seems out of the box - I can only can use PostScript. Any guidance is appreciated. In the SCO world - I used HPNP with no problems. (2 Replies)
Discussion started by: markb4
2 Replies

7. UNIX for Dummies Questions & Answers

Printing Landscape to PCL 6 Printer

I've looked around and am able to print landscape to a PCL 5 printer with this command: lp -o landscape -o cpi=20 -o page-right=30 -o page-left=30 -d <printer> <file>. Which gives me a nice 200 columns. But, when I send the same output and the same commands to a PCL 6 printer, it comes... (3 Replies)
Discussion started by: tariqjamal
3 Replies

8. IP Networking

Creating a printer emulator to capture PDL/PCL data coming in on port 9100.

I have a number of Windows CE operator terminals. They have facility to print alarms/messages to ... aser or Inkjet (so they're using PCL). USB or IP. IP connection takes just the IP address. Question How could I create a service or daemon on a server to capture all this data?... (7 Replies)
Discussion started by: transistor
7 Replies

9. UNIX and Linux Applications

netcat prints blank pages

Please direct me to the right forum tree if i am in the wrong section for this. i have netcat on a unix machine and there is no man nc or man netcat available. my command i am using is: cat $FILE1 | netcat -h $PRINTER -p 9100 (-h -p -d are the only flags available in this version of... (3 Replies)
Discussion started by: dunpealslyr
3 Replies

10. SCO

Printing to a working network printer using PCL

I am trying to get a network printer to work that currently works from my Unix (5.0.7) server when printing text files only. When I try to print post script files like a PDF file I get all of the controls so I am not sure if I have my printer configuration setup properly in Unix The printer... (1 Reply)
Discussion started by: ziggy6
1 Replies
FOOMATIC-RIP(1) 					      General Commands Manual						   FOOMATIC-RIP(1)

NAME
foomatic-rip - Universal print filter/RIP wrapper SYNOPSIS
General Options: foomatic-rip [-v] [-q] <spooler-specific options> Spooler-less printing/CPS (older versions) filter: foomatic-rip [-P <printer> | --ppd <ppdfile> ] [-J <jobtitle> ] [-o <option>=<value> [...]] [<files>] CUPS filter: foomatic-rip <jobid> <user> <jobtitle> <numcopies> <options> [<file>] LPRng filter: foomatic-rip --lprng [-J<jobtitle>][-Z<option>=<value>[,<option>=<value>[, ...]] <ppdfile> foomatic-rip [-J<jobtitle>][-Z<option>=<value>[,<option>=<value>[, ...]] (printcap :pdd=<ppdfile>) foomatic-rip --ppd <ppdfile>[-J<jobtitle>] [-Z<option>=<value>[,<option>=<value>[, ...]] LPD/GNUlpr filter: foomatic-rip [-w <number>] [-l <number>] [-x <number>] [-y <number>] [-i <number>] [-c] [-n <string>] [-h <string>] [-j|-J <jobti- tle>|<options>] <ppdfile> PPR RIP: foomatic-rip [<option>=<value> [...]] PPR interface: foomatic-rip <queue> <destaddress> <options> <jobbreak> <feedback> <codes> <jobname> <routing> <for> <filetype> [<file>] PDQ driver file generation: foomatic-rip [--ppd <ppdfile>] [-o <option>=<value> [...]] --genpdq|--appendpdq|--genrawpdq|--appendrawpdq PDQ filter: foomatic-rip --pdq --ppd <ppdfile>] [-o <option>=<value> [...]] <file> CPS (newer versions) filter: foomatic-rip --cps -P <printer> [-J <jobtitle>] [-o <option>=<value> [...]] [<files>] DESCRIPTION
foomatic-rip is a universal print filter which works with every known free software printer spooler. It has the following features: It translates PostScript and PDF (and also other file formats) from standard input to the printer's native language (usually put to stan- dard output). The translation is done with an external renderer, usually Ghostscript (gs(1)). If no translation is needed (PostScript printer) the ren- derer's command line reduces to cat(1). The way how this translation is done is described in a PPD file. Printer capabilities, how to handle user options, and how to build the renderer command line is always described by PPD files, these PPD files usually come from Foomatic or can be the ones supplied by the manufacturers of PostScript printers. The PPD files are the same for all spoolers. foomatic-rip works with every known spooler (CUPS, LPRng, LPD, GNUlpr, PPR, PDQ, CPS, and without spooler). It auto-detects the spooler from which it was called by the command line options and environment variables which were supplied by the spooler. Non-PostScript/PDF files are translated to PostScript before they are passed to the renderer. This is usually done by a2ps(1), enscript(1), or mpage(1). foomatic-rip auto-detects which program is installed, but manual configuration is also possible. foomatic-rip does not only apply option settings supplied by the user through the command line of the printing command, but also searches the entire job for embedded option settings (only PostScript jobs). Here not only settings which affect the whole job are taken into account, but also settings in the page headers, which are only valid for the page where they were found, so applications which produce PostScript code with page-specific printer option settings are fully supported. SPOOLER-LESS PRINTING Options -v verbose mode for debugging. WARNING: This will create a file in /tmp that contains the debugging information. This opens a security loophole and should not be used in production. -q quiet mode - minimal information output -P <printer> <printer> is the configured printer which should be used for this job. --ppd <ppdfile> The PPD file <ppdfile> should be applied for processing this job. -J <jobtitle> The <jobtitle> will be printed in the head line of every page of a plain text job. -o <option>=<value> Option settings for this job, do foomatic-rip -P <printer> -o docs <file> (<file> can be an arbitrary existing file, as .bashrc, will not be printed) to print a list of available options for the speci- fied <printer>. <files> The file(s) to be printed. foomatic-rip will print from standard input unless at least one file to be printed is specified on the command line. If your printer PPD file is stored as /etc/direct/<printer>.ppd or ~/.foomatic/direct/<printer>.ppd you can use it by simply specifying "-P <printer>". Put a line *FoomaticRIPPostPipe: "| <command>" into the PPD file, right after *PPD-Adobe: "4.3", where <command> is a command into which you want to re-direct the output data. Due to the restrictions of PPD files <, >, and " are not allowed in the <command>, replace them as follows: Character Replacement --------------------- < &lt; > &gt; " &quot; ' &apos; & &amp; This way you can print directly to your printer, use *FoomaticRIPPostPipe: "| cat &gt; /dev/lp0" or *FoomaticRIPPostPipe: "| cat &gt; /dev/usb/lp0" for local parallel or USB printers. To make normal users able to print this way add them to the group lp and make sure that the appropriate printer device file /dev/... is group-writable for the lp group. for a TCP/Socket/JetDirect printer with the host name printer listening on port 9100 you need this: *FoomaticRIPPostPipe: "| /usr/bin/nc -w 1 printer 9100" Note the "-w 1" in the "nc" command line, it makes "nc" exiting immediately after the data is transferred to the printer. *FoomaticRIPPostPipe: "| rlpr -Plp@printserver" directs your jobs to the LPD printer queue lp on the machine named printserver. See also http://www.openprinting.org/direct-doc.html PRINTING WITH SPOOLER
See the documentation on the OpenPrinting Web site: http://www.openprinting.org/ CONFIGURATION FILE
The file /etc/foomatic/filter.conf is read whenever foomatic-rip is executed. It allows to configure the behavior of foomatic-rip as follows (lines beginning with # are comments and therefore get ignored): textfilter: <command> Selects the filter for input files which are not PostScript or PDF. <command> is one of a2ps, enscript, or mpage. foomatic-rip automatically selects the needed command line options. debug: 0|1 Turns on (1) or off (0) the debug mode. This is equivalent to supplying the --debug command line option. Default setting is 0. ps_accounting: 0|1 Turns on (1) or off (0) inserting PostScript code for page accounting into PostScript jobs. The inserted PostScript code makes Ghostscript generating accounting output on stderr and CUPS can this way log each page which got printed. The code will only be inserted if CUPS is the spooler. Default setting is 1. echo: [<path>/]<executable> Sets the path to an echo(1) executable which supports -n. gspath: [<path>/]<executable> Sets the path to the Ghostscript (gs(1)) executable. To be used if Ghostscript is at a non-standard location or if an alternative Ghostscript should be used. execpath: <path>[:<path>]... Sets the $PATH variable to be used by foomatic-rip. cupsfilterpath: <path>[:<path>]... Sets the directories (colon-separated) in which foomatic-rip searches for CUPS filters. preferred_shell: [<path>/]<executable> Sets the preferred shell to use when executing FoomaticRIPCommandLine and friends. Several PPD files use shell constructs that require a more modern shell like bash, zsh, or ksh. FILES
/etc/cups/ppd/<printer>.ppd /etc/lpd/<printer>.ppd /etc/ppr/<printer>.ppd /etc/pdq/<printer>.ppd /etc/direct/<printer>.ppd The PPD files of the currently defined printers /etc/foomatic/filter.conf Configuration file for foomatic-rip EXIT STATUS
foomatic-rip returns 0 unless something unexpected happens. AUTHOR
Till Kamppeter <till.kamppeter@gmail.com> with parts of Manfred Wassmanns's <manolo@NCC-1701.B.Shuttle.de> man pages for the Foomatic 2.0.x filters. BUGS
None so far. Please send bug reports to the Foomatic mailing list: http://lists.freestandards.org/mailman/listinfo/printing-foomatic Foomatic Project 2002-11-26 FOOMATIC-RIP(1)
All times are GMT -4. The time now is 08:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy