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