Difference between revisions of "Installing MythTV on Fedora"

From MythTV Official Wiki
Jump to: navigation, search
m (Configure startup)
m (Remove atrpms reference)
 
(116 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This "How-To" guide is for installing MythTV on the latest release of Fedora.
 
  
{{Note box|This installation guide is currently undergoing an overhaul to remove outdated procedures and reduce the overall size.  Addressing the helpful comments in the discussion panel}}
+
{{User Manual TOC}}
 +
 
 +
This "How-To" guide is for installing MythTV on {{FedoraVersion}}.
  
 
==Introduction==
 
==Introduction==
  
This wiki entry will detail the installation of a combined frontend and backend in Fedora 20.  Ensure you have met the hardware requirements set out by  [http://www.mythtv.org/wiki/Hardware_Requirements MythTV].
+
This wiki entry will detail the installation of a combined frontend and backend in {{FedoraVersion}}.  Ensure you have met the [[Hardware_Requirements|hardware requirements]].
  
Fedora provides updates for a release until two releases after that. At the time of this writing, the current release is Fedora 20, which means support for Fedora 18 was discontinued a month after Fedora 20 was released. Thus, it makes sense to update to the latest release at least every other version, if not every version.  
+
Fedora provides updates for a release until two releases after that. At the time of this writing, the current release is {{FedoraVersion}}, which means support for {{FedoraVersion}} - 2 becomes discontinued a month after {{FedoraVersion}} is released. Thus, it makes sense to update to the latest release at least every other version, if not every version.  
  
 
You are welcome as a MythTV user and general wiki participant, to add to, and modify this document that will help the community the best way possible.
 
You are welcome as a MythTV user and general wiki participant, to add to, and modify this document that will help the community the best way possible.
Line 13: Line 14:
 
==Getting Fedora==
 
==Getting Fedora==
 
===ISO images===
 
===ISO images===
The latest version of Fedora can be downloaded from the [http://www.fedoraproject.org/en/get-fedora Fedora Download Page].  Note that the Desktop edition has the default [http://www.gnome.org/ GNOME] Desktop available whereas the DVD install has alternative desktop environments available.  For the remainder of this installation guide, the default desktop environment GNOME will be used to avoid confusion.  Other desktop environments should be similar.
+
 
 +
{{Download|getfedora.org/en/workstation/|Fedora download page}}
 +
 
 +
Note that the Workstation edition has the default [http://www.gnome.org/ GNOME] Desktop available whereas the DVD install has alternative desktop environments available.  For the remainder of this installation guide, the default desktop environment GNOME will be used to avoid confusion.  Other desktop environments should be similar.
  
 
===Physical media===
 
===Physical media===
Line 19: Line 23:
  
 
==Installing Fedora==
 
==Installing Fedora==
The official Fedora 20 [http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Quick_Start_Guide/index.html installation guide] is an excellent place to start when installing Fedora.  There are a few modifications on the procedure given in the official documentation; user creation and filesystem partitions.  The notes in this wiki will detail an installation from the '''Live Desktop Media'''.  It should be noted that additional desktop environments are also available if the GNOME 3 desktop is not suitable.  Some alternatives are listed in the Fedora [http://fedoraproject.org/wiki/Releases/20/Spins spins] page and installation is detailed [http://docs.fedoraproject.org/en-US/Fedora/20/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_.html here].  Desktop environments other than GNOME 3 are outside of the scope of this wiki for brevity.
+
The official {{FedoraVersion}} [http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/index.html installation guide] is an excellent place to start when installing Fedora.  There are a few modifications on the procedure given in the official documentation; user creation and filesystem partitions.  The notes in this wiki will detail an installation from the '''Live Desktop Media - Workstation'''.  It should be noted that additional desktop environments are also available if the GNOME 3 desktop is not suitable.  Some alternatives are listed in the Fedora [http://fedoraproject.org/wiki/Releases/21/Spins spins] page and installation is detailed [http://docs.fedoraproject.org/en-US/Fedora/21/html/Release_Notes/index.html here].  Desktop environments other than GNOME 3 are outside of the scope of this wiki for brevity.
  
 
===Date/Time===
 
===Date/Time===
Line 28: Line 32:
 
Among the MythTV community, it is highly recommend to use a custom partitioning scheme rather than auto-partitioning with a dedicated /video (or similar) partition for storage of all your recordings. If possible, for best efficiency, the video partition should be on a drive physically separate from the operating system partitions. Software RAID and LVM for your video partitions will only slow it down and should be avoided. LVM is no longer necessary for MythTV due to Storage Groups.
 
Among the MythTV community, it is highly recommend to use a custom partitioning scheme rather than auto-partitioning with a dedicated /video (or similar) partition for storage of all your recordings. If possible, for best efficiency, the video partition should be on a drive physically separate from the operating system partitions. Software RAID and LVM for your video partitions will only slow it down and should be avoided. LVM is no longer necessary for MythTV due to Storage Groups.
  
Currently EXT4 format is the default in Fedora and other distributions.  Here's a partition setup example:
+
Currently EXT4 format is the default in Fedora and other distributions.  A partition setup example is given in the Table below.
 +
 
 +
===User creation===
  
 +
When prompted during the installation, create a non-administrator user on the system with the username "mythtv".  You can set the password for this user to anything you want.  This should be a [http://en.wikipedia.org/wiki/Strong_password Strong Password] that is '''different than the root password.'''
  
 
<center>
 
<center>
Line 65: Line 72:
 
|}
 
|}
 
</center>
 
</center>
 
===User creation===
 
 
When prompted during the installation, create a non-administrator user on the system with the username "mythtv".  You can set the password for this user to anything you want.  This should be a [http://en.wikipedia.org/wiki/Strong_password Strong Password] that is '''different than the root password.'''
 
  
 
==First boot==
 
==First boot==
 
At this point Anaconda will ask you to remove the installation media from the drive and reboot the system.  Once your system has finished rebooting you will be prompted to do some final configurations and be given a short tour of GNOME 3.
 
At this point Anaconda will ask you to remove the installation media from the drive and reboot the system.  Once your system has finished rebooting you will be prompted to do some final configurations and be given a short tour of GNOME 3.
  
===Gnome Terminal===
+
===GNOME terminal===
  
Tasks in Linux are performed with greater ease through the command line and are therefore required in this How-To.  In GNOME 3, the terminal is accessed by going to Activities and typing <tt>terminal</tt> in the search box.
+
Tasks in linux are performed with greater ease through the command line and are therefore required in this How-To.  In GNOME 3, the terminal is accessed by going to Activities and typing <tt>terminal</tt> in the search box.
  
 
Some commands need to be run as the mythtv user, and some commands need to be run as the root user.  The boxes below will indicate with a prompt which user should run the command.  Commands with a "$" prompt should be run as the mythtv user.  If you see a command that starts with a "#", you will need to use the '''su''' command to become the root user.
 
Some commands need to be run as the mythtv user, and some commands need to be run as the root user.  The boxes below will indicate with a prompt which user should run the command.  Commands with a "$" prompt should be run as the mythtv user.  If you see a command that starts with a "#", you will need to use the '''su''' command to become the root user.
Line 113: Line 116:
  
 
===Network configuration===
 
===Network configuration===
On the Network Configuration screen (Activities -> Network Connections), setting a static IP address is highly recommended (could be either a static, or statically mapped DHCP address). It really isn't a huge deal if you only have one Myth box (though you probably don't want MythWeb to be a moving target), but it could cause major headaches once you have more than one machine, since non-primary systems won't know where the master backend is, if the address changes.
+
On the Network Configuration screen (Activities -> Network Connections), setting a static IP address is highly recommended (could be either a static, or statically mapped DHCP address). It really isn't a huge deal if you only have one Mythbox (though you probably don't want MythWeb to be a moving target), but it could cause major headaches once you have more than one machine, since non-primary systems won't know where the master backend is located if the address changes.
  
 
===Firewall===
 
===Firewall===
 +
 +
Note that since Fedora 21 Workstation the firewall application has been removed for ease of use.  The VNC ports are open on this machine by default.  It can be installed by
 +
<pre>
 +
# yum install firewall-config
 +
</pre>
 +
 
A basic MythTV box should not have any problems running with the default Public zone firewall settings.  If there are issues with service access you will at the very least want to enable SSH, Secure WWW (HTTPS) and WWW (HTTP) checkboxes to enable those services under the appropriate Firewall zone with the ''Permanent'' configuration.
 
A basic MythTV box should not have any problems running with the default Public zone firewall settings.  If there are issues with service access you will at the very least want to enable SSH, Secure WWW (HTTPS) and WWW (HTTP) checkboxes to enable those services under the appropriate Firewall zone with the ''Permanent'' configuration.
  
 
If you plan to run separate front end and back end servers you will need to allow those ports through on under "Other Ports".  Add TCP ports 6543 and 6544 to allow the MythTV protocol access through the firewall and TCP 3306 for MariaDB.
 
If you plan to run separate front end and back end servers you will need to allow those ports through on under "Other Ports".  Add TCP ports 6543 and 6544 to allow the MythTV protocol access through the firewall and TCP 3306 for MariaDB.
 +
 +
===Autologin and display timeout===
 +
You can choose to have GNOME autologin in the ''mythtv'' user on boot so that the mythfrontend can automatically load.  To set this behaviour go to Activities > Users.  Unlock the user panel with the administrator password and slide the ''Automatic Login'' to the on position.
 +
 +
The screen timeout will also cause problems when using MythTV.  You can set the display to not turn off by going to Activities > Power and setting the ''blank screen'' option to never.  Be sure not to leave the display on with this option as it can cause issues with the display panel (burn in etc).
 +
 +
===Sound setup===
 +
 +
Fedora uses PulseAudio by default, as do many Linux distributions. MythTV works with Pulseaudio. Ensure the sound is working in the GNOME desktop otherwise try changing the output (e.g., HDMI) in Activities > Sound.
 +
 +
===Remote desktop===
 +
 +
The remote desktop in GNOME can be enabled through Activities > System Settings > Sharing.  Turn on ''Screen Sharing'' and ''Allow Remote Control'' through the attached network device. It is '''strongly''' recommended that a secure password is set.
  
 
==Fedora setup==
 
==Fedora setup==
Line 125: Line 147:
 
===Configure package repositories===
 
===Configure package repositories===
 
====RPMFusion====
 
====RPMFusion====
Configuration of yum is needed to use the RPMFusion package repository.  Follow the links below and install the RPMs for the latest version and correct architecture for your system.  It should be noted ATrpms can also be used as an alternative to RPMFusion but they cannot be used simultaneously and ATrpms will require the priority of the repo file to be set higher as to not conflict with the official packages.
+
Configuration of yum is needed to use the RPMFusion package repository.  Follow the links below and install the RPMs for the latest version and correct architecture for your system.
  
RPMFusion
+
{{Webpage|rpmfusion.org/Configuration|RPMFusion}} 
  http://rpmfusion.org/Configuration
 
  
Note: You will need to download the packages rpmfusion-free-release and rpmfusion-nonfree-release and install with GNOME Software or rpm -ivh *.
+
Note: You will need to download the packages rpmfusion-free-release and rpmfusion-nonfree-release under ''Firefox graphical installation'' and install with GNOME Software or rpm -ivh *.
  
Many MythTV installations require additional kernel modules to make all the hardware work. When installing firmware/drivers such as the proprietary nVidia graphics drivers the '''akmod''' or '''kmod''' packages can be chosen.  The '''akmod''' packages automatically check and compile the driver on boot if required.  This incurs a small penalty of having to install development packages.  The '''kmod''' packages are built against a specific kernel version and if a new kernel is installed without the corresponding kmod then errors on boot may occur.  Therefore for system safety the akmod packages are recommended.
+
Some MythTV installations require additional kernel modules to make all the hardware work. When installing firmware/drivers such as the proprietary nVidia graphics drivers the '''akmod''' or '''kmod''' packages can be chosen.  The '''akmod''' packages automatically check and compile the driver on boot if required.  This incurs a small penalty of having to install development packages.  The '''kmod''' packages are built against a specific kernel version and if a new kernel is installed without the corresponding kmod then errors on boot may occur.  Therefore for system safety the akmod packages are recommended.
  
====libcssdvd====
+
=====NVIDIA=====
If you require DVD playback then you will need to install the <tt>libdvdcss</tt> package from an alternative repository.  Please check if this is legal in your country.
 
  
<pre>
+
We recommend you use a card that supports [[VDPAU]] for video acceleration.
# yum localinstall http://rpm.livna.org/livna-release.rpm
 
# yum install libdvdcss
 
</pre>
 
 
 
====NVIDIA====
 
 
 
We recommend you use a card that supports VDPAU for video acceleration. See http://www.mythtv.org/wiki/VDPAU.
 
  
 
You can install binary drivers from NVIDIA, but in most cases it's simpler to use yum to get and install them from RPMFusion. It is essential to get the proper version of the drivers. Start by running
 
You can install binary drivers from NVIDIA, but in most cases it's simpler to use yum to get and install them from RPMFusion. It is essential to get the proper version of the drivers. Start by running
Line 170: Line 183:
 
If you need a legacy package from RPM Fusion consult the available packages table at http://rpmfusion.org/.
 
If you need a legacy package from RPM Fusion consult the available packages table at http://rpmfusion.org/.
  
===Sound setup===
+
====DVD playback====
 +
If you require DVD playback then you will need to install the <tt>libdvdcss</tt> package from an alternative repository.  Please check if this is legal in your country.
  
Fedora uses PulseAudio by default, as do many Linux distributions. MythTV works with Pulseaudio. Ensure the sound is working in the GNOME Desktop otherwise try changing the output in Activites > Sound.
+
<pre>
 +
# yum localinstall http://rpm.livna.org/livna-release.rpm
 +
# yum install libdvdcss
 +
</pre>
  
===Remote desktop===
+
The <tt>libdvdcss</tt> package can also be installed by performing the following commands for 64 or 32 bit versions respectively:
 
+
<pre>
'''Please ensure that only local access is allowed for the VNC ports for security reasons.'''
+
# rpm -Uvh http://rpm.livna.org/repo/18/x86_64/libdvdcss-1.2.12-1.fc17.remi.x86_64.rpm
 
+
or
The remote desktop in GNOME can be enabled through the GUI from Activites > System Settings > Sharing. Turn on Screen Sharing and Allow Remote Control. It is '''strongly''' recommended that a secure password is set. After the remote desktop has been enabled the corresponding ports need to be allowed through the firewall (VNC-Server checkbox).
+
# rpm -Uvh http://rpm.livna.org/repo/18/i386/libdvdcss-1.2.12-1.fc17.remi.i686.rpm
 +
</pre>
  
 
==Install MythTV==
 
==Install MythTV==
  
MythTV has numerous required dependencies to function correctly, which are automatically taken care of with one simple command, using either repository:
+
MythTV has numerous required dependencies to function correctly, which are automatically taken care of with one simple command:
  
 
<pre>
 
<pre>
 
# yum install mythtv
 
# yum install mythtv
 
</pre>
 
</pre>
 
You may run into some problems with dependencies. These can usually be resolved by removing the offending package and re-running the above command. Dependency issues can be mitigated be keeping additional (third-party) repositories to a minimum. MythTV on Fedora requires only the default repositories plus RPMFusion to fulfil all requirements.
 
  
 
===SELinux===
 
===SELinux===
It is strongly recommended that SELinux is run in "permissive" mode by editing <tt>/etc/selinux/config</tt>.  There are a few things that will not work properly if you set SELinux to "enforcing" such as the MythWeb pluginIf you think you might want to run with SELinux in enforcing mode in the future, choose the permissive mode which will only warn you of problems. This will enable you to quickly and easily set SELinux to enforcing mode at a later time. 
+
It is strongly recommended that SELinux is run in "enforcing" mode as set by defaultYou can choose the permissive mode which will only warn you of problems.
  
Fedora 20 comes with the excellent [https://fedorahosted.org/setroubleshoot '''setroubleshoot'''] tool which will notify of denials whilst permitting you to leave SELinux enabled on your system.  Audit2allow in permissive mode can also be used to catch SELinux denials and rules can be automatically created to allow program access in the future.
+
Fedora comes with the excellent [https://fedorahosted.org/setroubleshoot '''setroubleshoot'''] tool which will notify of denials whilst permitting you to leave SELinux enabled on your system.  Audit2allow in enforcing mode can also be used to catch SELinux denials and rules can be automatically created to allow program access in the future.
  
 
If you prefer running enforcing SELinux with mythweb, the following commands may be helpful:
 
If you prefer running enforcing SELinux with mythweb, the following commands may be helpful:
 
<pre>
 
<pre>
  $ /usr/sbin/setsebool -P httpd_can_network_connect=1
+
  $ /usr/sbin/setsebool -P httpd_can_connect_mythtv 1
  $ /usr/sbin/setsebool -P httpd_ssi_exec=1
+
  $ /usr/sbin/setsebool -P httpd_can_network_connect 1
  $ chcon -R -t httpd_sys_content_rw_t /var/www/html/mythweb/data
+
</pre>
  $ semanage fcontext -a -t  httpd_sys_content_rw_t /var/www/html/mythweb/data
+
If you have followed the previous instructions and the MythTV recordings and videos are on a seperate drive and you wish to use MythWeb, then you will need to tell SELinux about this.  On the test machine the videos are mounted at <code>/mnt/sdb/Videos</code>.  The SELinux Troubleshooting tool gives errors that httpd wants to access these directories.  To allow httpd read permission:
 +
<pre>
 +
  $ chcon -R -t httpd_sys_content_t '/mnt/sdb/Videos*'
 +
  $ semanage fcontext -a -t  httpd_sys_content_t '/mnt/sdb/Videos*'
 
</pre>
 
</pre>
  
Line 207: Line 226:
 
Some capture card drivers have been included by default with Fedora. The IVTV drivers required for the PVR-150/250/350 and the drivers required for the Hauppauge HD-PVR 1212 are included, for example.
 
Some capture card drivers have been included by default with Fedora. The IVTV drivers required for the PVR-150/250/350 and the drivers required for the Hauppauge HD-PVR 1212 are included, for example.
  
Fedora may also automatically detect and install the needed firmware for some TV cards (e.g. Hauppauge HVR-1600).  If manual installation is required then it is best to refer to [http://www.linuxtv.org/wiki/index.php/Hardware_Device_Information linuxtv.org] for support information.
+
You can check if the kernel is able to detect the attached dvb tuner by checking the kernel messages.  This is done with:
 +
<pre>
 +
dmesg | grep -i dvb
 +
</pre>
 +
If the firmware loading was successful you may notice a message similar to:
 +
<pre>
 +
usb 1-6: dvb_usb_v2: 'Kworld UB499-2T T09' successfully initialized and connected
 +
</pre>
 +
Otherwise you will need to find the chipset details of the attached tuner.  If you have a '''usb''' attached tuner use <tt>lsusb</tt> or if you have a '''PCI''' tuner use <tt>lspci</tt>.
 +
 
 +
An example output of this might be:
 +
<pre>
 +
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 +
Bus 004 Device 002: ID 0609:0334 SMK Manufacturing, Inc. eHome Infrared Receiver
 +
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 +
Bus 001 Device 003: ID 1b80:e409 Afatech IT9137FN Dual DVB-T [KWorld UB499-2T]
 +
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 +
Bus 003 Device 002: ID 17ef:6022 Lenovo
 +
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 +
</pre>
 +
The entry with DVB gives the model name of the tuner (KWorld UB499-2T) and chipset (IT9137FN) which can be compared with the lists at [http://www.linuxtv.org/wiki/index.php/Hardware_Device_Information linuxtv.org].
  
===Remote control===
+
===Configure remote control===
  
 
Many remote control drivers have been moved to the kernel but manual key mapping may still be desired.  This can be achieved by installing the <tt>v4l-utils</tt> package for the <tt>ir-keytable</tt> command.
 
Many remote control drivers have been moved to the kernel but manual key mapping may still be desired.  This can be achieved by installing the <tt>v4l-utils</tt> package for the <tt>ir-keytable</tt> command.
Line 217: Line 256:
 
</pre>
 
</pre>
  
Once v4l-utils has successfully installed you can run the following command to capture the input and button name of each keypress.
+
Once v4l-utils has successfully installed you can check to see what protocol and keymap that the current remote control has by runnning:
 +
 
 +
<pre>
 +
# ir-keytable
 +
</pre>
  
 +
This might give the following output (for a MCE-USB remote):
 +
<pre>
 +
[root@machinename]# ir-keytable
 +
Found /sys/class/rc/rc0/ (/dev/input/event4) with:
 +
  Driver mceusb, table rc-rc6-mce
 +
  Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
 +
  Enabled protocols: RC-6
 +
  ...
 +
</pre>
 +
In this instance the keymap being used is <tt>/lib/udev/rc_keymaps/rc6-mce</tt>.
 +
 +
To test the key mappings run the following command that will capture the input and button name of each keypress.
 
<pre>
 
<pre>
 
# ir-keytable -t
 
# ir-keytable -t
 
</pre>
 
</pre>
  
The mappings can be changed by finding your corresponding keymap in <tt>/lib/udev/rc_keymaps</tt>.  Be sure to comment out the original mappings in case an error is made during the file modification.
+
The mappings can be changed by finding your corresponding keymap in <tt>/lib/udev/rc_keymaps</tt>.  Be sure to comment out the original mappings in case an error is made during the file modification and re-load the keymap using:
 +
<pre>
 +
# ir-keytable -c -w /lib/udev/rc_keymaps/<keymap name>
 +
</pre>
  
If your remote control does not exist in the kernel then you will have to install LIRC.
+
If your remote control does not exist in the kernel and you don't get any output in <tt>ir-keytable -t</tt> then you will have to install LIRC.
 +
 
 +
'''Note for rc6-mce''': at the top of the <tt>/lib/udev/rc_keymaps/rc6_mce</tt> keymap file the protocol is changed to RC6-MCE and this will need to be changed back to RC6 if an error regarding unsupported protocol occurs.
  
 
====Install LIRC====
 
====Install LIRC====
 +
 +
'''This LIRC instruction may well be outdated'''
  
 
Note for Fedora 12 + users the default LIRC socket file name has changed to /var/run/lirc/lircd , so you will need to update MythTV Settings -> General from /dev/lircd ->/var/run/lirc/lircd and then restart mythfrontend.
 
Note for Fedora 12 + users the default LIRC socket file name has changed to /var/run/lirc/lircd , so you will need to update MythTV Settings -> General from /dev/lircd ->/var/run/lirc/lircd and then restart mythfrontend.
Line 240: Line 302:
  
 
==Setup MariaDB==
 
==Setup MariaDB==
In Fedora 20, mySQL has been replaced with MariaDB but backwards compatibility is maintained such that the following commands should still be applicable.  We'll need to enable MySQL to load at startup, set some passwords, and create the MythTV database, which we'll populate shortly. The population of this database is handled by <tt>mythtv-setup</tt> in the next step, and all MythTV add-on module database additions must be done '''after''' running <tt>mythtv-setup</tt> at least one time.
+
In Fedora 20, mySQL has been replaced with MariaDB but backwards compatibility is maintained such that the following commands should still be applicable.  We'll need to enable MariaDB to load at startup, set some passwords and create the MythTV database which we'll populate shortly. The population of this database is handled by <tt>mythtv-setup</tt> in the next step, and all MythTV add-on module database additions must be done '''after''' running <tt>mythtv-setup</tt> at least one time.
 
+
Start by enabling automatic load at boot and start the database:
 
<pre>
 
<pre>
 
# systemctl enable mariadb.service
 
# systemctl enable mariadb.service
 
# systemctl restart mariadb.service
 
# systemctl restart mariadb.service
 
</pre>
 
</pre>
 
+
Then to setup the database:
Set the MySQL root password.
 
 
 
 
<pre>
 
<pre>
mysql_secure_installation
+
$ mysql_secure_installation
 
</pre>
 
</pre>
 
+
Set the MariaDB root password when prompted and accept all the defaults by pressing enter.  Now we can create the MythTV database (called mythconverg) to get us started:
Now we create the MythTV database (called mythconverg) to get us started:
 
 
 
 
<pre>
 
<pre>
 
$ mysql -u root -p < /usr/share/doc/mythtv-docs/database/mc.sql
 
$ mysql -u root -p < /usr/share/doc/mythtv-docs/database/mc.sql
Line 261: Line 319:
 
At this point, enter the password you just set above (ROOT_PWD) when prompted.
 
At this point, enter the password you just set above (ROOT_PWD) when prompted.
  
The above command gives users access to the database (see the main documentation) with the commands
+
The above command gives users access to the database (see the main documentation) with the  
 
<pre>
 
<pre>
$ /usr/bin/mysql -u root -p mythconverg
+
/usr/bin/mysql -u root -p mythconverg
 
mysql> GRANT ALL ON mythconverg.* TO mythtv@"%" identified by  "mythtv";
 
mysql> GRANT ALL ON mythconverg.* TO mythtv@"%" identified by  "mythtv";
 
mysql> flush privileges;
 
mysql> flush privileges;
Line 273: Line 331:
  
 
<pre>
 
<pre>
mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql
+
$ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql
 
</pre>
 
</pre>
  
These adjustments to <tt>/etc/my.cnf</tt> under the [mysqld] section improve performance with both MythTV (especially in the GUI) and MythWeb:
+
==Pre-launch checks==
 +
Before going further it is wise to check whether things have worked so far. Has a <tt>/dev/dvb/</tt> entry been created for a digital video source?
  
 
<pre>
 
<pre>
key_buffer = 16M
+
$ ls /dev/dvb*
table_cache = 128
 
sort_buffer_size = 2M
 
myisam_sort_buffer_size = 8M
 
query_cache_size = 16M
 
 
</pre>
 
</pre>
 
+
Which should return (or similiar if successful):
==Does /dev/dvb* exist?==
 
Before going further it is wise to check whether things have worked so far. Has a <tt>/dev/dvb/</tt> entry been created for a digital video source?
 
 
 
 
<pre>
 
<pre>
$ ls -la /dev/dvb*
+
adapter0 adapter1
 
</pre>
 
</pre>
If not, you should be reading https://fedoraproject.org/wiki/DavidTimms/DVB), if you have an digital source yet something has gone wrong with installing it (in which case you should look at /var/log/dmesg, and check whether udev, ivtv, and so on are working, and required modules are loaded). A useful quick test for USB video sources is to unplug them then plug them in again and look at the ends of whatever /var/log files get updated.
+
If not, you should be reading https://fedoraproject.org/wiki/DavidTimms/DVB), if you have an digital source yet something has gone wrong with installing it (in which case you should look at /var/log/dmesg using <tt>dmesg | grep -i dvb</tt>), and check whether udev, ivtv, and so on are working, and required modules are loaded). A useful quick test for USB video sources is to unplug them then plug them in again and look at the ends of whatever /var/log files get updated.
  
 
==Setup MythTV==
 
==Setup MythTV==
Recall what your video device was set up as (likely /dev/dvb/adapter* for digital video sources). Note that the actual device number is '''not''' what determines what order MythTV will use your cards in. What matters is the order that you enter them in <tt>mythtv-setup</tt>, so your best card doesn't have to be /dev/video0. If you set up /dev/video8 first, it'll be the first card used for recordings.
 
  
If you are in the US, you will need a paid account with [schedulesdirect.org]. The current pricing is $20 per year. This will give you television feed data that your myth box uses for scheduling once you have localized your acct to your zip code, chosen a content provider service and then set your channels from the webpage. There are a few other ways to get your data, but they are outside the scope of this document and the listings are not as accurate or as reliable.  
+
To launch the MythTV setup utility search for <tt>mythtv</tt> in the Activities overview.  You should be presented with a graphical interface and you may be required to update the database schema.  Now we will move onto assigning the tuners, channels and storage directories.
 +
 
 +
===1. General===
 +
In General settings, set the local and master backend IP address to the local IP address of your machine for a combined frontend / backend.  On the test machine this was 192.168.0.2 (may be different for you). Set your ''channel frequency table'' in the next page and continue to scroll through until you have reached '''Finished'''.
  
Now on to launching the MythTV setup utility. For this part, you need to have an X running, as the setup utility is an X application. Fire it up like so:
+
===2. Capture cards===
 +
In order for MythTV to record a stream, you must firstly setup the capture devices.  This is under '''2. Capture Cards'''.  Select the card type (DVB-T/S/C for terrestial) and make sure the DVB device is recognised correctly and select '''Finish'''.  Do this for each available capture device. At this stage you can also set each recording device to record multiple channels per [[Record_multiple_channels_from_one_multiplex|multiplex]] (DVB) by Recording Options > Max Recordings: and set to 3 (from a value of 2).
  
<pre>
+
===4. Video sources===
$ mythtv-setup
+
Once the capture devices have been created successfully and you have decided between SchedulesDirect or using EIT to schedule recordings, a video source is required.  Create a video source under '''4. Video sources''' and give it a name (e.g. vidSrc0) and enter in your SchedulesDirect details or use EIT under ''Listings Grabber'' and accept the remaining defaults.
</pre>
+
 
 +
===5. Input connections===
 +
 
 +
In the next section '''5. Input Connections''' assign each capture device a display name (adapterX) and a video source.  Then select '''Scan for channels''' and ensure the country and scan type (TV or TV+Radio) is correct and select '''Next'''.  The selected capture device will now scan for available channels.  Once complete, a summary of the channels is given, select '''Insert All''' and '''Finish'''. 
 +
 
 +
In many parts of the world the program guide data is transmitted free over the air and is used by MythTV to schedule recordings and provide program information (EIT).  However if you are in the US, you will may need a paid account with [http://www.schedulesdirect.org schedulesdirect]. The current pricing is $25US per year (current at November 2014). This will give you television feed data that your Mythbox uses for scheduling once you have localized your account to your zip code, chosen a content provider service and then set your channels from the web page.
 +
 
 +
===6. Channel Editor===
  
I'm told that non-U.S. folks may have issues getting through the tv_grab_xx/xmltv part of the setup correctly if "focus follows mouse" is already set (in KDE's Control Center), so keep that in mind. Just set "focus follows mouse" after everything else is configured.
+
There may be duplicate channels that can be removed safely and allows for less clutter for the backend to deal with when scheduling. In '''6. Channel Editor''' the duplicate channels can be deleted using key <tt>d</tt> and further additions to channels / transports can be done if desired. There may be icons available for you to download using <tt>Download icons</tt> option.
  
Note: If you receive an error involving permissions on a .so library, you may have SELinux installed and preventing you from accessing those libraries.  You can either turn off SELinux, or allow access to the libraries with the following command as root:
+
===7. Storage directories===
<pre>
 
chcon -t texrel_shlib_t /usr/lib/libmyth*.so*
 
</pre>
 
  
Those using a dedicated /video partition, per my example, should obviously set /video/recordings for storage of recorded shows. However, you can do pretty much whatever you like here, such as recording to an NFS or Samba mount, a software RAID array.  Just make sure your mythtv user has permission to read and write to whatever location you choose.
+
The storage directories can be configured in '''7. Storage Directories'''.  Those using a dedicated /video partition as per the previous recommendation, you should obviously set /video/recordings for storage of recorded shows. However, you can do pretty much whatever you like here, such as recording to an NFS or Samba mount.  Just make sure your mythtv user has permission to read and write to whatever location you choose.
  
It is highly recommended that you go through the setup steps in order. Follow the on-screen instruction, with aid from the MythTV website  [http://www.mythtv.org/wiki/MythTV-HOWTO#Configuring_MythTV documentation].
+
==Mythbackend startup==
  
Once you've gone through the setup, you have to populate the MythTV database with some program info. I spent a long time tweaking my channel lineup on schedulesdirect's site to remove all the junk channels I didn't really care to have show up. Once you have your listings to your liking, you're ready to fill your database with programming info. You must start up the backend first. We'll set it to autostart later.  
+
It is highly recommended that you go through the above setup steps in order. Follow the on-screen instruction, with aid from the MythTV website  [http://www.mythtv.org/wiki/MythTV-HOWTO#Configuring_MythTV documentation] where required.
  
 +
Once you've gone through the setup, you have to populate the MythTV database with some program info. Once you have your listings to your liking, you're ready to fill your database with programming info. You must start up the backend first and we'll set it to autostart later.  Enter the following command in a terminal:
 
<pre>
 
<pre>
$ mythbackend &
+
$ mythbackend
 
</pre>
 
</pre>
  
Assuming all goes well and the process doesn't exit on you (if it does, check out the troubleshooting section below), lets get some guide data:
+
Assuming all goes well and the process doesn't exit on you (if it does, check out the troubleshooting section below), lets get some guide data, in a new terminal window type:
  
 
<pre>
 
<pre>
Line 330: Line 390:
 
If you're using a guide data source other than SchedulesDirect (i.e., anyone outside the U.S. and Canada), you may need to add a "--manual" flag to the end of that command to get it to work. Look at the output of "mythfilldatabase --help" for more clues if you have problems.
 
If you're using a guide data source other than SchedulesDirect (i.e., anyone outside the U.S. and Canada), you may need to add a "--manual" flag to the end of that command to get it to work. Look at the output of "mythfilldatabase --help" for more clues if you have problems.
  
Also, '''be patient!''' This step can take a fairly long time, depending on your internet connection speed and how many channels your service provides. To get automatic updates of programming data daily, see below for configuration in mythfrontend.  
+
'''Be patient'''. This step can take a fairly long time, depending on your internet connection speed and how many channels your service provides. To get automatic updates of programming data daily, see the available options in '''mythtv-setup''', under '''1. General''' on the 10th page for further configuration.
  
Now start up the MythTV front-end (I recommend doing this in a separate shell window, so you can distinctly see the different output for the backend and frontend processes)...
+
==Mythfrontend configuration==
 +
 
 +
Now start up the MythTV frontend.  It is recommended launching <tt>mythfrontend</tt> in a separate shell window, so you can distinctly see the output for the backend and frontend processes for debugging purposes. From a terminal:
  
 
<pre>
 
<pre>
$ mythfrontend  
+
$ mythfrontend
 
</pre>
 
</pre>
  
There are various options within mythfrontend that you can tweak...a lot of this is covered by other parts of the wiki.  
+
There are various options within mythfrontend that you can tweak relating to appearance, video, audio and scheduling of recordings.
 +
 
 +
===Audio===
 +
 
 +
To configure the audio go to Setup > Audio. Choose the '''Audio output device''' that gives the current line output (e.g. HDMI).  On the test computer this was <tt>ALSA:hdmi:CARD=NVidia,DEV=0</tt>.  Use the inbuilt '''Test''' function to see if MythTV is outputting sound to the correct device.  Select '''Next''' to choose the mixer properties.  If your remote control has volume buttons then MythTV can respond the volume changes when the '''Mixer device''' is set to '''software'''.
  
It is recommended to use the built in features of MythTV to have mythfilldatabase updated automatically. After starting up mythfrontend, enter the Setup > General screen and advance to "Mythfilldatabase", the fourth screen. Select the checkbox, then complete the options as you see fit. If using SchedulesDirect for programming data, selecting the option to allow the scheduler to recommend the next mythfilldatabase option and changing the allowed update time to be from 0 to 24 is best, as it allows SchedulesDirect to balance the load on their servers. After setup the mythbackend program will now run mythfilldatabase for you.
+
===Video===
 +
 
 +
Likewise for the audio, the video can be configure under Setup > Video. If the captured streams are interlaced, then the [[Deinterlacing|choice]] of interlacer is critical to an enjoyable viewing experience. It is generally considered that nVidia with VDPAU has the most advanced deinterlacing methods (Advanced and Temporal) and these should be selected under Playback > Playback Profiles (3/8).  Here VDPAU / OpenGL / Normal settings can be tweaked along and rules set based on the source video resolution.  Advanced options are under Edit for each resolution rule.  Otherwise if your hardware is sufficient choose the YADIF filter.  Once tweaking is finished, select '''Next''' until you appear back in the menu.
 +
 
 +
===Scheduling of recordings ===
 +
 
 +
Recordings can be scheduled under Manage Recordings > Schedule Recordings > Program Guide. A variety of rules can be set but it should be noted that recordings can conflict and the priority will determine which program will be recorded.  This can be checked in ''Upcoming recordings''.
 +
 
 +
===Downloadable themes===
 +
 
 +
MythTV frontend allows multiple themes to be added with ease provided you have an internet connection.  Under Setup > Theme Chooser you can select between the available themes as desired.
  
 
==Configure automatic startup==
 
==Configure automatic startup==
Line 361: Line 437:
 
# gedit /home/mythtv/.config/autostart/autoLaunchFrontend.desktop
 
# gedit /home/mythtv/.config/autostart/autoLaunchFrontend.desktop
 
</pre>
 
</pre>
Copy and paste the following text into the newly created file
+
Copy and paste the following text into the newly created file (changing EN_AU to your langauge code):
 
<pre>
 
<pre>
 
[Desktop Entry]
 
[Desktop Entry]
Line 394: Line 470:
 
Reboot to test the autostart scripts are working.
 
Reboot to test the autostart scripts are working.
  
==Fedora Version Specific Tips==
+
=MythExit=
 +
 
 +
We're done!
 +
 
 +
This should be the entire guide required to get MythTV installed and operational on Fedora.  If you have any feedback or a request additonal explanations, post in the discussion panel or jump in and add it yourself!  Don't forget to checkout the troubleshooting section and the enhancements to get the best out of your Mythbox.
 +
 
 +
=Troubleshooting=
  
===Fedora 12/13===
+
==SELinux==
  
If analog sound doesn't work, try changing the audio device to ALSA:front, and change the ALSA:default mixer to control the Master control rather than PCM.
+
Note: If you receive an error involving permissions on a .so library, you may have SELinux installed and preventing you from accessing those libraries.  You can allow access to the libraries with the following command:  
 +
<pre>
 +
# chcon -t texrel_shlib_t /usr/lib/libmyth*.so*
 +
</pre>
  
==Troubleshooting==
+
==Tuners do not load on boot==
===Tuners do not load on boot===
 
  
 
If the DVB tuners do not load on boot when systemd loads <tt>mythbackend.service</tt> but can be accessed through mythfrontend after the following commands are issued:
 
If the DVB tuners do not load on boot when systemd loads <tt>mythbackend.service</tt> but can be accessed through mythfrontend after the following commands are issued:
Line 416: Line 500:
 
# same system as mythbackend.
 
# same system as mythbackend.
 
Wants=dev-dvb-adapter0-frontend0.device
 
Wants=dev-dvb-adapter0-frontend0.device
 +
# Uncomment below if running mythweb and comment the above
 +
# Wants=httpd.service dev-dvb-adapter0-frontend0.device
 
</pre>
 
</pre>
  
Line 421: Line 507:
 
[[Category:Fedora]]
 
[[Category:Fedora]]
  
===Auto-load scripts===
+
==Auto-load scripts==
 
I have a few things that don't seem to want to play nice anymore (i.e., nvidia-settings don't load like they should, alsa volume levels aren't restored), I decided to create a quick little shell script in ~/.kde/Autostart/myth-load.sh to handle loading up all the extra goodies I need/want to auto-start, as well as force stubborn things to work. This script loads my nvidia settings, restores alsa volumes, launches irexec for my little power button script (on the Tips 'n' Tricks page), then launches mythfrontend, all in one fell swoop. Just copy and paste all this into ~/.kde/Autostart/myth-load.sh (adjust accordingly for different desktop environments):
 
I have a few things that don't seem to want to play nice anymore (i.e., nvidia-settings don't load like they should, alsa volume levels aren't restored), I decided to create a quick little shell script in ~/.kde/Autostart/myth-load.sh to handle loading up all the extra goodies I need/want to auto-start, as well as force stubborn things to work. This script loads my nvidia settings, restores alsa volumes, launches irexec for my little power button script (on the Tips 'n' Tricks page), then launches mythfrontend, all in one fell swoop. Just copy and paste all this into ~/.kde/Autostart/myth-load.sh (adjust accordingly for different desktop environments):
  
Line 470: Line 556:
 
TimedLoginDelay=1 (Or however long you want to wait)
 
TimedLoginDelay=1 (Or however long you want to wait)
 
</pre>
 
</pre>
 +
 +
=Enhancements=
 +
 +
==Space saving==
 +
Since most Mythboxes would not be used as a general workstation some packages can be removed with relative certainty.  A big ticket item is the Libreoffice suite and the removal of this should make for much smaller updates.
 +
<pre>
 +
# yum remove libreoffice*
 +
</pre>
 +
 +
==MariaDB performance==
 +
 +
These adjustments to <tt>/etc/my.cnf</tt> under the [mysqld] section improve performance with both MythTV (especially in the GUI) and MythWeb:
 +
 +
<pre>
 +
key_buffer = 16M
 +
table_cache = 128
 +
sort_buffer_size = 2M
 +
myisam_sort_buffer_size = 8M
 +
query_cache_size = 16M
 +
</pre>
 +
 +
==Power saving==
 +
Since the frontend/backend is likely to be powered on around the clock, some power saving enhancements will allow the device to run cooler, quieter and reduce the impact on the electricity bill.  Firstly install <tt>powertop</tt> and <tt>tlp</tt> using
 +
<pre>
 +
# yum install powertop tlp
 +
</pre>
 +
And start <tt>tlp</tt> with:
 +
<pre>
 +
# tlp start
 +
</pre>
 +
And this should return the power on status (<tt>TLP Started in AC Mode</tt>).  You can modify the defaults in <tt>/etc/default/tlp</tt> to allow power saving modes while in ac mode.  Apply the changes with the tlp start command.  You can check if the power saving features are enabled by using <tt>powertop</tt> under the tunables tab by using:
 +
<pre>
 +
# powertop
 +
</pre>
 +
And using 'tab' to access the other pages in the terminal interface.  The status ''good'' should be reported next to each item.  If not try using turning on the experimental PCI-E support in <tt>/etc/default/tlp</tt> (assuming the hardware you have is recent).
 +
 +
 +
[[Category:Software Installation|1200]]

Latest revision as of 16:05, 4 August 2017


This "How-To" guide is for installing MythTV on Fedora 21.

Introduction

This wiki entry will detail the installation of a combined frontend and backend in Fedora 21. Ensure you have met the hardware requirements.

Fedora provides updates for a release until two releases after that. At the time of this writing, the current release is Fedora 21, which means support for Fedora 21 - 2 becomes discontinued a month after Fedora 21 is released. Thus, it makes sense to update to the latest release at least every other version, if not every version.

You are welcome as a MythTV user and general wiki participant, to add to, and modify this document that will help the community the best way possible.

Getting Fedora

ISO images

Download.png - Fedora download page

Note that the Workstation edition has the default GNOME Desktop available whereas the DVD install has alternative desktop environments available. For the remainder of this installation guide, the default desktop environment GNOME will be used to avoid confusion. Other desktop environments should be similar.

Physical media

CD-ROM and DVD-ROM discs can be purchased from online and local vendors.

Installing Fedora

The official Fedora 21 installation guide is an excellent place to start when installing Fedora. There are a few modifications on the procedure given in the official documentation; user creation and filesystem partitions. The notes in this wiki will detail an installation from the Live Desktop Media - Workstation. It should be noted that additional desktop environments are also available if the GNOME 3 desktop is not suitable. Some alternatives are listed in the Fedora spins page and installation is detailed here. Desktop environments other than GNOME 3 are outside of the scope of this wiki for brevity.

Date/Time

During installation you should adjust the date and time of the machine to the current date and time. To do this ensure the Network Time slider is set to on under the Localization options. Making sure the system is running to the correct time is important for timely scheduling of recordings.

Filesystems

Among the MythTV community, it is highly recommend to use a custom partitioning scheme rather than auto-partitioning with a dedicated /video (or similar) partition for storage of all your recordings. If possible, for best efficiency, the video partition should be on a drive physically separate from the operating system partitions. Software RAID and LVM for your video partitions will only slow it down and should be avoided. LVM is no longer necessary for MythTV due to Storage Groups.

Currently EXT4 format is the default in Fedora and other distributions. A partition setup example is given in the Table below.

User creation

When prompted during the installation, create a non-administrator user on the system with the username "mythtv". You can set the password for this user to anything you want. This should be a Strong Password that is different than the root password.

Partition Mount Point Size Format
/dev/sda1 /boot 500MB ext4
/dev/sda2 swap same as RAM (ex: 4096MB) swap
/dev/sda3 (for the OS) / 8-12GB ext4
/dev/sda4 /home 8-12GB ext4
/dev/sda5 /video Remainder ext4

First boot

At this point Anaconda will ask you to remove the installation media from the drive and reboot the system. Once your system has finished rebooting you will be prompted to do some final configurations and be given a short tour of GNOME 3.

GNOME terminal

Tasks in linux are performed with greater ease through the command line and are therefore required in this How-To. In GNOME 3, the terminal is accessed by going to Activities and typing terminal in the search box.

Some commands need to be run as the mythtv user, and some commands need to be run as the root user. The boxes below will indicate with a prompt which user should run the command. Commands with a "$" prompt should be run as the mythtv user. If you see a command that starts with a "#", you will need to use the su command to become the root user.

To execute commands as the root run "su -" and enter the Fedora root password.

[mythtv@machine_name ~]$ su -
Password:
[root@machine_name ~]#

Notice the way the username changes from mythtv to root and the prompt changes from "$" to "#". Be sure you run all of the following commands as the correct user. If you do not, you will likely run into problems sooner or later. To become the mythtv user again, type "exit".

[root@machine_name ~]# exit
logout
[mythtv@machine_name ~]$

Your screen should clear, and your prompt should be a "$" again. If this is not the case, keep typing "exit" until it is. You can copy and paste text in the terminal by using 'Control-Shift-C' and 'Control-Shift-V' respectively.

Update Fedora

Firstly get your system fully updated. Simply run the command from terminal:

# yum update

When you see the Transaction Summary, you will need to press "y" to begin downloading the packages.

 Transaction Summary
 =============================================================================
 Install      20 Package(s)
 Update      79 Package(s)
 Remove       0 Package(s)
 Total download size: 902 M
 Is this ok [y/N]: y

After the update has finished, reboot your computer for the effects to take place.

Network configuration

On the Network Configuration screen (Activities -> Network Connections), setting a static IP address is highly recommended (could be either a static, or statically mapped DHCP address). It really isn't a huge deal if you only have one Mythbox (though you probably don't want MythWeb to be a moving target), but it could cause major headaches once you have more than one machine, since non-primary systems won't know where the master backend is located if the address changes.

Firewall

Note that since Fedora 21 Workstation the firewall application has been removed for ease of use. The VNC ports are open on this machine by default. It can be installed by

# yum install firewall-config

A basic MythTV box should not have any problems running with the default Public zone firewall settings. If there are issues with service access you will at the very least want to enable SSH, Secure WWW (HTTPS) and WWW (HTTP) checkboxes to enable those services under the appropriate Firewall zone with the Permanent configuration.

If you plan to run separate front end and back end servers you will need to allow those ports through on under "Other Ports". Add TCP ports 6543 and 6544 to allow the MythTV protocol access through the firewall and TCP 3306 for MariaDB.

Autologin and display timeout

You can choose to have GNOME autologin in the mythtv user on boot so that the mythfrontend can automatically load. To set this behaviour go to Activities > Users. Unlock the user panel with the administrator password and slide the Automatic Login to the on position.

The screen timeout will also cause problems when using MythTV. You can set the display to not turn off by going to Activities > Power and setting the blank screen option to never. Be sure not to leave the display on with this option as it can cause issues with the display panel (burn in etc).

Sound setup

Fedora uses PulseAudio by default, as do many Linux distributions. MythTV works with Pulseaudio. Ensure the sound is working in the GNOME desktop otherwise try changing the output (e.g., HDMI) in Activities > Sound.

Remote desktop

The remote desktop in GNOME can be enabled through Activities > System Settings > Sharing. Turn on Screen Sharing and Allow Remote Control through the attached network device. It is strongly recommended that a secure password is set.

Fedora setup

The next section will require you to be logged in as the mythtv user.

Configure package repositories

RPMFusion

Configuration of yum is needed to use the RPMFusion package repository. Follow the links below and install the RPMs for the latest version and correct architecture for your system.

Webpage.png - RPMFusion

Note: You will need to download the packages rpmfusion-free-release and rpmfusion-nonfree-release under Firefox graphical installation and install with GNOME Software or rpm -ivh *.

Some MythTV installations require additional kernel modules to make all the hardware work. When installing firmware/drivers such as the proprietary nVidia graphics drivers the akmod or kmod packages can be chosen. The akmod packages automatically check and compile the driver on boot if required. This incurs a small penalty of having to install development packages. The kmod packages are built against a specific kernel version and if a new kernel is installed without the corresponding kmod then errors on boot may occur. Therefore for system safety the akmod packages are recommended.

NVIDIA

We recommend you use a card that supports VDPAU for video acceleration.

You can install binary drivers from NVIDIA, but in most cases it's simpler to use yum to get and install them from RPMFusion. It is essential to get the proper version of the drivers. Start by running

$ /sbin/lspci -nn | grep 'VGA'

This will give you the chipset name and the PCI id (which is after the colon inside the bracket set before the rev number). Compare these to the NVIDIA docs. Unless your card is in one of the legacy lists, you can install the latest drivers. If you have one of the legacy products you will have to modify the yum package name to get the proper drivers. The newer drivers will NOT work on "legacy" cards.

To install from the RPMFusion repository, run:

# yum install kernel-devel akmod-nvidia

You might encounter a message about a GPG key, accept this with y. Upon reboot the boot will be interrupted to build akmod-nvidia against the current kernel version which may take some time. You can check that the driver installed correctly by entering the following command in the terminal.

$ glxinfo | grep -i nvidia

Which should return an entry for the NVIDIA card.

If you need a legacy package from RPM Fusion consult the available packages table at http://rpmfusion.org/.

DVD playback

If you require DVD playback then you will need to install the libdvdcss package from an alternative repository. Please check if this is legal in your country.

# yum localinstall http://rpm.livna.org/livna-release.rpm
# yum install libdvdcss

The libdvdcss package can also be installed by performing the following commands for 64 or 32 bit versions respectively:

# rpm -Uvh http://rpm.livna.org/repo/18/x86_64/libdvdcss-1.2.12-1.fc17.remi.x86_64.rpm
or
# rpm -Uvh http://rpm.livna.org/repo/18/i386/libdvdcss-1.2.12-1.fc17.remi.i686.rpm

Install MythTV

MythTV has numerous required dependencies to function correctly, which are automatically taken care of with one simple command:

# yum install mythtv

SELinux

It is strongly recommended that SELinux is run in "enforcing" mode as set by default. You can choose the permissive mode which will only warn you of problems.

Fedora comes with the excellent setroubleshoot tool which will notify of denials whilst permitting you to leave SELinux enabled on your system. Audit2allow in enforcing mode can also be used to catch SELinux denials and rules can be automatically created to allow program access in the future.

If you prefer running enforcing SELinux with mythweb, the following commands may be helpful:

 $ /usr/sbin/setsebool -P httpd_can_connect_mythtv 1
 $ /usr/sbin/setsebool -P httpd_can_network_connect 1

If you have followed the previous instructions and the MythTV recordings and videos are on a seperate drive and you wish to use MythWeb, then you will need to tell SELinux about this. On the test machine the videos are mounted at /mnt/sdb/Videos. The SELinux Troubleshooting tool gives errors that httpd wants to access these directories. To allow httpd read permission:

 $ chcon -R -t httpd_sys_content_t '/mnt/sdb/Videos*'
 $ semanage fcontext -a -t  httpd_sys_content_t '/mnt/sdb/Videos*'

Install capture card drivers

Some capture card drivers have been included by default with Fedora. The IVTV drivers required for the PVR-150/250/350 and the drivers required for the Hauppauge HD-PVR 1212 are included, for example.

You can check if the kernel is able to detect the attached dvb tuner by checking the kernel messages. This is done with:

dmesg | grep -i dvb

If the firmware loading was successful you may notice a message similar to:

usb 1-6: dvb_usb_v2: 'Kworld UB499-2T T09' successfully initialized and connected

Otherwise you will need to find the chipset details of the attached tuner. If you have a usb attached tuner use lsusb or if you have a PCI tuner use lspci.

An example output of this might be:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0609:0334 SMK Manufacturing, Inc. eHome Infrared Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 1b80:e409 Afatech IT9137FN Dual DVB-T [KWorld UB499-2T]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 17ef:6022 Lenovo 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The entry with DVB gives the model name of the tuner (KWorld UB499-2T) and chipset (IT9137FN) which can be compared with the lists at linuxtv.org.

Configure remote control

Many remote control drivers have been moved to the kernel but manual key mapping may still be desired. This can be achieved by installing the v4l-utils package for the ir-keytable command.

# yum install v4l-utils

Once v4l-utils has successfully installed you can check to see what protocol and keymap that the current remote control has by runnning:

# ir-keytable

This might give the following output (for a MCE-USB remote):

[root@machinename]# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event4) with:
  Driver mceusb, table rc-rc6-mce
  Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
  Enabled protocols: RC-6
  ...

In this instance the keymap being used is /lib/udev/rc_keymaps/rc6-mce.

To test the key mappings run the following command that will capture the input and button name of each keypress.

# ir-keytable -t

The mappings can be changed by finding your corresponding keymap in /lib/udev/rc_keymaps. Be sure to comment out the original mappings in case an error is made during the file modification and re-load the keymap using:

# ir-keytable -c -w /lib/udev/rc_keymaps/<keymap name>

If your remote control does not exist in the kernel and you don't get any output in ir-keytable -t then you will have to install LIRC.

Note for rc6-mce: at the top of the /lib/udev/rc_keymaps/rc6_mce keymap file the protocol is changed to RC6-MCE and this will need to be changed back to RC6 if an error regarding unsupported protocol occurs.

Install LIRC

This LIRC instruction may well be outdated

Note for Fedora 12 + users the default LIRC socket file name has changed to /var/run/lirc/lircd , so you will need to update MythTV Settings -> General from /dev/lircd ->/var/run/lirc/lircd and then restart mythfrontend.

Check first if lirc is installed before proceeding below...(eg find / -name lircd)

# yum install lirc

This will install the Linux Infra-Red Control package. This is a daemon which translates infra-red key presses into keyboard events, therefore you will need to configure your remote control accordingly.

Setup MariaDB

In Fedora 20, mySQL has been replaced with MariaDB but backwards compatibility is maintained such that the following commands should still be applicable. We'll need to enable MariaDB to load at startup, set some passwords and create the MythTV database which we'll populate shortly. The population of this database is handled by mythtv-setup in the next step, and all MythTV add-on module database additions must be done after running mythtv-setup at least one time. Start by enabling automatic load at boot and start the database:

# systemctl enable mariadb.service
# systemctl restart mariadb.service

Then to setup the database:

$ mysql_secure_installation

Set the MariaDB root password when prompted and accept all the defaults by pressing enter. Now we can create the MythTV database (called mythconverg) to get us started:

$ mysql -u root -p < /usr/share/doc/mythtv-docs/database/mc.sql
Enter password:

At this point, enter the password you just set above (ROOT_PWD) when prompted.

The above command gives users access to the database (see the main documentation) with the

/usr/bin/mysql -u root -p mythconverg
mysql> GRANT ALL ON mythconverg.* TO mythtv@"%" identified by  "mythtv";
mysql> flush privileges;

Again, all subsequent database population for MythTV's add-on modules must now be done after running mythtv-setup at least one time. It's worth customizing some parameters in /etc/my.cnf for optimal performance with MythTV.

In the event the mythtv-setup fails (current in Fedora 20), it may be because the time zone tables are not loading. See the wiki on the time zones. This entry fixed the problem:

$ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql

Pre-launch checks

Before going further it is wise to check whether things have worked so far. Has a /dev/dvb/ entry been created for a digital video source?

$ ls /dev/dvb*

Which should return (or similiar if successful):

adapter0 adapter1

If not, you should be reading https://fedoraproject.org/wiki/DavidTimms/DVB), if you have an digital source yet something has gone wrong with installing it (in which case you should look at /var/log/dmesg using dmesg | grep -i dvb), and check whether udev, ivtv, and so on are working, and required modules are loaded). A useful quick test for USB video sources is to unplug them then plug them in again and look at the ends of whatever /var/log files get updated.

Setup MythTV

To launch the MythTV setup utility search for mythtv in the Activities overview. You should be presented with a graphical interface and you may be required to update the database schema. Now we will move onto assigning the tuners, channels and storage directories.

1. General

In General settings, set the local and master backend IP address to the local IP address of your machine for a combined frontend / backend. On the test machine this was 192.168.0.2 (may be different for you). Set your channel frequency table in the next page and continue to scroll through until you have reached Finished.

2. Capture cards

In order for MythTV to record a stream, you must firstly setup the capture devices. This is under 2. Capture Cards. Select the card type (DVB-T/S/C for terrestial) and make sure the DVB device is recognised correctly and select Finish. Do this for each available capture device. At this stage you can also set each recording device to record multiple channels per multiplex (DVB) by Recording Options > Max Recordings: and set to 3 (from a value of 2).

4. Video sources

Once the capture devices have been created successfully and you have decided between SchedulesDirect or using EIT to schedule recordings, a video source is required. Create a video source under 4. Video sources and give it a name (e.g. vidSrc0) and enter in your SchedulesDirect details or use EIT under Listings Grabber and accept the remaining defaults.

5. Input connections

In the next section 5. Input Connections assign each capture device a display name (adapterX) and a video source. Then select Scan for channels and ensure the country and scan type (TV or TV+Radio) is correct and select Next. The selected capture device will now scan for available channels. Once complete, a summary of the channels is given, select Insert All and Finish.

In many parts of the world the program guide data is transmitted free over the air and is used by MythTV to schedule recordings and provide program information (EIT). However if you are in the US, you will may need a paid account with schedulesdirect. The current pricing is $25US per year (current at November 2014). This will give you television feed data that your Mythbox uses for scheduling once you have localized your account to your zip code, chosen a content provider service and then set your channels from the web page.

6. Channel Editor

There may be duplicate channels that can be removed safely and allows for less clutter for the backend to deal with when scheduling. In 6. Channel Editor the duplicate channels can be deleted using key d and further additions to channels / transports can be done if desired. There may be icons available for you to download using Download icons option.

7. Storage directories

The storage directories can be configured in 7. Storage Directories. Those using a dedicated /video partition as per the previous recommendation, you should obviously set /video/recordings for storage of recorded shows. However, you can do pretty much whatever you like here, such as recording to an NFS or Samba mount. Just make sure your mythtv user has permission to read and write to whatever location you choose.

Mythbackend startup

It is highly recommended that you go through the above setup steps in order. Follow the on-screen instruction, with aid from the MythTV website documentation where required.

Once you've gone through the setup, you have to populate the MythTV database with some program info. Once you have your listings to your liking, you're ready to fill your database with programming info. You must start up the backend first and we'll set it to autostart later. Enter the following command in a terminal:

$ mythbackend

Assuming all goes well and the process doesn't exit on you (if it does, check out the troubleshooting section below), lets get some guide data, in a new terminal window type:

$ mythfilldatabase 

If you're using a guide data source other than SchedulesDirect (i.e., anyone outside the U.S. and Canada), you may need to add a "--manual" flag to the end of that command to get it to work. Look at the output of "mythfilldatabase --help" for more clues if you have problems.

Be patient. This step can take a fairly long time, depending on your internet connection speed and how many channels your service provides. To get automatic updates of programming data daily, see the available options in mythtv-setup, under 1. General on the 10th page for further configuration.

Mythfrontend configuration

Now start up the MythTV frontend. It is recommended launching mythfrontend in a separate shell window, so you can distinctly see the output for the backend and frontend processes for debugging purposes. From a terminal:

$ mythfrontend

There are various options within mythfrontend that you can tweak relating to appearance, video, audio and scheduling of recordings.

Audio

To configure the audio go to Setup > Audio. Choose the Audio output device that gives the current line output (e.g. HDMI). On the test computer this was ALSA:hdmi:CARD=NVidia,DEV=0. Use the inbuilt Test function to see if MythTV is outputting sound to the correct device. Select Next to choose the mixer properties. If your remote control has volume buttons then MythTV can respond the volume changes when the Mixer device is set to software.

Video

Likewise for the audio, the video can be configure under Setup > Video. If the captured streams are interlaced, then the choice of interlacer is critical to an enjoyable viewing experience. It is generally considered that nVidia with VDPAU has the most advanced deinterlacing methods (Advanced and Temporal) and these should be selected under Playback > Playback Profiles (3/8). Here VDPAU / OpenGL / Normal settings can be tweaked along and rules set based on the source video resolution. Advanced options are under Edit for each resolution rule. Otherwise if your hardware is sufficient choose the YADIF filter. Once tweaking is finished, select Next until you appear back in the menu.

Scheduling of recordings

Recordings can be scheduled under Manage Recordings > Schedule Recordings > Program Guide. A variety of rules can be set but it should be noted that recordings can conflict and the priority will determine which program will be recorded. This can be checked in Upcoming recordings.

Downloadable themes

MythTV frontend allows multiple themes to be added with ease provided you have an internet connection. Under Setup > Theme Chooser you can select between the available themes as desired.

Configure automatic startup

The necessary init script for the MythTV backend to automatically start at system boot is already in place for you, just simply turn it on:

# systemctl enable mythbackend.service

If the backend isn't already running, save yourself a reboot and issue this command:

# systemctl restart mythbackend.service

(If the backend fails at boot see: Systemd mythbackend Configuration (Works for Fedora 20))

It is possible to have mythfrontend start when the mythtv user logs in. This can be done by adding a .desktop file to the mythtv user home directory. Open a command line and enter:

# gedit /home/mythtv/.config/autostart/autoLaunchFrontend.desktop

Copy and paste the following text into the newly created file (changing EN_AU to your langauge code):

[Desktop Entry]
Type=Application
Exec=/home/mythtv/scripts/autoLaunchFrontend.sh
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_AU]=autoLaunchFrontend
Name=launchFrontend
Comment[en_AU]=
Comment=

Save and exit. Create a file in the Exec= path as such:

# mkdir -p /home/mythtv/scripts
# gedit /home/mythtv/scripts/autoLaunchFrontend.sh

And copy and paste the following text into the file. This script will wait 10 seconds before launching the frontend.

#!/bin/bash

# Autolaunch script for MythTV Frontend

sleep 10s
mythfrontend

Change the permissions to an executable with:

# chmod +x /home/mythtv/scripts/autoLaunchFrontend.sh

Reboot to test the autostart scripts are working.

MythExit

We're done!

This should be the entire guide required to get MythTV installed and operational on Fedora. If you have any feedback or a request additonal explanations, post in the discussion panel or jump in and add it yourself! Don't forget to checkout the troubleshooting section and the enhancements to get the best out of your Mythbox.

Troubleshooting

SELinux

Note: If you receive an error involving permissions on a .so library, you may have SELinux installed and preventing you from accessing those libraries. You can allow access to the libraries with the following command:

# chcon -t texrel_shlib_t /usr/lib/libmyth*.so*

Tuners do not load on boot

If the DVB tuners do not load on boot when systemd loads mythbackend.service but can be accessed through mythfrontend after the following commands are issued:

# systemctl stop mythbackend.service
$ mythbackend

Then this could mean that the tuners not ready when systemd starts the mythbackend.service. This can be fixed by following the instructions given in /etc/systemd/system/multi-user.target.wants/mythbackend.service and adding the tuners as a requirement on boot. Simply find the required device in /dev/dvb/adapter0 as a general guide (might not be specific to your tuner).

[Unit]
Description=MythTV backend service
After=network.target mariadb.service mysqld.service time-sync.target dev-dvb-adapter0-frontend0.device
# Uncomment the following line if you will be using the mythweb plugin on the
# same system as mythbackend.
Wants=dev-dvb-adapter0-frontend0.device
# Uncomment below if running mythweb and comment the above
# Wants=httpd.service dev-dvb-adapter0-frontend0.device

Auto-load scripts

I have a few things that don't seem to want to play nice anymore (i.e., nvidia-settings don't load like they should, alsa volume levels aren't restored), I decided to create a quick little shell script in ~/.kde/Autostart/myth-load.sh to handle loading up all the extra goodies I need/want to auto-start, as well as force stubborn things to work. This script loads my nvidia settings, restores alsa volumes, launches irexec for my little power button script (on the Tips 'n' Tricks page), then launches mythfrontend, all in one fell swoop. Just copy and paste all this into ~/.kde/Autostart/myth-load.sh (adjust accordingly for different desktop environments):

#!/bin/bash

# Only do this stuff if we're on the main display
# (i.e., don't do this in a vnc session)
if [ `echo $DISPLAY | grep -c ":0"` -ge 1 ]
then
    # Load nVidia driver custom settings
    nvidia-settings --load-config-only &
    # Restore audio settings
    /usr/sbin/alsactl restore
    # Launch irexec for myth power button stop/start
    irexec &
    # Launch myth welcome 
    mythwelcome &
    # Disable dynamic power management (screen blanking)
    /usr/bin/xset -dpms
    # Disable screen saver
    /usr/bin/xset s off
fi
exit 

Don't forget to make it executable:

$ chmod +x ~/.kde/Autostart/myth-load.sh 

You'll also have to set autologin for your mythtv user. You'll have to get a root terminal open then:

Add the following lines to /etc/gdm/custom.conf

[daemon]
AutomaticLoginEnable=true
AutomaticLogin=mythtv (or whatever user you want)

If you want a timed login, try:

[daemon]
TimedLoginEnable=true
TimedLogin=mythtv
TimedLoginDelay=1 (Or however long you want to wait)

Enhancements

Space saving

Since most Mythboxes would not be used as a general workstation some packages can be removed with relative certainty. A big ticket item is the Libreoffice suite and the removal of this should make for much smaller updates.

# yum remove libreoffice*

MariaDB performance

These adjustments to /etc/my.cnf under the [mysqld] section improve performance with both MythTV (especially in the GUI) and MythWeb:

key_buffer = 16M
table_cache = 128
sort_buffer_size = 2M
myisam_sort_buffer_size = 8M
query_cache_size = 16M 

Power saving

Since the frontend/backend is likely to be powered on around the clock, some power saving enhancements will allow the device to run cooler, quieter and reduce the impact on the electricity bill. Firstly install powertop and tlp using

# yum install powertop tlp

And start tlp with:

# tlp start

And this should return the power on status (TLP Started in AC Mode). You can modify the defaults in /etc/default/tlp to allow power saving modes while in ac mode. Apply the changes with the tlp start command. You can check if the power saving features are enabled by using powertop under the tunables tab by using:

# powertop

And using 'tab' to access the other pages in the terminal interface. The status good should be reported next to each item. If not try using turning on the experimental PCI-E support in /etc/default/tlp (assuming the hardware you have is recent).