Attachment 95713 Details for Bug 143456 – vdr-guide.xml

vdr-guide.xml

vdr-guide.xml (text/plain), 9.54 KB, created by Dimitry Bradt (RETIRED) on 2006-09-02 01:15:13 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dimitry Bradt (RETIRED)

Created: 2006-09-02 01:15:13 UTC

Size: 9.54 KB

patch

obsolete

><?xml version="1.0" encoding="UTF-8"?>
>
><!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
>
><guide link="/doc/en/vdr.xml">
><title>Gentoo Linux VDR Guide</title>
>
><author title="Author">
> <mail link="mail@ng-plasmon.de">Norman Golisz</mail>
></author>
><author title="Editor">
> <mail link="diox@swords.be">Dimitry Bradt</mail>
></author>
>
>
><abstract>
>This guide shows you how to prepare Gentoo Linux for DVB and VDR.
></abstract>
>
>
>
><license/>
>
><version>1.0</version>
><date>2006-07-12</date>
>
><chapter>
><title>General information to DVB</title>
><section>
><title>What is DVB?</title>
><body>
>
>
><e>DVB</e> stands for <e>Digital Video Broadcasting</e>. DVB describes methods
>to transfer digital data of TV, radio, interactive services like MHP, EPG and
>teletext. Through data compression with MPEG-2, or H.264 for HDTV, it's possible
>to transfer several channels on the same frequency. The more data compression,
>the more channels can be transfered, but you pay it with quality loss.
>
>
>
>DVB can be transfered in several ways. The trailing letter identifies the way
>of transfer, e.g. DVB-<e>T</e> for terrestrial transmission. There are some
>more:
>
>
><ul>
><li>DVB-S for transmission over satellites</li>
><li>DVB-C for transmission over cable</li>
><li>DVB-H for transmission to mobile devices (terrestrial)</li>
><li>DVB-IPI for transmission over IP based networks, e.g. internet</li>
><li>
>DVB-RC(S/C/T) return channel for the transmission of data services, e.g.
>broadband internet
></li>
></ul>
>
></body>
></section>
>
><section>
><title>Types and requirement of DVB cards</title>
><body>
>
>
>Beside the different methods available to receive a DVB stream, the cards are
>classified by their type of produced output. They are cards with a decoder
>implemented, which offer direct access to the stream by the device
><path>/dev/video</path>. These cards are called <e>Full featured cards</e>.
>Other cards have no own decoder implemented and require a software decoder on
>the computer and are called <e>Budget cards</e>. That implies a higher system
>requirement; you shouldn't use a computer based on a CPU with lower than 600
>MHz and a memory amount lower than 256 MB. <uri
>link="http://linuxtv.org/wiki/index.php/DVB_Card_Vendors">This list</uri> is
>useful to identify your card.
>
>
></body>
></section>
>
></chapter>
>
><chapter>
><title>Preparing the system</title>
><section>
><title>Configuring the kernel</title>
><body>
>
>
>At first we have to ensure that your kernel supports DVB and your DVB device.
>Since kernel version 2.6 the necessary drivers are included. Check your kernel
>configuration and make sure the following options are selected as a static
>driver, or as a module.
>
>
><pre caption="Required kernel options">
>Input Device Support --->
>* Event Interface
>Device Drivers --->
>Multimedia Devices --->
>Digital Video Broadcasting Devices --->
> [*] DVB For Linux
> * DVB Core Support
> M [Your driver]
></pre>
>
>
>Additionally we have to select the proper driver for your hardware. To find out
>the right module for your card, we mark every driver as module. If you have a
>PCI card, install <c>pciutils</c>, if you haven't already. If you want built-in
>drivers or you don't own a PCI card, skip this point and continue with <uri
>link="#kernel_output">Checking the kernel output</uri>.
>
>
><pre caption="Installing pciutils">
># emerge pciutils
></pre>
>
>
>After booting the new kernel, we run <c>pcimodules</c> to list the required
>modules.
>
>
><pre caption="Listing the required modules">
># pcimodules
>ohci-hcd
>ehci-hcd
>sis900
>snd-emu10k1
>b2c2-flexcop-pci
>nvidia
>nvidiafb
></pre>
>
>
>In this case we have to load the module <c>b2c2-flexcop-pci</c>. We add the name
>to <path>/etc/modules.autoload.d/kernel-2.6</path>.
>
>
><pre caption="Adding the module name">
># echo b2c2-flexcop-pci >> /etc/modules.autoload.d/kernel-2.6
></pre>
>
></body>
></section>
>
><section id="kernel_output">
><title>Checking the kernel output</title>
><body>
>
>
>It's recommended to mark every driver as module, so you are able to add the
>required module dynamically, especially if you don't know the module name. If
>you know the module name already, select the driver as built-in driver. Compile
>the kernel, install the modules and boot it. Check to see if your kernel
>hassuccessfully detected your card by using <c>dmesg</c>.
>
>
><pre caption="Checking kernel output">
># dmesg | grep DVB
><comment>If you own a TerraTec Cinergy T2, your output might look like this:</comment>
>DVB: registering new adaptor (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver).
>input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2
></pre>
>
>
>Now continue with <uri link="#inst_lirc">installing LIRC</uri>, if you want to
>use a remote control.
>
>
></body>
></section>
></chapter>
>
><chapter id="inst_lirc">
><title>Configuring the remote control - LIRC</title>
><section>
><title>Installing LIRC</title>
><body>
>
>
>If your card offers the possibility to control remotely, you may wish to
>configure LIRC. LIRC interprets the pressed keys and returns a name for each
>one. A program that supports LIRC waits for key events and runs the action
>configured in the config file, mostly stored in the config directory of the
>executing program (e.g. MPlayer loads the file <path>~/.mplayer/lircrc</path>).
>Before we install LIRC, you have to add <c>lirc</c> to the USE flags and add
>an option. To find the proper argument for LIRC_DEVICES, <uri
>link="http://www.lirc.org/html/table.html">use this list</uri>.
>
>
><pre caption="Installing LIRC">
><comment>Replace "devinput" with the proper driver</comment>
># nano -w /etc/make.conf
># echo "LIRC_DEVICES=\"devinput\"" >> /etc/make.conf
># emerge lirc
></pre>
>
>
>At first we have to define each key code with a name. Most supported remote
>controls are configured already, take a look at the
><uri link="http://lirc.sourceforge.net/remotes/">remote list</uri>. Download
>the required file and save it as <path>/etc/lircd.conf</path>. Now we have to
>find out where to access your remote control. Run the following command to get
>a list of the current input devices (make sure your device is running).
>
>
><pre caption="List of current input devices">
># cat /proc/bus/input/devices
>I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
>N: Name="AT Translated Set 2 keyboard"
>P: Phys=isa0060/serio0/input0
>S: Sysfs=/class/input/input0
>H: Handlers=kbd event0
>B: EV=120013
>B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
>B: MSC=10
>B: LED=7
>
>I: Bus=0000 Vendor=0000 Product=0000 Version=0000
>N: Name="TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control"
>P: Phys=usb-0000:00:1d.7-1/input0
>S: Sysfs=/class/input/input2
>H: Handlers=kbd event1
>B: EV=100003
>B: KEY=108fc210 2043 0 0 0 0 8000 2080 1 9e1680 0 0 ffc
>
>I: Bus=0011 Vendor=0002 Product=0007 Version=0000
>N: Name="SynPS/2 Synaptics TouchPad"
>P: Phys=isa0060/serio4/input0
>S: Sysfs=/class/input/input3
>H: Handlers=mouse0 event2
>B: EV=b
>B: KEY=6420 0 7000f 0 0 0 0 0 0 0 0
>B: ABS=11000003
></pre>
>
>
>In this case we have the Terratec Cinergy T2 device plugged in, so we can access
>the device over <path>/dev/input/event1</path>. Replace <c>event1</c> with the
>matching device in your output.
>
>
>
>lircd needs to know the device to use. Add the following line to
><path>/etc/conf.d/lircd</path>.
>
>
><pre caption="Adding options to lircd">
># echo "LIRCD_OPTS=\"-H devinput -d /dev/input/event1\"" >> /etc/conf.d/lirc.conf
></pre>
>
>
>Remember to replace <c>event1</c> with the actual device. It's time to start
>lircd.
>
>
><pre caption="Starting lircd">
># /etc/init.d/lircd start
></pre>
>
>
>To start it always while booting, we add it to the default runlevel.
>
>
><pre caption="Adding lircd to the default runlevel">
># rc-update add lircd default
></pre>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Setting up VDR</title>
><section>
><title>Installing VDR</title>
><body>
>
>
>To install VDR, we just emerge it.
>
>
><pre caption="Installing VDR">
># emerge vdr
></pre>
>
>
>If you want to be able to use your remote control, we have to enable LIRC
>support in VDR. Add the following line to the <path>/etc/conf.d/vdr</path>.
>
>
><pre caption="Enabling support for LIRC">
># nano /etc/conf.d/vdr
>IR_CTRL="lirc"
></pre>
>
>
>You can start vdr manually with <path>/etc/init.d/vdr</path> start, or by
>adding it to the default runlevel.
>
>
><pre caption="Adding vdr to the default runlevel">
># /etc/init.d/vdr start
># rc-update add vdr default
></pre>
>
>
>That's the basic installation over, to configure VDR, you switch to your
>output screen and follow the on-screen instructions. VDR asks you to press
>various keys on your remote control to learn the correct keys codes. In case
>you don't own a remote control unit, you can optionally use the keyboard. If you
>only have a budget card, you need to <uri link="#softdevice">install a
>software-output-plugin</uri> now. This device decodes the stream and offers a
>device to access.
>
>
></body>
></section>
>
><section id="softdevice">
><title>Optional: Installing the softdevice plugin</title>
><body>
>
><note>
><c>vdr-xineliboutput</c> is also supported via ebuilds
></note>
>
>
>To install a softdevice, we have to emerge <c>vdr-softdevice</c>. Don't forget
>to configure the plugin.
>
>
><pre caption="Installing the softdevice plugin">
># emerge vdr-softdevice
># emerge --config vdr-softdevice
></pre>
>
>
>To select the proper video and audio output, edit
><path>/etc/conf.d/vdr.softdevice</path>.
>
>
></body>
></section>
></chapter>
>
></guide>
>

Actions: View

Attachments on bug 143456: 93907 | 94020 | 95299 | 95323 | 95387 | 95713