[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2011-09-16 Thread 8200
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 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

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-11-28 Thread John
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 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 -umyth

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-10-18 Thread Karel Marik
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 "tda1004x: timeout waiting for DSP ready" issue is still present in the fresh install of Maverick. t...@milasek:~$ dmesg | egrep '(tda1004x)|(DVB)|(saa7133)|(1-004b)' [ 13.586981] saa7133[0]: found at

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-11 Thread Karel Marik
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 (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 f

Re: [Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-11 Thread Thomas Mashos
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 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 wrote: > *** This bug is a duplicate of bug 556204 *** >https://bugs.launch

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-11 Thread Karel Marik
*** 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 uni

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-11 Thread Thomas Mashos
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 Can you check that the "and started udev-finish" is still there? I would imagine that a mythtv upgrade would overwrite that. -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-11 Thread Karel Marik
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 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 myth

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-10 Thread Karel 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 -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You receive

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-10 Thread Karel 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)

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-06-10 Thread Jonathan Rogers
*** This bug is a duplicate of bug 556204 *** https://bugs.launchpad.net/bugs/556204 ** This bug has been marked a duplicate of bug 556204 myth-backend started before kernel driver it needs -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received this

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-05-27 Thread Lars Ola Liavåg
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. -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ub

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-05-26 Thread 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. ** Attachment added: "Firmware for the Philips SAA7131/SAA7133/SAA7135 TV Tunner" http://launchpadlibrarian.net/49168346/dvb-fe-tda10046.fw.tar.gz -- tda1004x: timeout waiting

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-05-16 Thread Ian Cunningham
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 -- tda1004x: t

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-05-16 Thread Ian Cunningham
Typo alert! Sorry I made a typo in the above link to the PPA repository should be ubuntu NOT ububtu -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ub

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-05-16 Thread Ian Cunningham
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/mainl

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-05-16 Thread Lars Ola Liavåg
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 In

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-03-27 Thread Karel 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. -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received this bug notification because you are a member of Ubuntu

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-03-26 Thread Lars Ola Liavåg
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. -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-02-11 Thread Karel 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. ===

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2010-01-02 Thread Lee
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-backe

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2009-12-30 Thread MarcRandolph
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 int

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2009-12-05 Thread Karel 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] in

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2009-11-23 Thread 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

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2009-11-22 Thread 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-o

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2009-11-21 Thread Karel Marik
** Attachment added: "after many restarts and days: dmesg when firmware load fails" http://launchpadlibrarian.net/35917021/dmesg_suddenly_after_many_successful_restarts.txt -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received this bug notification b

[Bug 486264] Re: tda1004x: timeout waiting for DSP ready

2009-11-21 Thread Karel Marik
** Attachment added: "dmesg after mythtv install - card is working" http://launchpadlibrarian.net/35917004/dmesg_after-mythtv-install.txt -- tda1004x: timeout waiting for DSP ready https://bugs.launchpad.net/bugs/486264 You received this bug notification because you are a member of Ubuntu Bug