tda1004x: timeout waiting for DSP ready

[Karel Marik]

Binary package hint: mythtv

MythTV causes problem with DVB-T card firmware. Symptoms are as follows:

1) After mythtv installation everything works fine for many restarts (few days)

2) Suddenly, firmware is not loaded. dmesg gives
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 80 -- invalid
tda1004x: firmware upload failed

3) Uninstall and reinstall of mythtv package revert this state so card (and mythtv) is working again well. dmesg gives
tda1004x: found firmware revision 20 -- ok

I repeated this 1-2-3 cycle three or four times since karmic-koala install.

===========================
Using:
Ubuntu 9.10 Karmic Koala
mythtv 0.22.0 (both backend and frontend)
tv card: AVerTV Digi Super 007 [Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)]
firmware: /lib/firmware/dvb-fe-tda10046.fw installed from linux-firmware-nonfree package

[Emil Kjer (emil-kjer)]

I have been doing two consecutive installations of Mythbuntu 9.10 today.
The pattern is the same every time:
Finish fresh installation, reboot, scan of tv-picture+sound is ok, shutdown, physically unplug IDE-dvd-drive, physically plug two IDE-HDD's, boot and the firmware will not load.

dmesg-output:
[ 21.868105] tda1004x: setting up plls for 48MHz sampling clock
[ 23.704021] eth0: no IPv6 routers present
[ 24.684096] tda1004x: timeout waiting for DSP ready
[ 24.732132] tda1004x: found firmware revision 0 -- invalid
[ 24.732141] tda1004x: trying to boot from eeprom
[ 27.824111] tda1004x: timeout waiting for DSP ready
[ 27.864099] tda1004x: found firmware revision 0 -- invalid
[ 27.864110] tda1004x: waiting for firmware upload...
[ 27.864124] saa7134 0000:02:01.0: firmware: requesting dvb-fe-tda10046.fw
[ 46.704017] tda1004x: timeout waiting for DSP ready
[ 46.744563] tda1004x: found firmware revision 9b -- invalid
[ 46.744573] tda1004x: firmware upload failed
[ 48.812017] tda1004x: timeout waiting for DSP ready
[ 48.852020] tda1004x: found firmware revision 9b -- invalid
[ 48.852030] tda1004x: firmware upload failed

The second time the detected firmware is 9b the first time it was 80.
Is this a bug in ubuntu of mythtv?

[Emil Kjer (emil-kjer)]

I have only discovered the problem on 32bit arch. not on 64bit arch. Since I have backends on both architectures "running" right now.

===========================
Spec:
Dist: Mythbuntu 9.10
Packages: mythtv 0.22.0 (backend from Mythbuntu standard repo.)
Tv-card: ASUS My Cinema-P7131 Hybrid (Digital)
Firmware: /lib/firmware/dvb-fe-tda10046.fw installed from linux-firmware-nonfree package and from linuxtv.org

[Karel Marik (kaja-marik)]

Problem still exists after recent upgrade to kernel 2.6.31-16. Mythtv works fine after install but restart causes "tda1004x: timeout waiting for DSP ready" ..
[code]
[ 17.868020] tda829x 1-004b: setting tuner address to 60
[ 17.977334] tda829x 1-004b: type set to tda8290+75a
[ 18.205044] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input4
[ 18.917870] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 19.167832] __ratelimit: 9 callbacks suppressed
[ 19.167841] type=1505 audit(1260008020.727:14): operation="profile_replace" pid=870 name=/usr/share/gdm/guest-session/Xsession
[ 19.180174] type=1505 audit(1260008020.743:15): operation="profile_replace" pid=871 name=/sbin/dhclient3
[ 19.180689] type=1505 audit(1260008020.743:16): operation="profile_replace" pid=871 name=/usr/lib/NetworkManager/nm-dhcp-client.action
[ 19.180980] type=1505 audit(1260008020.743:17): operation="profile_replace" pid=871 name=/usr/lib/connman/scripts/dhclient-script
[ 19.226447] type=1505 audit(1260008020.787:18): operation="profile_replace" pid=872 name=/usr/bin/evince
[ 19.286117] type=1505 audit(1260008020.847:19): operation="profile_replace" pid=872 name=/usr/bin/evince-previewer
[ 19.315749] type=1505 audit(1260008020.875:20): operation="profile_replace" pid=872 name=/usr/bin/evince-thumbnailer
[ 19.335641] type=1505 audit(1260008020.895:21): operation="profile_replace" pid=889 name=/usr/lib/cups/backend/cups-pdf
[ 19.338304] type=1505 audit(1260008020.899:22): operation="profile_replace" pid=889 name=/usr/sbin/cupsd
[ 19.342746] type=1505 audit(1260008020.903:23): operation="profile_replace" pid=890 name=/usr/sbin/mysqld
[ 22.024305] saa7133[0]: registered device video1 [v4l2]
[ 22.024354] saa7133[0]: registered device vbi0
[ 22.037076] alloc irq_desc for 22 on node -1
[ 22.037084] alloc kstat_irqs on node -1
[ 22.037103] VIA 82xx Audio 0000:00:11.5: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 22.042907] VIA 82xx Audio 0000:00:11.5: setting latency timer to 64
[ 22.043390] saa7134 ALSA driver for DMA sound loaded
[ 22.043411] IRQ 16/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 22.043469] saa7133[0]/alsa: saa7133[0] at 0xea800000 irq 16 registered as card -2
[ 22.225821] dvb_init() allocating 1 frontend
[ 22.320468] DVB: registering new adapter (saa7133[0])
[ 22.320485] DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
[ 22.439106] tda1004x: setting up plls for 48MHz sampling clock
[ 22.554678] codec_read: codec 0 is not valid [0x87e5370]
[ 22.571180] codec_read: codec 0 is not valid [0x87e5370]
[ 22.577823] codec_read: codec 0 is not valid [0x87e5370]
[ 22.613072] codec_read: codec 0 is not valid [0x87e5370]
[ 24.340155] tda1004x: setting up plls for 48MHz sampling clock
[ 24.742802] tda1004x: timeout waiting for DSP ready
[ 24.796089] tda1004x: found firmware revision 0 -- invalid
[ 24.796098] tda1004x: trying to boot from eeprom
[ 26.600014] tda1004x: timeout waiting for DSP ready
[ 26.640011] tda1004x: found firmware revision 0 -- invalid
[ 26.640015] tda1004x: trying to boot from eeprom
[ 27.136015] tda1004x: timeou...

[MarcRandolph (mrand)]

Howdy, and thank you for helping to improve Mythbuntu. Unfortunately (or fortunately, depending on your perspective), there is nothing that mythtv can do about firmware loading. Reloading mythtv packages won't fix this problem either... doing so simply provides another opportunity for the intermittent problem to not appear and you should get the same result from simply rebooting (without removing or reinstalling any packages). This is a kernel or firmware related issue. There are some recent posts in this thread which provide some work-arounds... please report back if they fix this issue:
 http://ubuntuforums.org/showthread.php?t=1316032

Thanks!

[Lee (lee-sodnpoo)]

I'm having similar problems - may be related to this: http://www.linuxtv.org/pipermail/linux-dvb/2008-June/026827.html ?

the following works around it for me:

blacklist tda1004x

then add:

/sbin/modprobe tda1004x
/sbin/modprobe -r saa7134_dvb
/sbin/modprobe saa7134_dvb
/sbin/restart mythtv-backend

to /etc/rc.local

~Lee

[Karel Marik (kaja-marik)]

Marc,

I agree it is probably kernel or firmware issue. What should i do in such case? Should I nominate this bug for another package? Which one? I am not skilled in symptom vs. package assignment. In any case, this issue is associated with mythtv. Other viewers (e.g. MeTV) works fine.

=========================

Lee,

I was in email contact with Hartmut Hackmann who is (probably) author of firmware. His description of issue is as follows:

> This issue is at least partly known:
> The problem is that the MythTV frontend initializes the (analog)
> tuner in a very early state (nothing wrong with that). If the
> driver for the tda10046 really needs to download the firmware, this
> takes a number of seconds. If any software tries to program the tuner
> in this time, this causes a bus conflict on the card. As a result, the
> DSP on the 10046 crashes and will not recover.
> A clean solution would be to implement a locking mechanism on board
> layer but i never did that (not a simple task).

He also indicated possible workaround:

> I assume that your system starts the mythtv server at boot time with an init
> script. This depends on the distribution you use but most have a directory
> /etc/init.d. You should find a shell script starting the server (sorry, i don't
> know the exact names). In this script, you might add a "sleep 10" right before
> invoking mythserver. If this does not do the trick, you migt add a "modprobe saa7134"
> right before the sleep command. This way it should be possible to get rid of the
> collision i mentioned.

But I didn't tested it as I was quite busy last few weeks and this in not a top priority issue I am solving :)

[Lars Ola Liavåg (l-liavag)]

I don't use mythtv but I've also been having the timeout issue. Lee's workaround works for me whereas the fix of Jose Catre-Vandis from http://ubuntuforums.org/showthread.php?t=1316032&page=3 does not.

[Karel Marik (kaja-marik)]

Well, I tried to assign this bug to V4L project (http://www.linuxtv.org/). However, it seems this project is not listed / supported by launchpad.

[Lars Ola Liavåg (l-liavag)]

The problem didn't seem to be fixed by Lee's workaround after all. Anyway, I recently migrated to Lucid and assumed bu the fast boot that the problem was gone. However, my syslog says:

May 16 19:18:51 Internetdatorn kernel: [ 17.560017] tda1004x: timeout waiting for DSP ready
May 16 19:18:51 Internetdatorn kernel: [ 17.600011] tda1004x: found firmware revision 0 -- invalid
May 16 19:18:51 Internetdatorn kernel: [ 17.600016] tda1004x: waiting for firmware upload...
May 16 19:18:51 Internetdatorn kernel: [ 17.600023] saa7134 0000:00:09.0: firmware: requesting dvb-fe-tda10046.fw
May 16 19:18:51 Internetdatorn kernel: [ 17.617613] saa7134 0000:00:09.0: firmware: requesting dvb-fe-tda10045.fw
May 16 19:18:51 Internetdatorn kernel: [ 17.620680] tda1004x: no firmware upload (timeout or file not found?)
May 16 19:18:51 Internetdatorn kernel: [ 17.620686] tda1004x: firmware upload failed

Contrary to in Karmic, it doesn't seem to cost me much time, though.

[Ian Cunningham (ttg-goldcoast)]

Lucid Mythbuntu is displaying same bug - firmware is there in /lib/firmware but fails to load (see dmesg below). from other threads I have come across some PPA kernels that seem to address this & am going to attempt to use one of these. They can be found @ http://kernel.ububtu.com/~kernel-ppa/mainline/

Dmesg output (combined frontend/backend)

    0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-22-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 (Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=2bcbd086-5ec9-446c-ab87-b2b2444b5c50 ro quiet splash
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fef0000 (usable)
[ 0.000000] BIOS-e820: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.3 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x7fef0 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-CFFFF uncachable
[ 0.000000] D0000-D7FFF write-back
[ 0.000000] D8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FF80000000 write-back
[ 0.000000] 1 base 007FF00000 mask FFFFF00000 uncachable
[ 0.000000] 2 base 00F0000000 mask FFF8000000 write-combining
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009f000 (usable)
[ 0.000000] modified: 000000000009f000 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000007fef0000 (usable)
[ 0.000000] modified: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
[ 0.000000] modified: 000000007fef3000 - 000000007ff00000 (ACPI data)
[ 0.000000] modified: 00000000fec00000 - 0000000...

[Ian Cunningham (ttg-goldcoast)]

Typo alert!

Sorry I made a typo in the above link to the PPA repository should be ubuntu NOT ububtu

[Ian Cunningham (ttg-goldcoast)]

Tried kernel above (v2.6.34-rc7-lucid) - no change whatsoever - I am at a loss as to the cause but notice when trying to tune the card the signal/noise bar is at 100% on this card while it varies on my A16D card that works OK (removed at the moment while trying to get the 007 going

[Traz (traz)]

I got this firmware from Ubuntu Hardy, copy it to /lib/firmware.

It is working for me in Lucid as it did in Hardy.

[Lars Ola Liavåg (l-liavag)]

Doesn't seem to work in my case. Well not every time at least. I'll keep it for a while and monitor how it works.

[Karel Marik (kaja-marik)]

I upgraded to Lucid and the problem is still present. It seems mythbacked started before firmware is loaded. I wonder if this bug may relate to this one - https://bugs.launchpad.net/mythbuntu/+bug/556204

[Karel Marik (kaja-marik)]

Workaround indicated in https://bugs.launchpad.net/mythbuntu/+bug/556204 resolved my issue. Modify /etc/init/mythtv-backend.conf as follows:

Replace line

start on (local-filesystems and net-device-up IFACE=lo)

with

start on (local-filesystems and net-device-up IFACE=lo and started udev-finish)

My mythtv is working now for several restarts. The only drawback is the boot is a bit longer.

[Karel Marik (kaja-marik)]

Sadly, I have to add the next day I booted firmware was not loaded. I tried it several time. I have to uninstall mythtv and using MeTV which has no conflict with 'dvb-fe-tda10046.fw' firmware. I will test mythtv after some time again.

[Thomas Mashos (tgm4883)]

Can you check that the "and started udev-finish" is still there? I would imagine that a mythtv upgrade would overwrite that.

[Karel Marik (kaja-marik)]

(RE 20)

Thomas, the mythtv-backend.conf file was there and content was identical as I left it yesterday. There is some strange interference between mythtv and loading 'dvb-fe-tda10046.fw' firmware. Once I uninstall mythtv then firmware is loaded and dvb-t card is working properly in MeTV. I still get "timeout" and "invalid" messages but finally firmware is load.

Here is sample from dmesg (without mythtv)
[ 15.583077] saa7134 ALSA driver for DMA sound loaded
[ 15.583118] IRQ 16/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 15.583163] saa7133[0]/alsa: saa7133[0] at 0xed800000 irq 16 registered as card -2
[ 15.640714] dvb_init() allocating 1 frontend
[ 15.761996] DVB: registering new adapter (saa7133[0])
[ 15.762012] DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
[ 18.160020] tda1004x: timeout waiting for DSP ready
[ 18.200049] tda1004x: found firmware revision 0 -- invalid
[ 18.200058] tda1004x: trying to boot from eeprom
[ 20.536082] tda1004x: timeout waiting for DSP ready
[ 20.576020] tda1004x: found firmware revision 0 -- invalid
[ 20.576029] tda1004x: waiting for firmware upload...
[ 20.576042] saa7134 0000:00:0d.0: firmware: requesting dvb-fe-tda10046.fw
[ 33.176021] tda1004x: found firmware revision 20 -- ok

[Thomas Mashos (tgm4883)]

That is odd. I don't suppose restarting the mythbackend service fixes the
issue?

On Fri, Jun 11, 2010 at 1:22 PM, Karel Marik <email address hidden> wrote:

> *** This bug is a duplicate of bug 556204 ***
> https://bugs.launchpad.net/bugs/556204
>
> (RE 20)
>
> Thomas, the mythtv-backend.conf file was there and content was identical
> as I left it yesterday. There is some strange interference between
> mythtv and loading 'dvb-fe-tda10046.fw' firmware. Once I uninstall
> mythtv then firmware is loaded and dvb-t card is working properly in
> MeTV. I still get "timeout" and "invalid" messages but finally firmware
> is load.
>
> Here is sample from dmesg (without mythtv)
> [ 15.583077] saa7134 ALSA driver for DMA sound loaded
> [ 15.583118] IRQ 16/saa7133[0]: IRQF_DISABLED is not guaranteed on shared
> IRQs
> [ 15.583163] saa7133[0]/alsa: saa7133[0] at 0xed800000 irq 16 registered
> as card -2
> [ 15.640714] dvb_init() allocating 1 frontend
> [ 15.761996] DVB: registering new adapter (saa7133[0])
> [ 15.762012] DVB: registering adapter 0 frontend 0 (Philips TDA10046H
> DVB-T)...
> [ 18.160020] tda1004x: timeout waiting for DSP ready
> [ 18.200049] tda1004x: found firmware revision 0 -- invalid
> [ 18.200058] tda1004x: trying to boot from eeprom
> [ 20.536082] tda1004x: timeout waiting for DSP ready
> [ 20.576020] tda1004x: found firmware revision 0 -- invalid
> [ 20.576029] tda1004x: waiting for firmware upload...
> [ 20.576042] saa7134 0000:00:0d.0: firmware: requesting
> dvb-fe-tda10046.fw
> [ 33.176021] tda1004x: found firmware revision 20 -- ok
>
> --
> tda1004x: timeout waiting for DSP ready
> https://bugs.launchpad.net/bugs/486264
> You received this bug notification because you are a bug assignee (via
> bug 556204).
>

[Karel Marik (kaja-marik)]

(RE 22)
I don't expect it would help as the problem is the firmware is not loaded due to startup interference with mythbackend . A candidate for workaround may be delaying start of mythbackend - either for fixed time or start mythbackend just manually. Once firmware is loaded then mythtv (or MeTV) works fine.

[Karel Marik (kaja-marik)]

"tda1004x: timeout waiting for DSP ready" issue is still present in the fresh install of Maverick.

<CODE>
tata@milasek:~$ dmesg | egrep '(tda1004x)|(DVB)|(saa7133)|(1-004b)'
[ 13.586981] saa7133[0]: found at 0000:00:0d.0, rev: 209, irq: 16, latency: 32, mmio: 0xed800000
[ 13.586994] saa7133[0]: subsystem: 1461:f01d, board: Avermedia Super 007 [card=117,autodetected]
[ 13.587042] saa7133[0]: board init: gpio is 40000
[ 14.126156] saa7133[0]: i2c eeprom 00: 61 14 1d f0 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 14.126178] saa7133[0]: i2c eeprom 10: ff ff ff ff ff 20 ff ff ff ff ff ff ff ff ff ff
[ 14.126194] saa7133[0]: i2c eeprom 20: 01 40 01 32 32 01 01 43 88 ff 00 55 ff ff ff ff
[ 14.126211] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126227] saa7133[0]: i2c eeprom 40: ff 21 00 c0 96 10 03 02 15 16 ff ff ff ff ff ff
[ 14.126242] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126258] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126274] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126290] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126306] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126322] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126338] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126354] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126370] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126386] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.126402] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 14.308789] tuner 1-004b: chip found @ 0x96 (saa7133[0])
[ 14.388634] tda829x 1-004b: setting tuner address to 60
[ 14.516127] tda829x 1-004b: type set to tda8290+75a
[ 18.589729] saa7133[0]: registered device video1 [v4l2]
[ 18.589806] saa7133[0]: registered device vbi0
[ 18.628298] saa7133[0]/alsa: saa7133[0] at 0xed800000 irq 16 registered as card -2
[ 18.828501] DVB: registering new adapter (saa7133[0])
[ 18.828519] DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)...
[ 18.980038] tda1004x: setting up plls for 48MHz sampling clock
[ 21.388074] tda1004x: timeout waiting for DSP ready
[ 21.428121] tda1004x: found firmware revision 0 -- invalid
[ 21.428131] tda1004x: trying to boot from eeprom
[ 23.752087] tda1004x: timeout waiting for DSP ready
[ 23.792061] tda1004x: found firmware revision 0 -- invalid
[ 23.792071] tda1004x: waiting for firmware upload...
[ 36.380021] tda1004x: found firmware revision 29 -- ok

</CODE>

[John (john1988-deactivatedaccount)]

This is the workaround that worked for me:

start mythtv-setup and in the cards section tick the box 'open on demand'. Or use mysql client and change the dvb_on_demand value in capturecard table:
mysql -umythtv -pyour_password mythconverg
update capturecard set dvb_on_demand=1 where cardid=1;

I presume it creates sufficient delay after mythbackend starts and before it attempts to open the card.

Hope this will help someone.

[8200 (8200)]

I can confirm this bug with Ubuntu 11.04 amd64 with all latest updates.

On a fresh install it the card worked without any problems just fine for about 3 weeks. No it doesn't work anymore.

Always the "[ 228.150042] tda1004x: trying to boot from eeprom
[ 230.520032] tda1004x: timeout waiting for DSP ready
[ 230.620028] tda1004x: found firmware revision 0 -- invalid"
bug.