Installing MythTV on Fedora
This "How-To" guide is for installing MythTV on the latest release of Fedora.
- 1 Introduction
- 2 Getting Fedora
- 3 Installing Fedora
- 4 First boot
- 5 Fedora setup
- 6 Install MythTV
- 7 Setup MariaDB
- 8 System checks
- 9 Setup MythTV
- 10 Configure automatic startup
- 11 Troubleshooting
- 12 Enhancements
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 MythTV.
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.
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.
The latest version of Fedora can be downloaded from the Fedora Download Page. Note that the Desktop 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.
The official Fedora 20 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 spins page and installation is detailed here. Desktop environments other than GNOME 3 are outside of the scope of this wiki for brevity.
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.
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:
|/dev/sda2||swap||same as RAM (ex: 4096MB)||swap|
|/dev/sda3 (for the OS)||/||8-12GB||ext4|
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.
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.
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.
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.
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.
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).
The next section will require you to be logged in as the mythtv user.
Configure package repositories
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.
Note: You will need to download the packages rpmfusion-free-release and rpmfusion-nonfree-release 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.
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
$ /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/.
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
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.
Please ensure that only local access is allowed for the VNC ports for security reasons.
The remote desktop in GNOME can be enabled through Activities > 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).
MythTV has numerous required dependencies to function correctly, which are automatically taken care of with one simple command:
# yum install mythtv
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.
It is strongly recommended that SELinux is run in "permissive" mode by editing /etc/selinux/config. There are a few things that will not work properly if you set SELinux to "enforcing" such as the MythWeb plugin. If 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.
Fedora 20 comes with the excellent 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.
If you prefer running enforcing SELinux with mythweb, the following commands may be helpful:
$ /usr/sbin/setsebool -P httpd_can_network_connect=1 $ /usr/sbin/setsebool -P httpd_ssi_exec=1 $ chcon -R -t httpd_sys_content_rw_t /var/www/html/mythweb/data $ semanage fcontext -a -t httpd_sys_content_rw_t /var/www/html/mythweb/data
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:
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.
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.
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:
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 commands
$ /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
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*
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.
To launch the MythTV setup utility enter the following into the terminal:
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.
Electronic Program Guide data
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. However if you are in the US, you will may need a paid account with schedulesdirect. The current pricing is $25US per year. 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.
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 documentation.
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:
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.
Now start up the MythTV frontend (I recommend doing this in a separate shell window, so you can distinctly see the different output for the backend and frontend processes)...
There are various options within mythfrontend that you can tweak...a lot of this is covered by other parts of the wiki.
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.
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
[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.
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
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)
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*
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
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:
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 (assuming the hardware you have is recent).