Author |
Message |
dog2bert
|
Posted: Wed Sep 13, 2006 7:26 pm |
|
Joined: Sat Sep 09, 2006 2:41 pm
Posts: 13
|
I downloaded MythTV version .20 and compiled it and ran make install. All of this worked just fine. I reboot the computer and MythTV starts up fine. Then when I go to watch live TV or pretty much anything besides Options is says: The server uses network protocol version 26, but this client only understands version 30. Make sure you are running compatible versions of the backend and frontend.
When I go to MythWeb everything looks like it did before the upgrade.
What do I have to change?
|
|
Top |
|
 |
tjc
|
Posted: Wed Sep 13, 2006 7:41 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Almost sounds like you only built/installed one of the 3 directories... Where you following the "how to build from SVN" directions on the wiki?
|
|
Top |
|
 |
dog2bert
|
Posted: Wed Sep 13, 2006 8:42 pm |
|
Joined: Sat Sep 09, 2006 2:41 pm
Posts: 13
|
I used the tarball instructions:
$ tar -xjf mythtv-0.20.tar.bz2
$ cd mythtv-0.20
$ ./configure
$ qmake mythtv.pro
$ make
$ su
# make install
# exit
|
|
Top |
|
 |
tjc
|
Posted: Wed Sep 13, 2006 8:55 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Top |
|
 |
dog2bert
|
Posted: Wed Sep 13, 2006 9:13 pm |
|
Joined: Sat Sep 09, 2006 2:41 pm
Posts: 13
|
Even though I shutdown the frontend, when I login with mythweb it still shows that it is recording shows. Does this mean the backend is still running?
|
|
Top |
|
 |
tjc
|
Posted: Wed Sep 13, 2006 9:43 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Possibly. They are seperate processes (or even sets of processes) after all.
|
|
Top |
|
 |
dog2bert
|
Posted: Wed Sep 13, 2006 10:43 pm |
|
Joined: Sat Sep 09, 2006 2:41 pm
Posts: 13
|
Ok. That worked.
How do you update MythWeb?
|
|
Top |
|
 |
dog2bert
|
Posted: Thu Sep 14, 2006 5:52 am |
|
Joined: Sat Sep 09, 2006 2:41 pm
Posts: 13
|
I did what the wiki told me to do about Myth Web :
cd ~/svn/mythplugins/mythweb
cp -fR * /var/www/mythweb
but now it shows this:
Fatal Error at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 159:
Incompatible protocol version (mythweb=26, backend=30)
Last edited by dog2bert on Sat Sep 16, 2006 4:26 pm, edited 1 time in total.
|
|
Top |
|
 |
tjc
|
Posted: Thu Sep 14, 2006 7:25 am |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Top |
|
 |
dog2bert
|
Posted: Thu Sep 14, 2006 12:12 pm |
|
Joined: Sat Sep 09, 2006 2:41 pm
Posts: 13
|
Yes but that didn't fix it.
So I re-copied the files over after I shut down mythtv backend & frontend
and then restarted Apache.
It seems to work fine now.
The new commercial skip technology in version 0.2.0 is a lot better than before.
Hopefully everything will be stable for awhile now.
|
|
Top |
|
 |
EvilTwin
|
Posted: Thu Sep 14, 2006 10:10 pm |
|
Joined: Tue Nov 08, 2005 7:31 am
Posts: 195
Location:
Secret Lair
|
There are new 0.20 fixes as recently as a couple hours ago, especially around MythWeb and the other plugins, so if you're still having problems it might pay to get the latest from SVN. At this point 0.20 is still very bleeding edge and prone to nasty surprises.
|
|
Top |
|
 |
nigelpearson
|
Posted: Sun Sep 17, 2006 2:12 am |
|
Joined: Wed Mar 03, 2004 7:43 pm
Posts: 748
Location:
Sydney, Australia
|
dog2bert wrote: I used the tarball instructions:
$ tar -xjf mythtv-0.20.tar.bz2 $ cd mythtv-0.20 $ ./configure
That will have built and installed 0.20 in /usr/local. KnoppMyth still has 0.19 in /usr. You will have to remove one of them.
I am also in the habit of shutting down both the frontend and backend, and deleting the existing libmyth*.so when compiling a new version of MythTV.
_________________ | Nigel Pearson, nigel.pearson.au@gmail.com| "Things you own end up owning you" - Tyler, Fight Club
|
|
Top |
|
 |
manicmike
|
Posted: Sun Sep 17, 2006 7:52 am |
|
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location:
Melbourne, Australia
|
I installed 0.20 the other day and it's bloody brilliant.
Crappy though DiG, ABC Jazz and SBS radio are, it's nice to have them.
There is one problem: The old problem of freezing between shows occasionally happens. Enough for it to be very noticeable after a few days (happened maybe five times). I had this problem until around (this is a complete guess) R5A22.
Has anyone else had this problem? Mythbackend reported:
### log starts here ###
2006-09-17 23:37:00.349 TVRec(1): Enabling Full LiveTV UI.
2006-09-17 23:37:01.666 Finished recording The Office: channel 1013
2006-09-17 23:37:01.979 TVRec(1): Enabling Full LiveTV UI.
[mpegts @ 0xb71f4238]Parser not found for Codec Id: 94211 !
0: start_time: 2628.718 duration: 199.368
1: start_time: 2628.664 duration: 199.385
2: start_time: 2628.676 duration: 199.388
3: start_time: 2628.663 duration: 199.399
stream: start_time: 29207.362 duration: 2215.820 bitrate=7800 kb/s
2006-09-17 23:37:02.229 AFD: Opened codec 0x82d1660, id(MPEG2VIDEO) type(Video)
2006-09-17 23:37:02.284 AFD: Opened codec 0x8200110, id(MP3) type(Audio)
2006-09-17 23:37:02.287 AFD: Opened codec 0x8200450, id(AC3) type(Audio)
[mpeg2video @ 0xb70e3300]2006-09-17 23:37:02.713 TVRec(1): RingBufferChanged()
2006-09-17 23:37:03.096 Finished recording Repossessed: channel 1013
### and stops here ###
While the frontend log (~/.xsession-errors) reports bugger all during this time.
Thanks
Mike
_________________ ********************* LinHES 7.4 Australian Dragon *********************
|
|
Top |
|
 |
bearwood
|
Posted: Tue Oct 17, 2006 4:10 pm |
|
Joined: Fri May 27, 2005 9:33 pm
Posts: 106
Location:
Cairns, Australia.
|
Manicmike, what do you mean the old freezing between shows? Are you talking about hesitations at the program change. I have had this problem since A22 and was hoping that 0.20 will fix this. bugger.
_________________ R8.1 combined backend/frontend ASUS P7H55-M Pro Intel i3-550, 4Gb Ram Seagate 500GB (Sata) 2x Dvico DVB-T Lite & Sony PlayTV (usb twin tuner) TP-Link TL-WN881ND PCIe wifi card (not working) Logitech Harmony One remote, CoolerMaster ATC-S case
|
|
Top |
|
 |
manicmike
|
Posted: Sat Oct 28, 2006 5:36 pm |
|
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location:
Melbourne, Australia
|
bearwood wrote: Manicmike, what do you mean the old freezing between shows? Are you talking about hesitations at the program change. I have had this problem since A22 and was hoping that 0.20 will fix this. bugger.
Hi, sorry to have taken this long, but I had not seen your question.
There has been a problem with mythfrontend freezing between scheduled shows in the past. This problem was particularly bad with my father-in-law's KM box.
After upgrading his to 0.20 the problem was still present.
He has stopped ringing me since I was last there (he lives in Melbourne, I live in Torquay) a few weeks ago. When I was there, I tweaked his setup. This means that what I did fixed the problem completely (I asked him to call if it happened again - prior to the last tweak it was happening many times per day).
What I did was simple. I just changed the output resolution of his XF86Config-4 file to 800x600. I'd previously had it at 1024x768 since this gave a better picture, but the box was having problems with the refresh rate at this resolution, which apparently led to the screen freezing.
Anyway, it's fixed now. The *best* way to diagnose frontend problems, btw, is to start up a terminal (ctrl-x) and start mythfrontend in it. This way, all of the errors go to stdout (the terminal) and you can switch to the terminal with alt-tab to view this. If you need to kill an unresponsive frontend, go to terminal, and ctrl-c.
Other handy-dandy built-in keyboard shortcuts are listed in /etc/X11/fluxbox/keys. The most useful are:
Mod1 x :ExecCommand xterm -fn *18*
Mod1 s :ExecCommand mythtv-setup
Mod1 m :ExecCommand mythfrontend
Mod1 1 :ExecCommand sudo /etc/init.d/mythtv-backend start
Mod1 2 :ExecCommand sudo /etc/init.d/mythtv-backend stop
Mod1 3 :ExecCommand sudo /etc/init.d/mythtv-backend restart
"Mod 1" is alt, so alt-2 will stop mythtv-backend, so you can run mythtv-setup with alt-s. If mythfrontend crashes for some reason, you can restart it with alt-m. If it crashes in the terminal, restart with the up arrow followed by enter (linux people say 'well, duh!' here).
Cheers
Mike
_________________ ********************* LinHES 7.4 Australian Dragon *********************
|
|
Top |
|
 |