[mythtv-users] Media MVP Setup Guide

Fri Sep 9 02:10:42 UTC 2005

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:
# cp dongle.bin.mvpmc /tftpboot

you will have to configure your firewall to allow all these services 
through. just turn it off and get mvpmc working.
# /etc/init.d/iptables stop
then go back and configure the firewall with guarddog or something similar. 
see attached guarddog config file and the howto in html format.

Building and using binary releases of mvpmc
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.

1 DHCP

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.
1.1 Installing the DHCP server
$ su
# apt-get install dhcp

1.2 Configuring the DHCP server
You need to edit your /etc/dhcpd.conf file first. In the example below, 
we're setting up a subnet 192.168.0.50 <http://192.168.0.50> through 
192.168.0.60 <http://192.168.0.60>. The DNS servers are xxx.xxx.xxx.xxx and 
xxx.xxx.xxx.xxx. Our default gateway is 192.168.0.1 <http://192.168.0.1>. We 
are going to permanently assign IP address
192.168.0.10<http://192.168.0.10>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.

NOTE: You must replace xx:xx:xx:xx:xx:xx with the MAC address of your actual 
MediaMVP.
---------------------------------------------------------------------------------------
ddns-update-style none;
# basic subnet declaration, my router is at 192.168.0.1 <http://192.168.0.1>
# and this reserves a range of 10 IP numbers for use
# by anything using DHCP to connect to the web.
# I left out my DNS numbers; you should plug in yours,
# or maybe they're not even necessary...
subnet 192.168.0.0 <http://192.168.0.0> netmask
255.255.255.0<http://255.255.255.0>{
# default gateway
option routers 192.168.0.1 <http://192.168.0.1>;
option domain-name-servers xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx;
# The following options are for dynamic IPs
range 192.168.0.50 <http://192.168.0.50> 192.168.0.60 <http://192.168.0.60>;
default-lease-time 21600;
max-lease-time 43200;
}

# you then should give your MediaMVP a fixed IP number,
# and a filename to boot from. Note you will need
# to get the MediaMVP's MAC address from the sticker
# on the bottom of the unit
host MVP1 {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 192.168.0.10 <http://192.168.0.10>;
filename "dongle.bin.mvpmc";
}
--------------------------------------------------------------------------------------

1.3 Starting the DHCP server
Make sure that dhcp is started at bootup:
# /sbin/chkconfig dhcpd on
Start dhcp now or restart if it is already running.
# /sbin/service dhcpd start

2 TFTP
2.1 Installing the TFTP server
# apt-get install tftp-server
2.2 Starting the TFTP server
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.
Make sure that xinetd is started at bootup:
# /sbin/chkconfig xinetd on
Start xinetd now or restart if it is already running.
# /sbin/service xinetd start

3 NFS
3.1 Installing the NFS server
# apt-get install nfs-utils
3.2 Configuring NFS server
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
192.168.0.10<http://192.168.0.10>read-only.
----------------------------------------------------------------------------------
/myth/tv 192.168.0.10(ro)
/myth/music 192.168.0.10(ro)
-----------------------------------------------------------------------------------

3.3 Starting the NFS server
Make sure that the NFS server is started at bootup:
# /sbin/chkconfig nfs on
Start the NFS server now or restart if it is already running.
# /sbin/service nfs start
4 Allow remote frontends to connect.
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.
On your back-end, you need to allow mysql connections from other hosts on 
your network. This example assumes your local area network is 
192.168.0.0/255.255.255.0 <http://192.168.0.0/255.255.255.0>, adjust 
accordingly for your network:
$ mysql -u root -p mythconverg
mysql> grant all on mythconverg.* to mythtv@"192.168.0.%" identified by 
"mythtv";
mysql> flush privileges;
mysql> quit

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
192.168.0.2<http://192.168.0.2>,
rather than the loopback address (127.0.0.1 <http://127.0.0.1>).

5 MVPMC
5.1 Obtaining an original dongle.bin
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.

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.

Download the Hauppauge Windows server software from 
http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exeand
extract the
dongle.bin file:
$ cd ~
$ wget 
http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe
$ unzip -Ln mediamvpsetup_22_22146.exe dongle.bin
# cp dongle.bin /tftpboot
#exit

5.2 Creating the dongle.bin.mvpmc file
Download a binary release of the mvpmc software to your home directory from 
http://prdownloads.sourceforge.net/mvpmc/mvpmc-0.1.2-bin.tar.gz?download. 
You will have to select your mirror.
$ cd ~
$ wget 
http://internap.dl.sourceforge.net/sourceforge/mvpmc/mvpmc-0.1.2-bin.tar.gz

Extract the mvpmc software from the tar.gz file. Then, build a new dongle 
file called dongle.bin.mvpmc.
$ tar –xvzf mvpmc-0.1.2-bin.tar.gz
$ cd mvpmc-0.1.2-bin
$ ./dongle_build.sh -d /tftpboot/dongle.bin -o dongle.bin.mvpmc
# cp dongle.bin.mvpmc /tftpboot
# exit

5.3 Creating the dongle.bin.mvpmc.config file
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,
192.168.0.2<http://192.168.0.2>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.
-----------------------------------------------------------------------------------
mkdir /myth
mkdir /myth/tv
mkdir /myth/music
/etc/nfsmount.sh 192.168.0.2:/myth/tv /myth/tv
/etc/nfsmount.sh 192.168.0.2:/myth/music /myth/music
/bin/mvpmc -f /etc/helvR10.fnt -s 192.168.0.2 <http://192.168.0.2> -o svideo 
-a 4:3 -m ntsc -r /myth/tv &
---------------------------------------------------------------------------------------

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.

/bin/mvpmc -f /etc/helvR10.fnt -s 192.168.0.2 <http://192.168.0.2> -o svideo 
-a 4:3 -m ntsc –r &

Copy dongle.bin.mvpmc.config to /tftpboot.
# cp dongle.bin.mvpmc.config /tftpboot
# exit

6 Testing
Reboot or power cycle the MediaMVP and see if everything works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20050908/6df1073c/attachment.htm