1 |
On Sunday 16 May 2010 02:56:23 Alex Schuster wrote: |
2 |
|
3 |
> Thanks, this made me install gutenprint which claims to support the |
4 |
> printer directly. I thought I had to use the iP4200 driver and hope it |
5 |
> would work. |
6 |
|
7 |
I think that gutenprint is the correct driver for your printer and this page |
8 |
also suggests the same: |
9 |
|
10 |
http://www.openprinting.org/printer/Canon/Canon-iP4000 |
11 |
|
12 |
However, this might have been the case before the latest cups version - so |
13 |
some further testing will be required (see below). |
14 |
|
15 |
> But my main problem is another one: How do I tell CUPS which device my |
16 |
> printer is? I tried usb:/dev/usb/lp0 (found this notation when googling |
17 |
> 'usb printer device uri'), but nothing happens when I try to print. |
18 |
|
19 |
This is the cups driver (in kernel) which ought to pick up your usb printer |
20 |
and use it without problems. However, according to your logs ... there seems |
21 |
to be a clash: |
22 |
|
23 |
> There is a message in syslog that is being repeated hundreds of times: |
24 |
> May 15 22:25:55 [kernel] usb 1-2: usbfs: interface 0 claimed by usblp |
25 |
> while 'usb' sets config #1 |
26 |
|
27 |
So, what happens if you build usblp as a module and you modprobe -rv ubslp? |
28 |
Does cups pick up your printer now? |
29 |
|
30 |
> And now it gets really crazy: In the printer overview I see not only the |
31 |
> 'iP5200' I just created, but also a 'iP52002' that has the device URI |
32 |
> 'usb://Canon/iP5200'. What did create this?! |
33 |
> |
34 |
> But printing to that does not work either. |
35 |
|
36 |
I suspect that this was created by the gutenprint driver that you installed. |
37 |
I believe that if you resolve the usblp error first then you'll know if |
38 |
gutenprint is necessary or if it will work. Some manual tweaking of the ppd |
39 |
file may also be needed to print in higher resolutions, but let's get it to |
40 |
print first. |
41 |
|
42 |
Stop press! |
43 |
|
44 |
I just checked again your first post: You are using cups 1.4 which accesses |
45 |
raw usb devices! Definitely remove usblp (or blacklist it and reboot if you |
46 |
don't want to recompile your kernel, or can't modprobe -r) and see if the cups |
47 |
back end picks up your printer on its own. |
48 |
|
49 |
HTH |
50 |
-- |
51 |
Regards, |
52 |
Mick |