> Stanley Merkx wrote:
>> Hi,
>>
>> I had this same problem on my FC5 box. Only approx 1 in 20 reboots
>> succeeded until I commented out the following line in
>> /etc/udev/rules.d/05-udev-early.rules :
>>
>> ACTION=="add", SUBSYSTEM=="firmware", ENV{FIRMWARE}=="*",
>> RUN="/sbin/firmware_helper", OPTIONS="last_rule"
>>
>> Now it works fine for me, every single reboot succeeds.
>>
>> Don't know if I broke something else: I do not have any other cards that
>> need firmware.
>
> I remember the firmware loading was changed not too long ago. This might
> be what is causing the problem but I am not sure.
>Just for the record: I just checked my own udev version, which is still at 084. So I'm not sure if this will work for others. As far as I can tell udev is starting multiple devices at the same time, each from a different thread (I also get many USB-related messages inbetween my ivtv-startup messages). Is it possible that firmware_helper may be opening the firmware file(s) with an exclusive lock, denying access to these files from the other thread(s)? This would explain the errors I see on successfull boots that the startup for the second card cannot find the firmware files (which were okay a split millisecond before that). Why do we need this firmware_helper in udev? At least my ivtv cards do not seem to need it... > Can the people who have these lockups check if you have this line in > udev-*.rules and if removing it solves it? One confirmed by Stanley :-) > > Greets > Sander > > PS: Please do not top post, thanks Sorry :-). (I prefer top-posting, but I understand it is the groups' policy not to do so...) Regards, Stanley. _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
