SuSE Linux: Versions up to (including) 7.3
You want to install your printer. If you are running SuSE Linux 8.0, 8.1, or 8.2, proceed as described in the support database articles "Printer Configuration with SuSE Linux 8.0", "Printer Configuration with SuSE Linux 8.1", or "Printer Configuration with SuSE Linux 8.2". Find these articles with the keyword "installing" or "installation". In case of problems, check whether the prerequisites below are fulfilled. For older versions from 6.4 on, proceed as described in the support database article "Installing a Printer Since SuSE Linux 6.4". Find this article with the keyword "installing". First, check that the prerequisites below are fulfilled.
Regarding SuSE Linux PowerPC, see the article Installing a Printer for PowerPC. Regarding SuSE Linux AXP, see the article Installing a Printer for AXP. Regarding SuSE Linux for S390, see the article Installing a Printer for S390.
If you own a GDI printer (a printer that does not understand a standard printer language), it is probably not supported by Linux or only usable with restrictions. Look at the support database, especially the articles GDI Printer and Purchase of Printers and Compatibility.
Regarding Ghostscript, find driver information on the web.
Sometimes a Ghostscript driver is listed that requires the current
"Aladdin Ghostscript" version.
To comply with licences, SuSE Linux includes only "GNU Ghostscript."
Enter gs -v
to display the version.
Normally, there is also a GNU Ghostscript driver that supports the printer.
If the printer is not connected directly to the first parallel port and you are having problems, connect it directly to the first parallel port and make a test configuration.
The BIOS settings for the first parallel interface should be set as follows:
echo -en "\rHello\r\f" >/dev/lp0
Provided the printer is connected to the first parallel port /dev/lp0,
you should get one sheet with the word Hello
printed on it.
The printer must be able to print ASCII text
(in this case, the word Hello
surrounded by the
ASCII character \r
, which initiates a carriage return,
and followed by the ASCII character \f
, which initiates
a form feed).
Printers unable to print ASCII text are mostly GDI printers, but there are some printers that cannot print ASCII text but work with Linux anyway. In this case, at least the manufacturer and the printer model should be shown in the output of the following command:
cat /proc/parport/0/autoprobeSince SuSE Linux 7.2, it is the command
cat /proc/sys/dev/parport/parport0/autoprobe
If neither the manufacturer or the model is shown, it normally makes no sense to make further configurations.
First, the printer has to be accessible via the parallel port. Regarding the configuration of the parallel interface, see section 2 in the article Printer Problems: Special Causes.
/etc/printcap
. Log in as root and type
mv /etc/printcap /etc/printcap.save
. After this, try a new
configuration.
Among the information sources mentioned in section 1: "Prerequisites", the correct Ghostscipt drivers for the different printer models are listed.
In file
/usr/doc/packages/ghostscript/catalog.devices
(since SuSE Linux 7.0
/usr/share/doc/packages/ghostscript/catalog.devices
),
find a list of Ghostscipt drivers and a selection of supported printers.
To read this file, use the following command:
less /usr/doc/packages/ghostscript/catalog.devices
(since SuSE Linux 7.0
less /usr/share/doc/packages/ghostscript/catalog.devices
)
Use arrow keys to scroll and Q to quit.
If you do not find your printer model, choose a Ghostscipt driver for a printer that is compatible with your printer. Refer to the manual of your printer or ask the manufacturer. (See Purchase of Printers and Compatibility)
There is a special kind of Ghostscript driver with the extension
.upp
.
This kind of driver are not regular Ghostscript drivers, but
parameter files for the uniprint
Ghostscript driver.
Since SuSE Linux 6.4. you can choose
the paper size a4dj
during the configuration, which is
necessary for most ink jet printers.
(See Setting the Page Size of ASCII files)
If you have a real PostScript printer, you do not need a special Ghostscipt driver.
/var/lib/apsfilter/SETUP
lprsetup
/dev/lp0
(if it is not displayed already) and choose OK
ascii ... a4dj ascii mono lp ... a4dj auto color lp-mono ... a4dj auto mono raw ... a4dj rawor, if you have chosen MONO,
ascii ... a4dj ascii mono lp ... a4dj auto mono raw ... a4dj rawWrite down the installed printer spooling queues, in this example ascii, lp, (lp-mono), and raw. Confirm with OK.
lpr file
lpr -Plp file
For example, execute:
lpr /etc/fstab
or
lpr -Plp /etc/fstab
If the chosen Ghostscript driver supports color printing,
test by printing the color ellipse with the command
lpr /usr/share/doc/packages/ghostscript/examples/colorcir.ps
lpr file
or lpr -Plp file
,
the type of the file (ASCII or Postscript) is determined automatically.
To force the type of file to be ASCII, use
lpr -Pascii file
(e.g., to print PostScript source as such and prevent it from being interpretted
as a PostScript file.)
Files that are already in a printer specific format should be
printed with the command lpr -Praw file
(e.g., if you print under Windows in a file and you want to print this file
under Linux).
Normally, you will not get a correct printout using the raw queue because the
file is sent "raw" to the printer and will not be converted into the
printer-specific format.
Using lpr -Plp-mono file
, monochrome printing will not
be forced automatically. To get monochrome printing, the corresponding
Ghostscript parameters must be set in an apsfilterrc file in
case of "$COLOR" = "mono".
(See
Installing a Printer Since SuSE Linux 6.4)
If the prerequisites are met and you followed the above instructions, the printer should work now. For more information, refer to the manuals. For special cases, see Printer Problems: Special Causes
For information, refer to the manuals or the support database article Printing from Applications.