udev rules not working with RMS300 on CentOS 5.6 #6

jheiss opened this Issue May 1, 2011 · 4 comments


None yet

2 participants


I haven't dug into it much yet, but I copied the sample udev rules into an appropriate place on my system, changing only the name of the group, and plugged in my RMS300. The resulting syslog messages were:

May 1 06:32:02 typhoon udevd[461]: add_to_rules: unknown key 'ATTRS{idProduct}'
May 1 06:32:02 typhoon udevd[461]: add_to_rules: unknown key 'ATTRS{idVendor}'
May 1 06:32:47 typhoon kernel: usb 2-2: USB disconnect, address 2
May 1 06:33:00 typhoon kernel: usb 2-2: new low speed USB device using uhci_hcd and address 3
May 1 06:33:00 typhoon kernel: usb 2-2: configuration #1 chosen from 1 choice
May 1 06:33:00 typhoon kernel: hiddev96: USB HID v1.10 Device [ ] on usb-0000:00:1d.0-2

As noted in the title I am running CentOS 5.6


Try changing the rule to read ATTR{} instead of ATTRS{} - I think udev may have changed over time.


Oh udev, how I hate you. I found I had to do the following to get this working:

  1. Order the rule after the default rules in 50-udev.rules.
  2. Remove the PROGRAM and NAME keys. If these were included the rule seemed to be ignored. The values for those keys were identical to the default rule for SUBSYSTEM=="usb_device" in 50-udev.rules, so their absence doesn't change anything.
  3. Change ATTRS to SYSFS. That does appear to have been a change in udev. Some of the older documentation online refers to ATTR or ATTRS, but the output of udevinfo on my system shows those keys being named SYSFS{idProduct}, etc.

In other words, my rule ended up looking like the following and was placed in a file starting with "99" in /etc/udev/rules.d

ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idProduct}=="ca01", SYSFS{idVendor}=="0fde", \
  MODE="0660", GROUP="weather"
@barnybug barnybug pushed a commit that closed this issue Jan 4, 2013
Barnaby Gray Update udev rules. closes #6 a6d9f76
@barnybug barnybug closed this in a6d9f76 Jan 4, 2013

Been a while.. but thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment