View previous topic :: View next topic |
Author |
Message |
mlybarger Guru
Joined: 04 Sep 2002 Posts: 480
|
Posted: Mon Jan 31, 2005 11:55 am Post subject: udev rule doesn't work on updated machine |
|
|
i have two gentoo machines. one was being used as only a print server, and i decided to decommission it. on the print server (machine 1), i have udev 024-r1 installed. it is able to create a device called /dev/optra for my printer with the following rule in /etc/udev/udev.rules:
Code: |
BUS="usb", SYSFS_serial="1138604", NAME="optra"
|
machine 2 is kept a bit more current and is running udev 050. i added the above rule to the top of my /etc/udev/rules.d/10-custom-udev.rules file. when i plug the printer into machine 2, and no device at all is created for the printer. dmesg on machine 2 shows the following output when i plug the printer in:
Code: |
usb 2-6.3: new full speed USB device using address 4
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x043D pid 0x000C
|
machine 1 shows a dmesg of:
Code: |
usb 1-1: new full speed USB device using address 2
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x043D pid 0x000C
drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
|
machine 2 does have the usblp module loaded the same as machine 1 does. any help in getting this to work would be most appreciated. i had thought that decommissioning this machine would be as easy as copying the printer configuration over to the new machine. |
|
Back to top |
|
|
mlybarger Guru
Joined: 04 Sep 2002 Posts: 480
|
Posted: Tue Feb 01, 2005 3:58 pm Post subject: |
|
|
this has been "fixed".
first, i noticed the SYSFS didn't match the current syntax of SYSFS{serial}. i changed that and the rule still didn't work.
next, i spent some time on irc trying to collect any ideas of what could be missing here.
finally, i removed udev from being arch enabled. then when i emerged udev, portage installed 045 instead of 050. this caused my device node to be careated. i still don't have any /dev/usb nodes being created which is strange. i also do not know where udev is suppose to be logging to when loggin is turned on. is this in the syslog? i'm looking for something that shows:
1. this device added by the kernel,
2. searching x file for rules. found -> this rule to match, creating this node, that link.
3. or, didn't find a match, checking next file... etc.
this type of info would be extremely helpfull in doing udev rules. and troubleshooting. |
|
Back to top |
|
|
TheCoop Veteran
Joined: 15 Jun 2002 Posts: 1814 Location: Where you least expect it
|
Posted: Thu Feb 10, 2005 6:02 pm Post subject: |
|
|
my rules have stopped working after upgrading to udev-051, /dev/sd* are created instead of /dev/usb* :
Code: | BUS="usb", SYSFS{manufacturer}="SMSC", SYSFS{product}="USB FDC GOLD-1.11", NAME="usbfloppy", GROUP="usb"
KERNEL="sd?", SYSFS{range}="16", SYSFS{size}="250880", NAME=""
KERNEL="sd?1", SYSFS{start}="32", SYSFS{size}="250848", NAME="usbstick2", GROUP="usb"
KERNEL="sd?", SYSFS{range}="16", SYSFS{size}="2880", NAME="usbstick1", GROUP="usb"
KERNEL="sd?", SYSFS{range}="16", SYSFS{size}="490234753", NAME=""
KERNEL="sd?1", SYSFS{start}="63", SYSFS{size}="490223412", NAME="usbdisk", GROUP="usb" |
Nothing has changed except the udev version _________________ 95% of all computer errors occur between chair and keyboard (TM)
"One World, One web, One program" - Microsoft Promo ad.
"Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler
Change the world - move a rock |
|
Back to top |
|
|
mlybarger Guru
Joined: 04 Sep 2002 Posts: 480
|
Posted: Thu Feb 10, 2005 11:13 pm Post subject: |
|
|
it's a nice concept, but it's the most unstable thing i've ever come across. udev that is. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|