Opensuse 11.0 - 11.2

From MythTV Official Wiki
Revision as of 03:43, 24 July 2010 by Comrad Kev (talk | contribs) (Removed 11.3 material which is now in its own page.)

Jump to: navigation, search
Other openSUSE version


openSUSE 11.0 and openSUSE 11.1 both work like a charm.

Setting up takes a bit of work.

Please update this page with your experience

See the User Experiences section on this page for more information.


Benefits of using openSUSE 11 for mythTV
  • Best hardware support available
  • Super fast software installation (package management) based on libzypp
  • openSUSE 1-click install technology, packages or package bundles can be installed with 1 click (No need to compile)
    • mythTV packages are available as a bundle with 1-click install on pacman
    • restricted formats (proprietary, patented formats) like MP3, Codecs, encrypted DVD support etc. are available with 1-click install on opensuse-community
    • proprietary video drivers for both AMD/ATI and NVIDIA are available with 1-click install
    • additional packages for the advanced user are also available with one 1-click install from (e.g. lcd support)
  • New and super fast installation, completing in roughly just 35 minutes (including mythTV software)
  • Good openSUSE, mythTV documentation and a friendly community ;-)

read more

About openSUSE

SUSE Linux, one of the oldest Linux distributions, was originally developed by a German company. SuSE is an acronym in the German language for “Software und System-Entwicklung” which translates as software and system development.

The openSUSE project is a community program sponsored by Novell. With the launch of the openSUSE project, openSUSE is now developed in an open model—public development builds, releases, and sources will be posted frequently and users will have access to the Bugzilla database for defect reporting.

Functional diagram.png

For rich, reliable and secure home computing like mythTV, there's no better choice than openSUSE. It features an easy-to-install Linux operating system that includes most of the required mythTV components standard in the box. While the official mythTV documentation attempts to be as distribution-agnostic as possible, this document is geared specifically toward building a mythTV system on the openSUSE Linux distribution.

openSUSE, in combination with the PackMan (thanks Herbert Graeber for building the rpm's) repository, provides you with an easy installation and all the latest packages of the mythTV rpms, ivtv, lirc, xmltv, php, mysql, mplayer, xine and many more that are necessary for a fully functional mythTV box.

Download.png - Download openSUSE

Webpage.png - openSUSE official documentation

Webpage.png - openSUSE 11.1 Release notes

Webpage.png - Guide to openSUSE 11.0

Wikipage.png - mythTV Executive_Overview mythTV wiki page

While mythTV can take quite some time to install, the result will be a fast box that can do nearly anything to entertain. Furthermore, the system is incredibly reliable, and if you leave it on, you can expect runtimes that last for years with little to no maintenance to be done (aside from updates if desired). We've also experienced that the WAF (Wife Acceptance Factor) for mythTV is enormous. As soon as you start playing with it, you need a second box because it becomes the most mission critical system in your house. I hope this document will help you in your quest for your ultimate mythbox. Remember this: "MythTV can be a time machine; hours can disappear for no reason at all."

Hardware considerations

Installing mythTV all starts with good hardware. The first requirement is a machine capable of running openSUSE x86 or x86-64 and that can be connected to the Internet. You will also need a decent audio card and a video card, a hard drive with as much storage space as you desire, as well as a TV tuner capable of performing hardware-level video encoding. Many people run mythTV without any problems on older hardware; however, if you are planning on doing anything with high definition video or complex transcoding jobs, you will need to have sufficient memory and processing power. Check this wiki and the mailinglist before you purchase any new hardware.

You might also find it useful to look at if you build a machine for your living room, in order to get advice on low power-consumption, low noise setups.

Wikipage.png - Bare_Bones_System mythTV wiki page

Wikipage.png - Cases mythTV wiki page


Join the community and get some help
Subscribe to the mythTV users mailing list

mythTV user mailing list

mythTV user mailing list archive

Chat with other mythTV users

IRC #mythtv-users

Initial system setup and considerations

openSUSE 11 Media (DVD and/or CD)

For users new to Linux, the supported version of openSUSE may be the best choice—you'll get complete end-user documentation, installable media for x86 and x86 64-bit systems, plus 90 days of end-user installation support. Others just download openSUSE from one of the sources.

Download.png - Download openSUSE

Webpage.png - Buy online (including 90 days support, a real manual and a fancy DVD)

Partitions and File Systems

openSUSE ships with a number of different file systems, including ReiserFS, Ext2, Ext3 and XFS, from which to choose at installation time. Each file system has its own advantages and disadvantages that can make it more suited to a scenario. Professional high-performance setups may require a different choice of file system than a home user's setup.

Earlier versions of openSUSE used ReiserFS as the default filesystem. From openSUSE 10.3 and on, ext3 is the default file system.


Use ext3 as your default file system. Consider using XFS for your video data. XFS is very good at manipulating and deleting large files and performs well on high-end hardware.


Make sure you understand what hardware you have - especially if you have issues an need to Google.

lspci -v and lsusb and hwinfo


Wikipage.png - File Systems mythTV wiki page

Webpage.png - SUSE Linux Enterprise documentation about file systems

Install mythTV software on openSUSE


STEP (1 of 4) - Repositories

Add the required software repositories.

Make sure that the standard openSUSE software repositories are configured: If you don't have a dual layer DVD set with the complete OSS and NON-OSS packages on their, the package manager relies on the software repositories on the internet. I suggest you point to the online repositories (tobe sure) and so you don't need you CD/DVD anymore.

Start YaST and look at your software repositories. You can remove/disable the CD/DVD media and make sure you have the following repositories:

Warning.png Warning: Make sure the standard openSUSE repositories are setup correct before you start installing the software.

Check 'Software Repositories' in YaST

openSUSE 11.1 Main Repository (NON-OSS)

protocol: HTTP


directory: /distribution/11.1/repo/non-oss/

To add the repo using the commandline:

sudo zypper ar "openSUSE 11.1 Main Repository (NON-OSS)"
sudo zypper mr --disable-autorefresh "openSUSE 11.1 Main Repository (NON-OSS)"
openSUSE 11.1 Main Repository (OSS)

protocol: HTTP


directory: /repositories/openSUSE:11.1/standard/

To add the repo using the commandline:

sudo zypper ar "openSUSE 11.1 Main Repository (OSS)"
sudo zypper mr --disable-autorefresh "openSUSE 11.1 Main Repository (OSS)"
openSUSE Update Respository

(this will be automatically added/configured when you select 'Online Update Configuration' in YaST.

If you added the new repos from the commandline and 'disabled the autorefresh', you need to fill the cache once

To update the repositories from the commandline, and update the local cache:

sudo zypper ref

Information.png Tip: For you information

1. You need todo the Online Update Configuration in YaST in order to get your Update Repository

2. The content in the main software repositories does not change. Disable the Automatically Refresh for these repositories will increase performance.

STEP (2 of 4) - multimedia

This will install the Restricted Multimedia Formats ranging from MP3 Codecs to playing Encrypted DVDs

Install Restricted Multimedia Formats for KDE users
Install Restricted Multimedia Formats for GNOME user

STEP (3 of 4) - Requirements

Install the prerequisite packages with zypper by copying and pasting the following into a terminal (as root)

sudo zypper in dvb
sudo zypper in libid3tag mysql php5 xine-ui xmms fame libcdaudio libfame MPlayer
sudo zypper in phpPgAdmin pvm transcode apache2 yast2-http-server apache2-mod_php5

STEP (4 of 4) - mythtv

This will install the mythTV packages for both frontend and backend from the packman repository.

Install mythTV from packman

Configure mythTV server components (mythbackend)

The server components within mythTV are referred to as the mythbackend.

Because the configuration of the mythTV application itself is not openSUSE specific, you find mainly links to the information. Documentation

Wikipage.png - Manual mythTV wiki page

Start required services

Make sure all required system services are running on startup: As root start 'yast2 runlevel' and enabel the following services and click OK after popup dialog

  • ntp
  • mysql

Notice there is a mythbackend option, would suggest that you do not enable "mythbackend" just yet, until you have tried running in a terminal window as below. If all steps below work then enable this to run.

Information.png Tip: You can manually add things to /etc/init.d/boot.local. After initializing and processing the boot procedure the boot.local script us executed, which can execute the local commands.

Create the database (mysql)

mythTV uses MySQL to store it's settings, listings, recording schedules, and other information. So we have to make sure openSUSE starts MySQL when it boots, and we have to initialize the database with some basic information that mythTV can work with. The database is probably the most important component of mythTV because without it, absolutely none of mythTV can function.


1.) The MySQL deamon (mysql) is not started automatically by default after a reboot. As root start 'yast2 runlevel', select mysql and make sure it's started at boot time.

2.) Create the database If the database is not started, start mysql (as root) by typing

/etc/init.d/mysql start

Watch for errors. Set up a root password by typing

mysqladmin -u root password <yourpasswordhere>

Once MySQL is setup, install the mythTV Database. This is done by running:

mysql -u root -p < /usr/share/doc/packages/mythtv-doc/database/mc.sql

(and key-in the previously entered password) You should see no output - this is a good thing!

By default, the database is named mythconverg and contains a set of tables that interact with one-another.

Information.png Tip: make the database multi user, so you can access it from more than 1 machine; this will assign a user named "mythtv" with a password of "mythtv " to the "mythconverg" database:

mysql -u root -p mythconverg

You will then be connected directly to the database. Enter the following commands at the mysql> prompt.

mysql> grant all on mythconverg.* to mythtv@"%" identified by "mythtv";
mysql> flush privileges;
mysql> quit;

MythTV backend setup application (mythtv-setup)


The server components within mythTV are referred to as the mythbackend.

Because the configuration of the mythTV application itself is not openSUSE specific, you find mainly links to the information. Documentation

Wikipage.png - Manual mythTV wiki page

Wikipage.png - User Manual mythTV wiki page

When everything works. The mythserver process (mythbackend) is not started automatically by default after a reboot.

As root start 'yast2 runlevel', select mythbackend and make sure it's started at boot time.

Digital Video capture card (DVB)


If you are lucky, your DVB device is automatically detected and drivers are automatically loaded. More information about Linux support for DVB cards can be found on:

In general:

1.) Check if your card is auto detected by Linux - You can see this in YaST / TV settings

2.) Google and find out if you need/can define your card manual in YaST / TV settings

3.) load the kernel module(s) for your hardware (if auto detected it's automatically done) YaST will write the modprobe settings to /etc/modprobe.d/tv. Alternative you load the kernel modules (drivers) with the modprobe <drivername>.

4.) See if everything get started

dmesg | grep dvb

Check if devices are created

ls /dev/dvb*

If there is no /dev/dvb* device - the driver does not support your hardware

1.) Check (and update) the hardware specific section on the mythTV wiki

Wikipage.png - Hauppauge_WinTV_Nova-T_500_PCI mythTV wiki page

Analogue Video capture card (IVTV)

A TV capture card, also called a TV tuner card, is a device that receives TV signals and converts

them into a digital format. With a minimum of one TV tuner card installed, you can watch and record TV by using your mythTV system. If you install a second TV tuner, you can record or watch TV from more than one channel at the same time.

If you have one TV tuner, for example the Hauppauge PVR-150, you can:

  • Record TV on one channel
  • Watch live TV on one channel
  • Watch a recorded show while you record another show

If you have two TV tuners, for example the Hauppauge PVR-500, you can:

  • Record TV on two different channels at the same time
  • Watch live TV on one channel while another show that is on a different channel is recorded
  • Watch a recorded show while you record two shows at the same time

mythTV supports a myriad of different video capture cards by utilizing the IVTV driver, a kernel driver for Linux and a driver for X11 for hardware based on Conexant's CX23415/CX23416 codec chip. The recommended analogue Standard Definition Cable (SDC) capture cards are the Hauppauge PVR.


Webpage.png - a complete list of supported hardware by IVTV

Wikipage.png - capture card matrix on the mythTV wiki page mythTV wiki page

Webpage.png - ivtv wiki, primary resource

Webpage.png - openSUSE wiki, supported TV cards

openSUSE 10.3 ships with IVTV version 0.10.3 and ivtv-firmware 0.10.3, everything is auto detected on the x86 and x86-64 bit version of the OS. Please make sure you install the ivtv-firmware from YaST from the NON-OSS openSUSE repository.

Download.png - ivtv, located on 10.3 media OSS

Download.png - ivt_firmware, located on 10.3 media NON_OSS


IVTV-based cards are hardware encoders, but the firmware does not exist in the card itself. Instead, you must point your hardware to an extracted version of the firmware on disk. One of the benefits of openSUSE is that it has the closed source ivtv-firmware drivers available in the NON-OSS repository. This Firmware is licensed for use only in conjunction with Hauppauge component products. More info about the license can be found in the license agreement included in the package.

Configuration Tips
Check the IVTV console output with dmesg
dmesg | egrep -i '(ivtv|tveeprom|tuner)'

Your output should look something like this example from the Hauppauge PVR500:

ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.x.x (tagged release) loading
ivtv:  Linux version: x.x.xx.x-default SMP mod_unload gcc-4.1
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: This is the first unit of a PVR500
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: Encoder revision: 0x02060039

The lspci command can give you more information about your card and tuner
lspci | grep -i itv
Your output should look something like this example from the Hauppauge PVR500:
03:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
03:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)

Check if the firmware is installed in the correct location
ls /lib/firmware -l
  • license-end-user.txt
  • license-oemihvisv.txt
  • v4l-cx2341x-dec.fw
  • v4l-cx2341x-enc.fw
  • v4l-cx2341x-init.mpg
  • v4l-cx25840.fw
  • v4l-pvrusb2-24xxx-01.fw
  • v4l-pvrusb2-29xxx-01.fw

Check what version of ivtv is installed

To check what version is installed, issue the command:

rpm -qa | grep ivtv

Your output should look something like:


The IVTV configuration is maintained by YaST and it is not recommended to edit the file directly. To see the configuration of the device
cat /etc/modprobe.d/tv

Your output should look something like this example from the Hauppauge PVR500:

alias char-major-81 videodev
options i2c-algo-bit bit_test=1
# YaST configured TV card
# Uog3.chCB1CyIbw9:WinTV PVR 150
alias char-major-81-0 ivtv
# YaST configured TV card
# ZvjX.sZc4ePByvkF:WinTV PVR 150
alias char-major-81-1 ivtv
alias char-major-81-2 off
alias char-major-81-3 off

Reload the ivtv module manually
rmmod ivtv
modprobe ivtv

Check if the video devices are available to the system
ls /dev/vi* -l

Your output should look something like this example from the (dual tuner) Hauppauge PVR500:

lrwxrwxrwx 1 root root 6 Dec 29 06:27 /dev/video -> video0
crw-rw----+ 1 root video 81, 0 Dec 29 06:27 /dev/video0
crw-rw----+ 1 root video 81, 1 Dec 29 06:27 /dev/video1
crw-rw----+ 1 root video 81, 24 Dec 29 06:27 /dev/video24
crw-rw----+ 1 root video 81, 25 Dec 29 06:27 /dev/video25
crw-rw----+ 1 root video 81, 32 Dec 29 06:27 /dev/video32
crw-rw----+ 1 root video 81, 33 Dec 29 06:27 /dev/video33

The above is for a PVR-500. Here is what each device corresponds to in this case:

Tuner unit #1: - For your info

/dev/video0 – The encoding capture device (Read-only)
/dev/video24 – The raw audio capture device (Read-only)
/dev/video32 – The raw video capture device (Read-only)
/dev/radio – The radio tuner device
/dev/vbi0 – The "vertical blank interval" (Teletext) capture device

Tuner unit #2: - For your info

/dev/video1 – The encoding capture device (Read-only)
/dev/video25 – The raw audio capture device (Read-only)
/dev/video33 – The raw video capture device (Read-only)
/dev/vbi1 – The "vertical blank interval" (Teletext) capture device

Check (and update) the hardware specific section on this page and the dedicated mythTV wiki pages

Wikipage.png - Video capure cards on the mythTV wiki page

Hauppauge PVR-150
Hauppauge PVR-150

Wikipage.png - Hauppauge_PVR-150, single tuner mythTV wiki page

Wikipage.png - Hauppauge_PVR-150, with IR Blaster support mythTV wiki page

Hauppauge PVR-250
Hauppauge PVR-250

Wikipage.png - Hauppauge_PVR-250 mythTV wiki page

Hauppauge PVR-350
Hauppauge PVR-350

Wikipage.png - Hauppauge_PVR-350, single tuner and TV-out mythTV wiki page

Hauppauge PVR-500
Hauppauge PVR-500

Wikipage.png - Hauppauge_PVR-500, dual tuner mythTV wiki page

If you are lost; here are some screenshots of mythtv-setup for a PVR-500 in the Netherlands.

Channels and frequencies

You can fill the channel table and frequencies from mythtv-setup

Since there must be more MythTV users in your area, this could be a good moment to make some new friends. Chances are that someone already did this and exported this channel information and published it on the web. Check the country specific information on the mythtv wiki or some local mythtv sites and with some luck you can import a channel file to your database.

Country specific information Generate mythTV Channels for the Netherlands, place holder, place holder,

Information.png Tip: For some countries, providers, areas there are channel.sql files available that hold all channels and frequencies for your area and that can be imported directly into the mySQL database. See the XMLTV page for more details about your country specific information.

<debug>Show the channel table from the mythtv database from the commandline</debug>
mysql -uuser -ppassword mythconverg -e 'SELECT name, freqid, chanid, channum, xmltvid  FROM `channel`  WHERE sourceid = "1"  ';

Electronic Program Guide (EPG)

The most difficult part of installing/configuring MythTV is getting the data, name and frequency of all the channels in the database. One of the reasons is; it's country and region specific information and it also depends on your type of TV signal. Most analogue mythTV systems need to grab information from some local website and import it into the mythTV datastore. For this to work, a technology called grabbers is used. A grabber, 'grabs' EPG information from a website and transforms the data to XML format. Most DVB-C infrastructures send EPG information in streams over the cable so other techniques are used.

The best advise we can give you, is to search for country/provider specific information because for EPG there is no 'one size fits all'.

Country specific information Netherlands, North America data direct, North America zap2it, UK, more


mythfilldatabase is nothing more that a nice wrapper around your EPG handler. Normally mythfilldatabase is run automatically by mythbackend every 24 hours. It uses your EPG handler (grabber) as defined in mythtv-setup.


Most grabbers use XMLTV to get the EPG data into the database. Make sure you install the XMLTV software packages. XMLTV ships with a set of standard grabbers per country. Although these might work - again, search for country specific information - better grabbers may be around.

The program guide in mythTV is a listing of TV shows that you receive over the network.

XMLTV is a set of utilities to transfer and store EPG (Electronic Program Guide) in a XML format for various countries.

It's good to understand the following components before you begin:

  • XMLTV Grabber = country specific module to grab EPG (Electronic Program Guide) info from a source and translates it to XML format.
  • XMLTV ID = Value that exists in the XMLTV data and in the Channel table. It's the link/mapping to get the information on the correct channel.
  • CHANNELS = Your TV channels, with their channel number and frequencies as defined in mythtv-setup
  • CHANNEL_ICONS = Bitmaps that are displayed by mythfrontend as a graphical representation of the channel. (example: CNN logo)
  • mythfilldatabase = An mythTV application that uses the XMLTV grabber that you defined in mythtv-setup and stores the information in the MySQL database.

The most essential data in your database is the channel mapping: The mythconverg_channel table in the database links/maps the following information channel number frequency name of the channel XMLTV number Without this information the EPG (Electronic Program Guide) can not work.

Install XMLTV from pacman

For most European countries you need XMLTV and a grabber.

The first thing you should do to get listings into the database is to set up your channels. In mythtv-setup, after you have set up your card, you can configure a video source based on your geographic location. The video source config page has a field for "grabber"; select your country there and mythTV will be ready to run a program called "mythfilldatabase" that will use XMLTV and tv_grab_XX, where XX is your country specific method. So, XMLTV works by running a custom grabber for your country. This grabber collects guide data from the sources appropriate to your country.

Country specific information Netherlands, North America, UK, more

Different countries and providers have different ways of configuring XMLTV.

Wikipage.png - XMLTV mythTV wiki page

to see specifics for your country about XMLTV and the EPG:


1.) Understand what grabber technology you should use and are currently trying to configure - read !

2.) Location of the grabber config file and current user. The grabber for your country may have it's settings stored in the users home directory (~./.xmltv or ~./.mythtv). Normally your should run mythfilldatabase as user and not as root!!

3.) Check the XML-TV-ID in database and grabber

Have a quick look in the database This will show channel numbers, xmltvid etc.

mysql -u<username> -p<password> mythconverg -e 'SELECT name, freqid, chanid, channum, xmltvid  FROM `channel`  WHERE sourceid = "1"  ';

The XMLTVID should match the ID's in your grabbers configuration file. (if exists for your country)

Example bash script to check the EPG days in the database

 SQL='SELECT TO_DAYS(max(endtime)) - TO_DAYS(now()) FROM program;'
 EPG_DB_DAYS=`mysql -u<<your userid>> -p<<your password>> --skip-column-names -B -D mythconverg --execute "$SQL"`
 if [ $EPG_DB_DAYS -lt 8 ]; # Check for 8 days of EPG
   # run mythfilldatabase 
   echo "Need to update the EPG - run mythfilldatabase"
   # EPG seems fine
   echo "$EPG_DB_DAYS days in your database."

Use and configure mythTV clients (frontends)

Integrated LCD or VFD panel (LCDProc)

LCDproc is used by mythTV
Mythfrontend (the integrated mythlcdserver) can control a LCD (Liquid Crystal Display) or a VFD (Vacuum Fluorescent Display) panel through the LCDproc API. LCDproc is a small piece of software that displays real-time system information from your Linux box on a LCD/VFD.

  • Install LCDproc and configure your device
LCDproc is not part of the openSUSE 10.3 distribution, but a rpm is available:

Download.png - download LCDproc rpm from


LCDproc for openSUSE
  • Configure mythfrontend to use the LCD/VCD
The mythlcdserver is started automatically when configured in mythfrontend.
You can find the setup options in Utilities/Setup->Setup->Appearance->LCD device display Check the Enable LCD device.


Here are some tips that can help you find the best information to configure your hardware specific device information.

Check (and update) the hardware specific section on the mythTV wiki

Wikipage.png - LCDproc mythTV wiki page

Wikipage.png - iMON (Silverstone, Cooler Master) mythTV wiki page

Wikipage.png - Futaba (MSI Media Live, Hiper HMC-2K53A) mythTV wiki page

The most important files of the LCDproc package
  • /usr/sbin/LCDd - executable can be started with option -c /etc/LCDd.conf
  • /etc/LCDd.conf - configuration file

List-add.png Todo: Don't think LCDproc comes with a startup/init script. Please describe howto create a init script from the skeleton for the newbies

The LCDproc deamon (?LCDd?) is not started automatically by default after a reboot.
As root start 'yast2 runlevel', select (?LCDd>) and make sure it's started at boot time.}}


Wikipage.png - LCDproc mythTV wiki page

Wikipage.png - IMON (Silverstone Technology, Cooler Master, Thermaltake Technology, Zalman Tech, 3R System) mythTV wiki page

Wikipage.png - Futaba (MSI Media Live, Hiper HMC-2K53A) mythTV wiki page

Wikipage.png - mythlcdserver mythTV wiki page

Remote Control (LIRC)

mythTV uses LIRC for the iMON_PAD
The configuration of your remote control can be one of the most time consuming aspects of your mythTV setup. The remote controller itself can never be detected by the system so it requires some manual work. If your remote control device is not supported, it's required to learn the system about your device and define it's behavior.

LIRC is the package that allows you to decode and send infra-red signals of many commonly used remote controls. openSUSE 11.1 ships with LIRC 0.8.4. To use LIRC, you need a configuration file for your remote control. A list of supported remote control is available on

If you can't find a configuration file for your remote control on the lirc page, it does not mean that your remote control is not supported but there is no configuration file for it yet. You don't have to be a developer to create a configuration file by using irxevent and mode2. More info about these LIRC programs can be found on

If you have created a new configuration file for a remote control, please send it to the LIRC team.

  • /etc/sysconfig/lirc = Hardware config file

You must install the lirc kernel modules package that corresponds to your installed kernel.

sudo zypper in lirc-kmp-default

Information.png Tip: You can check the kernel version from the command line with 'uname'. The word 'default' in the below example means a default kernel (in most cases the only other possibility is 'bigsmp').

# uname -r

You must edit this file so that lirc knows which device to use. For example, if you have a PVR-150 make the following changes:


See PVR150 Remote for more information.

Information.png Tip: If your lirc kernel module is working and detects the card properly you will see the device /dev/lirc appear when lirc is started. If that device does not appear check /var/log/messages and dmesg for clues. Also, it has been reported that a full cold boot is sometimes required to bring the PVR150's IR back to life even going so far as to remove the card from the motherboard for a few moments. Be sure to try this before taking any other drastic steps (such as compiling lirc from source).

  • /etc/lircd.conf = LIRC remote control configuration file that maps scancodes to logic functions (like value to play, poweroff, pause etc.)
  • lircrc = Application specific mapping of the remote functions (play, poweroff etc) to the app specific functions for mythTV, mplayer and or Xine
Every application that you want to control with your remote (and has support for remote control) needs it's own lircrc configuration file.
The lircrc maps the keynames defined in lircd.conf (example: poweroff) to an application specific function (example: exit application). Make sure that the key names in lircrc should correspond with the same button names in lircd.conf.

  • mythTV = /home/user/.mythtv/lircrc
  • xine = /home/user/.xine/lircrc (TODO: check if this is correct)
  • mplayer = /home/user/lircrc

Information.png Tip: Instead of creating an individual lircrc file for each application, you can create one master file and put symbolic links to this in the appropriate places. The command for creating a lircrc file in your /home/userid/.mythtv directory, symbolically linked to lircrc in your home directory, follows:

ln -s ~/.mythtv/lircrc ~/lircrc


The LIRC deamon (lircd) is not started automatically by default after a reboot.

As root start 'yast2 runlevel', select lircd and make sure it's started at boot time.

The lirc deamon does not start without a configuration file. Please make sure your create the configuration file before you start lircd.

  • Copy/rename the file to /etc/lirc.conf.
  • Start /etc/init.d/lirc deamon and try irw, irxevent, mode2
  • TODO: howto get a sample ~/.mythtv/lircrc - google for a lircrc for your remote - try the mythtv remote control wiki pages
  • there can be only one, make sure you have 1 lircrc file for mythtv. Create links to it.
  • the ~/.mythtv directory is user specific and created in the users home directory when he starts mythfrontend for the first time and ask for an ip address of the backend. If you don't have a ~/.mythtv directory, start mythfrontend first. The directory is hidden, try ls -al.

example: /etc/lircd.conf

Play      0x00007be9

The lircrc is application specific, here your define that the 'Play' key is the same as function 'P' (P is by default Play in mythfrontend)

example: ~/.mythtv/lircrc

    prog   = mythtv
    button = Play
    config = P


Webpage.png - Official LIRC page

Wikipage.png - LIRC mythTV wiki page


Wikipage.png - ATI Remote Wonder mythTV wiki page

Wikipage.png - Hauppauge WinTV Nova T500 Remote Control mythTV wiki page

Wikipage.png - iMON mythTV wiki page

Wikipage.png - Logitech Harmony 880 mythTV wiki page

Wikipage.png - Microsoft MCE Remote mythTV wiki page

Wikipage.png - more Remote Control mythTV wiki page

Audio setup

For PulseAudio setup, see Configuring Digital Sound#PulseAudio

TV Output (Proprietary Driver)

You can use several different types of connections to connect your mythTV frontend PC to a TV. The S-Video cable works well with most standard TVs. The picture below explains the different types of connections that can be used to connect yout TV.

The type of output your PC's video card can do, and the type of inputs your TV can handle are primarily what dictates what you should use to connect them. From highest- to lowest-quality, the order of consideration is: HDMI, DVI (both of which are digital), VGA, Component, S-Video and finally Composite (all of the rest are analog).


HDMI digital
DVI digital
VGA analog
Component analog
S-Video analog
Composite analog

Install the ATI driver with 1-Click Install
ATI driver from the opensuse-community

Manual download and install the driver

Download.png - Download the latest driver from ATI


Wikipage.png - AtiProprietaryDriver mythTV wiki page

Webpage.png - openSUSE AMD/ATI page

Install the NVIDIA driver with 1-Click Install
If you have a new NVIDIA cards
If you have a legacy NVIDIA cards

List of Legacy NVIDIA cards

Manual download and install the driver

Download.png - Download the latest driver from NVIDIA


Wikipage.png - NVidiaProprietaryDriver mythTV wiki page

Webpage.png - openSUSE NVIDIA page

Hauppauge PVR-350
Hauppauge PVR-350

Wikipage.png - Hauppauge_PVR-350, single tuner and TV-out mythTV wiki page

Web frontend (mythweb)

MythWeb provides a frontend for scheduling and managing recordings on your mythTV system from a web browser located on another machine. Provided the security is set up correctly on your MythBox you can access your machine from anywhere on the internet, or even your mobile phone as long as you have a compatible browser. Of course it is just as useful to browse your myth content from your laptop while your partner is watching their favorite programme.

Make sure the following packages are installed

yast2-http-server, apache2, apache2-mod-php5

You can quickly check if the package is already installed with the following command

rpm -qa | grep apache

Activate the required server module for the Apache HTTP server

The Rewrite Server Module provides a rule-based rewriting engine to rewrite requested URLs on the fly. By default it's turned off and you need to turn it on. The Environment Server Module modifies the environment passed to CGI scripts and SSI pages

Start YaST and goto the HTTP server menu (commandline: yast2 http-server) follow the menu's by next,next,next,next and click the HTTP Server Expert Configuration, here you see a tab with 'Server Modules'

The Rewrite module is disabled by default - Enable this option

The Env module is disabled by default - Enable this option

Securing mythweb

If you plan to open your mythweb to the internet, you should seriously consider securing it. That and more information can be found here. Follow the section specifically for openSUSE here

Security Example for mythweb

To secure your Mythweb you can configure the access to it. For example you can set up 'limit access'. It will ask you for an username and password if you try to access the mythweb page. It's very simple:

First make a file where you store the username and password for a user.

htpasswd2 -c /etc/apache2/htpasswd <username>

Type in a password (2x)

Then just add the lines below in your http.conf or default-server.conf

<Directory "/srv/www/htdocs/mythweb">
 AuthType Basic
 AuthName "Mythweb Login"
 AuthUserFile /etc/apache2/htpasswd
 Require user <username>

Restart apache

rcapache2 restart

If you now access the Mythweb (http://ip number/mythweb/) it will ask you for an username and password.

Information.png Tip: You can access your MythWeb remotely if you know your IP address. However, if you are a DHCP client, your IP will probably change. To resolve the issue of having an IP address that is constantly changing, you can sign up for an account with a dynamic DNS site (such as and create a unique unchanging hostname that can be forwarded to your IP address - even if it changes.

Making it an appliance

Start all required services remove the services crom cron and database maintencance tricks acpi wakeup mythfilldatabase scheduled

Wakeup using the bios

Switching computers that do not need to run 24 by 7 on and off as required can cut your power consumption. There are different methods of programming a wakeup time under Linux without needing to set the time manually in the computer’s BIOS.

NVRAM wakeup uses the BIOS settings stored in non-volatile RAM (NVRAM). The nvram kernel module allows Linux to access a maximum of 128 bytes of non-volatile memory. To get this to work, you need to compile the nvram kernel module. Basically nvram is directly poking into your bios.

ACPI has a (limited) standard interface to change the value in the bios.

The kernel transfers the time directly to your computer’s RTC (real time clock), but not the date. This leads to the computer waking up at the same time every day, and not just on the given date. The problem is that there is a more-orless standardized method of transferring the time to the RTC, but no such standard for the wakeup date.

ACPI RTC Alarm works with openSUSE 11.1 - more information on the following page

Wikipage.png - ACPI Wakeup mythTV wiki page

Document.png - Wakeup call

Remove KDE or GNOME

autorun mythfrontend or automatically start mythfrontend and not start the full gnome The mythtv rpm's create an xsession configuration for you, so that you can select mythtv as your session from gdm, this way gnome is not started (faster and saver you some memory) You can select the session from the initial login screen (logout and select another session)

gdm sessions are stored on the following locations:

  • Directory for xsession configuration files = /usr/share/xsessions
  • ~/.dmrc = stored the xsession for the current user

If you want to add an xsession for mythwelcome;

  • Add a xsession by copying cp /usr/share/xsessions/mythtv.desktop /usr/share/xsessions/mythwelcm.desktop
  • Edit /usr/share/xsessions/mythwelcm.desktop so that it executes /usr/bin/mythwelcome and the name = mythwelcm
  • Now edit ~/.dmrc and change your session to mythwelcm

Result, gnome is not started but mythwelcome is started

Tips and tricks

Working with phpMyAdmin

Install phpMyAdmin from the build server.

directory = /srv/www/htdocs/phpMyAdmin

http://ip address/phpMyAdmin

I don't need a password on phpMyAdmin

cd /srv/www/htdocs/phpMyAdmin
cp ./ ./
edit ./

Make the following changes:

/* Authentication type */
$cfg['Servers'][$i]['auth_type'] = 'http';

/* User for advanced features */

$cfg['Servers'][$i]['controluser'] = ;
$cfg['Servers'][$i]['controlpass'] = ;

Upgrading from 10.2 with Packman

Over the weekend I managed to upgrade-in-place my existing MythTV installation from OpenSUSE 10.2 to 11. I did not nuke my root partition and just do a new install, I upgraded my / partition. It went rather well, but there were a few speed bumps. First, the speed-bumps:

  • The Lirc install still doesn't support the IR Blaster on a Hauppauge PVR150.
  • Due to the number of packages being thrown around, several reboots are needed for things to settle down.
  • 11 sets up XGL/Compiz by default, which may have some affect on how MythTV renders video. This will have to be diddled after the install is completed, and will probably depend on hardware. This guide doesn't cover that.

And now, the process I followed.

  1. Back up everything you need to back up. This makes recovery a lot easier if things go badly.
  2. Boot to the installation media and perform the upgrade.
    1. Pay attention to the packages and patterns you are installing. Go through them and verify everything you want is checked. I didn't have any troubles with this, but this is an area where things can go wrong.
    2. During the upgrade process it will remove all packages not part of the OS, and not flagged as locked. Since the Packman MythTV packages show up as locked, they'll still be around. We'll fix this later.
  3. Log in as Root to your console.
  4. Run Online Update to get the latest openSUSE patches, which includes a kernel already and will require a reboot.
  5. Log in again, launch YaST, and run Software Repositories
  6. Select Community Repositories (at the top of the list)
  7. Add Packman and any others you might need, like the NVidia repo.
  8. Exit Software Repositories, and launch Software Management
  9. Search for "myth". Note the MythTV packages you have installed, and explicitly remove them. These are the 10.2 packages and will not work with 11.0. Especially since most of their multimedia dependencies were removed as part of the OS upgrade.
  10. Once that is completed, go back into Software Management and reinstall the MythTV packages you removed in the previous step.
  11. It will give a big list of dependencies required by the MythTV packages; OK their install, and let it go.
  12. Once everything is installed, reboot to settle things down.
  13. By this point things should be in a good state. From a terminal window, launch "mythtvsetup" and see if it segfaults. If it runs correctly, MythTV as a whole should run correctly. If it does segfault, then this guide has failed you and I apologize.
  14. If you are using a Hauppauge PVR150 and its IR Blaster, you will have to compile a "lirc_pvr150" module from source. You already had to do this with 10.2, so the process should be familiar. The update to 11.0 doesn't require any config file changes.
  15. Go into YaST and launch System Services. Set "mythtvbackend" (and "lirc" if you use an IR remote) to run automatically, if that's what you do.
  16. Log in as your MythTV user and make any Gnome/KDE/whatever changes you need. 11.0 includes significant updates to the desktop from 10.2. In my case I just nuked my profile and began anew. Your mileage may vary.
  17. A final reboot to make sure everything is working as planned.

The above worked for me, and should be pretty solid for 10.2 to 11.0 while using the Packman MythTV packages.

Using Firefox as integrated Mythbrowser

In Opensuse 11 just changing the configuration setting in Mythbrowser to /usr/lib/firefox does not work any more. To make it work create a file in the Mythtv home directory i.e. /home/mythtv/

The script should contain something like:

shift #shift down the arguments that were passed so we can access the url
/usr/bin/firefox $9 --fullscreen  #what was argument 11 (the url) becomes 9
echo $* #show all the passed arguments

Make the file executable

chmod +x /home/mythtv/

To finalize change the default browser Utilites/Setup->Setup->Info Center Settings->Web Settings->browser box. to /home/mythtv/

User Experiences

Moosy did several boxes based on openSUSE 11.0 during 2008.

As of Mythtv 0.21 version 27 packman got some support for H.264 LATM/AAC required for Norway, New Zealand and possibly some Hungarian DVB-T users. Basic playback works. This is based on a patch from Paul Kendall.

openSUSE 11.2RC1, mythTV0.22RC1, vdpau

Using eVGA 8400GS PCI on a low end HP server (ML110G5 E2160), AverMedia A828 (0.28alpha driver fixed by AverMedia tech support). Note serious bugs still in openSUSE YaST automatic repair - auto repair disks/partitions/raid with extreme caution. Prefer to fix manually. Bugs reported/acknowledged in openSUSE bugzilla.

Getting bugs out of mysql install was a pain. Getting an install clean enough to run mysql_secure_installation seems the least painful route (See also config validation script).

mythTV0.22RC1 has built in vdpau support. No problems with default compile. ndpau needs to be manually activated by frontend TV setting profile: mythfrontend>Utiliites/Setup>Setup>TV Settings>Playback>...Playback Profiles(3/9)>Current Profile>AddNew'vdpau'>AddNewEntry>Decoder:NVidiaVDPAU; Primary Deinterlacer:Advanced2x(hw)

Old mythTV theme looks and works fine. (New default theme still in the works.) Everything seems to work so far with 1080 source on 1280x720display. Not bad for a cheap media server. Still waiting for 1080 HDTV display to test it on.

Should be awesome when 11.2 is final and mythTV0.22 is final and setup can be automated.

--Blouis79 23:00, 23 October 2009 (UTC)