no /dev entry for printer when it is out of ink

no /dev entry for printer when it is out of ink

[Mike]

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.

Any ideas?

Thanks


-------------------------------------------------------
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

Re: no /dev entry for printer when it is out of ink

[Kay Sievers]

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

Re: no /dev entry for printer when it is out of ink

[Mike]

[-- 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 --]

Re: no /dev entry for printer when it is out of ink

[Kay Sievers]

On Mon, Nov 21, 2005 at 08:10:54PM -0500, Mike wrote:
> The rule I wrote is supposed to create /dev/printers/EPC80. It was 
> creating this directory, up until recently.

How does the rule look like?

> 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

> 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?

Looks all fine. What does:
 - find /sys/class/usb

 - udevtest /class/usb/lp0 usb

 - udevinfo -q all -p /class/usb/lp0

print, when the printer is connected?

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

Re: no /dev entry for printer when it is out of ink

[Mike]

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

The rule:
BUS="usb", SYSFS{serial}="0HSLL0108041158030", NAME="lp0", 
SYMLINK="printers/EPC80"

# find /sys/class/usb
/sys/class/usb
/sys/class/usb/lp0
/sys/class/usb/lp0/dev
/sys/class/usb/lp0/driver
/sys/class/usb/lp0/device
/sys/class/usb/hiddev0
/sys/class/usb/hiddev0/dev
/sys/class/usb/hiddev0/driver
/sys/class/usb/hiddev0/device


# udevtest /sys/class/usb/lp0 usb
main: looking at device '/class/usb/lp0' from subsystem 'usb'
main: opened class_dev->name='lp0'
udev_rules_get_name: rule applied, 'lp0' becomes 'lp0'
create_node: creating device node '/dev/lp0', major = '180', minor = 
'0', mode =  '0660', uid = '0', gid = '7'

/dev/lp0 is being created. So it looks like the generic udev rule is 
working. I can change my path to now point there. I don't understand why 
my rule quit working though. I tried escputil with it pointing to 
/dev/lp0 but it just times out.

# udevinfo -q all -p /class/usb/lp0
no record for '/class/usb/lp0' in database

I changed my printer to point /dev/lp0 but nothing happens when I print. 
I am just going to give in an replace all my color ink cartridges and 
see if that changes anything.

Thanks again for the help.

Mike



Kay Sievers wrote:

>On Mon, Nov 21, 2005 at 08:10:54PM -0500, Mike wrote:
>  
>
>>The rule I wrote is supposed to create /dev/printers/EPC80. It was 
>>creating this directory, up until recently.
>>    
>>
>
>How does the rule look like?
>
>  
>
>>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
>>    
>>
>
>  
>
>>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?
>>    
>>
>
>Looks all fine. What does:
> - find /sys/class/usb
>
> - udevtest /class/usb/lp0 usb
>
> - udevinfo -q all -p /class/usb/lp0
>
>print, when the printer is connected?
>
>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: 4382 bytes --]

Re: no /dev entry for printer when it is out of ink

[Kay Sievers]

On Mon, Nov 21, 2005 at 10:08:44PM -0500, Mike wrote:
> The rule:
> BUS="usb", SYSFS{serial}="0HSLL0108041158030", NAME="lp0", SYMLINK="printers/EPC80"

You may look at:
  udevinfo -a -p /class/usb/lp0

if that matches your keys and better use "=" for comparison, but with
the keys you use, it should not cause a problem.

> /dev/lp0 is being created. So it looks like the generic udev rule is 
> working. I can change my path to now point there. I don't understand why 
> my rule quit working though. I tried escputil with it pointing to 
> /dev/lp0 but it just times out.
> 
> I changed my printer to point /dev/lp0 but nothing happens when I print. 
> I am just going to give in an replace all my color ink cartridges and 
> see if that changes anything.

Yeah, that may help to get it to print something, but it's unlikely to
change udev's behavior.

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

Re: no /dev entry for printer when it is out of ink

[Mike]

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

I found the problem with udev. udev-073 did not work but 071 works fine. 
I didn't remember recently upgrading to 073.

I still couldn't get the status from the printer until I added ink.

Thanks for your help!

Mike

Kay Sievers wrote:

>On Mon, Nov 21, 2005 at 10:08:44PM -0500, Mike wrote:
>  
>
>>The rule:
>>BUS="usb", SYSFS{serial}="0HSLL0108041158030", NAME="lp0", SYMLINK="printers/EPC80"
>>    
>>
>
>You may look at:
>  udevinfo -a -p /class/usb/lp0
>
>if that matches your keys and better use "==" for comparison, but with
>the keys you use, it should not cause a problem.
>
>  
>
>>/dev/lp0 is being created. So it looks like the generic udev rule is 
>>working. I can change my path to now point there. I don't understand why 
>>my rule quit working though. I tried escputil with it pointing to 
>>/dev/lp0 but it just times out.
>>
>>I changed my printer to point /dev/lp0 but nothing happens when I print. 
>>I am just going to give in an replace all my color ink cartridges and 
>>see if that changes anything.
>>    
>>
>
>Yeah, that may help to get it to print something, but it's unlikely to
>change udev's behavior.
>
>Kay
>
>  
>


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