I have set up a HP P1005 under Slackware-12.2 and Slamd64-12.2 on 2 separate boxes. Slamd64 is a 64 bit port of slack. For the record, the foo2zjs docs are excellent. Slackware & slamd64 use /etc/rc.d/rc.cups and http://localhost:631
for configuring a printer. It offers kde, not gnome; it also has xfce as a 'low cholesterol window manager' and my personal choice.
This printer replaces my Epson Stylus C70, and works this way: I can turn on, rapidly download the firmware, the cat <fw> >/dev/usb/lp0 >/dev/usb/lp0 (a very simple instruction is erratic). If the firmware goes down (orange light for a few secs) it prints.
After any length of standby, /dev/usb/lp0 vanishes. Here's the transaction in dmesg
usb 1-3: new high speed USB device using ehci_hcd and address 3
usb 1-3: New USB device found, idVendor=03f0, idProduct=3d17
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3: Product: HP LaserJet P1005
usb 1-3: Manufacturer: Hewlett-Packard
usb 1-3: SerialNumber: BB08HLP
usb 1-3: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3D17
usbcore: registered new interface driver usblp
I have no clue why /dev/usb/lp0 is gone and hoped you might know why, if not where. usblp.ko is still loaded. This occurs on 32 bit and 64 bit boxes, and never occurred with the Epson, so I conclude it's printer related. Printing is disabled, of course, and cups jobs vanish I then get
/dev/usb/lp0: No such device in the logs
kernel versions are 188.8.131.52 & 184.108.40.206 hplip never heard of slackware, and bombs out. I tried it before I found foozjs on the 64 bit machine, and it's firmware.py is sometimes the only way to get firmware down to the printer.
The word 'sometimes' is most un-linux like, but this is the situation.
Finally a newbie question: When the P1005 throws an error (e.g. out of paper), and sits there with the orange light on, what's the recovery procedure.
Edited 2 time(s). Last edit at 05/14/2009 02:49PM by rickrich.