Re: Printing to HP Deskjet 940c
Wayne Topa wrote:
> lrhorer wrote:
>> I have CUPS setup under Debian "Lenny" an an AMD Athlon 64 x 2 CPU with
>> 4G
>> of RAM. I cannot get the system to print to my HP Deskjet 940c printer
>> attached via USB. The system says it sees the printer,
>
> What in the system sees the printer, the cups interface
> (http://localhost:631) or something in the logs?
>
> and the driver
>> seems to be properly installed, but if I send a print job to the printer,
>> it just sits there in the queue. This was working previously with an HP
>> PhotoSmart 3210 printer attached via the Ethernet LAN, but the PhotoSmart
>> printer died, so I need to use the 940c. Where should I start my
>> troubleshooting?
>>
>>
> 1. Did you use the cups interface to install the new printer, and remove
> the old one?
No, not that I recall. Certainly I did not remove the old printer, but as I
recall I just plugged the 940c in and CUPS recognized it was there.
Perhaps I previously installed the printer and just do not recall doing so.
> 2. What does lpstat -t show when run by root or a user?
RAID-Server:/etc# lpstat -t
scheduler is running
system default destination: DESKJET_940C
device for DESKJET_940C: usb://HP/DESKJET%20940C?serial=MX22C6D0Q3BH
device for PhotoSmartPrinter: socket://192.168.0.32:9100
DESKJET_940C accepting requests since Sun 07 Jun 2009 07:39:32 AM CDT
PhotoSmartPrinter accepting requests since Sat 30 May 2009 10:01:32 PM CDT
printer DESKJET_940C now printing DESKJET_940C-0. enabled since Sun 07 Jun
2009 07:39:32 AM CDT
printer PhotoSmartPrinter is idle. enabled since Sat 30 May 2009 10:01:32
PM CDT
DESKJET_940C-13 root 18432 Sat 30 May 2009 10:15:55 PM
CDT
DESKJET_940C-14 root 18432 Sat 30 May 2009 10:31:54 PM
CDT
DESKJET_940C-15 root 18432 Sat 30 May 2009 10:33:48 PM
CDT
RAID-Server:/etc#
> It should show what printer is 'seen' by cups.
It looks like it is there. When I pull or replace the USB cable, the status
changes accordingly.
> 3. If lpstat -t says it can't find the server, see a post by me about
> "Strange printer problems" on June 3.
It doesn't sound like the same issue, I don't think.
Reply to: