Forum: General Discussion
The loopback is standard on all computers, but it must be defined or
many applications will break. It is defined in
If you take a look at
/etc/hosts, you should see that
localhost is defined with the machine name and the loopback address.
cat /etc/hosts | grep 127.0.0.1
Should output something similar to
127.0.0.1 localhost toshy inetw.net
You should also check that the loopback network device has been brought up. The command
ifconfig should yield an entry similar to
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:30 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2076 (2.0 Kb) TX bytes:2076 (2.0 Kb)
You need to add the printer to OpenOffice separately. You can do
this by running the
oopadmin program. The
is found in newer versions of OpenOffice. There are two ways to
First Method: Many newer distributions have the printer setup as a separate menu choice. For example, in RedHat 9, the printer setup utility is on the OO menu – click on the red hat in the lower left, click on OpenOffice, and there printer setup is right along side writer, calc, impress, and the rest.
Second Method: Just start OpenOffice. Make a new printer, and when
presented with the
Choose a Driver screen, click on
browse to the location of your printer's PPD.
Use the default print commands, name the printer, set it as default, and you are ready to go! Start OpenOffice.org1.0 and go to the print screen, and select your printer. Print a test page, and you are done.
OpenOffice.org (and also other PPD-aware applications or print filters) inserts printer-specific PostScript code into the PostScript output file according to the definitions of the options in the PPD file, so that the printer prints the document in the way the user has configured it by the options in the “Properties” dialog. These inserted PostScript commands are not generally understood by every PostScript interpreter (every printer has its own PPD file), so GhostScript does not need to understand them.
If you are using any recent distribution, USB is probably already setup on your machine. You can still check it yourself. Please note that you may need root privelages for many of the commands.
Here are the steps to find out if you have USB setup and enabled for printing.
1. Check your loaded
2. See if the USB
Printer Driver is listed.
3. Look at the
Kernel Log for usb traffic.
4. Look at the list of
You can search the currently loaded modules. This method is the quickest, but won't work if your USB drivers are compiled into the kernel, the printer driver has been renamed, or the modules simply are not loaded.
lsmod | grep printer # printer
If you see
printer as the output, then you probably
have USB printing setup and working. If not, don't worry. This
command will fail on many systems.
You can search the list of USB drivers available on your system,
and look for the
usblp driver. If
the USB driver has been renamed, this method may fail.
cat /proc/bus/usb/drivers | grep usblp # 0- 15: usblp
usblp device is there, then you have a USB printer
driver. If not, try loading the printer driver manually
modprobe printer cat /proc/bus/usb/drivers | grep usblp # 0- 15: usblp
If you see an error message like
cat: /proc/bus/usb/drivers: No such file or directory
We will use the
tail command to look at the kernel
log messags. If you don't know what a UNIX tail does, then
tail command on your kernel or
system log files, and then disconnect and reconnect the printer.
You will see the kernel print messages about the event.
I can't tell you where your system log is, or what it is called,
because it varies between distributions. Log files are usually
/var/log/. Some common names are
tail -f /var/log/sys.log
Now, disconnect and reconnect the printer to see it register. Example Output
Mar 19 04:32:06 localhost kernel: hub.c: USB new device connect on bus1/1/4/4, assigned device number 12 Mar 19 04:32:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 12 if 0 alt 1 proto 2 vid 0x050D pid 0x0002
If there is no activity, you probably don't have USB enabled at all. There is one last thing to try.
You can check the list of all USB devices that are installed and recognized on your system. This method will tell you if your printer is being recognized or not, even if the printer modules is not loaded.
cat /proc/bus/usb/devices | grep usblp
Outputs something like
I: If#= 0 Alt= 0 #EPs= 1 Cls=07(print) Sub=01 Prot=01 Driver=usblp I: If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp I: If#= 0 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usblp
if you see an error
cat: /proc/bus/usb/drivers: No such file or directory
If you have USB enabled, but the USB printer driver is not working, then you can get around this by comparing the USB devices list before and after your printer has been plugged in.
cat /proc/bus/usb/devices > log1
Now (dis)connect the printer.
cat /proc/bus/usb/devices > log2
Compare the two logs, they should be different.
diff log1 log2
The output will vary, an example output is
< T: Bus=01 Lev=03 Prnt=08 Port=03 Cnt=02 Dev#= 10 Spd=12 MxCh= 0 < D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 < P: Vendor=050d ProdID=0002 Rev= 1.04 < C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 98mA < I: If#= 0 Alt= 0 #EPs= 1 Cls=07(print) Sub=01 Prot=01 Driver=usblp < E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms < I: If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp < E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms < E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms < I: If#= 0 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usblp < E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms < E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms < E: Ad=83(I) Atr=03(Int.) MxPS= 4 Ivl=1ms
If you see something like
Driver=<none> then the USB
printer driver is not loaded on your machine. Try
Disconnect and reconnect the printer, and check the devices
cat /proc/bus/usb/devices | grep usblp
It should now say
If nothing up to this point worked, you can try to load all the USB modules by hand, and start over.
modprobe usbcore.o usb-uhci.o usb-ohci.o printer.o
Most systems don't need both
If you have USB printing working, then you will need a node so that programs can communicate with the device. To see if a node has already been created
cd /dev find | grep usb
You should have an
lp entry, similar to one of these.
/dev/usblp /dev/usblp0 /dev/usb/lp0
lp entries indicate a parallel port, not a
lp0 lp1 lp2 lp3
If the USB printer node is not there, then you will need to create it.http://www.linux-usb.org/USB-guide/x342.html
If the printer still won't print to the device, try deleting
it and recreating node. Old versions of the USB manual contained
mknod command, and your system may have the incorrect
device numbering. Use the
rm command to delete
the node, and
mknod to recreate the node according to
the USB manual
Browse your local machine at port 631, and if a printer web interface comes up, you have CUPS installed and running on that machine.
As root, you can find out if you have CUPS installed.
which cupsd # /usr/sbin/cupsd
If you look at the file
/etc/printcap and the printer names do not
have any lines following them, you are most likely using CUPS. The top of
the file may also say it was generated by cupsd.
If you are using any other spooler, the
will contain many more lines for each printer entry.
p2raw|wmakerp2-raw|wannamaker_p2_raw_postscript_files|[Apple_Laserwriter16/600PS]:\ :lp=:mx#0:rm=wmakerp1.oit.duke.edu:\ :rp=text:\ :sd=your_spool_directory_path_name_for_p2raw:\ :sd=/usr/spool/lpd/p2raw :lf=p2_raw_printer_log_file_pathname :lf=/usr/spool/lpd/p2rawlog
The fuser is not able to maintain temperature.
This can be caused by running the program
which is a proprietary application. Please obtain a license from
easy software. See http://www.easysw.com/printpro/faq0002.html
The Zero One Technology print server is an arm processor running Linux. They are available with both centronics and usb connectors, and they work well with Linux. They are also very stable, and do not require reboots.
The models known to be working are:
If you have <fn>tftp</fn>, the print server supports tftp'ing the MAC address to upload and download a configuration file. In this case, the MAC address is simply the “Node ID” printed on the print server. Refer to the manual on the included CD-ROM for directions.
To use a web browser, you will need the print server's IP address. The print server comes with a fixed IP address. To discover what it is, you can do the following steps.
1. Download and install arpmonitor which is locate at http://planeta.terra.com.br/informatica/gleicon/code/index.html
2. Start arpmonitor, so that it will monitor the wireless network, and report activity to STDERR. This program must be run as root.
arpmonitor -i eth0 -e
3. Power cycle (turn off, then back on) the print server.
4. Monitor the arpmonitor output for new IP addresses. IIIRC, the print server announced itself as <fn>192.168.4.1</fn>.
5. Change your wireless network settings so you are on the same subnet. I would recommend, as root, to bring your primary network interface down.
ifconfig eth0 down
Now bring up the interface on the same subnet as the router.
ifconfig eth0 192.168.4.2 up
6. Start a web browser, and in the URL bar, type the IP address of the printer.
7. Now you can configure the printer. I would recommend keeping a static IP address, but change the IP address so the printer is on the same subnet that you normally use with wireless printing.
8. CUPS Configuration: To configure CUPS is simple. All the steps except the URI entry should be self explanatory. Configure CUPS using the local interface http://localhost:631 click on “Printers” and then “Add Printer”.
9. CUPS URI: While several backends work, I only tested the LPD backend. For Device select <fn>LPD/LPR Host or Printer</fn>, and click continue. The URI you want to type in is
For example, since I configure my print server to be on <fn>192.168.254.1</fn>
Set up samba on GNU/Linux to handle the Windows clients.
Setup Postscript emulation by installGhostScript/GSview for windows.
These pages will give you a general idea of how to setup postscript emulation.
If you have a PostScript version 2 or 3 compatible printer, and the printer is not listed on openprinting.org, then most likely the printer manufacturer offers a driver on their installation disk.
Locating the driver is not easy. What you are looking for is a
text file with an extension
.ppd or similar. The
file may be “hidden” in a zip archive, which can have an extension
.exe. You can use the program
unzip to unzip
both of these types of archives, and search the files for a PPD.
You can also try contacting the manufacturer technical support, and searching their website for a downloadable driver.
If you are unable to find a PPD file from the manufacturer, try using a PPD file from a printer with similar features to yours. It is important to match resolution.
Finally, a Adobe provides a number of PPD files.http://www.adobe.com/support/downloads/product.jsp?product=44&platform=Windows
It's possible that the Samba
*.tdb files, used by Samba to
store print queue info which a native NT print server would store in
the “Registry”, got corrupted when the power failed.
tdbtool may be able to verify that.
tdbtool is a Samba developer
tool and not compiled or installed by default.
Either you have a *.tdb backup, created with
tdbbackup, or you need to
re-install all queues…
Yes. See [kpfeifle/LinuxKongress2002/Tutorial/IX.CUPS-Samba/IX.Samba-HOWTO-Collection-Chapter-7.html CUPS and SAMBA Howto]
Tip: If you use Foomatic or Gimp-Print PPDs, check the
in the PPDs and if they contain a comma, remove the comma (will be fixed
later in Foomatic).
It is easy to use the incorrect URI. They are case-sensitive. The URI should look like this:
Probably your samba configuration
smb.conf is not allowing
access. If you do not enable a guest account, then only clients with an
account on your GNU/Linux machine will be able to connect and share
files/services. You should also check your hosts deny and hosts allow
statements in your samba configuration, to verify that other machines on
your local network are permitted to connect. Finally, I believe your
printer entries must specify
public = yes and
printable = yes.
If all this appears to be in order, there is still the issue of password encryption. You must make sure that both the clients and your GNU/Linux machine are treating passwords the same (encrypted or unencrypted).
Anything that parses a PPD expects two formats for
the internal naming of resolutions: either
The Gimp-Print PPDs use a sensible but non-offical internal naming format, like 360sw, 720x360sw and 360swuni.
CUPS, being more flexible than offical Postscript, parses these internal
names without trouble, so the web interface works without problems.
However, the PostScript Generic driver for Windows does not recognize the
resolution format, fails to parse it and puts up
300dpi as default in
the resolution combo box because it doesn't know what else to do.
Modify the Epson Stylus Color 900 PPD so that the internal names follow the standard format. I.E.:
360x360dpi instead of 360sw 720x720dpi instead of 720sw
In the special options:
365x365dpi instead of 360swuni (the unidirectional option)
Because the 365x365dpi is an internal name only, the combo box in the
Windows and CUPS setup still shows
360dpi Unidirectional as the choice.
And ultimately it does not matter, because it adds the proper HWResolution
command to the PS file.
1. Click the
Printer Setup button in the printing dialog of the GIMP
2. In the upcoming dialog choose
PostScript Level 2 as printer model
3. Very Imported: Remove the
-oraw from the printing command
4. Choose the PPD file of your print queue
the printer´s PPD file.
5. After clicking
OK you will be able to choose the most important options for
Print the Invoking Summary.
lpr -o docs /proc/cpuinfo
It is a list of
-o options you can
pass to the
lpr command. You can tell your printer to print
lpr -o docs /proc/cpuinfo or
lpr -o docs LaTeXConfig.lyx
LaTeXConfig.lyx can be any file.
Here is the template for this command:
lp -P<queue-name> -o docs <some-random-printable-filename>
If you do not know the port number or the protocol of the printer's network interface, do
nmap <IP or host name of the printer>
This lists all open ports of the box.
We recommend you use the TCP/Socket protocol, because it requires only the
For the LPD protocol you would need the printer's internal queue name, and there is no known way to auto-detect it.
For the TCP/Socket protocol simply use a CUPS URI like
socket://<printer's hostname or IP>:<port>
The most frequently used port for that is
Many people have found that GNU/Linux will not detect their parallel port unless they disable “Plug and Play” in their PC BIOS. See [howto/kernel.html Chapter 4] of [howto/kernel.html http://www.openprinting.org/howto/kernel.html]
is what you are looking for. Some driver modifications may be required.
Inkjets (which with free operating systems)
Both come with a tray for printing CDs. This tray is a more or less Letter-sized plastic board with a hole for a CD in it. You can print on the CD the same as you would paper.
You must put the paper thickness lever into the envelope or CD position depending on the thickness of the material.
On the Epson Stylus Pro large-format printers you simply proceed as with single paper sheets.
The GhostScript version of align.ps is missing a necessary header, and the spooler fails to correctly recognize it as PostScript.
This is not a printing problem. It is either a hardware problem, or a kernel (software) problem.
Check whether the printer appears as a SCSI device.
If so, you need a CUPS version with SCSI backend (the current 1.1.x has it): Check for the existence of
When you have this file (with or without update of CUPS), restart the CUPS daemon and do
If there is a SCSI entry, this is the entry for your printer. Use this URI when setting up your print queue.
If this does not help, please post on a Forum of CUPS:http://www.cups.org/newsgroups.php
The only solution is that you buy a USB controller PCI card.
There are no known USB adapters for the PS/2 mouse port. There are also no low level driver in the Linux kernel which allow printing through the PS/2 port.