|
|
| (47 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | {| cellspacing=0 cellpadding=2 border=0
| + | #redirect [[Opensuse_11.0_-_11.2]] |
| − | |width=22|{{Click || image=Go-up.png | link=Operating_system#openSUSE | width=22px | height=22px}}
| |
| − | |[[Operating_system#openSUSE|Other openSUSE version]]
| |
| − | |}
| |
| − | | |
| − | = Introduction =
| |
| − | | |
| − | | |
| − | {{SUSE_head|Benefits of using openSUSE 11.0 for mythTV}}
| |
| − | * Best hardware support available today with kernel 2.6.25 - compared to openSUSE 10.3 (kernel 2.6.22) - [http://kernelnewbies.org/Linux_2_6_23 what's new in 2.6.23], [http://kernelnewbies.org/Linux_2_6_24 what's new in 2.6.24], [http://kernelnewbies.org/Linux8_2_6_25 what's new in 2.6.25]
| |
| − | * Software installation (package management) is improved in openSUSE 11.0 and super fast. (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 [http://packman.links2linux.org/package/mythtv pacman]
| |
| − | ** '''restricted formats''' (proprietary, patented formats) like MP3, Codecs, encrypted DVD support etc. are available with '''1-click install''' on [http://opensuse-community.org/Restricted_Formats/11.0 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 [http://software.opensuse.org/search software.opensuse.org] (e.g. lcd support)
| |
| − | * New and super fast installation, completing in roughly just 35 minutes (including mythTV software)
| |
| − | * Improved ACPI functionality for suspend and wake-up to reduce power consumption
| |
| − | * Good openSUSE, mythTV documentation and a friendly community ;-)
| |
| − | read [http://en.opensuse.org/OpenSUSE_11.0 more]
| |
| − | | |
| − | http://gk2.sk/countdown/full.png
| |
| − | | |
| − | | |
| − | [[Image:Myth_suse.jpg|right|275px|]]
| |
| − | | |
| − | | |
| − | {{SUSE_head|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 [http://opensuse.org openSUSE project] is a community program sponsored by [http://www.novell.com 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.
| |
| − | [[Image:Functional_diagram.png|right|280px|]]
| |
| − | 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.
| |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | {{Webpage|www.novell.com/documentation/suse.html|openSUSE official documentation}}
| |
| − | | |
| − | {{Webpage|www.novell.com/products/opensuse/sysreqs.html|System requirements for openSUSE}}
| |
| − | | |
| − | {{Webpage|www.novell.com/products/linuxpackages/opensuse/index.html|All packages included in openSUSE}}
| |
| − | | |
| − | {{Wikipage|Executive_Overview|mythTV Executive_Overview}}
| |
| − | 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."''
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|Hardware considerations}}
| |
| − | Installing mythTV all starts with good hardware. The first requirement is a machine capable of running [http://opensuse.org 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 http://www.silentpcreview.com/ if you build a machine for your living room, in order to get advice on low power-consumption, low noise setups.
| |
| − | | |
| − | {{Wikipage|Bare_Bones_System|Bare_Bones_System}}
| |
| − | {{Wikipage|Cases|Cases}}
| |
| − | [http://www.mythtv.org/wiki/index.php/Category:Hardware more]
| |
| − | | |
| − | {{SUSE_head|Join the community and get some help}}
| |
| − | ;Subscribe to the mythTV users mailing list
| |
| − | mythTV user mailing list [http://www.mythtv.org/mailman/listinfo/mythtv-users www.mythtv.org/mailman/listinfo/mythtv-users]
| |
| − | | |
| − | mythTV user mailing list archive [http://www.gossamer-threads.com/lists/mythtv/users/ www.gossamer-threads.com/lists/mythtv/users/]
| |
| − | | |
| − | ;Chat with other mythTV users
| |
| − | IRC
| |
| − | irc.freenode.net #mythtv-users
| |
| − | | |
| − | =Initial system setup and considerations =
| |
| − | | |
| − | {{SUSE_head|openSUSE 11.0 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|software.opensuse.org|Download openSUSE 11.0}}
| |
| − | | |
| − | {{Webpage|en.opensuse.org/Buy_openSUSE|Buy online (including 90 days support, a real manual and a fancy DVD)}}
| |
| − | | |
| − | | |
| − | {{SUSE_head|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.
| |
| − | | |
| − | | |
| − | {{SUSE_head|FILE SYSTEM RECOMMENDATIONS}}
| |
| − | 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.
| |
| − | | |
| − | | |
| − | {{SUSE_head|OTHER RECOMMENDATIONS}}
| |
| − | Make sure you understand what hardware you have - especially if you have issues an need to Google.
| |
| − | | |
| − | <code>lspci -v</code> and <code>lsusb</code> and <code>hwinfo</code>
| |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | | |
| − | {{Wikipage|File_storage#File_systems|File Systems}}
| |
| − | {{Webpage|www.novell.com/documentation/sles10/sles_admin|SUSE Linux Enterprise documentation about file systems}}
| |
| − | | |
| − | = Install mythTV software on openSUSE =
| |
| − | [[Image:Package.png|24px]]{{SUSE_head|INSTALL, THE EASY WAY }} | |
| − | ;STEP (1 of 4)
| |
| − | Add the required software repositories
| |
| − | {{Tip box|Describe howto add/check the required repositories.}}
| |
| − | | |
| − | | |
| − | ;STEP (2 of 4)
| |
| − | This will install the Restricted Multimedia Formats ranging from MP3 Codecs to playing Encrypted DVDs
| |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_10.3 | width=146px | height=52px}}
| |
| − | |[http://opensuse-community.org/codecs-kde.ymp Install Restricted Multimedia Formats for KDE users]
| |
| − | |}
| |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_10.3 | width=146px | height=52px}}
| |
| − | |[http://opensuse-community.org/codecs-gnome.ymp Install Restricted Multimedia Formats for GNOME user]
| |
| − | |}
| |
| − | | |
| − | | |
| − | ;STEP (3 of 4)
| |
| − | [[Image:Package.png|24px]]
| |
| − | Install the prerequisite packages with zypper by copying and pasting the following into a terminal (as root)
| |
| − | | |
| − | {{Mythtv_version|mythTV 0.20 or openSUSE 10.3}}
| |
| − | | |
| − | <code>
| |
| − | '''sudo zypper in''' alsa audit-libs dvb flac gcc ivtv ivtv-firmware kernel-source libao libdvdread3
| |
| − | '''sudo zypper in''' libid3tag lirc mjpegtools mysql php5 python xine-ui xmms fame libcdaudio libfame lame MPlayer
| |
| − | '''sudo zypper in''' phpMyAdmin pvm transcode xvid apache2 yast2-http-server apache2-mod_php5
| |
| − | </code>
| |
| − | | |
| − | | |
| − | | |
| − | ;STEP (4 of 4)
| |
| − | This will install the mythTV packages for both frontend and backend from the packman repository.
| |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_10.3 | width=146px | height=52px}}
| |
| − | |[http://packman.links2linux.org/install/mythtv Install mythTV from packman]
| |
| − | |}
| |
| − | | |
| − | | |
| − | {{Incomplete}}
| |
| − | | |
| − | = Configure openSUSE =
| |
| − | == Adding a mythtv user ==
| |
| − | Create a mythtv user that you are gonna use to run the software.
| |
| − | sudo useradd mythtv -mG users,video,audio,cdrom
| |
| − | sudo passwd mythtv
| |
| − | | |
| − | {{SUSE_head|AUTOLOGIN FOR THE USER}}
| |
| − | YaST - user management - expert options - login settings - check autlogin
| |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | [http://www.novell.com/documentation/opensuse103/opensuse103_startup/data/cha_y2_userman.html openSUSE 10.3 Manual - Managing users with YaST]
| |
| − | | |
| − | == Synchronize your system clock (NTP) ==
| |
| − | [[Image:Time.png||right]]
| |
| − | To get the correct start and stop times for programming, it's ''very'' important to setup NTP (Network Time Protocol).
| |
| − | NTP is a protocol designed to synchronize the clocks of computers over a network.
| |
| − | | |
| − | | |
| − | 1. Configure the NTP Client
| |
| − | YaST -> Network Services -> NTP Configuration
| |
| − | 2. Ignore the warning when selecting Automatically start, there is no significant delay.
| |
| − | NTP daemon -> During Boot -> Check "Use Random Servers from pool.ntp.org"
| |
| − | Click Advanced Configuration -> Security Settings -> Check "Open Port in Firewall" -> Finish
| |
| − | | |
| − | == Disable services ==
| |
| − | Disable some services you don't need
| |
| − | | |
| − | ;Firewall
| |
| − | A basic MythTV box should not have any problems running with the firewall turned on however you will probably save yourself a lot of headaches if you disable it completely. This is especially recommended for new users. If you do need to enable the firewall, you will at the very least want to enable SSH, Secure WWW (HTTPS) and WWW (HTTP) checkboxes to enable those services.
| |
| − | | |
| − | 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 mysql.
| |
| − | | |
| − | | |
| − | ;AppArmor
| |
| − | If you're not paranoid about security, I recommend to disable AppArmor on your machine.
| |
| − | | |
| − | | |
| − | ;Disable other services you don't need
| |
| − | Beagle search engine from the control centre
| |
| − | | |
| − | == Audio setup ==
| |
| − | [[Image:Audio.png|right|30px|]]
| |
| − | Most sound cards are automatically recognized by openSUSE and do not need any specific configuration. Most of the time, everything is auto detected during the installation and usually just works.
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | {{Wikipage|Configuring_Digital_Sound_with_AC3_and_SPDIF|Configuring Digital Sound with AC3 and SPDIF}}
| |
| − | | |
| − | == Remote Control (LIRC) ==
| |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | | |
| − | [[Image:imon_pad.jpg|right|80px|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 10.3 ships with LIRC 0.8.2. To use LIRC, you need a configuration file for your remote control. A list of supported remote control is available on http://lirc.org/remotes/
| |
| − | | |
| − | If you can't find a configuration file for your remote control on the [http://lirc.org/remotes 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 [http://lirc.org/html/irxevent.html irxevent] and [http://lirc.org/html/mode2.html mode2]. More info about these LIRC programs can be found on http://lirc.org/html/programs.html
| |
| − | | |
| − | If you have created a new configuration file for a remote control, please send it to the LIRC team.
| |
| − | | |
| − | | |
| − | {{SUSE_head|REMOTE CONTROL CONFIGURATION FILES}}
| |
| − | */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
| |
| − | | |
| − | {{Tip box|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
| |
| − | 2.6.22.13-0.3-default}}
| |
| − | | |
| − | 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:
| |
| − | | |
| − | LIRCD_DRIVER="default"
| |
| − | LIRCD_DEVICE="/dev/lirc"
| |
| − | LIRC_MODULE=lirc_i2c
| |
| − | See [http://www.mythtv.org/wiki/index.php/PVR150_Remote PVR150 Remote] for more information.
| |
| − | | |
| − | {{Tip box|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.
| |
| − | | |
| − | | |
| − | {{SUSE_head|APPS AND THEIR lircrc CONFIGURATION}}
| |
| − | *mythTV = /home/user/.mythtv/lircrc
| |
| − | | |
| − | *xine = /home/user/.xine/lircrc (TODO: check if this is correct)
| |
| − | | |
| − | *mplayer = /home/user/lircrc
| |
| − | | |
| − | | |
| − | {{Tip box|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}}
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|NOTE}}
| |
| − | 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.''
| |
| − | | |
| − | | |
| − | {{SUSE_head|CONFIGURATION TIPS}}
| |
| − | * Visit the [http://lirc.sourceforge.net/remotes/ http://lirc.sourceforge.net/remotes] website and download a setup file for your remote.
| |
| − | | |
| − | * 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
| |
| − | begin
| |
| − | prog = mythtv
| |
| − | button = Play
| |
| − | config = P
| |
| − | end
| |
| − |
| |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | {{Webpage|lirc.org|Official LIRC page}}
| |
| − | {{Wikipage|LIRC|LIRC}}
| |
| − | | |
| − | | |
| − | {{SUSE_head|DEVICE SPECIFIC}}
| |
| − | {{Wikipage|ATI_Remote_Wonder#openSUSE_10.2|ATI Remote Wonder}}
| |
| − | {{Wikipage|Hauppauge_WinTV_Nova-T_500_PCI|Hauppauge WinTV Nova T500 Remote Control}}
| |
| − | {{Wikipage|Imon|iMON}}
| |
| − | {{Wikipage|Logitech_Harmony_880_remote|Logitech Harmony 880}}
| |
| − | {{Wikipage|MCE_Remote|Microsoft MCE Remote}}
| |
| − | {{Wikipage|Remote_Controls|more Remote Control}}
| |
| − | | |
| − | == Integrated LCD or VFD panel (LCDProc) ==
| |
| − | [[Image:LCDproc.jpg|right|135px|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. [http://lcdproc.omnipotent.net/ LCDproc] is a small piece of software that displays real-time system information from your Linux box on a LCD/VFD.
| |
| − | | |
| − | | |
| − | {{SUSE_head|STEPS}}
| |
| − | * Install LCDproc and configure your device
| |
| − | :[http://lcdproc.omnipotent.net/ LCDproc] is not part of the openSUSE distribution, but a rpm is available:
| |
| − | :{{Download|software.opensuse.org/download/LCD/|download LCDproc rpm from opensuse.org}}
| |
| − | | |
| − | or
| |
| − | | |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_11.0 | width=146px | height=52px}}
| |
| − | |[http://software.opensuse.org/search?baseproject=openSUSE%3A11.0&p=1&q=lcdproc LCDproc for openSUSE 11.0]
| |
| − | |}
| |
| − | * 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.
| |
| − | | |
| − | | |
| − | {{SUSE_head|TROUBLESHOOT/CONFIGURATION TIPS }}
| |
| − | Here are some tips that can help you find the best information to configure your hardware specific device information.
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|Check (and update) the hardware specific section on the mythTV wiki}}
| |
| − | {{Wikipage|LCDproc|LCDproc}}
| |
| − | {{Wikipage|Imon|iMON (Silverstone, Cooler Master) }}
| |
| − | {{Wikipage|Futaba|Futaba (MSI Media Live, Hiper HMC-2K53A) }}
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|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
| |
| − | | |
| − | | |
| − | {{Todo_box|Don't think LCDproc comes with a startup/init script. Please describe howto create a init script from the skeleton for the newbies
| |
| − | }}
| |
| − | | |
| − | | |
| − | {{SUSE_head|NOTE}} 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.}}
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | {{Wikipage|LCDproc|LCDproc}}
| |
| − | {{Wikipage|Imon|IMON (Silverstone Technology, Cooler Master, Thermaltake Technology, Zalman Tech, 3R System)}}
| |
| − | {{Wikipage|Futaba|Futaba (MSI Media Live, Hiper HMC-2K53A)}}
| |
| − | {{Wikipage|mythlcdserver|mythlcdserver}}
| |
| − | | |
| − | == Analogue Video capture card (IVTV)==
| |
| − | [[Image:Pvr500.jpg|right|100px|]]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.
| |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | {{Webpage|www.ivtvdriver.org/index.php/Supported_hardware|a complete list of supported hardware by IVTV}}
| |
| − | {{Wikipage|Video_capture_card#Capture_Card_Matrix|capture card matrix on the mythTV wiki page}}
| |
| − | {{Webpage|ivtvdriver.org/index.php/Howto:Suse#openSUSE_10.2|ivtv wiki, primary resource}}
| |
| − | {{Webpage|en.opensuse.org/HCL/TV_Cards|openSUSE wiki, supported TV cards}}
| |
| − | | |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | 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|ivtv|ivtv, located on 10.3 media OSS}}
| |
| − | {{Download|ivt_firmware|ivt_firmware, located on 10.3 media NON_OSS}}
| |
| − | | |
| − | {{SUSE_head|FIRMWARE}}
| |
| − | 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 ===
| |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | {{SUSE_head|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
| |
| − | etc..
| |
| − | | |
| − | | |
| − | {{SUSE_head|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)
| |
| − | | |
| − | | |
| − | {{SUSE_head|Check if the firmware is installed in the correct location:}}
| |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | 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
| |
| − | | |
| − | | |
| − | {{SUSE_head|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:
| |
| − | ivtv-kmp-default-0.10.3
| |
| − | ivtv-0.10.3
| |
| − | | |
| − | | |
| − | {{SUSE_head|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
| |
| − | | |
| − | | |
| − | {{SUSE_head|Reload the ivtv module manually:}}
| |
| − | rmmod ivtv
| |
| − | modprobe ivtv
| |
| − | | |
| − | | |
| − | {{SUSE_head|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
| |
| − | | |
| − | | |
| − | {{SUSE_head|Check (and update) the hardware specific section on this page and the dedicated mythTV wiki pages}}
| |
| − | {{Wikipage|Video_capture_card|Video capure cards on the}}
| |
| − | | |
| − | === Hauppauge PVR-150 ===
| |
| − | {{SUSE_head|Hauppauge PVR-150}}
| |
| − | {{Wikipage|Hauppauge_PVR-150|Hauppauge_PVR-150, single tuner}}
| |
| − | place holder
| |
| − | | |
| − | .
| |
| − | | |
| − | === Hauppauge PVR-250 ===
| |
| − | {{SUSE_head|Hauppauge PVR-250}}
| |
| − | {{Wikipage|Hauppauge_PVR-250|Hauppauge_PVR-250}}
| |
| − | place holder
| |
| − | | |
| − | .
| |
| − | | |
| − | === Hauppauge PVR-350 ===
| |
| − | {{SUSE_head|Hauppauge PVR-350}}
| |
| − | {{Wikipage|Hauppauge_PVR-350|Hauppauge_PVR-350, single tuner and TV-out}}
| |
| − | place holder
| |
| − | | |
| − | .
| |
| − | | |
| − | === Hauppauge PVR-500 ===
| |
| − | {{SUSE_head|Hauppauge PVR-500}}
| |
| − | {{Wikipage|Hauppauge_PVR-500|Hauppauge_PVR-500, dual tuner}}
| |
| − | | |
| − | If you are lost; [http://www.flickr.com/photos/98068939@N00/tags/mythtv/ here] are some screenshots of mythtv-setup for a PVR-500 in the [[Netherlands]].
| |
| − | | |
| − | == Digital Video capture card (TV-in) ==
| |
| − | ..
| |
| − | | |
| − | === Configuration Tips ===
| |
| − | {{SUSE_head|TROUBLESHOOT/CONFIGURATION TIPS }}
| |
| − | | |
| − | {{Todo_box|generic tips for DVB users. What needs tobe checked when working with DVB, where are files stored. See the analogue section for inspiration}}
| |
| − | | |
| − | 1.) Check (and update) the hardware specific section on the mythTV wiki
| |
| − | {{Wikipage|Hauppauge_WinTV_Nova-T_500_PCI|Hauppauge_WinTV_Nova-T_500_PCI}}
| |
| − | | |
| − | | |
| − | "Unable to query frontend status"
| |
| − | | |
| − | check: http://www.suseforums.net/index.php?showtopic=40881&hl=
| |
| − | | |
| − | === Firewire ===
| |
| − | A firewire connection to your settopbox
| |
| − | | |
| − | {{Todo_box|The standard used to connect FireWire to your computer is IEEE 1394, IEC 1883.
| |
| − | All the libraw1394, libavc1394, libiec61883 are included in openSUSE.
| |
| − | | |
| − | | |
| − | What I suggest you check before you start:
| |
| − | | |
| − | 1.) What Firewall interface does your PC have. Is it supported, see
| |
| − | http://www.linux1394.org
| |
| − | | |
| − | 2.) What brand is your settopbox
| |
| − | Search on the mailinglist archive on the word in combination with firewire.
| |
| − | http://www.gossamer-threads.com/lists/mythtv/users/
| |
| − | | |
| − | 3.) Subscribe to the mailinglist and ask if people have experience with
| |
| − | the combination (your brand cablebox and your brand firewire interface
| |
| − | in the machine)
| |
| − | | |
| − | ''Please put your info here''
| |
| − | }}
| |
| − | | |
| − | | |
| − | === Hauppauge WinTV Nova-T500 PCI ===
| |
| − | | |
| − | {{SUSE_head|WinTV_Nova-T_500_PCI}}
| |
| − | {{Wikipage|Hauppauge_WinTV_Nova-T_500_PCI|Hauppauge_WinTV_Nova-T_500_PCI}}
| |
| − | place holder
| |
| − | | |
| − | .
| |
| − | | |
| − | == Connect your system to a TV ==
| |
| − | 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).
| |
| − | | |
| − | .
| |
| − | [[Image:Hdmiconnector.jpg|thumb|80px|left|HDMI digital]][[Image:Dviconnector.jpg|thumb|80px|left|DVI digital]]
| |
| − | [[Image:Vgaconnector.jpg|thumb|80px|left|VGA analog]]
| |
| − | [[Image:Componentconnector.jpg|thumb|80px|left|Component analog]][[Image:Svideoconnector.png|thumb|80px|left|S-Video analog]][[Image:Compositeconnector.jpg|thumb|80px|left|Composite analog]]
| |
| − | .
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | === ATI/AMD ===
| |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | {{SUSE_head|Install the ATI driver with 1-Click Install}}
| |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_10.3 | width=146px | height=52px}}
| |
| − | |[http://opensuse-community.org/ati.ymp ATI driver from the opensuse-community]
| |
| − | |}
| |
| − | | |
| − | | |
| − | {{SUSE_head|Manual download and install the driver}}
| |
| − | {{Download|ati.amd.com/support/driver.html|Download the latest driver from ATI}}
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | {{Wikipage|AtiProprietaryDriver|AtiProprietaryDriver}}
| |
| − | {{Webpage|en.opensuse.org/ATI|openSUSE AMD/ATI page}}
| |
| − | | |
| − | === NVIDIA ===
| |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | | |
| − | {{SUSE_head|Install the NVIDIA driver with 1-Click Install}}
| |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_10.3 | width=146px | height=52px}}
| |
| − | |[http://opensuse-community.org/nvidia.ymp If you have a new NVIDIA cards]
| |
| − | |}
| |
| − | {| cellspacing=0 cellpadding=2 border=0
| |
| − | |width=146|{{Click || image=1click.jpg | link=Opensuse_10.3 | width=146px | height=52px}}
| |
| − | |[http://opensuse-community.org/nvidia-legacy.ymp If you have a legacy NVIDIA cards]
| |
| − | |}
| |
| − | | |
| − | List of [http://en.opensuse.org/NVIDIA/Legacy Legacy NVIDIA cards]
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|Manual download and install the driver}}
| |
| − | {{Download|www.nvidia.com/object/unix.html|Download the latest driver from NVIDIA}}
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | {{Wikipage|NVidiaProprietaryDriver|NVidiaProprietaryDriver}}
| |
| − | {{Webpage|en.opensuse.org/Nvidia|openSUSE NVIDIA page}}
| |
| − | | |
| − | === Hauppauge PVR-350 ===
| |
| − | {{SUSE_head|Hauppauge PVR-350}}
| |
| − | {{Wikipage|Hauppauge_PVR-350|Hauppauge_PVR-350, single tuner and TV-out}}
| |
| − | place holder
| |
| − | | |
| − | == Wireless Keyboard ==
| |
| − | [[Image:BTC9019URF.jpg|right|110px|]]
| |
| − | Once your Myth box has been setup you wont need to use your keyboard that much. Many users will often just SSH into their machine or use a remote desktop such as VNC to get access. Of course its also nice to have a keyboard directly connected, in which case a wireless keyboard is preferred. Have a look at the section on [[Wireless Keyboards]] to see which ones work.
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | .
| |
| − | | |
| − | == Network Interfaces ==
| |
| − | The main reason you will connect your mythTV box to the internet is because MythTV gets its program guide data over the Internet.
| |
| − | If you don't happen to have ethernet cables around your house, you could use wireless (WiFi).
| |
| − | | |
| − | | |
| − | To configure your network wired or wireless card in YaST, select Network Devices>Network Card. After starting the module, YaST displays a general network configuration dialog. Choose whether to use YaST or NetworkManager to manage all your network devices. If you want to configure your network in the traditional way with the YaST, check Traditional Method with ifup and click Next. To use NetworkManager, check User Controlled with NetworkManager and click Next.
| |
| − | | |
| − | For wireless support openSUSE ships [http://en.opensuse.org/Ndiswrapper ndiswrapper], [http://en.opensuse.org/Atheros_madwifi madwifi] and [http://intellinuxwireless.org/ iwlwifi]
| |
| − | | |
| − | | |
| − | {{Mythtv_version|openSUSE 10.3}}
| |
| − | [http://www.novell.com/documentation/opensuse103/opensuse103_reference/index.html?page=/documentation/opensuse103/opensuse103_reference/data/sec_wireless_wlan.html openSUSE 10.3 Documentation - wireless LAN]
| |
| − | | |
| − | | |
| − | {{SUSE_head|TIPS FOR INSTALLATION}}
| |
| − | The chipset is what determines which driver you need, not the manufacturer of the card. Here are a number of ways to find out. All the commands should be run as root.
| |
| − | | |
| − | Try this.
| |
| − | | |
| − | hwinfo --wlan
| |
| − | | |
| − | Otherwise use this command if you have a pcmcia card or an onboard card:
| |
| − | | |
| − | lspci
| |
| − | | |
| − | Or this if you have a usb card:
| |
| − | | |
| − | lsusb
| |
| − | | |
| − | This won't output very detailed information, but it'll give you a unique hardware ID, for example 046d:c01b. Search for it with Google or another internet search engine to find out which chipset is on the device.
| |
| − | | |
| − | | |
| − | | |
| − | {{SUSE_head|ADDITIONAL INFORMATION}}
| |
| − | *[http://en.opensuse.org/Wireless_Network_Card_Installation openSUSE wiki - Wireless Network Card Installation]
| |
| − | | |
| − | *[http://en.opensuse.org/HCL/Network_Adapters_%28Wireless%29 openSUSE wiki - Wireless Network Adapters]
| |
| − | | |
| − | =User Experiences=
| |
| − | --[[User:Moosylog|The Moose]] 17:38, 27 April 2008 (UTC) Started the page
| |
| − | | |
| − | | |
| − | [[Category:OpenSUSE]]
| |
