Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • You can use the command at raftaman.net/?p=343 to check for more information on the usb drive. Also, the C program on the bottom of kernel.org/doc/pending/hotplug.txt is really useful for listening to uevents, which makes it easier to see what information you can use. Could also be as simple as some earlier rule is declared as final rule. Commented May 16, 2013 at 8:54
  • I will take a look at the C program, but it's looks like a little bit tricky, isn't it? Commented May 16, 2013 at 9:09
  • Somewhat, but you don't need to understand it. It is useful as a util :). Btw, I think you misspelled ATTR, should be ATTRS for usb properties. Commented May 16, 2013 at 9:31
  • I had the same problem a while ago. Mabye that solution will work for you too. Commented May 16, 2013 at 12:51
  • @don_crissti After running udevadm test --action --add /dev/sdc1 (I dont have a devpath directory, I guess devpath is the usb device path?) I had a list of rules, but mine didnt appear and I got a unable to open device '/sys/dev/sdc1' Commented May 17, 2013 at 6:50