Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 93907 Details for
Bug 143456
New Gentoo VDR Guide
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Gentoo VDR Guide
vdr.xml (text/plain), 9.55 KB, created by
Norman Golisz
on 2006-08-10 06:07:19 UTC
(
hide
)
Description:
Gentoo VDR Guide
Filename:
MIME Type:
Creator:
Norman Golisz
Created:
2006-08-10 06:07:19 UTC
Size:
9.55 KB
patch
obsolete
><?xml version="1.0" encoding="UTF-8"?> ><!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> ><!-- $Header$ --> > ><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> > ><abstract> >This guide shows you how to prepare Gentoo Linux for DVB and VDR. ></abstract> > ><!-- The content of this document is licensed under the CC-BY-SA license --> ><!-- See http://creativecommons.org/licenses/by-sa/2.5 --> ><license/> > ><version>1.0</version> ><date>2006-07-12</date> > ><chapter> ><title>General information to DVB</title> ><section> ><title>What is DVB?</title> ><body> > ><p> ><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. ></p> > ><p> >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: ></p> > ><ul> > <li>DVB-S for transmission over satelites</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> > ><p> >Beside the different methods to receive the DVB stream, the cards are classified >by their type of produced output. They're 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 havn't an 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. ></p> > ></body> ></section> > ></chapter> > ><chapter> ><title>Preparing the system</title> ><section> ><title>Configuring the kernel</title> ><body> > ><p> >At first we have to ensure that your kernel supports DVB and your DVB device. >Since kernel version 2.6 the neccassary drivers are included. Check your kernel >configuration and make sure the following options are selected as static driver, >or as module. ></p> > ><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> > ><p> >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 havn'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>. ></p> > ><pre caption="Installing pciutils"> ># emerge pciutils ></pre> > ><p> >After booting the new kernel, we run <c>pcimodules</c> to list the required >modules. ></p> > ><pre caption="Listing the required modules"> ># pcimodules >ohci-hcd >ehci-hcd >sis900 >snd-emu10k1 >b2c2-flexcop-pci >nvidia >nvidiafb ></pre> > ><p> >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>. ></p> > ><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> > ><p> >It's recommend to mark every driver as module, so you are able to add the >required module dynamicly, especially if you don't know the modules name. If you >know the module name already, select the driver as built-in driver. Compile the >kernel, install the modules and boot it. Let's check if your kernel has >successfully detected your card by using <c>dmesg</c>. ></p> > ><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 adapter (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver). >input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2 ></pre> > ><p> ><!--If you can't find a proper kernel message, you should try downloading a proper >driver, try <uri link="#inst_firmware">installing a firmware</uri>.--> Now >continue <uri link="#inst_lirc">installing LIRC</uri>, in case you want to use a >remote control. ></p> > ></body> ></section> > ><!--<section> ><title>Optional: Installing a firmware</title> ><body> > ><p> >After you have compiled the kernel with generic DVB functionality, you can >download a firmware from <uri>http://www.linuxtv.org/download/firmware</uri>. ></p> > ></body> ></section>--> ></chapter> > ><chapter id="inst_lirc"> ><title>Configuring the remote control - LIRC</title> ><section> ><title>Installing LIRC</title> ><body> > ><p> >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. ></p> > ><pre caption="Installing LIRC"> ># nano -w /etc/make.conf ># echo "LIRC_OPTS=\"--with-driver=devinput\"" >> /etc/make.conf ># emerge lirc ></pre> > ><p> >At first we have to define each key code with a name. Most supported remote >controls are configured already, take a look at ><uri>http://lirc.sourceforge.net/remotes/</uri>. Download the proper 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). ></p> > ><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> > ><p> >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. ></p> > ><p> >lircd needs to know the device to use. Add the following line to ><path>/etc/conf.d/lircd</path>. ></p> > ><pre caption="Adding options to lircd"> ># echo "LIRCD_OPTS=\"-H dev/input -d /dev/input/event1\"" ></pre> > ><p> >Remember to replace <c>event1</c> with the actual device. It's time to start >lircd. ></p> > ><pre caption="Starting lircd"> ># /etc/init.d/lircd start ></pre> > ><p> >To start it always while booting, we add it to the default runlevel. ></p> > ><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> > ><p> >To install VDR, we just emerge it. ></p> > ><pre caption="Installing VDR"> ># emerge vdr ></pre> > ><p> >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>. ></p> > ><pre caption="Enabling support for LIRC"> ># echo "IR_CTRL=\"lirc\"" >> /etc/conf.d/vdr ></pre> > ><p> >You can start VDR manually by starting <path>/etc/init.d/vdr</path>, or always >the system gets started. ></p> > ><pre caption="Adding vdr to the default runlevel"> ># /etc/init.d/vdr start ># rc-update add vdr default ></pre> > ><p> >The installation has finished so far, to configure VDR, you switch to your >output screen and follow the instructions on the screen. VDR asks you to press >various keys on your remote control to learn the correct keys codes. In case you >havn't a remote control unit, you can optionally use the keyboard. If you have >a budget card, we need to <uri link="#softdevice">install a softdevice</uri> now. >This device decodes the stream and offers a device to access. ></p> > ></body> ></section> > ><section id="softdevice"> ><title>Optional: Installing the softdevice plugin</title> ><body> > ><p> >To install a softdevice, we have to emerge <c>vdr-softdevice</c>. Don't forget >to configure the plugin. ></p> > ><pre caption="Installing the softdevice plugin"> ># emerge vdr-softdevice ># emerge --config vdr-softdevice ></pre> > ><p> >To select the proper video- and audio output, edit ><path>/etc/conf.d/vdr.softdevice</path>. To switch to the output screen, press >Ctrl, Alt and F8. ></p> > ></body> ></section> ></chapter> > ></guide> >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 143456
: 93907 |
94020
|
95299
|
95323
|
95387
|
95713