invalid Dot4ReverseReply packet size

[Tim Waugh]

Hi,

A Fedora user is getting no luck using their parallel port HP LaserJet
4000 with HPLIP:

https://bugzilla.redhat.com/show_bug.cgi?id=249191

They've tried 1.7.4a, 2.7.6 and 2.7.7, all with the same error messages
when trying to print a job:

Sep 21 16:47:10 banach parport0: io/hpmud/dot4.c 243: invalid
Dot4ReverseReply packet size: size=8224, buf=8192
Sep 21 16:47:10 banach parport0: io/hpmud/dot4.c 330: invalid DOT4InitReply: cmd=0, result=20#012, revision=0
Sep 21 16:47:10 banach parport0: INFO: open print channel failed; will retry in 30 seconds...
Sep 21 16:47:40 banach parport0: io/hpmud/pp.c 586: failed claim_pp fd=5: Invalid argument
Sep 21 16:47:40 banach parport0: INFO: open print channel failed; will retry in 30 seconds...

Could it be that the HPMUD_BUFFER_SIZE just needs to be larger?

Tim.
*/

[Suffield, David]

Hi Tim,
1284.4 support is problematic for Laserjets with EIO cards. Most of
these laserjets are networked so parallel and/or usb support was a minor
issue. Or users just used the CUPS "parallel" or "usb" backend instead
of the "hp" backend.

The work around for the "hp" backend is to print "raw" instead of over
1284.4. This can be done by setting the hp_laserjet_4000_series io_mode
from 6 to 1 in the models.dat file.

Since 1284.4 support is a problem for these laserjets, I going to make
this change permanent and use PJL to get laserjet status instead of PML.
Should be in a future HPLIP release.

-dave

-----Original Message-----
Of Tim Waugh
Sent: Friday, October 05, 2007 1:40 AM
Subject: [HPLIP-Devel] invalid Dot4ReverseReply packet size
Hi,
A Fedora user is getting no luck using their parallel port HP
https://bugzilla.redhat.com/show_bug.cgi?id=249191
They've tried 1.7.4a, 2.7.6 and 2.7.7, all with the same
Sep 21 16:47:10 banach parport0: io/hpmud/dot4.c 243: invalid
Dot4ReverseReply packet size: size=8224, buf=8192 Sep 21
16:47:10 banach parport0: io/hpmud/dot4.c 330: invalid
DOT4InitReply: cmd=0, result=20#012, revision=0 Sep 21
16:47:10 banach parport0: INFO: open print channel failed;
will retry in 30 seconds...
Sep 21 16:47:40 banach parport0: io/hpmud/pp.c 586: failed
claim_pp fd=5: Invalid argument Sep 21 16:47:40 banach
parport0: INFO: open print channel failed; will retry in 30 seconds...
Could it be that the HPMUD_BUFFER_SIZE just needs to be larger?
Tim.
*/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[Tim Waugh]

Hi David,

Thanks for the analysis.

Post by Suffield, David
The work around for the "hp" backend is to print "raw" instead of over
1284.4. This can be done by setting the hp_laserjet_4000_series io_mode
from 6 to 1 in the models.dat file.

Like this?:

-io-mfp-mode=6
+io-mfp-mode=1

Tim.
*/

[Suffield, David]

Actually I miss-spoke, should be like this:

-io-mode=3
+io-mode=1

sorry,

-dave

-----Original Message-----
Sent: Tuesday, October 09, 2007 1:44 AM
To: Suffield, David
Subject: RE: [HPLIP-Devel] invalid Dot4ReverseReply packet size
Hi David,
Thanks for the analysis.

Post by Suffield, David
The work around for the "hp" backend is to print "raw"

instead of over

Post by Suffield, David
1284.4. This can be done by setting the hp_laserjet_4000_series
io_mode from 6 to 1 in the models.dat file.

-io-mfp-mode=6
+io-mfp-mode=1
Tim.
*/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/