On Aug 16, "C.Y.M" <[EMAIL PROTECTED]> wrote: > loads the dvb modules. If I do not put a wait statement in the script right > after probing the dvb modules, the next call to my dvb application will fail > because the device has not been created fast enough by udev. I have to use > something like this: This is expected, modprobe returns while udev keeps working asynchronously. You should use a RUN rule to start your program, this way you will be sure that the device has been created.
> Also, after the machine has booted with udev's debug off, if I manually > modprobe > the modules, and then I run "udevstart", the devices get created. But, If I > try > to reload the modules *after* I have alread ran "udevstart", the devices fail > to > create again. Please add this rule to /etc/udev/rules.d/, start /sbin/udevmonitor and repeat your tests. Then attach the log. RUN+="socket:/org/kernel/udev/monitor" -- ciao, Marco
signature.asc
Description: Digital signature
