All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: My udev rule doesn't work
Date: Sun, 08 Apr 2007 19:53:35 +0000	[thread overview]
Message-ID: <200704082153.35803.mb@bu3sch.de> (raw)
In-Reply-To: <200704071544.36669.mb@bu3sch.de>

On Sunday 08 April 2007 21:37, Kay Sievers wrote:
> On 4/7/07, Michael Buesch <mb@bu3sch.de> wrote:
> > I have the following rule:
> >
> > mb@powermac:/etc/udev/rules.d$ cat 01-deathadder.rules
> > # Configure the Razer DeathAdder mouse
> > ACTION="add", SUBSYSTEM="usb_device", SYSFS{idVendor}="1532", SYSFS{idProduct}="0007", RUN+="deathaddercfg -C"
> >
> > It's for autoconfiguration of the mouse when it's hotplugged.
> > But somehow this doesn't work. It seems like
> > the program is not called.
> > Does someone have an idea what could cause this?
> >
> > mb@powermac:~$ udevtest /class/usb_device/usbdev1.8/
> > main: looking at device '/class/usb_device/usbdev1.8' from subsystem 'usb_device'
> > run_program: 'usb_device_name --export usbdev1.8'
> > run_program: '/lib/udev/usb_device_name' (stdout) 'USB_BUS\01'
> > run_program: '/lib/udev/usb_device_name' (stdout) 'USB_DEV\08'
> > run_program: '/lib/udev/usb_device_name' returned with status 0
> > udev_rules_get_name: rule applied, 'usbdev1.8' becomes 'bus/usb/001/008'
> > udev_device_event: device '/class/usb_device/usbdev1.8' already known, remove possible symlinks
> > udev_node_add: creating device node '/dev/bus/usb/001/008', major = '189', minor = '7', mode = '0664', uid = '0', gid = '0'
> > main: run: 'deathaddercfg -C'
> > main: run: 'socket:/org/freedesktop/hal/udev_event'
> > main: run: 'socket:/org/kernel/udev/monitor'
> 
> Hmm, udevtest is working fine, I fear that this is another indication,
> that some USB-attributes are not readable at event time. We've seen
> something similar with a new process scheduler recently.
> 
> If you add:
>    ACTION="add", SUBSYSTEM="usb_device", PROGRAM="/bin/sleep 1"
> before your rule, does it work?

No, doesn't seem to.
I tried with one and five seconds sleep.

root@powermac:/etc/udev/rules.d# udevtest /class/usb_device/usbdev1.12/
main: looking at device '/class/usb_device/usbdev1.12' from subsystem 'usb_device'
run_program: '/bin/sleep 5'
run_program: '/bin/sleep' returned with status 0
run_program: 'usb_device_name --export usbdev1.12'
run_program: '/lib/udev/usb_device_name' (stdout) 'USB_BUS\01'
run_program: '/lib/udev/usb_device_name' (stdout) 'USB_DEV\x012'
run_program: '/lib/udev/usb_device_name' returned with status 0
udev_rules_get_name: rule applied, 'usbdev1.12' becomes 'bus/usb/001/012'
udev_device_event: device '/class/usb_device/usbdev1.12' already known, remove possible symlinks
udev_node_add: creating device node '/dev/bus/usb/001/012', major = '189', minor = '11', mode = '0664', uid = '0', gid = '0'
main: run: 'deathaddercfg -C'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: 'socket:/org/kernel/udev/monitor'

I also tried to put deathaddercfg into PROGRAM (although that's incorrect).
Isn't called, too.

root@powermac:/etc/udev/rules.d# udevtest /class/usb_device/usbdev1.15
main: looking at device '/class/usb_device/usbdev1.15' from subsystem 'usb_device'
run_program: 'deathaddercfg -C'
run_program: '/lib/udev/deathaddercfg' (stdout) 'run_program: program '/lib/udev/deathaddercfg' not found'
run_program: '/lib/udev/deathaddercfg' returned with status 1
run_program: 'usb_device_name --export usbdev1.15'
run_program: '/lib/udev/usb_device_name' (stdout) 'USB_BUS\01'
run_program: '/lib/udev/usb_device_name' (stdout) 'USB_DEV\x015'
run_program: '/lib/udev/usb_device_name' returned with status 0
udev_rules_get_name: rule applied, 'usbdev1.15' becomes 'bus/usb/001/015'
udev_device_event: device '/class/usb_device/usbdev1.15' already known, remove possible symlinks
udev_node_add: creating device node '/dev/bus/usb/001/015', major = '189', minor = '14', mode = '0664', uid = '0', gid = '0'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: 'socket:/org/kernel/udev/monitor'

My deathaddercfg tool uses libusb to find the device, if that matters
(I doubt it. It seems it's not called at all).
I also tried "touch /foobar" for RUN and it doesn't create the file /foobar.

-- 
Greetings Michael.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

  parent reply	other threads:[~2007-04-08 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07 13:44 My udev rule doesn't work Michael Buesch
2007-04-08 19:37 ` Kay Sievers
2007-04-08 19:53 ` Michael Buesch [this message]
2007-04-08 19:58 ` Michael Buesch
2007-04-08 19:59 ` Michael Buesch
2007-04-08 20:28 ` Bryan Kadzban

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200704082153.35803.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.