After trying to upgrade to 2.6.11 and
/sbin/modprobe dvb-ttpci hw_sections=0
i get:
linux video capture interface: v1.00 saa7146: register extension 'dvb'. ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 177 saa7146: found saa7146 @ mem e0a5ce00 (revision 1, irq 177) (0x13c2,0x0003). dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware dvb-ttpci: and can be downloaded here http://www.linuxtv.org/download/dvb/firmware/ ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 169 saa7146: found saa7146 @ mem e0a5cc00 (revision 1, irq 169) (0x13c2,0x0003). dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware dvb-ttpci: and can be downloaded here http://www.linuxtv.org/download/dvb/firmware/ ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 17 (level, low) -> IRQ 177 saa7146: found saa7146 @ mem e0a5ca00 (revision 1, irq 177) (0x13c2,0x0000). dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware dvb-ttpci: and can be downloaded here http://www.linuxtv.org/download/dvb/firmware/
But the firmware is there:
# ll /usr/lib/hotplug/firmware total 464 -rw-r--r-- 1 root root 231952 Dec 26 01:02 dvb-ttpci-01.fw -rw-r--r-- 1 root root 231952 Dec 26 01:02 dvb-ttpci-01.fw-261d
What is the real meaning of "could not load firmware, file not found:"?
Google found that message a lot(too often), but no useful answer.
Rainer
anssi.hannula@gmail.com(Anssi Hannula) 27.05.05 21:44
Rainer Zocholl wrote:
saa7146: found saa7146 @ mem e0a5ca00 (revision 1, irq 177) (0x13c2,0x0000). dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware dvb-ttpci: and can be downloaded here http://www.linuxtv.org/download/dvb/firmware/
Added the message above: Maybe google will now find this solution now...
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.
That was the problem. an "aptitude install hotplug" solved the problem. Thanks.
I had "hotplug" removed because with it i could not boot the 2.4.29 kernel anymore with sarge because that oopses.
But maybe the driver can state more clearly what is going on? The only, minmal "hint" that this may has to do with "hotplug" is in the path!
Maybe:
dvb-ttpci: firmware.agent can't load firmware dvb-ttpci-01.fw dvb-ttpci: usually it should be in /usr/lib/hotplug/firmware and dvb-ttpci: can be downloaded from http://www.linuxtv.org/download/dvb/firmware/ dvb-ttpci: activate hotplug if the file exists and you see this message
It's lengthly, true, but the realtionship is really not obvious for a non programmer. Of course it would be better if the dirver could activate the resoruces it needs by it's own...writing that text is easier ;-)
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
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.
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 ;)
On Saturday 28 May 2005 10:15, 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.
The big advantage of hotplugging the firmware is that you can replace the firmware without recompiling the kernel or rebooting. Just reload the (dvb) driver.
The major slowdown on boot is IMO the coldplug, where all hotplugable devices are scanned. But if you only want to have the dvb firmware, you should be fine if you remove the hotplug from your runlevel's rc directory (e.g. /etc/rc5.d).
--Stefan
castet.matthieu@free.fr(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 ------------
Rainer Zocholl wrote:
castet.matthieu@free.fr(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.
just remove hotplug init.d script or do something like : chmod a-x /etc/hotplug/*.rc
And if you want you could even write a script that only manage firmware event and make /proc/sys/kernel/hotplug point to it...
Matthieu
-
Anssi Hannula -
Lauri Tischler -
matthieu castet -
Rainer Zocholl -
Stefan Taferner