[linux-dvb] Nova-T (Philips TDA10045H) on FC3 firmware upload starts but never succeeds

Phil Quiney phil.quiney at bigfoot.com
Sun Jul 3 20:25:54 CEST 2005


Hi Guys,

This is my first post to this list but I did search the archive and 
nobody else seems to be having exactly the same problem.

I have a FC3 box (voyager) which has been upgraded to kernel 
2.6.11-1.27_FC3 and the Nova-T card appears to be correctly detected at 
boot  time, all the modules load and devices under /dev/ seem to be there.

lspci shows
00:0e.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

Here is the output of /var/log/messages regarding the card
Jul  1 21:02:44 voyager kernel: DVB: registering new adapter 
(TT-Budget/WinTV-NOVA-T  PCI).
Jul  1 21:02:44 voyager kernel: adapter has MAC addr = 00:d0:5c:23:34:af
Jul  1 21:02:44 voyager hal.hotplug[4347]: DEVPATH is not set
Jul  1 21:02:44 voyager kernel: DVB: registering frontend 0 (Philips 
TDA10045H DVB-T)...

The problem occurs when I attempt to use the 'scan' progam - the scan 
fails and /var/log/messages shows the following...
Jul  1 21:04:11 voyager kernel: tda1004x: waiting for firmware upload...
Jul  1 21:04:17 voyager kernel: tda1004x: Error during firmware upload
Jul  1 21:04:17 voyager kernel: tda1004x: firmware upload failed

The firmware file was obtained using the script in the Documentation 
directory of the kernel source tree. The md5sum I got agreed with 
another post on the subject so  I am fairly sure that this is OK. For 
the record it was:
2105fd5bf37842fbcdfa4bfd58f3594a  dvb-fe-tda10045.fw

 For FC3 this file resides in /lib/firmware (confirmed by checking the 
value of FIRMWARE_DIR in /etc/hotplug/firmware.agent)

The hotplug mechanism is new to me but it looks like the script is 
firing. I found that setting DEBUG=yes in /etc/hotplug/firmware.agent 
and /etc/hotplug.d/default/default.hotplug enabled me to see a bit more 
of what was going on (I added some extra debug myself to be sure that 
the firmware file was being found as well as checking that the 
$SYSFS/$DEVPATH/loading file exists).

I am assuming that the $SYSFS/$DEVPATH/loading and $SYSFS/$DEVPATH/data 
are transient files as they exist when the script runs but not 
otherwise. Anyway the following is the output with the debug turned on 
(using 'scan' again to trigger the firmware upload)....

Jul  1 22:35:40 voyager default.hotplug[4692]: arguments (firmware) env 
(PHYSDEVPATH=/devices/pci0000:00/0000:00:0e.0 SUBSYSTEM=firmware 
OLDPWD=/ DEVPATH=/class/firmware/0000:00:0e.0 
FIRMWARE=dvb-fe-tda10045.fw PATH=/bin:/sbin:/usr/sbin:/usr/bin 
ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 PHYSDEVDRIVER=budget_ci dvb 
DEBUG=yes PHYSDEVBUS=pci SEQNUM=613 _=/bin/env)
Jul  1 22:35:40 voyager default.hotplug[4692]: invoke 
/etc/hotplug/firmware.agent ()
Jul  1 22:35:40 voyager kernel: tda1004x: waiting for firmware upload...
Jul  1 22:35:40 voyager firmware.agent[4692]: firmware.agent: action: 
add  path: /sys//class/firmware/0000:00:0e.0
Jul  1 22:35:40 voyager firmware.agent[4692]: loading now exists # <- My 
diagnostic
Jul  1 22:35:40 voyager firmware.agent[4692]: firmware exists # <- My 
diagnostic
Jul  1 22:35:40 voyager default.hotplug[4718]: arguments (firmware) env 
(PHYSDEVPATH=/devices/pci0000:00/0000:00:0e.0 SUBSYSTEM=firmware 
OLDPWD=/ DEVPATH=/class/firmware/0000:00:0e.0 
FIRMWARE=dvb-fe-tda10045.fw PATH=/bin:/sbin:/usr/sbin:/usr/bin 
ACTION=remove PWD=/etc/hotplug HOME=/ SHLVL=2 PHYSDEVDRIVER=budget_ci 
dvb DEBUG=yes PHYSDEVBUS=pci SEQNUM=614 _=/bin/env)
Jul  1 22:35:40 voyager default.hotplug[4718]: invoke 
/etc/hotplug/firmware.agent ()
Jul  1 22:35:40 voyager firmware.agent[4718]: firmware.agent: action: 
remove  path: /sys//class/firmware/0000:00:0e.0
Jul  1 22:35:41 voyager kernel: tda1004x: Error during firmware upload
Jul  1 22:35:41 voyager kernel: tda1004x: firmware upload failed

I am not sure where to look next, I assume I need to look at debugging 
the kernel modules  - to find where that firmware file is being read?

TIA

Phil Q




More information about the linux-dvb mailing list