i wrote this back before the days of pre-built dongle.bin.mvpmc
files. anyway, sections 5.1 and 5.2 are no longer necessary just
get the ppc binary package from sourceforge:<br>
# cp dongle.bin.mvpmc /tftpboot<br>
<br>
you will have to configure your firewall to allow all these services through. just turn it off and get mvpmc working.<br>
# /etc/init.d/iptables stop<br>
then go back and configure the firewall with guarddog or something
similar. see attached guarddog config file and the howto in html
format.<br>
<br>
Building and using binary releases of mvpmc<br>
This guide was written for those who want to use binary releases and
avoid the whole cross-compile process. It is geared toward using
Red Hat's Fedora Core 2 Linux distribution since that is what I use.
For the most part, this document should still be applicable to Fedora
Core 3 as well. Questions and suggestions should be sent to
mceachrw at gmail dot com.<br>
<br>
1 DHCP<br>
<br>
DHCP is required assign an IP address to the MediaMVP. It also
specifies the location of the tftp server in the DHCP response packet,
otherwise the MediaMVP will not be able to boot.<br>
1.1 Installing the DHCP server<br>
$ su<br>
# apt-get install dhcp<br>
<br>
1.2 Configuring the DHCP server<br>
You need to edit your /etc/dhcpd.conf file first. In the example below,
we're setting up a subnet <a href="http://192.168.0.50">192.168.0.50</a> through <a href="http://192.168.0.60">192.168.0.60</a>. The
DNS servers are xxx.xxx.xxx.xxx and xxx.xxx.xxx.xxx. Our default
gateway is <a href="http://192.168.0.1">192.168.0.1</a>. We are going to permanently assign IP
address <a href="http://192.168.0.10">192.168.0.10</a> to our MediaMVP. Most of these values are not used
by the MediaMVP, but this is how you could use a linux DHCP server in
your own environment.<br>
<br>
NOTE: You must replace xx:xx:xx:xx:xx:xx with the MAC address of your actual MediaMVP.<br>
---------------------------------------------------------------------------------------<br>
ddns-update-style none;<br>
# basic subnet declaration, my router is at <a href="http://192.168.0.1">192.168.0.1</a><br>
# and this reserves a range of 10 IP numbers for use<br>
# by anything using DHCP to connect to the web.<br>
# I left out my DNS numbers; you should plug in yours,<br>
# or maybe they're not even necessary...<br>
subnet <a href="http://192.168.0.0">192.168.0.0</a> netmask <a href="http://255.255.255.0">255.255.255.0</a> {<br>
# default gateway<br>
option routers <a href="http://192.168.0.1">192.168.0.1</a>;<br>
option domain-name-servers xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx;<br>
# The following options are for dynamic IPs<br>
range <a href="http://192.168.0.50">192.168.0.50</a> <a href="http://192.168.0.60">192.168.0.60</a>;<br>
default-lease-time 21600;<br>
max-lease-time 43200;<br>
}<br>
<br>
# you then should give your MediaMVP a fixed IP number,<br>
# and a filename to boot from. Note you will need<br>
# to get the MediaMVP's MAC address from the sticker<br>
# on the bottom of the unit<br>
host MVP1 {<br>
hardware ethernet xx:xx:xx:xx:xx:xx;<br>
fixed-address <a href="http://192.168.0.10">192.168.0.10</a>;<br>
filename "dongle.bin.mvpmc";<br>
}<br>
--------------------------------------------------------------------------------------<br>
<br>
1.3 Starting the DHCP server<br>
Make sure that dhcp is started at bootup:<br>
# /sbin/chkconfig dhcpd on<br>
Start dhcp now or restart if it is already running.<br>
# /sbin/service dhcpd start<br>
<br>
2 TFTP<br>
2.1 Installing the TFTP server<br>
# apt-get install tftp-server<br>
2.2 Starting the TFTP server<br>
The tftp server runs under xinetd server. I'm not sure how to
start tftp other than through the Gnome gui. Click System
Settings, Server Settings, Services. Scroll down and check off
tftp and xinetd.<br>
Make sure that xinetd is started at bootup:<br>
# /sbin/chkconfig xinetd on<br>
Start xinetd now or restart if it is already running.<br>
# /sbin/service xinetd start<br>
<br>
3 NFS<br>
3.1 Installing the NFS server<br>
# apt-get install nfs-utils<br>
3.2 Configuring NFS server<br>
You need to edit your /etc/exports file first. In the example below, we
export or share /myth/tv and /myth/music to our MediaMVP at
<a href="http://192.168.0.10">192.168.0.10</a> read-only.<br>
----------------------------------------------------------------------------------<br>
/myth/tv 192.168.0.10(ro)<br>
/myth/music 192.168.0.10(ro)<br>
-----------------------------------------------------------------------------------<br>
<br>
3.3 Starting the NFS server<br>
Make sure that the NFS server is started at bootup:<br>
# /sbin/chkconfig nfs on<br>
Start the NFS server now or restart if it is already running.<br>
# /sbin/service nfs start<br>
4 Allow remote frontends to connect.<br>
Configuring a remote front-end is relatively easy. There are two steps
you need to take on your back-end machine, followed by a quick edit of
a config file and a breeze through the mythtvsetup utility on the
remote front-end.<br>
On your back-end, you need to allow mysql connections from other hosts
on your network. This example assumes your local area network is
<a href="http://192.168.0.0/255.255.255.0">192.168.0.0/255.255.255.0</a>, adjust accordingly for your network:<br>
$ mysql -u root -p mythconverg<br>
mysql> grant all on mythconverg.* to mythtv@"192.168.0.%" identified by "mythtv";<br>
mysql> flush privileges;<br>
mysql> quit<br>
<br>
In the mythtvsetup application on your back-end, you'll need to make
sure you set the variables for "IP address for <host>" and
"Master Server IP address" to the IP address of the back-end's network
card <a href="http://192.168.0.2">192.168.0.2</a>, rather than the loopback address (<a href="http://127.0.0.1">127.0.0.1</a>).<br>
<br>
5 MVPMC<br>
5.1 Obtaining an original dongle.bin<br>
dongle.bin is the name of the Linux kernel and ramdisk that Hauppauge
supplies for the MediaMVP. The mvpmc project creates a new version of
this file, replacing Hauppauge's frontend software with mvpmc.<br>
<br>
You will need to place a copy of the Hauppauge-supplied dongle.bin file
into /tftpboot. The mvpmc build procedure will be looking for the
software in that location.<br>
<br>
Download the Hauppauge Windows server software from
<a href="http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe">http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe</a>
and extract the dongle.bin file:<br>
$ cd ~<br>
$ wget <a href="http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe">http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe</a><br>
$ unzip -Ln mediamvpsetup_22_22146.exe dongle.bin<br>
# cp dongle.bin /tftpboot<br>
#exit<br>
<br>
5.2 Creating the dongle.bin.mvpmc file<br>
Download a binary release of the mvpmc software to your home directory
from
<a href="http://prdownloads.sourceforge.net/mvpmc/mvpmc-0.1.2-bin.tar.gz?download">http://prdownloads.sourceforge.net/mvpmc/mvpmc-0.1.2-bin.tar.gz?download</a>.
You will have to select your mirror.<br>
$ cd ~<br>
$ wget <a href="http://internap.dl.sourceforge.net/sourceforge/mvpmc/mvpmc-0.1.2-bin.tar.gz">http://internap.dl.sourceforge.net/sourceforge/mvpmc/mvpmc-0.1.2-bin.tar.gz</a><br>
<br>
Extract the mvpmc software from the tar.gz file. Then, build a new dongle file called dongle.bin.mvpmc.<br>
$ tar –xvzf mvpmc-0.1.2-bin.tar.gz<br>
$ cd mvpmc-0.1.2-bin<br>
$ ./dongle_build.sh -d /tftpboot/dongle.bin -o dongle.bin.mvpmc<br>
# cp dongle.bin.mvpmc /tftpboot<br>
# exit<br>
<br>
5.3 Creating the dongle.bin.mvpmc.config file<br>
When the MediaMVP is booting, it will try to download this file from
the tftp server. If you would like your MediaMVP to automatically start
the mvpmc application, you should make your config file look something
like to use NFS for recording playback. In this case, <a href="http://192.168.0.2">192.168.0.2</a> is
the IP address of the master backend server. We are creating a mount
point called /myth/tv and then mounting the directory using NFS. The -r
parameter instructs mvpmc to look for the recordings in /myth/tv.
Since mvpmc can play mp3 files, I mounted /myth/music as well.<br>
-----------------------------------------------------------------------------------<br>
mkdir /myth<br>
mkdir /myth/tv<br>
mkdir /myth/music<br>
/etc/nfsmount.sh 192.168.0.2:/myth/tv /myth/tv<br>
/etc/nfsmount.sh 192.168.0.2:/myth/music /myth/music<br>
/bin/mvpmc -f /etc/helvR10.fnt -s <a href="http://192.168.0.2">192.168.0.2</a> -o svideo -a 4:3 -m ntsc -r /myth/tv &<br>
---------------------------------------------------------------------------------------<br>
<br>
In the example above, mvpmc would get the MythTV program guide info via
the MythTV protocol, but it would play the recordings via NFS.
The mvpmc software can also use the Myth protocol for recording
playback rather than using NFS. If you would like to use the Myth
protocol, the last line in dongle.bin.mvpmc.config would look like this.<br>
<br>
/bin/mvpmc -f /etc/helvR10.fnt -s <a href="http://192.168.0.2">192.168.0.2</a> -o svideo -a 4:3 -m ntsc –r &<br>
<br>
Copy dongle.bin.mvpmc.config to /tftpboot.<br>
# cp dongle.bin.mvpmc.config /tftpboot<br>
# exit<br>
<br>
6 Testing<br>
Reboot or power cycle the MediaMVP and see if everything works.<br>
<br>