SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You probably need to modify the device reference in the command. The command states /dev/lp0, however, I think it would be on /dev/usb/printer0 instead for a USB printer. You can probably use the "dmesg" command to review the kernel buffer messages. It might state what was assigned when the kernel or module detected the printer.
well, appended to this message are the contents of my /dev/usb/ directory. unfortunately i don't appear to have a /dev/usb/printer ... does this mean it was not detected when i turned the machine on (i made sure the printer was plugged in and turned on)?
so one another thing: all the entries in /dev/usb/ are highlighted in yellow except for /dev/usb/lpo (seems to be a lowercase letter O and not a zero). does this mean anything?
when i try to point the command to that location the command appears to run successfully but the printer just sits there silent.
You are correct, printer0 doesn't exist on mine either! Hmm, I can only figure it must of been another distro, like SuSE that I use at work.
I connected a USB printer converter device that uses the printer.o module. The module detected and responded with an assignment on "usblp0" without any slashes and a zero. That doesn't exist either. But the device /dev/usb/lp0 exists. If your /dev/usb/lpo is a char device on major 180 minor 0 then it is the correct device just rename it to lp0. Or you can delete it and recreate it;
mknod /dev/usb/lp0 char 180 0
But from the listing you provided I see both a lp0 and lpo. The lpo may be just a file that was created from a mistyped command as the output. Recommend deleting the lpo. Below is what a long listing should look like for the first two lp devices to verify the settings for the devices.
bash-2.05a# ls -l /dev/usb/lp*
crw-rw---- 1 root lp 180, 0 Mar 25 2001 /dev/usb/lp0
crw-rw---- 1 root lp 180, 1 Mar 25 2001 /dev/usb/lp1
If you are using modules, check to see if the "printer" module is loaded by using the command "lsmod". Not sure on the hpijs driver, if module, then perhaps it needs to be loaded, as well or instead of "printer". Best to review the docs for it. You may need to "modprobe hpijs" or "modprobe printer". If it needs to be loaded each time you boot, then you may consider adding the command to the /etc/rc.d /rc.local file.
If you want to remove the jobs from the queue to empty it, since you may not know for sure where it is attempting to print then;
should list the jobs and the job numbers.
lprm -Plp #xxx
where xxx is the job numbers listed in the previous command.
# Copyright (c) 1983 Regents of the University of California.
# All rights reserved.
# Redistribution and use in source and binary forms are permitted
# provided that this notice is preserved and that due credit is given
# to the University of California at Berkeley. The name of the University
# may not be used to endorse or promote products derived from this
# software without specific prior written permission. This software
# is provided ``as is'' without express or implied warranty.
# @(#)etc.printcap 5.2 (Berkeley) 5/5/88
# DecWriter over a tty line.
#lp|ap|arpa|ucbarpa|LA-180 DecWriter III:\
# Generic printer:
# typical remote printer entry
#ucbvax|vax|vx|ucbvax line printer:\
# HP Laser jet plus
#lp|Generic dot-matrix printer entry:\
OK, the printap file reveals that it is the stock printcap setup for the device on /dev/lp0. So a spooler filter has not been setup as yet.
Now, to your dmesg output. I can see where you unloaded the module and reloaded the module. But if you disconnected the printer and reconnected it, then I am not seeing anything there. Unless it is that last line on printer.c. When I disconnect and reconnect devices I see vendor and product ID codes for the device and if a module isn't present then reports it as not claimed. An example from my output.
hub.c: USB new device connect on bus2/1, assigned device number 7
usb.c: kmalloc IF cd40d680, numif 1
usb.c: new device strings: Mfr=0, Product=0, SerialNumber=0
printer.c: usblp0: USB Bidirectional printer dev 7 if 0 alt 1 proto 2 vid 0x0711 pid 0x0302
usb.c: usblp driver claimed interface cd40d680
The same basic kind of output as before. OK, then try the command "lspci". It will provide a listing of the PCI devices that the kernel is able to see on the system.
An example of my VIA Apollo:
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 16)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 16)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:09.0 Unknown mass storage controller: Promise Technology, Inc. 20262 (rev 01)
00:0a.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage XL AGP 2X (rev 65)
As you can see it reports two USB Controllers, for a total of four USB connectors. See if your system provides similar.
If you have multiple devices attached it can be very difficult to read, but I think each device section starts with the letters T:. Sometimes it includes an S: line that inlcudes a plain text string to really help with the ID. As you can see from above though this device does not. But perhaps your HP printer will. The key above is the I: lines where it contains the word "print" and the device is usblp.
If you only have two "T:" sections that describe a USB root hub, then nothing is being detected by the root hub. Check the cable and stuff. Maybe even the BIOS IRQ assignment, etc. The root hubs looks something like: