Beta internet install vs DVD install for a working mythtv

[purps]

Hi all,

I'm having big problems getting mythtv working. I abandoned my DVD install for an internet install to try and get MDs working - that done, I focussed my efforts on myth, which has given me no end of trouble http://forum.linuxmce.org/index.php?topic=9117.0

As I just can't work out what the problem is, I've gone back to the DVD install to see if it makes any difference.... but mythtv setup is not even in the computing section of the orbiter!! How do I run mythtv setup? I'm just having no luck trying to run it from the KDE desktop or from the terminal.

Should I have stuck with the internet install version? Why is myth causing so many problems, when it was so easy with 0710?

[tkmedia]

The problem was introduced when the avenard testing repo added mythtv .22 try  just changing "testing" to "release."
Prior to installing the lmce  portion off the dvd.



HTH


Tim

[purps]

Thank you for the extremely fast reply! I shall give this a go.

I'll add the necessary steps to the wiki if I can get it working.

[purps]

Whilst this approach has made "MythTV Setup" appear in the "Computing" menu on the onscreen orbiter, I'm unfortunately getting the same problem as before 

When I click on "TV", myth loads up like normal, but then dumps me back at the orbiter.

Is it at all possible for it to be a hardware/firmware problem if I've had it working under VDR? If I've had it working under VDR, can we definitely say it's a myth issue?

Any suggestions as to what I could try next would be very much appreciated.

[tkmedia]

tail -f  the DCErouter.log and look for protocol errors when running mythtv

I think there is a plugin mismatch



Tim

[purps]

Awfully sorry Tim, but I'm not sure what you mean there. I'm assuming this command is to take a snapshot of the DCErouter.log, but I have no idea how to go about doing this (or where it is).

Would anybody mind giving me some pointers? I'm sure this would be handy to know in the future when trying to diagnose problems.

Also, could you elaborate more on the possible plugin mismatch you mentioned? A mismatch between what? Why would this cause problems for me, and not anybody else that I can see? Please forgive the relentless questions here, but I gotta learn! 

[totallymaxed]

Awfully sorry Tim, but I'm not sure what you mean there. I'm assuming this command is to take a snapshot of the DCErouter.log, but I have no idea how to go about doing this (or where it is).

Would anybody mind giving me some pointers? I'm sure this would be handy to know in the future when trying to diagnose problems.

Also, could you elaborate more on the possible plugin mismatch you mentioned? A mismatch between what? Why would this cause problems for me, and not anybody else that I can see? Please forgive the relentless questions here, but I gotta learn! 

Hi there.

Are you sure that you have completed all of the setup of your capture cards, sources etc etc in 'MythTV Setup' on the Core? What your describing is indicative of your backend not being configured correctly... just a thought for investigation.

All the best


Andrew

[Viking]

Hi,

mythtv-setup crashed for me when i started it from the computing menu. If I got to KDE start a terminal and do :

sudo mythtv-setup

I could complete it without problems.

Greetings
Viking

[purps]

Andrew & Viking,

Thanks for the replies. I have had no problems running mythtv-setup itself; I was able to access this from the computing menu after following Tim's advice regarding the avenard repo.

With respect to configuring the backend properly, I have gone through exactly the same process that I did in 0710...

1. I changed the format to "PAL" and the broadcast(?) to "europe-west" (I'm in the UK).
2. I added the 4 tuners (I have x2 KWorld 399s) with no problems
3. Sources - I made an EIT jobby
4. For each of the tuners, I linked it with the EIT source and did a channel scan, which I watched like a hawk and saw all the various channels pop up as it was scanning.

Then, I ran "sudo mythfilldatabase" on the KDE desktop, and then left it overnight just to be sure everything had finished doing it's thing, and it didn't work. Have I missed something?

@Andrew, the only other thing I'd mention (not that I think it's relevant, because my tuners appear to be working) is that before I plugged in my tuners, I tried to install the "v4l2-firmware_0+hg20090324-1_all.deb" that you sent me, but it didn't work as it was conflicting with "linux-firmware". After, I installed "v4l2-modules-source_0+hg20090324-1_all.deb", which did work. However, myth was not recognising my tuners. So then I put "dvb-usb-af9015.fw" (downloaded from the linuxtv wiki) in /lib/firmware/, which made myth recognise the tuners. Could any of this be causing problems?

[purps]

tail -f  the DCErouter.log and look for protocol errors when running mythtv

I think there is a plugin mismatch

Would anybody mind quickly explaining how to do this please? Am very keen to get myth working on my beta install, I just can't work out what's wrong with it. Cheers.

[Viking]

cd /var/log/pluto
tail -f  the DCErouter.log

Viking