dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



castet.matthieu@xxxxxxx(matthieu castet)  28.05.05 10:46

>Lauri Tischler wrote:
>> Anssi Hannula wrote:
>>
>>> Rainer Zocholl wrote:
>>>
>>>>
>>>> What is the real meaning of "could not load firmware, file not
>>>> found:"?
>>>
>>>
>>>
>>> Check the correct firmware directory with:
>>> $ grep FIRMWARE_DIR= /etc/hotplug/firmware.agent
>>>
>>> If that file is not present, please install hotplug.
>>
>>
>> Things should work without the stupid hotplug.
>> If the firmware files are in the correct directory,
>> why cant they be loaded without hotplug.
>>
>Because some script need to that :
>echo 1 > /sys/$DEVPATH/loading
>cat $HOTPLUG_FW_DIR/$FIRMWARE > /sys/$DEVPATH/data
>echo 0 > /sys/$DEVPATH/loading

>you could to it by hand if you don't like hotplug, but you shoud
>increase the timeout and be fast ;)

After reactivating hotpkug is noticed, that the boot process
needs significantly longer than without.

If your sequence would allow to avoid hotplug delays,
i see no reason why the script which do the "insmods"
shouldn't do the firmware load too, or why the driver 
him self shouldn't do it. Maybe thate useless, because another
fw is requierd later, but that wil not happen often.
IIRC once the firmware was coded inti the drivers source.


One problem i (often run in):

Where can is see how many DVB cards with which features 
are behind which /dev/videoX ?
And:
Is there a trick test is the cards are "on" and running? 
(ACPI? a "NOP" command?)

Rainer---<=====>                         Vertraulich
             //
           //                              
         <=====>--------------ocholl, Kiel, Germany ------------



[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux