I wrote this to see when the kernel was reacting to cards being plugged and unplugged. SUBSYSTEM=="pci", ACTION=="add", RUN+="/usr/bin/sox -n -d synth .1 sin 700" SUBSYSTEM=="pci", ACTION=="remove", RUN+="/usr/bin/sox -n -d synth .1 sin 500" SUBSYSTEM=="firewire", ACTION=="remove", RUN+="/usr/bin/sox -n -d synth .1 sin 500" plugged in works fine - seems instant. unplugging seems to be around 2 seconds for the first beep and 10 seconds for the 2nd. the gap between 1st and 2nd can be seen: juser@pc9e:~$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1306905305.865025] add /devices/pci0000:00/0000:00:1c.2/0000:04:00.0 (pci) UDEV [1306905306.035403] add /devices/pci0000:00/0000:00:1c.2/0000:04:00.0 (pci) KERNEL[1306905306.424395] add /devices/pci0000:00/0000:00:1c.2/0000:04:00.0/fw1 (firewire) UDEV [1306905306.425754] add /devices/pci0000:00/0000:00:1c.2/0000:04:00.0/fw1 (firewire) KERNEL[1306905309.874340] remove /devices/pci0000:00/0000:00:1c.2/0000:04:00.0/fw1 (firewire) UDEV [1306905309.875007] remove /devices/pci0000:00/0000:00:1c.2/0000:04:00.0/fw1 (firewire) KERNEL[1306905319.874299] remove /devices/pci0000:00/0000:00:1c.2/0000:04:00.0 (pci) UDEV [1306905320.055101] remove /devices/pci0000:00/0000:00:1c.2/0000:04:00.0 (pci) I don't know if this is causing a problem, but I suspect it is. I know I have often unplugged one card and plugged in another within the 10 second window. I assumed the drivers would have been unloaded by then. Now that I have the beeps I know how long to wait. Also, is there a better way to make the beep? sox seems a bit heavy, (it takes over 2 seconds to play a .1 second beep) and is not installed by default on ubuntu. -- Carl K -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
