Re: [tlug] Printer Not Responding

["Josh Glover" <jmglov@example.com>]

On 16/04/06, Dave M G <martin@example.com> wrote:

> Here is the output of "tail -f /var/log/messages":
>
> drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 6 if 0
> alt 0 proto 2 vid 0x04A9 pid 0x1094

This looks good. It means that the usblp kernel module has identified
that you have plugged a printer in, and has assigned it to a device
node.

Please show us the output of:

sudo find /dev -name usblp0 | xargs sudo ls -l

> I'm pretty sure the USB system in my computer is working on a hardware
> level. I have a couple other devices, such as a Wacom tablet and Kenwood
> USB sound device which are working fine.

Ah yes, I had forgotten that the Wacom tablet was USB.

> Josh said:
>
> > [1] Dave, please make sure to attribute properly so we know who said
> > what when and to whom. ;)
>
> Sorry, was I not doing this correctly?

Not in the message I replied to. The convention for inline replies
(the sort that we encourage, nay, require, on TLUG) is to start your
reply with a line like:

"On 16/04/06, Dave M G <martin@example.com> wrote:"

The wonderful thing about that is that when someone replies to your
reply, they can quote your attribution, and everyone knows who is
talking. Placing a "Josh said:" above the portion that you are quoting
is OK, but how do we know which Josh said it (there are at least two
on this list, for instance). Stephen Turnbull has an even fancier
attribution style, but you do not have to go that far. Doesn't your
email client have an option to automatically start replies with an
attribution line?

> I think I mentioned this before, but this is the status of my printer as
> shown in the CUPS interface:
> Description: Canon Pixus iP3100
> Location: Desktop
> Make and Model: Canon PIXUS iP3100 Ver.2.50x
> Printer State: idle, accepting jobs, published.
> Device URI: file:///dev/usblp0
>
> Is that device URI matching my actual /dev file correctly? I'm not sure
> if all those backslashes are a healthy thing or not.

Well, those "backslashes" are actually *front*slashes. :) And yes,
that is correct for a file URI. Just as for an HTTP URI, the protocol
is identified by the characters before the "://", and the rest is the
resource identifier. So "http://www.tlug.jp"; actually means: "use the
HTTP protocol to connect to the www.tlug.jp resource". And
"file:///dev/usblp0" means, "use the file protocol to connect to the
/dev/usblp0 resource".

If we are lucky, this is just a permissions problem. CUPS is a
notorious pain in the arse when it doesn't "just work", because it
often does not give any indication what the problem is.

-Josh