HP LaserJet Professional 1606dn Device communication error

[Viktor Mojr]

Printer can be found and visible in network (school network, 802.1x) by my linux PC (mdv 2010.2), configuration page is reachable in browser by typing its IP. Newest HPLIP alredy downloaded and installed, additional plugin also installed and there is still "Device communication error". It's imposible to print anything.

[Srikanth (srikanth-lokare)]

Hi,

Can you please run "hp-check -t" command from the terminal and post the complete output here.

Thanks and Regards,
Srikanth Lokare

[Raghavendra (raghavendra-chitpadi)]

Good work Srikanth. I appreciate you keeping tab on the customer issues.

Thanks
Raghu

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Lokare, Srikanth
Sent: Tuesday, May 03, 2011 9:11 AM
To: Chitpadi, Raghavendra
Subject: [Bug 775879] Re: HP LaserJet Professional 1606dn Device communication error

Hi,

Can you please run "hp-check -t" command from the terminal and post the
complete output here.

Thanks and Regards,
Srikanth Lokare

--
You received this bug notification because you are subscribed to HPLIP.
https://bugs.launchpad.net/bugs/775879

Title:
  HP LaserJet Professional 1606dn Device communication error

Status in HP Linux Imaging and Printing:
  New

Bug description:
  Printer can be found and visible in network (school network, 802.1x)
  by my linux PC (mdv 2010.2), configuration page is reachable in
  browser by typing its IP. Newest HPLIP alredy downloaded and
  installed, additional plugin also installed and there is still "Device
  communication error". It's imposible to print anything.

[Viktor Mojr (mojrv)]

hp-check -t

HP Linux Imaging and Printing System (ver. 3.11.3a)
Dependency/Version Check Utility ver. 14.3

Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper
dependencies are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball
has the proper dependencies installed to successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies).

Saving output in log file: hp-check.log

Initializing. Please wait...

---------------
| SYSTEM INFO |
---------------

Basic system information:
Linux a255-mojrv 2.6.33.7-desktop586-2mnb #1 SMP Mon Sep 20 18:19:58 UTC 2010 i686 i686 i386 GNU/Linux

Distribution:
mandriva 2010.2

Checking Python version...
OK, version 2.6.5 installed

Checking PyQt 4.x version... ...

[Viktor Mojr (mojrv)]

Thanks for quick answer, Srikanth.

[goutam kodu (goutam-hplip)]

Hi,

Can you provide us some more debug information.

Please follow the below steps to provide the same

1.Open the file /etc/cups/cupsd.conf in write permissions.
$su -c "vim /etc/cups/cupsd.conf "
 Change LogLevel warn to LogLevel 15 and below that line add HPLogLevel 15.

2. Restart the cups
$su -c"/etc/init.d/cups restart"

3. Enter the hplip source folder and open the file io/hpmud/hpmudi.h and uncomment the line containing this
//#define HPMUD_DEBUG and save it.

4.Open the terminal and change directory to hplip_source_directory and run "make" and su -c "make install" .

5.make the log file empty
$su -c "cat /dev/null > /var/log/messages os syslog "

6. Send a print job or print a test page.

7 When you get the "Device communication error" . Copy the contents of log file in text file and attach me that file
$su -c "cat /var/log/messages or syslog > debug.txt"

Attach me the debug.txt file.

Sorry for having you to do so much of work, but we are not able to see this problem in-house. Please let us know if you find any difficulty in obtaining the debug information.

Thanks & Regards,
Goutam Kodu