linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike <mike@kordik.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: no /dev entry for printer when it is out of ink
Date: Tue, 22 Nov 2005 01:10:54 +0000	[thread overview]
Message-ID: <4382701E.6020607@kordik.net> (raw)
In-Reply-To: <4381C39A.6080907@kordik.net>

[-- Attachment #1: Type: text/plain, Size: 4662 bytes --]

Thanks for the help!

The rule I wrote is supposed to create /dev/printers/EPC80. It was 
creating this directory, up until recently.

udevmonitor output:
UEVENT[1132621451.657266] 
add@/devices/pci0000:00/0000:00:02.1/usb2/2-1/2-1.3
UEVENT[1132621451.661395] 
add@/devices/pci0000:00/0000:00:02.1/usb2/2-1/2-1.3/2-1.3:1.0
UEVENT[1132621451.669255] add@/class/usb/lp0
UDEV  [1132621454.756357] 
add@/devices/pci0000:00/0000:00:02.1/usb2/2-1/2-1.3
UDEV  [1132621456.822296] add@/class/usb/lp0
UDEV  [1132621458.547985] 
add@/devices/pci0000:00/0000:00:02.1/usb2/2-1/2-1.3/2-1.3:1.0

dmesg:
usb 2-1.3: new full speed USB device using ohci_hcd and address 18
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 18 if 0 
alt 0 proto 2 vid 0x04B8 pid 0x0005


lsusb -v:
Bus 002 Device 018: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x04b8 Seiko Epson Corp.
  idProduct          0x0005 Stylus Printer
  bcdDevice            1.00
  iManufacturer           1 EPSON
  iProduct                2 USB Printer
  iSerial                 3 0HSLL0108041158030
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         7 Printer
      bInterfaceSubClass      1 Printer
      bInterfaceProtocol      2 Bidirectional
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
  Language IDs: (length=4)
     0409 English(US)

I understand what you are saying about udev not communicating with the 
printer. It appears to me that the kernel is telling udev that the 
printer is connected but why isn't udev creating the device directory entry?

Thanks

Mike

Kay Sievers wrote:

>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_id=7628&alloc_id=16845&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
>
>  
>


[-- Attachment #2: Type: text/html, Size: 9728 bytes --]

  parent reply	other threads:[~2005-11-22  1:10 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
2005-11-22  1:10 ` Mike [this message]
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=4382701E.6020607@kordik.net \
    --to=mike@kordik.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).