Marco d'Itri wrote:
> On Aug 16, "C.Y.M" <[EMAIL PROTECTED]> wrote:
>
>
>>Ooops again. I take that back. It seems to create the devices with 067 only
>>when udev is in debug mode. If I put it back to only write to log on error,
>>the
>>devices fail to be created again.
>
> I find hard to believe this. Please try some more testing.
>
With 067, if I start the system with udev's debug off, the devices still fail to
load on boot. If I start the system with udev's debug on, the devices get
created on boot every time. This does make sense because there has always been
some kind of lag when udev creates its dvb devices. For example, I have a
script that starts my dvb application. The first thing the script does is it
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:
--SNIP--
# probe dvb modules
modprobe dvbmodule1 dvbmodule2 etc. etc..
until [ -e /dev/dvb/adapter0/video0 ]; do
sleep 1
done
# load dvb application
start
--SNIP--
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.
Regards,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
