Still screwing with HP1020

Wed Jan 28 21:11:40 UTC 2015

On Wed, 2015-01-28 at 18:47 +0000, Colin Law wrote:
> On 28 January 2015 at 14:40, Chris <cpollock at embarqmail.com> wrote:
> > Yes, I'm still messing with this printer and getting more and more
> > annoyed. The printer is seen by CUPS
> >
> > Description:    Hewlett-Packard HP LaserJet 1020
> > Location:       localhost
> > Driver: HP LaserJet 1020 Foomatic/foo2zjs-z1 (recommended) (grayscale,
> > 2-sided printing)
> > Connection:     usb://HP/LaserJet%201020?serial=JL1F0DC
> > Defaults:       job-sheets=none, none media=na_letter_8.5x11in sides=one-sided
> >
> > Last night running 'sudo lsusb' the printer wasn't seen:
> >
> > Bus 002 Device 005: ID 04e8:6865 Samsung Electronics Co., Ltd GT-I9300
> > Phone [Galaxy S III] (PTP mode)
> 
> I see you had your phone plugged in at the time the printer was not
> seen.  Have you checked that is just coincidence?
> 
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 008 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for
> > Business
> > Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 001 Device 009: ID 1058:0830 Western Digital Technologies, Inc.
> > Bus 001 Device 008: ID 0bc2:2120 Seagate RSS LLC
> > Bus 001 Device 007: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port
> > Hub
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 003 Device 006: ID 1241:1166 Belkin MI-2150 Trust Mouse
> > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> >
> > This morning I again did three things, 1)removed the toner cartridge and
> > reinserted (for some reason this worked last night) but not today.
> > 2)Removed power to it and powered up again, no joy. 3)Tried another USB
> > port, nothing so I reinserted into the original USB port and the printer
> > initialized. I again ran 'sudo lsusb' and the printer now shows up:
> >
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 008 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for
> > Business
> > Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 001 Device 009: ID 1058:0830 Western Digital Technologies, Inc.
> > Bus 001 Device 008: ID 0bc2:2120 Seagate RSS LLC
> > Bus 001 Device 007: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port
> > Hub
> > Bus 001 Device 015: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 003 Device 006: ID 1241:1166 Belkin MI-2150 Trust Mouse
> > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> >
> > Great, I thought, so I went to CUPS web interface and tried to print a
> > test page:
> >
> > processing since
> > Wed 28 Jan 2015 08:27:02 AM CST
> > "Waiting for printer to become available."
> >
> > This had me so annoyed last night I had a hard time sleeping! I have no
> > idea what the heck I'm missing in regards to getting this thing to work
> > again!
> 
> If sometimes the printer is seen in lsusb and sometimes not then it is
> likely an intermittent hardware problem.  The fact that it sometimes
> works and sometimes not even when it is seen is also suggestive of
> hardware.
> 
> I suggest you run
> tail -f /var/log/syslog
> which will show you that file and will show new stuff as it happens.
> Then plug the printer usb in.  You should see it being recognised.
> Unplug it and it should show it removed.  Plug it in again.  Try
> wiggling the lead at each end, see if it comes and goes.  If you see
> any problem try it in a different usb port.  I don't know whether you
> have said, but if you are plugging it into a hub then try plugging it
> in direct.
> 
> Colin
> 

Hi Colin, the output of the above command is here
http://pastebin.com/hhyZfv3v
Note the kernel: [62592.864034] usb 1-1: device descriptor read/64,
error -110 and the kernel: [62643.860227] usb 1-1: device descriptor
read/8, error -110 I've tried finding these on Google to no avail. The
printer is plugged in direct to the computer. I have a hub connected but
only my two backup drives are connected to it. Turning it off then on
again will apparently initialize it however CUPS web interface shows:

processing since
Wed 28 Jan 2015 03:03:26 PM CST 
"Waiting for printer to become available."

That's what gets me if lsusb sees the printer and it's apparently
initialized and CUPS is waiting for the printer to become available (it
should always be available) why isn't it printing. Here is some more
output of tail -f /var/log/syslog

http://pastebin.com/j15PQyLK

This is from when the printer had a print job in queue and I turned it
off then on again. 

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
14:46:00 up 17:50, 3 users, load average: 0.16, 0.23, 0.40
Ubuntu 14.04.1 LTS, kernel 3.13.0-44-generic