All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: no /dev entry for printer when it is out of ink
Date: Mon, 21 Nov 2005 18:44:18 +0000	[thread overview]
Message-ID: <20051121184418.GA4881@vrfy.org> (raw)
In-Reply-To: <4381C39A.6080907@kordik.net>

On Mon, Nov 21, 2005 at 07:54:50AM -0500, Mike wrote:
> My printer has been working fine but now udev won't create a /dev entry 
> for it. I have used usbview, udevinfo, I have looked in the logs. 
> Everything says the printer is connected. The only thing I can think of 
> is that the printer is returning some sort of status to udev and it 
> decides not to create the node. I have a 4 color printer and I need the 
> /dev entry so escputil can connect and tell me which ink needs to be 
> replaced.
> 
> Assuming that this is a problem with udev not creating the node because 
> it is getting an error from the printer, I could solve this by replacing 
> all the inks.
> 
> The log doesn't have any udev messages to tell me it is not creating the 
> node yet there is no /dev entry. I have debug, in udev.conf, set to yes.

Udev does not care or ask the printer anything, it just reflects the
kernel's state.

What device node name do you expect to appear?

What does "udevmonitor" print, while connecting the printer?

What does "dmesg" tell about the printer after it was connected?

What does "lsusb -v" tell about the printer?

Kay


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id\x16845&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2005-11-21 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 12:54 no /dev entry for printer when it is out of ink Mike
2005-11-21 18:44 ` Kay Sievers [this message]
2005-11-22  1:10 ` Mike
2005-11-22  2:18 ` Kay Sievers
2005-11-22  3:08 ` Mike
2005-11-22  3:32 ` Kay Sievers
2005-11-22 23:28 ` Mike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051121184418.GA4881@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.