On 9/14/07, j t mark473@gmail.com wrote:
On 9/14/07, Michael Bourgeous sts.nitrogen@gmail.com wrote:
I just spent the last three hours trying to fix this problem, and I can only come to the conclusion that udev is horribly broken. For example, my firmware load rule gets called not only when the USB device comes on, but each time ALSA adds a new device from the usx2y (i.e. control, mixer, PCM, etc.), resulting in a lot of wasted time, and many erroneous calls to usx2yloader. Moreover, the rule gets called once for every device /removed/, even though it says ACTION="add". Finally, it seems that every now and then, udev tries the whole process over again, even though the firmware is loaded and us428control is running. Why do we have to keep breaking things that work?
I'm not sure whether it will help you, but I had similar problems when I converted over to udev - I ended up using the following as the rule:
ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idProduct}=="8006", SYSFS{idVendor}=="1604", RUN+="/lib/udev/tascam"
If I didn't do this, then udev called /lib/udev/tascam too many times (more than once!).
I can't help right now, but I will have a look at this over this weekend to see if it still works.
HTH, Jaime
Ooops, sorry - my bad... :-( I included the wrong line. Try this:
ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idProduct}=="8007", SYSFS{idVendor}=="1604", RUN+="/usr/bin/usx2yloader"
That's better :-)