SingletonMillerWiki - User contributions [en]

Streaming Video

2015-03-28T17:04:38Z

Martin: Created page with " Category:RaspberryPi Category:Projects == Introduction == The objective of this How To is install setup and stream high resolution, high frame rate video from your R..."

[[Category:RaspberryPi]]
[[Category:Projects]]

== Introduction ==
The objective of this How To is install setup and stream high resolution, high frame rate video from your Raspberry Pi (with a Camera module) over a network.
Based on [http://www.ics.com/blog/raspberry-pi-camera-module#.VJFhbyvF-b8].

=== Equipment ===
* Raspberry Pi
* Raspberry Pi camera module

=== Initial Setup ===
It is assumed that your Raspberry Pi is running Raspian and that the camera module is connected correctly.
Familiarity with the command line prompt is of benefit as most of the work here is via the command line.
If you're using the desktop, open a Terminal from the desktop menu or use a remote connection via SSH [[Enable SSH#Connect_via_SSH_on_a_Local_network]]

To test the camera is working take a picture from the camera.
<pre>
$ cd ~
$ raspistill -o test_image.jpg
</pre>
To check the picture use the file browser the picture should be in your home folder (~) [http://thepihut.com/blogs/raspberry-pi-tutorials/16021420-how-to-install-use-the-raspberry-pi-camera].

If its not working, try the following,
<pre>
$ sudo apt-get update
$ sudo apt-get upgrade
</pre>
check the camera is enabled
<pre>
$ sudo raspi-config
</pre>
Reboot to bring your pi back up in a known good state and hopefully a retest of the picture capture will work.
<pre>
$ sudo reboot
</pre>

== Streaming ==
=== Install vlc ===
<pre>
$ sudo apt-get install vlc
</pre>
Enable he v4l module
<pre>
sudo modprobe bcm2835-v4l2
</pre>

=== VLC command ===
Use the command line version of vlc to directly stream the camera output to a port.
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
cvlc v4l2:///dev/video0 --v4l2-width 640 --v4l2-height 480 --v4l2-chroma h264 --sout '#standard{access=http,mux=ts,dst=0.0.0.0:8085}' &
</pre>

Change the <code>--v4l2-width</code> and <code>--v4l2-height</code> to adjust the screen resolution.
I've tested up to 1900 x 1080.
Change <code>8085</code> to adjust the port to broadcast on.

=== Monitor the Stream ===
Check that this is working by monitoring the stream on anther PC (is best).
We need to know the IP address of your Pi on your network and the port (from above):
<pre>
$ ifconfig | grep 'inet addr:'
</pre>
should give something like
<pre>
inet addr:192.168.0.31 Bcast:192.168.0.255 Mask:255.255.255.0
inet addr:127.0.0.1 Mask:255.0.0.0
</pre>

Point your Firefox browser to the address <code>http://192.168.0.31:8085</code> to see the live feed.
Alternatively use the same address in the VLC GUI under a 'Open Network Stream'.

== Stream Capture ==
It is possible to capture the stream on any computer than can see the stream.
If your router is correctly configured the stream can be viewed by any computer on the internet.
 
Use VLC to record the stream (use the figures below as a guide)
# Enter the network stream address
# Select the Convert Save button
# Create a Raw Capture Profile using the
# Select the Raw profile and select the file save location.

<gallery>
File:VLC_convert_save.png|VLC_convert_save.png
File:VLC_convert_save_open_media_network.png|VLC_convert_save_open_media_network.png
File:VLC_convert_save_raw_profile.png|VLC_convert_save_raw_profile.png
File:VLC_convert_save_open_media_network_convert.png|VLC_convert_save_open_media_network_convert.png
</gallery>

== TO DO LIST ==
# Add scripts for running the code from a script
# How to set up a router to forward a stream port
# How to get your internet IP address for external viewing (no-ip)

== References ==
# [http://www.ics.com/blog/raspberry-pi-camera-module#.VJFhbyvF-b8 ICS Insight Blog>The Raspberry Pi Camera Module]
# [http://thepihut.com/blogs/raspberry-pi-tutorials/16021420-how-to-install-use-the-raspberry-pi-camera How to take a photo with your Raspberry Pi]

File:VLC convert save raw profile.png

2015-03-28T16:41:45Z

Martin:

File:VLC convert save open media network convert.png

2015-03-28T16:41:31Z

Martin:

File:VLC convert save open media network.png

2015-03-28T16:41:19Z

Martin:

File:VLC convert save open media.png

2015-03-28T16:41:04Z

Martin:

File:VLC convert save.png

2015-03-28T16:40:43Z

Martin:

Motion MMAL

2015-03-28T13:36:02Z

Martin: /* init.d */

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions you are assumed to have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
Here we simulate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
$ wget --output-document=motion.conf_for_motionstills_debug.conf "http://pastebin.com/raw.php?i=tSjgys2q"
$ ./motion -n -c motion.conf_for_motionstills_debug.conf
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 

== Auto Running at Boot ==
There are several methods to do this.

=== cron ===
TODO

=== rc.local ===
edit the rc.local file as superuser and add the command to the end of the file.
see
http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs

=== init.d ===
create a runtime script for motion in the init.d folder
<pre>
$ sudo nano /etc/init.d/run_motion.sh
</pre>

add the following lines
<pre>
#!/bin/sh
/home/pi/motion/./motion
</pre>
Save the script and exit using Ctrl-X

Initialise the runtime using
<pre>
$ sudo update-rc.d run_motion.sh defaults
</pre>

==== disable init.d ====
<pre>
sudo update-rc.d run_motion.sh stop levels .
</pre>
or
<pre>
sudo update-rc.d -f run_motion.sh remove
</pre>

For temporary disable add a '#' to the call to the motion program, re-save the script and reboot the Pi.
<pre>
#!/bin/sh
# /home/pi/motion/./motion
</pre>

== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

Motion MMAL

2015-03-28T13:13:15Z

Martin: /* Adapting the Config File */

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions you are assumed to have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
Here we simulate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
$ wget --output-document=motion.conf_for_motionstills_debug.conf "http://pastebin.com/raw.php?i=tSjgys2q"
$ ./motion -n -c motion.conf_for_motionstills_debug.conf
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 

== Auto Running at Boot ==
There are several methods to do this.

=== cron ===
TODO

=== rc.local ===
edit the rc.local file as superuser and add the command to the end of the file.
see
http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs

=== init.d ===
create a runtime script for motion in the init.d folder
<pre>
$ sudo nano /etc/init.d/run_motion.sh
</pre>

add the following lines
<pre>
#!/bin/sh
/home/pi/motion/./motion
</pre>
Save the script and exit using Ctrl-X

Initialise the runtime using
<pre>
$ sudo update-rc.d run_motion.sh defaults
</pre>

to prevent the autostart either delete the script or for temporary disable add a '#' to the call to the motion program, resave the script and reboot the Pi.
<pre>
#!/bin/sh
# /home/pi/motion/./motion
</pre>

== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

File:Robox3DPrinter20140925 171644.jpg

2014-10-13T18:05:56Z

Martin: Kickstarter 3D Printer, ROBOX

Kickstarter 3D Printer, ROBOX

File:CISECOPiLite.JPG

2013-12-24T11:54:53Z

Martin: CISECO PiLite LED array for Raspberry Pi.

CISECO PiLite LED array for Raspberry Pi.

Pi Lite

2013-12-23T00:53:37Z

Martin:

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
Install minicom
<pre>
sudo apt-get install minicom
</pre>

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/298-pilite-twitter-feed

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python ~/PiLite/Python_Examples/PiLiteWeather.py</pre>

== Using Minicom ==
Access the serial port using
<pre>
minicom -b 9600 -o -D /dev/ttyAMA0
</pre>

<pre>
Welcome to minicom 2.6.1

OPTIONS: I18n
Compiled on Apr 28 2012, 19:24:31.
Port /dev/ttyAMA0

Press CTRL-A Z for help on special keys
</pre>

Short phrases can be types to the terminal, due to the timeout longer phrases should be pasted from a text file, try this
<code>The quick brown fox jumped over the lazy dog.</code>

To exit the terminal press CTRL-A then x to access the quit prompt.

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== Known Issues ==
# 'PiLiteXively.py' does not work and throws an error
<pre>
python ~/PiLite/Python_Examples/PiLiteXively.py
Traceback (most recent call last):
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 42, in <module>
main()
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 34, in main
source = XivelyDatastream(44519)
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 24, in __init__
self.api = xively.XivelyAPIClient(conf.get('xively', 'apikey'))
File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'xively'
</pre>

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:45:55Z

Martin: /* Minicom */

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
Install minicom
<pre>
sudo apt-get install minicom
</pre>

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/298-pilite-twitter-feed

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python ~/PiLite/Python_Examples/PiLiteWeather.py</pre>

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== Known Issues ==
# 'PiLiteXively.py' does not work and throws an error
<pre>
python ~/PiLite/Python_Examples/PiLiteXively.py
Traceback (most recent call last):
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 42, in <module>
main()
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 34, in main
source = XivelyDatastream(44519)
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 24, in __init__
self.api = xively.XivelyAPIClient(conf.get('xively', 'apikey'))
File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'xively'
</pre>

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:43:38Z

Martin: /* Twitter Feed Installation */

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
sudo apt-get install minicom

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/298-pilite-twitter-feed

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python ~/PiLite/Python_Examples/PiLiteWeather.py</pre>

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== Known Issues ==
# 'PiLiteXively.py' does not work and throws an error
<pre>
python ~/PiLite/Python_Examples/PiLiteXively.py
Traceback (most recent call last):
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 42, in <module>
main()
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 34, in main
source = XivelyDatastream(44519)
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 24, in __init__
self.api = xively.XivelyAPIClient(conf.get('xively', 'apikey'))
File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'xively'
</pre>

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:42:34Z

Martin:

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
sudo apt-get install minicom

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python ~/PiLite/Python_Examples/PiLiteWeather.py</pre>

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== Known Issues ==
# 'PiLiteXively.py' does not work and throws an error
<pre>
python ~/PiLite/Python_Examples/PiLiteXively.py
Traceback (most recent call last):
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 42, in <module>
main()
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 34, in main
source = XivelyDatastream(44519)
File "/home/pi/PiLite/Python_Examples/PiLiteXively.py", line 24, in __init__
self.api = xively.XivelyAPIClient(conf.get('xively', 'apikey'))
File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'xively'
</pre>

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:38:26Z

Martin: /* Example Python Programmes */

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
sudo apt-get install minicom

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python ~/PiLite/Python_Examples/PiLiteWeather.py</pre>

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:36:22Z

Martin: /* Example Python Programmes */

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
sudo apt-get install minicom

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python PiLiteWeather.py</pre>

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:31:38Z

Martin: /* Example Python Programmes */

[[Category:RaspberryPi]]
[[Category:NOOBS]]

The Pi-Lite is an LED matrix display designed for scrolling text and graphics. It connects directly into the Raspberry Pi GPIO ports and requires no hardware hacking [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/]

== Starting Point ==
The following assumes you have a working RPi set-up with the default user, see [[Setup_NOOBS]].
Your RPi is connected to the internet ans is up to date.

== Installation ==
The Pi-Lite developer provides the full documentation [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide] and user guide [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi]

The following assumes you are logging into your Raspberry Pi via ans SSH terminal [[Enable_SSH#Connect_via_SSH_on_a_Local_network]]

=== Access to the serial port ===
By default the Raspberry Pi’s serial port is configured to be used for console input/output. Whilst this is useful if you want to login using the serial port, it means you can't use the Serial Port in your programs. The Pi-Lite requires access to the Serial Port.

To enable the serial port for your own use you need to disable login on the port. There are two files that need to be edited '/etc/inittab' and '/boot/cmdline.txt'

Edit 'inittab' and comment out the line 'T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100' using the '#'. Its at the end of the file
<pre>
sudo nano /etc/inittab
</pre>
Edit 'cmdline.txt' and delete the highlighted section
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
<pre>
sudo nano /boot/cmdline.txt
</pre>

Reboot your Pi.
<pre>
sudo reboot
</pre>

=== Minicom ===
sudo apt-get install minicom

=== Serial Port Access Group : DialOut ===
Add the pi user to the dialout group
<pre>
sudo usermod -a -G dialout pi
</pre>

=== GIT the code ===
Install the required tools

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/303-pi-lite-setting-up-for-python-examples

<pre>
sudo apt-get install git python-serial python-setuptools
sudo easy_install pip
</pre>

<pre>sudo pip install arrow
sudo pip install --pre xively-python
</pre>

Clone the Pi-Lite GIT repository
<pre>
cd ~ && git clone git://github.com/CisecoPlc/PiLite.git
</pre>

==== Twitter Feed Installation ====
The Twitter module installation is a bit more involved
<pre>
git clone git://github.com/bear/python-twitter.git
cd python-twitter
sudo pip install -r requirements.txt
python setup.py build
sudo python setup.py install
</pre>

== Example Python Programmes ==
List the examples with
<pre>
ls -l ~/PiLite/Python_Examples/
</pre>

<pre>
-rwxr-xr-x 1 pi pi 1622 Dec 23 00:36 Bargraph_tk.py
-rwxr-xr-x 1 pi pi 7117 Dec 23 00:36 BarScroll.py
-rwxr-xr-x 1 pi pi 3232 Dec 23 00:36 BarUpDown.py
-rwxr-xr-x 1 pi pi 646 Dec 23 00:36 Pacman.py
-rwxr-xr-x 1 pi pi 29151 Dec 23 00:36 PiLiteEmulator.py
-rw-r--r-- 1 pi pi 1635 Dec 23 00:36 PiLiteLib.py
-rwxr-xr-x 1 pi pi 1146 Dec 23 00:36 PiLiteStock.py
-rwxr-xr-x 1 pi pi 1898 Dec 23 00:36 PiLiteTwitter.py
-rwxr-xr-x 1 pi pi 874 Dec 23 00:36 PiLiteWeather.py
-rwxr-xr-x 1 pi pi 720 Dec 23 00:36 PiLiteWorldTime.py
-rwxr-xr-x 1 pi pi 931 Dec 23 00:36 PiLiteXively.py
-rw-r--r-- 1 pi pi 1895 Dec 23 00:36 ReadMe.txt
drwxr-xr-x 2 pi pi 4096 Dec 23 00:36 twitter
-rwxr-xr-x 1 pi pi 913 Dec 23 00:36 VUSample.py
-rwxr-xr-x 1 pi pi 655 Dec 23 00:36 VU_tk.py
</pre>

Run any of the examples using the script name
<pre>python PiLiteWeather.py</pre>
or
<pre>./PiLiteWeather.py</pre>

== Developing your own uses ==
The Pi-lite developers offer a user graphical interface for emulating the Pi-Lite, thisi is useful for development and experimentation.

http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/305-pi-lite-python-emulator

see
'Python_Examples/PiLiteEmulator.py'

== References ==
# [http://shop.ciseco.co.uk/pi-lite-lots-of-leds-for-the-raspberry-pi-0805-red/ Pi-Lite - Lots of LEDs for the Raspberry Pi]
# [http://www.openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/280-b040-pi-lite-beginners-guide Pi-lite documentation]
# [http://openmicros.org/index.php/articles/94-ciseco-product-documentation/raspberry-pi/283-setting-up-my-raspberry-pi Pi-Lite set-up user guide]

Pi Lite

2013-12-23T00:29:36Z

Martin: /* GIT the code */

Pi Lite

2013-12-23T00:25:30Z

Martin: /* Starting Point */

Pi Lite

2013-12-23T00:24:21Z

Martin: /* GIT the code */

Pi Lite

2013-12-23T00:18:04Z

Martin: /* Access to the serial port */

Pi Lite

2013-12-23T00:10:27Z

Martin: initial version - not tested!

Setup NOOBS

2013-12-22T23:54:44Z

Martin: /* Updates */ patience notice

[[Category:RaspberryPi]]

This article aims to walk through the installation process as defined for NOOBS version 1.3.2 (Nov 2013). The official documentation can be found here. [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf]

== What is NOOBS ==
NOOBS is the Raspberry Pi Foundations own simple Operating System installation software for the Raspberry Pi. It's called 'New Out Of Box Software' (NOOBS) [http://www.raspberrypi.org/archives/4100]

The NOOBS system aims to reduce the complexity of installation by providing the user a simpler method of copying the operating system the RPi SD card and to allow multiple operating systems to be installed on the same SD card (subject to capacity).

== Download the NOOBS ZIP File ==
The RPi Foundation maintains numerous ways of obtaining the NOOBS installation package. [http://www.raspberrypi.org/downloads].
Whichever way you download NOOBS you end up with a single zip file like 'NOOBS_v1_3_2.zip'.

== Format your SD card ==
There areseveral ways of doing this depending on the operating system of the computer you have available.
=== Windows ===
Download and install the SD Association's Formatting tool from [https://www.sdcard.org/downloads/formatter_4/eula_windows/].
Install the tools and Open the Application. Simple follow the oline instructions.

=== Linux GUI ===
If you're using a flavour of Linux with a user interface it is recommended to use 'gparted'.

=== Raspberry Pi or Linux Command Line ===
The following describes each step.

<pre>sudo fdisk -cu /dev/sdc</pre>
<pre> Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e7b31
Device Boot Start End Blocks Id System
/dev/sdc1 8192 122879 57344 c W95 FAT32 (LBA)
/dev/sdc2 122880 15278079 7577600 83 Linux</pre>

The example SD card has an existing installation, delete the partitions using:
<pre>
Command (m for help): d
Partition number (1-4): 1

Command (m for help): d
Selected partition 2

Command (m for help):
</pre>

Add a new partion and set the type to FAT32

<pre>
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (2048-15278079, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-15278079, default 15278079):
Using default value 15278079
</pre>
Change the partion type
<pre>
Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 83 Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): L

0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
1 FAT12 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT-
2 XENIX root 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT-
3 XENIX usr 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
4 FAT16 <32M 41 PPC PReP Boot 85 Linux extended c7 Syrinx
5 Extended 42 SFS 86 NTFS volume set da Non-FS data
6 FAT16 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / .
7 HPFS/NTFS 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility
8 AIX 4f QNX4.x 3rd part 8e Linux LVM df BootIt
9 AIX bootable 50 OnTrack DM 93 Amoeba e1 DOS access
a OS/2 Boot Manag 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
b W95 FAT32 52 CP/M 9f BSD/OS e4 SpeedStor
c W95 FAT32 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
e W95 FAT16 (LBA) 54 OnTrackDM6 a5 FreeBSD ee GPT
f W95 Ext'd (LBA) 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
10 OPUS 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b
11 Hidden FAT12 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
12 Compaq diagnost 61 SpeedStor a9 NetBSD f4 SpeedStor
14 Hidden FAT16 <3 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary
16 Hidden FAT16 64 Novell Netware af HFS / HFS+ fb VMware VMFS
17 Hidden HPFS/NTF 65 Novell Netware b7 BSDI fs fc VMware VMKCORE
18 AST SmartSleep 70 DiskSecure Mult b8 BSDI swap fd Linux raid auto
1b Hidden W95 FAT3 75 PC/IX bb Boot Wizard hid fe LANstep
1c Hidden W95 FAT3 80 Old Minix be Solaris boot ff BBT
1e Hidden W95 FAT1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 c W95 FAT32 (LBA)
</pre>

Write the changes and exist
<pre>
Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
</pre>

Format the partition
<pre>
sudo mkfs.vfat /dev/sdc1
</pre>

== Copy contents of the NOOBS zip ==

=== Linux ===
Copy and extract the files to your SD Card, note the device can be found using the <code> df -h </code> command one the SD card is re-inserted to the host machine and auto mounted.
<pre>
unzip NOOBS_v1_3_2.zip -d /media/3D4D-A03B/
</pre>

Unmount the SD card
<pre>
sudo umount /media/3D4D-A03B/
</pre>

Install the SD card in your RPi SD Card slot, make sure your Pi si connected to a monitor. mouse and keyboard.

== NOOBS First Boot ==
Power up your RPi and you'll be presented with a screen image on your monitor or TV that shows it formatting the spare space on your SD card then showing the OS selection prompt / screen.

Select the Operating System of your choice (here we select the recommended Raspian).

Wait whilst the NOOBS installer overwrites the SD card. Approximately 2GB of data (@NOOBS 1.3.2) is required, on my system the write speed is ~1MB/s, the installation requires about 3minutes.

If you are new to the RPI its worth watching the screen shots during installation as they offer a wealth of useful info.

Click OK once the installation prompt appears and the RPi will reboot.

== Post installation set-up ==
On first boot the NOOBS installation of Raspian will show the installation helper raspi-config which allow location and many other features to be defined.

Consult the official documentation for the many options available. The minimum is to set your language,location,timezone and keyboard.

Remember the default user is 'pi' and the username is 'raspberry'.

== Updates ==
Optionally after intial set-up its recommended that the user update their operating system, this is easily achieved using the command line interface using
<pre>
sudo apt-get update
sudo apt-get -y upgrade
sudo /usr/bin/rpi-update
sudo apt-get clean
</pre>

The sequence of commands can be executed is series using
<pre>
sudo apt-get update && sudo apt-get -y upgrade && sudo /usr/bin/rpi-update && sudo apt-get clean
</pre>

Depending on how many changes there are, updating can take a long time, please be patient.

== References ==
# [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf NOOBS quick Start Guide from the RPI Foundation]
# [http://www.raspberrypi.org/archives/4100 Raspberry Pi Foundation NOOBS release notification]
# http://www.raspberrypi.org/downloads
# [https://www.sdcard.org/downloads/formatter_4/eula_windows/ Official Windows SD card formatting tools]

Setup NOOBS

2013-12-22T23:53:46Z

Martin: /* Format you SD card */ typo

[[Category:RaspberryPi]]

This article aims to walk through the installation process as defined for NOOBS version 1.3.2 (Nov 2013). The official documentation can be found here. [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf]

== What is NOOBS ==
NOOBS is the Raspberry Pi Foundations own simple Operating System installation software for the Raspberry Pi. It's called 'New Out Of Box Software' (NOOBS) [http://www.raspberrypi.org/archives/4100]

The NOOBS system aims to reduce the complexity of installation by providing the user a simpler method of copying the operating system the RPi SD card and to allow multiple operating systems to be installed on the same SD card (subject to capacity).

== Download the NOOBS ZIP File ==
The RPi Foundation maintains numerous ways of obtaining the NOOBS installation package. [http://www.raspberrypi.org/downloads].
Whichever way you download NOOBS you end up with a single zip file like 'NOOBS_v1_3_2.zip'.

== Format your SD card ==
There areseveral ways of doing this depending on the operating system of the computer you have available.
=== Windows ===
Download and install the SD Association's Formatting tool from [https://www.sdcard.org/downloads/formatter_4/eula_windows/].
Install the tools and Open the Application. Simple follow the oline instructions.

=== Linux GUI ===
If you're using a flavour of Linux with a user interface it is recommended to use 'gparted'.

=== Raspberry Pi or Linux Command Line ===
The following describes each step.

<pre>sudo fdisk -cu /dev/sdc</pre>
<pre> Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e7b31
Device Boot Start End Blocks Id System
/dev/sdc1 8192 122879 57344 c W95 FAT32 (LBA)
/dev/sdc2 122880 15278079 7577600 83 Linux</pre>

The example SD card has an existing installation, delete the partitions using:
<pre>
Command (m for help): d
Partition number (1-4): 1

Command (m for help): d
Selected partition 2

Command (m for help):
</pre>

Add a new partion and set the type to FAT32

<pre>
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (2048-15278079, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-15278079, default 15278079):
Using default value 15278079
</pre>
Change the partion type
<pre>
Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 83 Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): L

0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
1 FAT12 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT-
2 XENIX root 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT-
3 XENIX usr 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
4 FAT16 <32M 41 PPC PReP Boot 85 Linux extended c7 Syrinx
5 Extended 42 SFS 86 NTFS volume set da Non-FS data
6 FAT16 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / .
7 HPFS/NTFS 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility
8 AIX 4f QNX4.x 3rd part 8e Linux LVM df BootIt
9 AIX bootable 50 OnTrack DM 93 Amoeba e1 DOS access
a OS/2 Boot Manag 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
b W95 FAT32 52 CP/M 9f BSD/OS e4 SpeedStor
c W95 FAT32 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
e W95 FAT16 (LBA) 54 OnTrackDM6 a5 FreeBSD ee GPT
f W95 Ext'd (LBA) 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
10 OPUS 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b
11 Hidden FAT12 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
12 Compaq diagnost 61 SpeedStor a9 NetBSD f4 SpeedStor
14 Hidden FAT16 <3 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary
16 Hidden FAT16 64 Novell Netware af HFS / HFS+ fb VMware VMFS
17 Hidden HPFS/NTF 65 Novell Netware b7 BSDI fs fc VMware VMKCORE
18 AST SmartSleep 70 DiskSecure Mult b8 BSDI swap fd Linux raid auto
1b Hidden W95 FAT3 75 PC/IX bb Boot Wizard hid fe LANstep
1c Hidden W95 FAT3 80 Old Minix be Solaris boot ff BBT
1e Hidden W95 FAT1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 c W95 FAT32 (LBA)
</pre>

Write the changes and exist
<pre>
Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
</pre>

Format the partition
<pre>
sudo mkfs.vfat /dev/sdc1
</pre>

== Copy contents of the NOOBS zip ==

=== Linux ===
Copy and extract the files to your SD Card, note the device can be found using the <code> df -h </code> command one the SD card is re-inserted to the host machine and auto mounted.
<pre>
unzip NOOBS_v1_3_2.zip -d /media/3D4D-A03B/
</pre>

Unmount the SD card
<pre>
sudo umount /media/3D4D-A03B/
</pre>

Install the SD card in your RPi SD Card slot, make sure your Pi si connected to a monitor. mouse and keyboard.

== NOOBS First Boot ==
Power up your RPi and you'll be presented with a screen image on your monitor or TV that shows it formatting the spare space on your SD card then showing the OS selection prompt / screen.

Select the Operating System of your choice (here we select the recommended Raspian).

Wait whilst the NOOBS installer overwrites the SD card. Approximately 2GB of data (@NOOBS 1.3.2) is required, on my system the write speed is ~1MB/s, the installation requires about 3minutes.

If you are new to the RPI its worth watching the screen shots during installation as they offer a wealth of useful info.

Click OK once the installation prompt appears and the RPi will reboot.

== Post installation set-up ==
On first boot the NOOBS installation of Raspian will show the installation helper raspi-config which allow location and many other features to be defined.

Consult the official documentation for the many options available. The minimum is to set your language,location,timezone and keyboard.

Remember the default user is 'pi' and the username is 'raspberry'.

== Updates ==
Optionally after intial set-up its recommended that the user update their operating system, this is easily achieved using the command line interface using
<pre>
sudo apt-get update
sudo apt-get -y upgrade
sudo /usr/bin/rpi-update
sudo apt-get clean
</pre>

The sequence of commands can be executed is series using
<pre>
sudo apt-get update && sudo apt-get -y upgrade && sudo /usr/bin/rpi-update && sudo apt-get clean
</pre>

== References ==
# [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf NOOBS quick Start Guide from the RPI Foundation]
# [http://www.raspberrypi.org/archives/4100 Raspberry Pi Foundation NOOBS release notification]
# http://www.raspberrypi.org/downloads
# [https://www.sdcard.org/downloads/formatter_4/eula_windows/ Official Windows SD card formatting tools]

Setup NOOBS

2013-12-22T23:25:07Z

Martin: added update commands

[[Category:RaspberryPi]]

This article aims to walk through the installation process as defined for NOOBS version 1.3.2 (Nov 2013). The official documentation can be found here. [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf]

== What is NOOBS ==
NOOBS is the Raspberry Pi Foundations own simple Operating System installation software for the Raspberry Pi. It's called 'New Out Of Box Software' (NOOBS) [http://www.raspberrypi.org/archives/4100]

The NOOBS system aims to reduce the complexity of installation by providing the user a simpler method of copying the operating system the RPi SD card and to allow multiple operating systems to be installed on the same SD card (subject to capacity).

== Download the NOOBS ZIP File ==
The RPi Foundation maintains numerous ways of obtaining the NOOBS installation package. [http://www.raspberrypi.org/downloads].
Whichever way you download NOOBS you end up with a single zip file like 'NOOBS_v1_3_2.zip'.

== Format you SD card ==
There areseveral ways of doing this depending on the operating system of the computer you have available.
=== Windows ===
Download and install the SD Association's Formatting tool from [https://www.sdcard.org/downloads/formatter_4/eula_windows/].
Install the tools and Open the Application. Simple follow the oline instructions.

=== Linux GUI ===
If you're using a flavour of Linux with a user interface it is recommended to use 'gparted'.

=== Raspberry Pi or Linux Command Line ===
The following describes each step.

<pre>sudo fdisk -cu /dev/sdc</pre>
<pre> Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e7b31
Device Boot Start End Blocks Id System
/dev/sdc1 8192 122879 57344 c W95 FAT32 (LBA)
/dev/sdc2 122880 15278079 7577600 83 Linux</pre>

The example SD card has an existing installation, delete the partitions using:
<pre>
Command (m for help): d
Partition number (1-4): 1

Command (m for help): d
Selected partition 2

Command (m for help):
</pre>

Add a new partion and set the type to FAT32

<pre>
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (2048-15278079, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-15278079, default 15278079):
Using default value 15278079
</pre>
Change the partion type
<pre>
Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 83 Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): L

0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
1 FAT12 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT-
2 XENIX root 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT-
3 XENIX usr 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
4 FAT16 <32M 41 PPC PReP Boot 85 Linux extended c7 Syrinx
5 Extended 42 SFS 86 NTFS volume set da Non-FS data
6 FAT16 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / .
7 HPFS/NTFS 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility
8 AIX 4f QNX4.x 3rd part 8e Linux LVM df BootIt
9 AIX bootable 50 OnTrack DM 93 Amoeba e1 DOS access
a OS/2 Boot Manag 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
b W95 FAT32 52 CP/M 9f BSD/OS e4 SpeedStor
c W95 FAT32 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
e W95 FAT16 (LBA) 54 OnTrackDM6 a5 FreeBSD ee GPT
f W95 Ext'd (LBA) 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
10 OPUS 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b
11 Hidden FAT12 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
12 Compaq diagnost 61 SpeedStor a9 NetBSD f4 SpeedStor
14 Hidden FAT16 <3 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary
16 Hidden FAT16 64 Novell Netware af HFS / HFS+ fb VMware VMFS
17 Hidden HPFS/NTF 65 Novell Netware b7 BSDI fs fc VMware VMKCORE
18 AST SmartSleep 70 DiskSecure Mult b8 BSDI swap fd Linux raid auto
1b Hidden W95 FAT3 75 PC/IX bb Boot Wizard hid fe LANstep
1c Hidden W95 FAT3 80 Old Minix be Solaris boot ff BBT
1e Hidden W95 FAT1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 c W95 FAT32 (LBA)
</pre>

Write the changes and exist
<pre>
Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
</pre>

Format the partition
<pre>
sudo mkfs.vfat /dev/sdc1
</pre>

== Copy contents of the NOOBS zip ==

=== Linux ===
Copy and extract the files to your SD Card, note the device can be found using the <code> df -h </code> command one the SD card is re-inserted to the host machine and auto mounted.
<pre>
unzip NOOBS_v1_3_2.zip -d /media/3D4D-A03B/
</pre>

Unmount the SD card
<pre>
sudo umount /media/3D4D-A03B/
</pre>

Install the SD card in your RPi SD Card slot, make sure your Pi si connected to a monitor. mouse and keyboard.

== NOOBS First Boot ==
Power up your RPi and you'll be presented with a screen image on your monitor or TV that shows it formatting the spare space on your SD card then showing the OS selection prompt / screen.

Select the Operating System of your choice (here we select the recommended Raspian).

Wait whilst the NOOBS installer overwrites the SD card. Approximately 2GB of data (@NOOBS 1.3.2) is required, on my system the write speed is ~1MB/s, the installation requires about 3minutes.

If you are new to the RPI its worth watching the screen shots during installation as they offer a wealth of useful info.

Click OK once the installation prompt appears and the RPi will reboot.

== Post installation set-up ==
On first boot the NOOBS installation of Raspian will show the installation helper raspi-config which allow location and many other features to be defined.

Consult the official documentation for the many options available. The minimum is to set your language,location,timezone and keyboard.

Remember the default user is 'pi' and the username is 'raspberry'.

== Updates ==
Optionally after intial set-up its recommended that the user update their operating system, this is easily achieved using the command line interface using
<pre>
sudo apt-get update
sudo apt-get -y upgrade
sudo /usr/bin/rpi-update
sudo apt-get clean
</pre>

The sequence of commands can be executed is series using
<pre>
sudo apt-get update && sudo apt-get -y upgrade && sudo /usr/bin/rpi-update && sudo apt-get clean
</pre>

== References ==
# [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf NOOBS quick Start Guide from the RPI Foundation]
# [http://www.raspberrypi.org/archives/4100 Raspberry Pi Foundation NOOBS release notification]
# http://www.raspberrypi.org/downloads
# [https://www.sdcard.org/downloads/formatter_4/eula_windows/ Official Windows SD card formatting tools]

Setup NOOBS

2013-12-22T23:16:42Z

Martin: Initial NOOBS installation for Raspian

[[Category:RaspberryPi]]

This article aims to walk through the installation process as defined for NOOBS version 1.3.2 (Nov 2013). The official documentation can be found here. [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf]

== What is NOOBS ==
NOOBS is the Raspberry Pi Foundations own simple Operating System installation software for the Raspberry Pi. It's called 'New Out Of Box Software' (NOOBS) [http://www.raspberrypi.org/archives/4100]

The NOOBS system aims to reduce the complexity of installation by providing the user a simpler method of copying the operating system the RPi SD card and to allow multiple operating systems to be installed on the same SD card (subject to capacity).

== Download the NOOBS ZIP File ==
The RPi Foundation maintains numerous ways of obtaining the NOOBS installation package. [http://www.raspberrypi.org/downloads].
Whichever way you download NOOBS you end up with a single zip file like 'NOOBS_v1_3_2.zip'.

== Format you SD card ==
There areseveral ways of doing this depending on the operating system of the computer you have available.
=== Windows ===
Download and install the SD Association's Formatting tool from [https://www.sdcard.org/downloads/formatter_4/eula_windows/].
Install the tools and Open the Application. Simple follow the oline instructions.

=== Linux GUI ===
If you're using a flavour of Linux with a user interface it is recommended to use 'gparted'.

=== Raspberry Pi or Linux Command Line ===
The following describes each step.

<pre>sudo fdisk -cu /dev/sdc</pre>
<pre> Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e7b31
Device Boot Start End Blocks Id System
/dev/sdc1 8192 122879 57344 c W95 FAT32 (LBA)
/dev/sdc2 122880 15278079 7577600 83 Linux</pre>

The example SD card has an existing installation, delete the partitions using:
<pre>
Command (m for help): d
Partition number (1-4): 1

Command (m for help): d
Selected partition 2

Command (m for help):
</pre>

Add a new partion and set the type to FAT32

<pre>
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (2048-15278079, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-15278079, default 15278079):
Using default value 15278079
</pre>
Change the partion type
<pre>
Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 83 Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): L

0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
1 FAT12 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT-
2 XENIX root 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT-
3 XENIX usr 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
4 FAT16 <32M 41 PPC PReP Boot 85 Linux extended c7 Syrinx
5 Extended 42 SFS 86 NTFS volume set da Non-FS data
6 FAT16 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / .
7 HPFS/NTFS 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility
8 AIX 4f QNX4.x 3rd part 8e Linux LVM df BootIt
9 AIX bootable 50 OnTrack DM 93 Amoeba e1 DOS access
a OS/2 Boot Manag 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
b W95 FAT32 52 CP/M 9f BSD/OS e4 SpeedStor
c W95 FAT32 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
e W95 FAT16 (LBA) 54 OnTrackDM6 a5 FreeBSD ee GPT
f W95 Ext'd (LBA) 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
10 OPUS 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b
11 Hidden FAT12 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
12 Compaq diagnost 61 SpeedStor a9 NetBSD f4 SpeedStor
14 Hidden FAT16 <3 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary
16 Hidden FAT16 64 Novell Netware af HFS / HFS+ fb VMware VMFS
17 Hidden HPFS/NTF 65 Novell Netware b7 BSDI fs fc VMware VMKCORE
18 AST SmartSleep 70 DiskSecure Mult b8 BSDI swap fd Linux raid auto
1b Hidden W95 FAT3 75 PC/IX bb Boot Wizard hid fe LANstep
1c Hidden W95 FAT3 80 Old Minix be Solaris boot ff BBT
1e Hidden W95 FAT1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

Command (m for help): p

Disk /dev/sdc: 7822 MB, 7822376960 bytes
241 heads, 62 sectors/track, 1022 cylinders, total 15278080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c7b31

Device Boot Start End Blocks Id System
/dev/sdc1 2048 15278079 7638016 c W95 FAT32 (LBA)
</pre>

Write the changes and exist
<pre>
Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
</pre>

Format the partition
<pre>
sudo mkfs.vfat /dev/sdc1
</pre>

== Copy contents of the NOOBS zip ==

=== Linux ===
Copy and extract the files to your SD Card, note the device can be found using the <code> df -h </code> command one the SD card is re-inserted to the host machine and auto mounted.
<pre>
unzip NOOBS_v1_3_2.zip -d /media/3D4D-A03B/
</pre>

Unmount the SD card
<pre>
sudo umount /media/3D4D-A03B/
</pre>

Install the SD card in your RPi SD Card slot, make sure your Pi si connected to a monitor. mouse and keyboard.

== NOOBS First Boot ==
Power up your RPi and you'll be presented with a screen image on your monitor or TV that shows it formatting the spare space on your SD card then showing the OS selection prompt / screen.

Select the Operating System of your choice (here we select the recommended Raspian).

Wait whilst the NOOBS installer overwrites the SD card. Approximately 2GB of data (@NOOBS 1.3.2) is required, on my system the write speed is ~1MB/s, the installation requires about 3minutes.

If you are new to the RPI its worth watching the screen shots during installation as they offer a wealth of useful info.

Click OK once the installation prompt appears and the RPi will reboot.

== Post installation set-up ==
On first boot the NOOBS installation of Raspian will show the installation helper raspi-config which allow location and many other features to be defined.

Consult the official documentation for the many options available. The minimum is to set your language,location,timezone and keyboard.

Remember the default user is 'pi' and the username is 'raspberry'.

== References ==
# [http://www.raspberrypi.org/wp-content/uploads/2012/04/quick-start-guide-v2_1.pdf NOOBS quick Start Guide from the RPI Foundation]
# [http://www.raspberrypi.org/archives/4100 Raspberry Pi Foundation NOOBS release notification]
# http://www.raspberrypi.org/downloads
# [https://www.sdcard.org/downloads/formatter_4/eula_windows/ Official Windows SD card formatting tools]

Motion MMAL

2013-10-22T21:43:15Z

Martin: /* Adapting the Config File */

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions you are assumed to have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
Here we simulate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
$ wget --output-document=motion.conf_for_motionstills_debug.conf "http://pastebin.com/raw.php?i=tSjgys2q"
$ ./motion -n -c motion.conf_for_motionstills_debug.conf
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 

== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

Motion MMAL

2013-10-22T21:41:41Z

Martin: /* Adapting the Config File */

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions you are assumed to have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
Here we simulate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
wget --output-document=motion.conf_for_motionstills_debug.conf "http://pastebin.com/raw.php?i=tSjgys2q"
./motion -n -c motion.conf_for_motionstills_debug.conf
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 

== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

Motion MMAL

2013-10-22T21:33:50Z

Martin: /* Introduction */

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions you are assumed to have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
Here we simulate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
wget http://pastebin.com/raw.php?i=tSjgys2q
mv raw.php?i=tSjgys2q motion.conf_for_motionstills_debug.txt
./motion -n -c motion.conf_for_motionstills_debug.txt
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 
== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

Motion MMAL

2013-10-22T21:32:51Z

Martin: /* Install dependencies for Motion */

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions assume you have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
Here we simulate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
wget http://pastebin.com/raw.php?i=tSjgys2q
mv raw.php?i=tSjgys2q motion.conf_for_motionstills_debug.txt
./motion -n -c motion.conf_for_motionstills_debug.txt
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 
== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

Motion MMAL

2013-10-22T21:12:56Z

Martin: first version

[[Category:RaspberryPi]]
[[Category:Projects]]

Collated from the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]

== Introduction ==
The objective of this How To is install a special binary of Motion compiled with support for the Raspberry Pi Camera Module.

A special binary for motion has been compiled by the RPi community. Specifically dozencrows [http://www.raspberrypi.org/phpBB3/memberlist.php?mode=viewprofile&u=29285]

Before you start these instructions assume you have a configured RPi running an up to date version of Raspian, a RPi Camera module plugged in and working with stock tools such as the <code>raspistill</code>.

== Installation ==
=== Install dependencies for Motion ===
He we similate the installation of the standard version of motion which works with USB webcams but not the RPi Camera.
The purpose is to determine what packages and dependencies are needed.

<pre> $ sudo apt-get -s install motion</pre>
Should return something like
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 mysql-common
Suggested packages:
jackd2 libraw1394-doc speex mysql-client postgresql-client
The following NEW packages will be installed:
ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0
libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3
libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1
libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion
mysql-common
0 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
</pre>

Install the dependcies using
<pre> $ sudo apt-get install -y <list from the above step here> </pre>
on my system this is
<pre style="white-space: pre-wrap;"> $ sudo apt-get install -y ffmpeg libav-tools libavcodec53 libavdevice53 libavfilter2 libavformat53 libavutil51 libdc1394-22 libdirac-encoder0 libgsm1 libjack-jackd2-0 libmp3lame0 libmysqlclient18 libopencv-core2.3 libopencv-imgproc2.3 libpostproc52 libpq5 libraw1394-11 libschroedinger-1.0-0 libspeex1 libswscale2 libtheora0 libva1 libvpx1 libx264-123 libxvidcore4 motion mysql-common</pre>

Wait patiently for the installation to complete.

=== Download the pre-compiled binary ===
Download and unzip the binary provided by Dozencrows.
<pre>
$ wget https://www.dropbox.com/s/xdfcxm5hu71s97d/motion-mmal.tar.gz
$ tar -zxvf motion-mmal.tar.gz
</pre>

=== Test Run ===
Run motion with the default configuration file and monitor the output.
<pre>
$ ./motion -n -c motion-mmalcam.conf
</pre>
Naviate to <your.RPI.IP>:8081 from anther computer to see the video. Some users have reported issues with this when using InternetExplorer on windows. An alternative browser such as FireFox or Chrome should work.

== Adapting the Config File ==
My test download file can be downloaded and tried using the following
<pre>
wget http://pastebin.com/raw.php?i=tSjgys2q
mv raw.php?i=tSjgys2q motion.conf_for_motionstills_debug.txt
./motion -n -c motion.conf_for_motionstills_debug.txt
</pre>

[[File:MotionExampleImg3044.jpg|200px|thumb|left| Example Output running at 1920x720]]
 
== TO DO LIST ==
# Add scripts for starting and stopping motion with Cron.
# Set up Motion to work with a NAS to record data [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]
# Offload Motion to another Pi or Linux PC using streaming (should improve frame rates).

== References ==
# [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=44966 Raspberry Pi forum for using Motion with a Raspberry Pi Camera Module]
# [http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/ http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/]

Mythbuntu12.04

2013-09-29T12:54:39Z

Martin: /* Install TV Card Drivers */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
Drivers can be obtained from http://www.tbsdtv.com/download/#tbs6280 other resources which i use to determine if there are updated drivers include:
# https://www.changedetection.com/log/tbsdtv/drivers-applications-update_log.html
# http://www.changedetection.com/accountfeed.xml?feedid=427127285759800

<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver: use <code>-j3</code> for dual core and <code>-j5</code> for quad to speed up the compilation.
<pre>
$ make -j5
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make clean
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting ===
In the MythtvFronend selection the Setup/Setup Wizard, follow the simple instructions to select and test your audio and video.
My system which uses an Intel GPU supports Audio over HDMI and VA-API[http://en.wikipedia.org/wiki/Video_Acceleration_API]
 [[File:7.1.AudioVideoSetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.2.AudioSettingsetupWizard.png|200px|Initial Screen After Reboot]] 
 [[File:7.3.VideoSettingsVAAPISetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.4.VideoTestVAAPISetupWizard.png|200px|Initial Screen After Reboot]] 

== Adding Tuner Cards ==
<code>Application/System/MythBackendSetup</code>, the backend will have to be stopped before you can continue, agree to the prompt and authorise it with your password.
 [[File:10.1.BackEndSetupOverview.png|200px|Initial Screen After Reboot]] 
=== General ===
Follow the wizard, the defaults are fine, just make sure you set the IP address and select the correct TV Format for the region.
 [[File:8.1.MythtvSetupGeneral001.png|200px|Initial Screen After Reboot]] 
=== Capture Cards ===
Follow the prompts and add your cards, these should be auto detected if the drivers were properly installed [[Mythbuntu12.04#Install_TV_Card_Drivers]]

 [[File:10.2.CaptureCardsList001.png|200px|Initial Screen After Reboot]]
[[File:10.3.CaptureCardsList002.png|200px|Initial Screen After Reboot]] 

=== Video Sources ===
My prefered video source is to use XMLTV, use the following [http://www.mythtv.org/wiki/Uk_xmltv#RECOMMENDED]

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280
# http://linuxtv.org/wiki/index.php/TBS6280
# http://en.wikipedia.org/wiki/Video_Acceleration_API

Mythbuntu12.04

2013-09-13T21:07:00Z

Martin: /* Audio and Video Setting */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting ===
In the MythtvFronend selection the Setup/Setup Wizard, follow the simple instructions to select and test your audio and video.
My system which uses an Intel GPU supports Audio over HDMI and VA-API[http://en.wikipedia.org/wiki/Video_Acceleration_API]
 [[File:7.1.AudioVideoSetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.2.AudioSettingsetupWizard.png|200px|Initial Screen After Reboot]] 
 [[File:7.3.VideoSettingsVAAPISetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.4.VideoTestVAAPISetupWizard.png|200px|Initial Screen After Reboot]] 

== Adding Tuner Cards ==
<code>Application/System/MythBackendSetup</code>, the backend will have to be stopped before you can continue, agree to the prompt and authorise it with your password.
 [[File:10.1.BackEndSetupOverview.png|200px|Initial Screen After Reboot]] 
=== General ===
Follow the wizard, the defaults are fine, just make sure you set the IP address and select the correct TV Format for the region.
 [[File:8.1.MythtvSetupGeneral001.png|200px|Initial Screen After Reboot]] 
=== Capture Cards ===
Follow the prompts and add your cards, these should be auto detected if the drivers were properly installed [[Mythbuntu12.04#Install_TV_Card_Drivers]]

 [[File:10.2.CaptureCardsList001.png|200px|Initial Screen After Reboot]]
[[File:10.3.CaptureCardsList002.png|200px|Initial Screen After Reboot]] 

=== Video Sources ===
My prefered video source is to use XMLTV, use the following [http://www.mythtv.org/wiki/Uk_xmltv#RECOMMENDED]

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280
# http://linuxtv.org/wiki/index.php/TBS6280
# http://en.wikipedia.org/wiki/Video_Acceleration_API

File:10.3.CaptureCardsList002.png

2013-09-13T20:17:45Z

Martin:

File:10.2.CaptureCardsList001.png

2013-09-13T20:17:22Z

Martin:

File:10.1.BackEndSetupOverview.png

2013-09-13T20:15:57Z

Martin:

File:8.1.MythtvSetupGeneral001.png

2013-09-13T19:28:10Z

Martin:

Mythbuntu12.04

2013-09-09T22:07:42Z

Martin: /* References */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting ===
In the MythtvFronend selection the Setup/Setup Wizard, follow the simple instructions to select and test your audio and video.
My system which uses an Intel GPU supports Audio over HDMI and VA-API[http://en.wikipedia.org/wiki/Video_Acceleration_API]
 [[File:7.1.AudioVideoSetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.2.AudioSettingsetupWizard.png|200px|Initial Screen After Reboot]] 
 [[File:7.3.VideoSettingsVAAPISetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.4.VideoTestVAAPISetupWizard.png|200px|Initial Screen After Reboot]] 

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280
# http://linuxtv.org/wiki/index.php/TBS6280
# http://en.wikipedia.org/wiki/Video_Acceleration_API

Mythbuntu12.04

2013-09-09T22:06:57Z

Martin: /* References */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting ===
In the MythtvFronend selection the Setup/Setup Wizard, follow the simple instructions to select and test your audio and video.
My system which uses an Intel GPU supports Audio over HDMI and VA-API[http://en.wikipedia.org/wiki/Video_Acceleration_API]
 [[File:7.1.AudioVideoSetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.2.AudioSettingsetupWizard.png|200px|Initial Screen After Reboot]] 
 [[File:7.3.VideoSettingsVAAPISetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.4.VideoTestVAAPISetupWizard.png|200px|Initial Screen After Reboot]] 

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280
#
# http://en.wikipedia.org/wiki/Video_Acceleration_API

Mythbuntu12.04

2013-09-09T22:06:11Z

Martin: /* Audio and Video Setting */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting ===
In the MythtvFronend selection the Setup/Setup Wizard, follow the simple instructions to select and test your audio and video.
My system which uses an Intel GPU supports Audio over HDMI and VA-API[http://en.wikipedia.org/wiki/Video_Acceleration_API]
 [[File:7.1.AudioVideoSetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.2.AudioSettingsetupWizard.png|200px|Initial Screen After Reboot]] 
 [[File:7.3.VideoSettingsVAAPISetupWizard.png|200px|Initial Screen After Reboot]]
[[File:7.4.VideoTestVAAPISetupWizard.png|200px|Initial Screen After Reboot]] 

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280

File:7.4.VideoTestVAAPISetupWizard.png

2013-09-09T22:06:10Z

Martin:

File:7.3.VideoSettingsVAAPISetupWizard.png

2013-09-09T22:05:10Z

Martin:

File:7.2.AudioSettingsetupWizard.png

2013-09-09T22:03:55Z

Martin:

Mythbuntu12.04

2013-09-09T21:59:44Z

Martin: /* Install TV Card Drivers */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting ===
In the MythtvFronend selection the Setup/Setup Wizard

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280

File:7.1.AudioVideoSetupWizard.png

2013-09-09T21:59:26Z

Martin:

Mythbuntu12.04

2013-09-08T21:14:41Z

Martin: /* Restoring Old Database */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / reload loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

After the database schema is updated, the hostname needs to be changed.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>
If there are other changes to file and folder structures these need to be all changed before any fronends are connected to the restored backend.
'''I can never get this to work satisfactorily'''.

=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting
In the MythtvFronend selection the Setup/Setup Wizard
=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280

Mythbuntu12.04

2013-09-08T21:11:47Z

Martin: /* Restoring Old Database */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>
Also need to change the hostname.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / relode loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>
=== Alternative Approach to Database Backup ===
It seems I can never port an old system and the database sucessfully, usually there's a conflict with some setting or I've restructured the support systems.
Either way, one possible way to export all your recording and reimporting them as videos without changing the can done using mythlink.pl[http://www.mythtv.org/wiki/Mythlink.pl].
# run mythlink to create simlinks on our old backend.
# cp the simlinks to a backup drive, NAS or other external media with plenty of space. When copied the simlink will retain the folder and name structure from mythlink making the filenames user readable.
# Import the old recording into the video folder

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting
In the MythtvFronend selection the Setup/Setup Wizard
=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280

Mythbuntu12.04

2013-09-08T16:37:55Z

Martin:

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>
Also need to change the hostname.
<pre>
/usr/share/mythtv/mythconverg_restore.pl --change_hostname --old_hostname="mr-flibble" --new_hostname="BlueMidget"
</pre>

At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / relode loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Audio and Video Setting
In the MythtvFronend selection the Setup/Setup Wizard
=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280

Mythbuntu12.04

2013-09-08T14:19:01Z

Martin: /* Accessing Network Shares */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
</pre>
don't forget
# create creds file <code>$ nano ~/cifs.cred</code>
# add NAS IP and hostname to <code>/etc/hosts</code>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>
At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / relode loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280

Mythbuntu12.04

2013-09-08T14:15:14Z

Martin: /* Accessing Network Shares */

[[Category: MythTV]]
This page records the setup of Mythbuntu [http://www.mythbuntu.org/] a standalone media PVR suite based on MythTV [http://www.mythtv.org/]

== Hardware ==
*Streacom FC9 Black Full Aluminium Fanless Chassis
*Gigabyte GA-Z87MX-D3H LGA1150 Micro ATX Motherboard
*Intel 4th Gen Core i7 4770 3.4GHz 84W HD4600 8M Quad Core CPU
*Corsair 16GB (2x8GB) Vengeance LP DDR3 Memory
*picoPSU 160W picoPSU and AC/DC adapter block
*Intel 80GB 335 Solid State Drive SSD
*2 off WD Green Power WD20NPVX 2TB 2.5in HDD OEM
*Streacom ST-OB2 Slot-Load Blu-ray Drive for Streacom Chassis
*Streacom Internal IR Receiver and Remote Control
*TBS 6280 Dual Freeview HD Low-profile PCIe TV Tuner Card DVB-T2
*TBS 6981 Dual Satellite HD Low-profile PCIe TV Tuner Card DVB-S2

This machines memory and CPU is overkill even for HD TV, the important things are that there is at least one TV tuner source and ample storage space for recordings.

== Installation ==
Firstly identify the architecture of your PC, most CPUs these days (2013) are 64Bit.
Head over to the download page [http://www.mythbuntu.org/download-type] and download the required iso file.
This guide covers the installation of Mythbuntu12.04 on to a vanilla system, that is an entirely fresh install using '''mythbuntu-12.04.3-desktop-amd64.iso'''.
Basic Installation is straightforward but is somewhat dependent on you hardware and BIOS settings.
This system is connected to a SHARP Aquos TV via an HDMI cable with a USB keyboard and mouse and connected to the internet and my network via an ethernet cable.
# Burn the ISO to a DVD
# Install and boot the PC from the ISO
# Select 'Install Mythbuntu'
# Select the Drive to install the OS too. I used the SSD drive and disabled LVM so i can mount the main storage myself later.
# Select country, timezone, keyboard etc. This is all the normal questions, pay special attention to the following
## enable the check box to install 3rd party software that is not Open Source.
## if you intend to remotely connect to your system during setup, ensure VNC and SSH service are enabled

Once installation is complete the PC will ask you to remove the DVD and press <code>Enter</code> to reboot the machine.

== System Setup ==
=== Objectives ===
# Demonstrate HD TV, both live recording
# Configure TV listings using XMLTV
# Control the system with the IR Remote

Since this system is replacing my currently deployed HD-PVR I will also be transfering existing MythTV database and SD recordings to the new system.

=== Update the System ===
Once your PC has rebooted it should autologin with the default user and launch the MythTV Frontend. Note
 [[File:1.MainScreenAfterReboot.png|200px|Initial Screen After Reboot]] 

Using the Update Manager or Terminal update the system, you will need to authenticate using the password of the user created during installation.
 [[File:2.UpdateManagerGUI.png|200px|Update Manager GUI]] 

<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get upgrade
$ uname -a
Linux BlueMidget 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
=== Mythbuntu Control Center ===
Launch the Control Center from <code>Applications/System/Mythbuntu Control Center</code>
Work through each of the sections selecting the prefered options, in this first pass I'm only interested in
# Graphics Drivers, this wizard will assist in the installation of proprietary drivers for your GPU which can significantly improve performance. On my systems i'm using the embedded Intel GPU which isn't identified so I'm using the stock drivers.
# Repository. This is where you can select which version of MythTV you want to run, the default is v0.25. V0.26 is stable and V0.27 is experimental. I selected V0.26 and added both the Mythbuntu and XMLTV repos.
# Infrared, this allows you to select enable any remotes for your system. I have a Windows Media Center compatable Receiver and Remote.

After applying any changes it is important to update the system again if you've changed MythTV versions.
<pre style="white-space: pre-wrap;">
$ sudo apt-get update
$ sudo apt-get dist-upgrade
</pre>

If you use the above SSH you will be presented with the following prompts
 [[File:4.1.SSHUpdatePrompt001.png|200px|Update promt]]
[[File:4.2.SSHUpdatePrompt002.png|200px|Update prompt]] 
After a further reboot, the database will be updated.
 [[File:5.1.MythTVDatabaseUpgradePrompt.png|200px|Database Upgrade prompt]]
[[File:5.2.MythTVDatabaseUpgradeBackupNotification.png|200px|Initial Screen After Reboot]] 
=== Accessing Network Shares ===
My system requires access to a NAS for media files, backup etc. I use the method defined here [[Accessing_Network_Shares]].
<pre>
$ sudo apt-get install autofs cifs-utils
$ nano ~/cifs.cred
</pre>

=== Mounting Addition HardDrives ===
There are numerous methods for doing this but the follwing is my prefered solution.
==== Use UUID To Mount Partitions ====
Identify the hard drive device in you PC.
<pre style="white-space: pre-wrap;">
$ sudo lshw -class disk
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXB1AA3V5194
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d569
*-disk
description: ATA Disk
product: WDC WD20NPVX-00E
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdb
version: 01.0
serial: WD-WXB1AA3V2082
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=11a7d565
</pre>
Mine are <code>/dev/sda /dev/sdb</code>

Use <code>fdisk</code> to manually create single large partitions and format to ext4 [http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html].

Find the UUID of each partition
<pre style="white-space: pre-wrap;">
$ sudo blkid -o full -s UUID
/dev/sda1: UUID="dd3e3288-eb4a-48f3-a1c4-42043b96f645"
/dev/sdb1: UUID="61d71482-8a81-469c-ae12-d0b539335fc2"
</pre>

Add the mountpoints
<pre style="white-space: pre-wrap;">
$ sudo mkdir /media/disk01
$ sudo mkdir /media/disk02
</pre>

Add the following to the end of fstab. [http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab/]
<pre style="white-space: pre-wrap;">
UUID=dd3e3288-eb4a-48f3-a1c4-42043b96f645 /media/disk01 ext4 rw 0 0
UUID=61d71482-8a81-469c-ae12-d0b539335fc2 /media/disk01 ext4 rw 0 0
</pre>

Mount the drives and make the writable.
<pre style="white-space: pre-wrap;">
$ sudo mount -a
$ sudo chown jack:jack /media/disk01/
$ sudo chown jack:jack /media/disk02/
</pre>

=== Restoring Old Database ===
This is only required if your porting a database from and existing system or restoring after a rebuild, see
[http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions| Database Backup and Restore] for details. [http://www.mythbuntu.org/upgrading]

Backup the existing database in case anything goes wrong
<pre style="white-space: pre-wrap;">
$ /usr/share/mythtv/mythconverg_backup.pl
</pre>
Check the database is created
<pre style="white-space: pre-wrap;">
ls -l /var/lib/mythtv/db_backups/
-rw-r--r-- 1 root mythtv 39832 Sep 6 19:09 mythconverg-1299-20130906190902.sql.gz
-rw-r--r-- 1 mythtv mythtv 47373 Sep 7 14:36 mythconverg-1299-20130907133615.sql.gz
-rw-rw-r-- 1 mythtv mythtv 49280 Sep 7 14:36 mythconverg-1307-20130907133652.sql.gz
-rw-rw-r-- 1 mythtv mythtv 50022 Sep 7 18:41 mythconverg-1307-20130907184143.sql.gz
</pre>
Copy the original database from its location to the default '/var/lib/mythtv/db_backups/'
<pre style="white-space: pre-wrap;">
$ cp /media/nfsshares/mythtv_db_backups/mythconverg-1264-20130907185125.sql.gz /var/lib/mythtv/db_backups/
</pre>
Stop the backend:
<pre style="white-space: pre-wrap;">
$ sudo stop mythtv-backend
</pre>
Obtain the mythtv password from here:
<pre style="white-space: pre-wrap;">
$ grep DBPassword /etc/mythtv/config.xml
<DBPassword>JHxeUhn0</DBPassword>
</pre>
Restore the original system database to the new system using:
<pre style="white-space: pre-wrap;">
/usr/share/mythtv/mythconverg_restore.pl --drop_database --create_database --directory /var/lib/mythtv/db_backups --filename mythconverg-1264-20130907185125.sql.gz
</pre>
At this stage your system is fragile. You must do the following
# Run <code>mythtv-setup</code> and allow the schema to be upgraded
# Check the setting in mythtv-setup, in particular the IP address of the backend etc.

If you reboot the system and the frontend get stuck in a crash / relode loop, Kill the frontend using
<pre style="white-space: pre-wrap;">
$ sudo killall mythfrontend
$ sudo killall mythfrontend.real
</pre>
 [[File:6.1.SchemaUpdateNotification.png|200px|Schema Update Notification]]
[[File:6.2.NetworkProtocolNotification.png|200px|Network Protocol Notification]] 

Ensure both the front and backends are at version 75 shown by:
<pre style="white-space: pre-wrap;">
$ mythfrontend --version
xprop: unable to open display ''
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1-14-gdbdd455
MythTV Branch : fixes/0.26
Network Protocol : 75
Library API : 0.26.20130225-1
QT Version : 4.8.1
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
</pre>

=== Install TV Card Drivers ===
The TV cards in the system require drivers to be compiled in to the kernel, which means this needs to be repeated each time theres a kernel update.
<pre style="white-space: pre-wrap;">
$ lspci | grep media
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)
02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
</pre>
Installing the drivers [http://linuxtv.org/wiki/index.php/TBS6280].
<pre style="white-space: pre-wrap;">
$ cd ~
$ wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
--2013-09-07 20:58:24-- http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130802.zip
Resolving www.tbsdtv.com (www.tbsdtv.com)... 143.95.60.2
Connecting to www.tbsdtv.com (www.tbsdtv.com)|143.95.60.2|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16296304 (16M) [application/zip]
Saving to: `tbs-linux-drivers_v130802.zip'

100%[======================================>] 16,296,304 1.27M/s in 22s

2013-09-07 20:58:46 (731 KB/s) - `tbs-linux-drivers_v130802.zip' saved [16296304/16296304]
$ mkdir tbs-linux-drivers
$ cd tbs-linux-drivers
$ sudo apt-get install unzip
$ sudo apt-get install build-essential
$ unzip ../tbs-linux-drivers_v130802.zip
</pre>

The instructions for the continued installation are in the readme file <code>README_TBS6981</code>.
Extract linux-tbs-drivers.tar.bz2 archive:
<pre>
$ tar xjvf linux-tbs-drivers.tar.bz2
</pre>
The permissions of the tarball are wrong, this can be corrected using
<pre>
chmod -R 755 .
</pre>
The build script needed is depending on your kernel version. Determine the kernel version using:
<pre>
$ uname -a
3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
</pre>
for any x86_64 kernel (x86 64 bit installations of Linux):
<pre>
$ cd linux-tbs-drivers/
~/tbs-linux-drivers/linux-tbs-drivers
$ ./v4l/tbs-x86_64.sh
TBS drivers configured for x86_64 platform.
</pre>
Build and install the driver:
<pre>
$ make
$ sudo make install
</pre>
Reboot in order to load the newly installed driver:
<pre>
$ shutdown -r now
</pre>
After reboot check that the newly installed driver is loaded correctly:
<pre>
$ dmesg | grep frontend
</pre>
If everything is OK, the output from the above command lists the registered
frontends for your card model and their number is equal to the number of
tuners on the card, for example:
<pre>
DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
If its not ok you'll get something like
<pre>
[ 1.355497] videobuf_dvb: disagrees about version of symbol dvb_frontend_deta ch
[ 1.355498] videobuf_dvb: Unknown symbol dvb_frontend_detach (err -22)
</pre>
To fix it...
<pre style="white-space: pre-wrap;">
sudo rm -R /lib/modules/$(uname -r)/kernel/drivers/media
sudo make install
sudo reboot
</pre>
Try again!
<pre>
$ dmesg | grep frontend
[ 2.087311] DVB: registering adapter 0 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.174999] DVB: registering adapter 1 frontend 0 (TurboSight TBS 62x0 DVBT/T2 frontend)...
[ 2.676974] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.760952] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[ 2.787563] cx23885_dvb_register() allocating 1 frontend(s)
[ 2.867740] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
</pre>
Success.

=== Figure Gallery ===
<gallery mode="packed-hover">
Image:1.MainScreenAfterReboot.png| ''Initial Screen After Reboot'' (Oscar)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Epinephelus lanceolatus|Epinephelus lanceolatus]]'' (Giant grouper)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Pterois volitans|Pterois volitans]]'' (Red Lionfish)
Image:CloseUpCameraModuleRev1 3.jpg|''[[commons:Macropodus opercularis|Macropodus opercularis]]'' (Paradise fish)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Psetta maxima|Psetta maxima]]'' (Turbot)
File:CloseUpCameraModuleRev1 3.jpg|''[[commons:Category:Ecsenius|Ecsenius axelrodi]]''
</gallery>

== References ==
# http://www.mythbuntu.org/
# http://www.mythtv.org/
# http://www.mythbuntu.org/download-type
# http://www.yolinux.com/TUTORIALS/LinuxTutorialAdditionalHardDrive.html
# http://www.cyberciti.biz/faq/linux-finding-using-uuids-to-update-fstab
# http://www.mythbuntu.org/upgrading
# http://linuxtv.org/wiki/index.php/TBS6280