Hi,

I have the main functions working including MythWeb over a 100Mb local net. The best setup is to use a FireFox plugin called mediaplayerconnectivity (v9.3) and VLC. The streaming to my 64bit Vista laptop is smooth, HD (1080), and full screen looks great.

What I had were some issues learning about Apache and how to do the MythWeb build, but it works when configured. The build against 0.23.1 is my best to date.

The basic scenario after 'make install' and all the main database stuff (from the main mythtv dir) is to perform a build in the mythplugin directory, then move into the mythweb dir and do the following:

sudo /etc/rc.d/rc.httpd stop
sudo rm -rf /var/www/htdocs/mythweb
sudo cp -r . /var/www/htdocs/mythweb
sudo rm /var/www/htdocs/mythweb/*.conf
if test -d ~/.mythtv/channels; then
sudo mkdir /var/www/htdocs/mythweb/data/tv_icons
sudo cp ~/.mythtv/channels/* /var/www/htdocs/mythweb/data/tv_icons
fi
sudo chgrp -R apache /var/www/htdocs/mythweb/data
sudo chmod g+rw /var/www/htdocs/mythweb/data
if test -e mythweb.conf.apache; then
if ! test -e mythweb.conf; then
cp mythweb.conf.apache mythweb.conf
fi
fi
sudo cp mythweb.conf /etc/httpd/extra
sudo chmod -R a+rw /var/www/htdocs/mythweb/data

Of course, please read, investigate, learn about, and choose each step for yourself. This is a manual extraction from a tested install script I use and I might have elminated some important parts or chosen insecure permissions. YMMV, but this works without intervention during my larger build script. The icon stuff required mythfilldatabase and other commands to get the ~/.mythtv config dir built and populated, but these are the relevant mythweb parts.

This works once Apache (/etc/httpd in Slackware) installed and working, the main myth build working with prerequisites, and lots testing.

I find that the prerequisite tree to get mythtv working well creates a cascade with complexity not unlike the CPAN automation for perl.

For the ffmpeg tree, I have included the expansion below. My build arrangement is based on a main directory tree with names like:
Level_Slack (Slackware installed)
Level_Atomic (no prereqs, maybe Slackware)
Level_One (Atomic or Slackware prereqs only)
Level_Two (Level_One, Atomic, Slackware)
and so on.

Here is ffmpeg:

Time-HiRes-1.9721 Level_Atomic
avifile-0.7-0.7.45 Level_Five
avifile_prereqs
libiconv-1.13 Level_Atomic
libiconv_prereqs
gettext-0.17-i486-3 Level_Slack
sdl-1.2.14-i486-2 Level_Slack
x264 Level_Two
faac Level_Atomic
freetype-2.3.12-i486-1 Level_Slack
imlib-1.9.15-i486-6 Level_Slack
lame Level_Eight
lame_prereqs
libsndfile-1.0.21 Level_Atomic
libvorbis-1.3.1 Level_Four
libvorbis_prereqs
libogg-1.1.4-i486-1 Level_Slack
libdts-0.0.2 Level_Atomic
libfame-0.9.1 Level_Atomic
libvorbis-1.3.1 Level_Four
libvorbis_prereqs
libogg-1.1.4-i486-1 Level_Slack
sdl-1.2.14-i486-2 Level_Slack
xvidcore Level_Atomic

Of course, there are some I likely missed. Each one is either a source code build or a SlackBuild with its own issues (mostly not =;?).

I manually spaced this post, but the forum destroys the formatting so I copied it for upload upon request. Perhaps someone can give some guidance how to post code and formatted text here.

Remember, its a hobby!

Brett

1 members found this post helpful.

You can format your code by using the "code tags". For example

[code]
Your code in here
[/code]


Help on "bbcode" is here
http://www.linuxquestions.org/questi....php?do=bbcode

I've been using Slackware for mythtv since Slackware 11. Basically I have a machine (in a HTPC case) connected to my TV and acts as both mythtv frontend and backend. Currently I use mythtv (version 0.23.1) with 64-bit 13.1 with two hauppauge cards (PVR-150 & PVR-350) for recording, NVidia card with vdpau for playback and lirc (iguanaIR with RadioShack 15-100 8-in-1 universal remote) for remote control.

Machine is connected to network via wireless and has been chugging along nicely. Packages like mythtv, mythplugins, myththemes, ivtv-utils & iguanaIR are my own scripts, rest are from SBo. I also use this machine to capture/encode home videos.

You've got to love sbopkg queues. I just downloaded the master list an installed the queues to /var/lib/sbopkg/queues. Now mythtv has 38 dependencies and optional dependencies. It is installing just now by the simple method of running sbopkg and loading the queue for mythtv, all additional queues for dependencies are automatically resolved.

Thank you chess and all others involved with sbopkg and its queues.

samac

duplicate

samac

I happily used mythtv on slack 10.2 for a long while. I had a hauppauge pvr150 working with the supplied remote for both receiving commands and blasting them to my fios (super basic) set-top box. It took a fair amount of work because I was new to mythtv, but I did get the play/record/schedule/commercial flagging features working, and life was good.

I found myself in need of a motherboard, so I took the opportunity to upgrade a bunch of hardware, which effectively turned into a new host inside the old chassis. I'm currently running slack 13.1, with mythtv 0.23. My main problem has been due to the many changes happening in the land of lirc. I have a new kernel 2.6.36 working well, but I've still had no luck getting either the infrared receiver or transmitter working. I'm fairly confused at the state of affairs for the lirc kernel modules recently included in 2.6.36 vs. whatever I might still need from the lirc-0.8.7 package.

If I'm patient, I think jarod at wilsonet is the primary operative for the lirc work, and so I feel waiting a bit might be my current best option (I'm cheap and I don't need to make this work).

No kidding about the confusion with LIRC... IIUC, LIRC modules are being slowly moved into the Linux kernel and the process won't be complete until 2.6.37. Well, I, too, am trying to use my formerly working Hauppauge remote (old, analog WinTV USB2 *) with the 2.6.35.7 kernel without success. The module, ir-kbd-i2c, doesn't recognize the key presses anymore and the LIRC stack, lirc_dev & lirc_i2c, doesn't work either.... terribly broken in the 2.6.35.7 kernel.

* Oh, yes, I could buy another MCE USB remote for ~$25, but my current Hauppauge remote is of very good quality. Furthermore, I shouldn't NEED to buy another remote as my current one used to work just dandy.

Greetz
I apologize for going all tangential on you but please tell me... why, oh why is anyone using Slackware resorting to s.....s......s........s........<cringe> sudo ??. Now if you'll excuse me I need to go wash up.

Why is it that some Slackware users seem to think sudo is an evil command? It has it's place and has been around a long time as part of Slackware. I use both su and sudo as needed.

since resurrecting old topics seems to be popular...

sudo is only bad the way Ubuntu uses it. Ubuntu makes a super user and no root. So one user enters their normal password to do everything. sudo is supposed to be configured to only allow you to do certain commands and commands with restrictions. I also believe there are a lot of configurations for shadow with /etc/login.defs that people should take advantage of.

1 members found this post helpful.

i have been persisting mythtv for a month now (13.1 with 0.23, mythbuntu 10.10 with 0.23 and since a couple of days ago 13.1 with mythtv 0.24 from sbo). all i have had is trouble. i think i have had one day in the last month where everything worked... every other day is either tuner trouble, playback trouble, segmentation faults, machine freezing... i'm ready to give up...

slackware 13.1 and mythtv 0.24 problems i have (and am trying to fix) are:
- freezing x (ssh still works, x uses all the cpu)
- freezing machine (ssh doesn't work, hard reset is the only thing that gets me out of that trouble)
- the frontend seg faults when escaping from some menus (not too much of a worry, need to do some more research as well)
- every few minutes the live tv will freeze for a fraction of a second (sound will stop as well), and then it will continue playback in slow motion for about one second (the sound is back to normal at this point) and then the playback will return to normal

don't know if the first two could be related to the radeon video card... my dad's machine with a radeon card exibits these problems as well. i'd be happy if i solve the first two problems (they drive me mental)... the other two are ok for now.

@ lockups...

Don't forget that the default log seetings in the slackware packages are extreemly verbose depending on your configuration settings

rc.mythbackend
"-l $LOG -v important,general"

This will cause a MASSIVE! log file to build up that will end up locking your system if it isn't stored on a separate 'log' partition.

I really wish they would remove that from the default start-up script.

I've been using mythtv since version 0.19 (I think) and slackware 11.0. I've always had nvidia cards and never had any trouble. Currently I'm running slackware -current 64-bit with mythtv 0.24 connected to my HDTV. No playback problems whatsoever, CPU never goes above 30% on playback with mythfrontend. With mplayer, it is about 10%.

Your problems could very well be related to ATI GPU. BTW, I don't use the rc script for mythtv startup.

i don't mind the detailed log while having all these problems. i'd probably look at the logrotate configuration for mythbackend.log if it causes me problems.

yes... my machine will go through memtest soon. i will report the findings.