HP LaserJet P1005 / P1007 :  foo2zjs - foo2hp - foo2xqx - foo2lava - foo2qpdl - foo2oak
Support for linux printer drivers
The fastest message board... ever.
 
New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 07, 2013 08:11AM

Hi. I got a Samsung 350V (Intel Panther Point chipset) and the usb is fussy. I have kernel 3.7.1, & slackware 14, and foo2zjs installed as per docs. Rid myself of system-config-printer. Only strange one is that the hplj1000 script in /etc/hotplug/usr had the wrong FW directory (foo2zjs) whereas sihpP1005.dl is in foo2xqx.

xhci_hcd is throwing hysterical messages. From dmesg |tail
[ 2566.045906] usb 3-2: New USB device found, idVendor=03f0, idProduct=3d17
[ 2566.045912] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2566.045917] usb 3-2: Product: HP LaserJet P1005
[ 2566.045921] usb 3-2: Manufacturer: Hewlett-Packard
[ 2566.045925] usb 3-2: SerialNumber: BB08HLP
[ 2566.046099] usb 3-2: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 2566.046105] usb 3-2: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 2566.046425] xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
[ 2566.046524] usb 3-2: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 2566.046533] usb 3-2: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 2566.046841] xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
[ 2566.046956] usblp0: USB Bidirectional printer dev 10 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3D17
[ 2571.898075] xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
[ 2571.899668] xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
[ 2571.899835] xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
[ 2571.900057] xhci_hcd 0000:00:14.0: WARN: short transfer on control ep

/var/log/messages:
Jan 7 12:49:02 RoseViolet kernel: [ 2566.032958] usb 3-2: new high-speed USB device number 10 using xhci_hcd
Jan 7 12:49:02 RoseViolet kernel: [ 2566.045906] usb 3-2: New USB device found, idVendor=03f0, idProduct=3d17
Jan 7 12:49:02 RoseViolet kernel: [ 2566.045912] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 7 12:49:02 RoseViolet kernel: [ 2566.045917] usb 3-2: Product: HP LaserJet P1005
Jan 7 12:49:02 RoseViolet kernel: [ 2566.045921] usb 3-2: Manufacturer: Hewlett-Packard
Jan 7 12:49:02 RoseViolet kernel: [ 2566.045925] usb 3-2: SerialNumber: BB08HLP
Jan 7 12:49:02 RoseViolet kernel: [ 2566.046956] usblp0: USB Bidirectional printer dev 10 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3D17
Jan 7 12:49:02 RoseViolet logger: loading HP Device 003 010
Jan 7 12:49:02 RoseViolet mtp-probe: checking bus 3, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Jan 7 12:49:02 RoseViolet mtp-probe: bus: 3, device: 10 was not an MTP device
Jan 7 12:49:02 RoseViolet /etc/hotplug/usb/hpljP1005: foo2zjs: loading HP LaserJet P1005 firmware /usr/share/foo2xqx/firmware/sihpP1005.dl to /dev/usb/lp0 ...
Jan 7 12:49:02 RoseViolet /etc/hotplug/usb/hpljP1005: foo2zjs: ... download successful.

GET_DEVICE_ID string:
MFG:Hewlett-Packard;MDL:HP LaserJet P1005;CMD:HBS,PJL,ACL;CLS:PRINTER;DES:HP LaserJet P1005;FWVER:20090916;


But when I try to print:

Queue Name Description Location Make and Model Status
HP_LaserJet_P1005 HP LaserJet P1005 Dec's room HP LaserJet P1005 Foomatic/foo2xqx (recommended) Paused - "Unable to send data to printer."

and the whole "Administration" page on cups isn't working.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 07, 2013 08:26AM

"Only strange one is that the hplj1000 script in /etc/hotplug/usr had the wrong FW directory (foo2zjs) whereas sihpP1005.dl is in foo2xqx."

HP 1005 == foo2zjs
HP P1005 == foo2xqx

There is a difference;

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 07, 2013 09:53AM

What does this say:
$ cd foo2zjs

$ foo2xqx-wrapper testpage.ps > xxx.prn

$ ll xxx.prn
-rw-rw-r-- 1 rick rick 92675 Jan  7 08:49 xxx.prn

$ usb_printerid /dev/usb/lp0
MFG:Hewlett-Packard;MDL:HP LaserJet P1005;CMD:HBS,PJL,ACL;CLS:PRINTER;DES:HP LaserJet P1005;FWVER:20090916;

$ cp xxx.prn /dev/usb/lp0



Edited 2 time(s). Last edit at 01/07/2013 07:46PM by rickrich.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 07, 2013 02:30PM

Goes OK until
cp xxx.prn /dev/usb/lp0
which hangs. I found that with lsof. lsof |grep lp0 gives me a line about cp hung.

It's loading the firmware wrong, I think. The firmware is also loaded twice. The second time the 'cat' instruction hangs there. The orange light comes on when the firmware is loading (OK) but stays on and the second 'cat' dowsn't succeed(Not OK). The light goes green after 30 seconds but the printer is dead. I get the "device busy" error until I kill the outhanging cat instruction. Then usb_printerid answers. I can print from the printer with anther box. The firmware checks out with md5sum with a backup from that other box.

I can swap in files wholesale from the backup, if you know what might be the issue.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 07, 2013 03:23PM

Power down, and then power up the printer. Wait for the orange light to go green, then do:

$ cp xxx.prn /dev/usb/lp0

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 08, 2013 12:18PM

When the light goes green, there is a hung cat process there from the hplj1000 script trying to send the firmware. The error "Device busy /dev/lp0" If i kill that process, the printer is unresponsive.

The firmware is ok - I have md5summed it from a backup. Could the xhci-hcd module be screwing this up? It's the only difference I can think of and it seems like a comms problem.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 08, 2013 12:50PM

So, put it on another controller.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 09, 2013 04:08AM

The printer? I did put it on another box running foo2zjs and it works no problem. I think I mentioned that in post #4. I blacklisted xhci-hcd but it made no @#$£%! difference. I'll try with the module removed from the kernel tree, or put an 'install' line in modprobe.d and see how I get on.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 09, 2013 06:59AM

OK. Eliminated some things.
I tried to get xhci-hcd out of 3.7.1 with install lines, etc. Managed to kill the boot that way! I came at it with Slackware's original 3.2.29 kernel, and that doesn't have xghci-hcd. It still jams. I got quick about checking and realised from the PID number that it's the _first_ download of the firmware that hangs the cat or cp process. But another box on a 3.2.29 kernel prints from the printer.

I am led to the conclusion that it's a comms problem on the box. It's an Intel Panther Point chipset, and I have no experience of it. The fact that it's cat or cp which hangs clears your software for the moment. The xhci-hcd module has the disposition of some high strung thoroughbred - a bit hysterical at best. It won't let go when it isn't wanted, which is a pain. uhci-hcd never loads.

Options: ReplyQuote
Probably as far as I will get ...
Posted by: business_kid ()
Date: January 09, 2013 03:02PM

Had another go.
I eliminated the ssd by adding in an sdcard, mouning it first on /dev/usb, and then on /usr/share/foo2xqx/firmware :-D. SSD is not a source of problems. Firmware travels ok.

If I suspend the box, power up the printer and resume, I can kill the hung cat process that results and usually get away with loading the firmware. Cups still says "Unable to send to /dev/usb/lp0" and refuses to print. Plug in the printer, or power it on while plugged in, and it hangs 100% of the time. Should we try inserting a wait in the script to allow the printer to wake up before we hit it with firmware?

Even when cups is saying "Unable to send to /dev/usb/lp0" cat of firmware succeeds by itself. Lastly,
lp <ghostscript's> tiger.eps compains that no printer is set as default. Do I have to reinstall system-config-printer to get the admin stuff in cups working. With Slackware, I can explode the package and only add back what I need of it. My user is in the lp group. I ran usermod -aG lp <me> to be sure and sent the firmware as my luser.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 09, 2013 03:20PM

$ man lpoptions

Options: ReplyQuote
[SOLVED] Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 10, 2013 06:22AM

Surprise - I'm going, after a fashion. One show stopper was that the perms on /etc/cups/* were wrong, so lusers couldn't read :-/. I took the lazy way out and replaced /etc/cups/{printers.conf,printers.conf.O,cupsd.conf} with known working files, made the rest root:lp and 0664.

Turning on the printer while plugged in after an error always sthrows an error, and killing the hung cat process doesn't help.

Coming along with the printer on, but no firmware lets me in. If it hangs, I can kill the cat process and resend the firmware. I imagine the ssd needs a delay in the script because ACCESS IS TOO FAST. The printer might be getting firmware while reser is still on. Changing to the sdcard for 218k of firmware didn't slow it appreciably.

xxx.prn is the Redhat Printconf Test Page, and I even got a page out of Libreoffice!

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 11, 2013 05:44AM

Now today, I can't load the firmware for love or money. if I power up and plug in, The cat $fw > $dev hangs, then the printer is unresponsive. This worked fine last evening. If I cycle power, cat hangs and the printer is unresponsive. It won't accept a second attempt at loading firmware. Mind you, it's a bit cooler today, and the sun has come out from behind a cloud . . .but it's not shining on the printer yet :-/.

EDIT: I'm seeing Error 71 - protocol error



Edited 1 time(s). Last edit at 01/11/2013 10:09AM by business_kid.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 11, 2013 10:34AM

This is actually a bug. Your firmware loading setup is not working with an ssd attached.

I got going with a workaround. The cure was
chmod -x /etc/hotplug/usb/hplj1000

and every time the printer comes on (and settles)
cat /usr/share/foo2xqx/firmware/sihpP1005.dl > /dev/usb/lp0

For the record, the hdparm is about 450Mb/S on the disk. Throughput is low, so after I try once, the firmware is in the cache. I feel a symlink going in to save a bit of typing, but you need to fix it. Intel Panther Point HM76 chipset.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 11, 2013 11:22AM

$ head ChangeLog 
2013-01-13      Rick Richardson <rick.richardson@comcast.net>
        * hplj1000: add a sleep 3

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 12, 2013 04:36AM

Can you email me the script, or throw up a url and I'll try it?

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: rickrich ()
Date: January 12, 2013 07:07AM

Tarball last modified: Fri Jan 11 10:21:20 2013 CST - ChangeLog

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: January 13, 2013 10:25AM

I put in a 'sleep 3' near the beginning of the script, and it works. It does repeatedly download the firmware, but I can live with that failing. Apparently after I print a few pages.

Options: ReplyQuote
Re: New Box, new problem w/P1005 on Slackware 14.
Posted by: business_kid ()
Date: April 03, 2013 01:12PM

business_kid Wrote:
-------------------------------------------------------
> I put in a 'sleep 3' near the beginning of the
> script, and it works. It does repeatedly download
> the firmware, but I can live with that failing.
> Apparently after I print a few pages.


This has moved on, so I came back for advice.
It sends the firmware twice, usually, and then prints. On my usb-3 ports particularly, it continually reloads firmware (twice) and throws the error.

thunar-volman: unsupported usb device type.

Now it's failing to recognize the printer. No firmware load. usb_printerid picks up the download of firmware Here's a chunk of the page log. 10 this morning - everything went fine. 17:00 in the afternoon - not one page printed.
http://pastebin.com/zn5vTQka

Options: ReplyQuote


Sorry, only registered users may post in this forum.
This forum powered by Phorum.