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 :) -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
