Attachment #95323 for bug #143456

View | Details | Raw Unified | Return to bug 143456 | Differences between
Collapse All | Expand All




<?xml version="1.0" encoding="UTF-8"?>
<!-- $Header:$ -->
<!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>
<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>

<!-- The content of this document is licensed under the CC-BY-SA license -->

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>


<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 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.
</p>

</body>
</section>

</chapter>

    * 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">
# <i>emerge pciutils</i>
</pre>

<p>
After booting the new kernel, we run <c>pcimodules</c> to list the required
modules.
</p>

<pre caption="Listing the required modules">
# <i>pcimodules</i>
ohci-hcd
ehci-hcd
sis900
snd-emu10k1
b2c2-flexcop-pci
nvidia

<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">
# <i>echo b2c2-flexcop-pci >> /etc/modules.autoload.d/kernel-2.6</i>
</pre>

</body>
</section>

<section id="kernel_output">

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">
# <i>dmesg | grep DVB</i>
<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>

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>.
</p>

<pre caption="Installing LIRC">
<comment>Replace "devinput" with the proper driver</comment>
# <i>nano -w /etc/make.conf</i>
# <i>echo "LIRC_DEVICES=\"devinput\"" >> /etc/make.conf</i>
# <i>emerge lirc</i>
</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 link="http://lirc.sourceforge.net/remotes/">remote list</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">
# <i>cat /proc/bus/input/devices</i>
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>

<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">
# <i>echo "LIRCD_OPTS=\"-H devinput -d /dev/input/event1\"" >> /etc/conf.d/lirc.conf</i>
</pre>

<p>
Remember to replace <c>event1</c> with the actual device. It's time to start
lircd.
</p>

<pre caption="Starting lircd">
# <i>/etc/init.d/lircd start</i>
</pre>

<p>
To start it always while booting, we add it to the default runlevel.
</p>

<pre caption="Adding lircd to the default runlevel">
# <i>rc-update add lircd default</i>
</pre>

</body>
</section>
</chapter>



<p>
To install VDR, we just emerge it.
</p>

<pre caption="Installing VDR">
# <i>emerge vdr</i>
</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">
# <i>nano /etc/conf.d/vdr</i>
IR_CTRL="lirc"
</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">
# <i>/etc/init.d/vdr start</i>
# <i>rc-update add vdr default</i>
</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
only have a budget card, we need to <uri link="#softdevice">install a
software-output-plugin</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>

<note>
<c>vdr-xineliboutput</c> is also supported via ebuilds
</note>

<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">
# <i>emerge vdr-softdevice</i>
# <i>emerge --config vdr-softdevice</i>
</pre>

<p>
To select the proper video- and audio output, edit
<path>/etc/conf.d/vdr.softdevice</path>.
Ctrl, Alt and F8.
</p>

</body>
</section>
</chapter>


Return to bug 143456

Lines 1-16 Link Here

(-)vdr.xml.orig (-50 / +62 lines)
1	<?xml version="1.0" encoding="UTF-8"?>	1	<?xml version="1.0" encoding="UTF-8"?>
		2	<!-- $Header:$ -->
2	<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">	3	<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3	<!-- $Header$ -->
4		4
5	<guide link="/doc/en/vdr.xml">	5	<guide link="/doc/en/vdr.xml">
6	<title>Gentoo Linux VDR Guide</title>	6	<title>Gentoo Linux VDR Guide</title>
7		7
8	<author title="Author">	8	<author title="Author">
9	<mail link="mail@ng-plasmon.de">Norman Golisz</mail>	9	<mail link="mail@ng-plasmon.de">Norman Golisz</mail>
10	</author>	10	</author>
		11	<author title="Editor">
		12	<mail link="diox@swords.be">Dimitry Bradt</mail>
		13	</author>
		14
11		15
12	<abstract>	16	<abstract>
13	This guide shows you how to prepare Gentoo Linux for DVB and VDR.	17	This guide shows you how to prepare Gentoo Linux for DVB and VDR.
14	</abstract>	18	</abstract>
15		19
16	<!-- The content of this document is licensed under the CC-BY-SA license -->	20	<!-- The content of this document is licensed under the CC-BY-SA license -->
Lines 33-45 Link Here
33	to transfer several channels on the same frequency. The more data compression,	37	to transfer several channels on the same frequency. The more data compression,
34	the more channels can be transfered, but you pay it with quality loss.	38	the more channels can be transfered, but you pay it with quality loss.
35	</p>	39	</p>
36		40
37	<p>	41	<p>
38	DVB can be transfered in several ways. The trailing letter identifies the way	42	DVB can be transfered in several ways. The trailing letter identifies the way
39	of transfer, e.g. DVB-<e>T</e> for terrestrial transmission. There are some more:	43	of transfer, e.g. DVB-<e>T</e> for terrestrial transmission. There are some
		44	more:
40	</p>	45	</p>
41		46
42	<ul>	47	<ul>
43	<li>DVB-S for transmission over satelites</li>	48	<li>DVB-S for transmission over satelites</li>
44	<li>DVB-C for transmission over cable</li>	49	<li>DVB-C for transmission over cable</li>
45	<li>DVB-H for transmission to mobile devices (terrestrial)</li>	50	<li>DVB-H for transmission to mobile devices (terrestrial)</li>
Lines 55-76 Link Here
55		60
56	<section>	61	<section>
57	<title>Types and requirement of DVB cards</title>	62	<title>Types and requirement of DVB cards</title>
58	<body>	63	<body>
59		64
60	<p>	65	<p>
61	Beside the different methods to receive the DVB stream, the cards are classified	66	Beside the different methods to receive the DVB stream, the cards are
62	by their type of produced output. They're cards with a decoder implemented, which	67	classified by their type of produced output. They are cards with a decoder
63	offer direct access to the stream by the device <path>/dev/video</path>. These	68	implemented, which offer direct access to the stream by the device
64	cards are called <e>Full featured cards</e>. Other cards havn't an own decoder	69	<path>/dev/video</path>. These cards are called <e>Full featured cards</e>.
65	implemented and require a software decoder on the computer and are called	70	Other cards have no own decoder implemented and require a software decoder on
66	<e>Budget cards</e>. That implies a higher system requirement; you shouldn't use	71	the computer and are called <e>Budget cards</e>. That implies a higher system
67	a computer based on a CPU with lower than 600 MHz and a memory amount lower than	72	requirement; you shouldn't use a computer based on a CPU with lower than 600
68	256 MB. <uri link="http://linuxtv.org/wiki/index.php/DVB_Card_Vendors">This list	73	MHz and a memory amount lower than 256 MB. <uri
69	</uri> is useful to identify your	74	link="http://linuxtv.org/wiki/index.php/DVB_Card_Vendors">This list</uri> is
70	card.	75	useful to identify your card.
71	</p>	76	</p>
72		77
73	</body>	78	</body>
74	</section>	79	</section>
75		80
76	</chapter>	81	</chapter>
Lines 93-126 Link Here
93	* Event Interface	98	* Event Interface
94	Device Drivers --->	99	Device Drivers --->
95	Multimedia Devices --->	100	Multimedia Devices --->
96	Digital Video Broadcasting Devices --->	101	Digital Video Broadcasting Devices --->
97	[*] DVB For Linux	102	[*] DVB For Linux
98	* DVB Core Support	103	* DVB Core Support
99	M [Your driver]	104	M [Your driver]
100	</pre>	105	</pre>
101		106
102	<p>	107	<p>
103	Additionally we have to select the proper driver for your hardware. To find out	108	Additionally we have to select the proper driver for your hardware. To find out
104	the right module for your card, we mark every driver as module. If you have a	109	the right module for your card, we mark every driver as module. If you have a
105	PCI card, install <c>pciutils</c>, if you havn't already. If you want built-in	110	PCI card, install <c>pciutils</c>, if you havn't already. If you want built-in
106	drivers or you don't own a PCI card, skip this point and continue with <uri	111	drivers or you don't own a PCI card, skip this point and continue with <uri
107	link="#kernel_output">Checking the kernel output</uri>.	112	link="#kernel_output">Checking the kernel output</uri>.
108	</p>	113	</p>
109		114
110	<pre caption="Installing pciutils">	115	<pre caption="Installing pciutils">
111	# emerge pciutils	116	# <i>emerge pciutils</i>
112	</pre>	117	</pre>
113		118
114	<p>	119	<p>
115	After booting the new kernel, we run <c>pcimodules</c> to list the required	120	After booting the new kernel, we run <c>pcimodules</c> to list the required
116	modules.	121	modules.
117	</p>	122	</p>
118		123
119	<pre caption="Listing the required modules">	124	<pre caption="Listing the required modules">
120	# pcimodules	125	# <i>pcimodules</i>
121	ohci-hcd	126	ohci-hcd
122	ehci-hcd	127	ehci-hcd
123	sis900	128	sis900
124	snd-emu10k1	129	snd-emu10k1
125	b2c2-flexcop-pci	130	b2c2-flexcop-pci
126	nvidia	131	nvidia
Lines 130-142 Link Here
130	<p>	135	<p>
131	In this case we have to load the module <c>b2c2-flexcop-pci</c>. We add the name	136	In this case we have to load the module <c>b2c2-flexcop-pci</c>. We add the name
132	to <path>/etc/modules.autoload.d/kernel-2.6</path>.	137	to <path>/etc/modules.autoload.d/kernel-2.6</path>.
133	</p>	138	</p>
134		139
135	<pre caption="Adding the module name">	140	<pre caption="Adding the module name">
136	# echo b2c2-flexcop-pci >> /etc/modules.autoload.d/kernel-2.6	141	# <i>echo b2c2-flexcop-pci >> /etc/modules.autoload.d/kernel-2.6</i>
137	</pre>	142	</pre>
138		143
139	</body>	144	</body>
140	</section>	145	</section>
141		146
142	<section id="kernel_output">	147	<section id="kernel_output">
Lines 149-171 Link Here
149	know the module name already, select the driver as built-in driver. Compile the	154	know the module name already, select the driver as built-in driver. Compile the
150	kernel, install the modules and boot it. Let's check if your kernel has	155	kernel, install the modules and boot it. Let's check if your kernel has
151	successfully detected your card by using <c>dmesg</c>.	156	successfully detected your card by using <c>dmesg</c>.
152	</p>	157	</p>
153		158
154	<pre caption="Checking kernel output">	159	<pre caption="Checking kernel output">
155	# dmesg \| grep DVB	160	# <i>dmesg \| grep DVB</i>
156	<comment>If you own a TerraTec Cinergy T2, your output might look like this:</comment>	161	<comment>If you own a TerraTec Cinergy T2, your output might look like this:</comment>
157	DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver).	162	DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver).
158	input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2	163	input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2
159	</pre>	164	</pre>
160		165
161	<p>	166	<p>
162	<!--If you can't find a proper kernel message, you should try downloading a proper	167	<!--If you can't find a proper kernel message, you should try downloading a
163	driver, try <uri link="#inst_firmware">installing a firmware</uri>.--> Now	168	proper driver, try <uri link="#inst_firmware">installing a firmware</uri>.-->
164	continue <uri link="#inst_lirc">installing LIRC</uri>, in case you want to use a	169	Now continue <uri link="#inst_lirc">installing LIRC</uri>, in case you want to
165	remote control.	170	use a remote control.
166	</p>	171	</p>
167		172
168	</body>	173	</body>
169	</section>	174	</section>
170		175
171	<!--<section>	176	<!--<section>
Lines 191-245 Link Here
191	If your card offers the possibility to control remotely, you may wish to	196	If your card offers the possibility to control remotely, you may wish to
192	configure LIRC. LIRC interprets the pressed keys and returns a name for each	197	configure LIRC. LIRC interprets the pressed keys and returns a name for each
193	one. A program that supports LIRC waits for key events and runs the action	198	one. A program that supports LIRC waits for key events and runs the action
194	configured in the config file, mostly stored in the config directory of the	199	configured in the config file, mostly stored in the config directory of the
195	executing program (e.g. MPlayer loads the file <path>~/.mplayer/lircrc</path>).	200	executing program (e.g. MPlayer loads the file <path>~/.mplayer/lircrc</path>).
196	Before we install LIRC, you have to add <c>lirc</c> to the USE flags and add	201	Before we install LIRC, you have to add <c>lirc</c> to the USE flags and add
197	an option.	202	an option. To find the proper argument for LIRC_DEVICES, <uri
		203	link="http://www.lirc.org/html/table.html">use this list</uri>.
198	</p>	204	</p>
199		205
200	<pre caption="Installing LIRC">	206	<pre caption="Installing LIRC">
201	# nano -w /etc/make.conf	207	<comment>Replace "devinput" with the proper driver</comment>
202	# echo "LIRC_OPTS=\"--with-driver=devinput\"" >> /etc/make.conf	208	# <i>nano -w /etc/make.conf</i>
203	# emerge lirc	209	# <i>echo "LIRC_DEVICES=\"devinput\"" >> /etc/make.conf</i>
		210	# <i>emerge lirc</i>
204	</pre>	211	</pre>
205		212
206	<p>	213	<p>
207	At first we have to define each key code with a name. Most supported remote	214	At first we have to define each key code with a name. Most supported remote
208	controls are configured already, take a look at	215	controls are configured already, take a look at
209	<uri>http://lirc.sourceforge.net/remotes/</uri>. Download the proper file and	216	<uri link="http://lirc.sourceforge.net/remotes/">remote list</uri>. Download
210	save it as <path>/etc/lircd.conf</path>. Now we have to find out where to access	217	the proper file and save it as <path>/etc/lircd.conf</path>. Now we have to
211	your remote control. Run the following command to get a list of the current	218	find out where to access your remote control. Run the following command to get
212	input devices (make sure your device is running).	219	a list of the current input devices (make sure your device is running).
213	</p>	220	</p>
214		221
215	<pre caption="List of current input devices">	222	<pre caption="List of current input devices">
216	# cat /proc/bus/input/devices	223	# <i>cat /proc/bus/input/devices</i>
217	I: Bus=0011 Vendor=0001 Product=0001 Version=ab41	224	I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
218	N: Name="AT Translated Set 2 keyboard"	225	N: Name="AT Translated Set 2 keyboard"
219	P: Phys=isa0060/serio0/input0	226	P: Phys=isa0060/serio0/input0
220	S: Sysfs=/class/input/input0	227	S: Sysfs=/class/input/input0
221	H: Handlers=kbd event0	228	H: Handlers=kbd event0
222	B: EV=120013	229	B: EV=120013
223	B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe	230	B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
224	B: MSC=10	231	B: MSC=10
225	B: LED=7	232	B: LED=7
226		233
227	I: Bus=0000 Vendor=0000 Product=0000 Version=0000	234	I: Bus=0000 Vendor=0000 Product=0000 Version=0000
228	N: Name="TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control"	235	N: Name="TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control"
229	P: Phys=usb-0000:00:1d.7-1/input0	236	P: Phys=usb-0000:00:1d.7-1/input0
230	S: Sysfs=/class/input/input2	237	S: Sysfs=/class/input/input2
231	H: Handlers=kbd event1	238	H: Handlers=kbd event1
232	B: EV=100003	239	B: EV=100003
233	B: KEY=108fc210 2043 0 0 0 0 8000 2080 1 9e1680 0 0 ffc	240	B: KEY=108fc210 2043 0 0 0 0 8000 2080 1 9e1680 0 0 ffc
234		241
235	I: Bus=0011 Vendor=0002 Product=0007 Version=0000	242	I: Bus=0011 Vendor=0002 Product=0007 Version=0000
236	N: Name="SynPS/2 Synaptics TouchPad"	243	N: Name="SynPS/2 Synaptics TouchPad"
237	P: Phys=isa0060/serio4/input0	244	P: Phys=isa0060/serio4/input0
238	S: Sysfs=/class/input/input3	245	S: Sysfs=/class/input/input3
239	H: Handlers=mouse0 event2	246	H: Handlers=mouse0 event2
240	B: EV=b	247	B: EV=b
241	B: KEY=6420 0 7000f 0 0 0 0 0 0 0 0	248	B: KEY=6420 0 7000f 0 0 0 0 0 0 0 0
242	B: ABS=11000003	249	B: ABS=11000003
243	</pre>	250	</pre>
244		251
245	<p>	252	<p>
Lines 251-280 Link Here
251	<p>	258	<p>
252	lircd needs to know the device to use. Add the following line to	259	lircd needs to know the device to use. Add the following line to
253	<path>/etc/conf.d/lircd</path>.	260	<path>/etc/conf.d/lircd</path>.
254	</p>	261	</p>
255		262
256	<pre caption="Adding options to lircd">	263	<pre caption="Adding options to lircd">
257	# echo "LIRCD_OPTS=\"-H dev/input -d /dev/input/event1\""	264	# <i>echo "LIRCD_OPTS=\"-H devinput -d /dev/input/event1\"" >> /etc/conf.d/lirc.conf</i>
258	</pre>	265	</pre>
259		266
260	<p>	267	<p>
261	Remember to replace <c>event1</c> with the actual device. It's time to start	268	Remember to replace <c>event1</c> with the actual device. It's time to start
262	lircd.	269	lircd.
263	</p>	270	</p>
264		271
265	<pre caption="Starting lircd">	272	<pre caption="Starting lircd">
266	# /etc/init.d/lircd start	273	# <i>/etc/init.d/lircd start</i>
267	</pre>	274	</pre>
268		275
269	<p>	276	<p>
270	To start it always while booting, we add it to the default runlevel.	277	To start it always while booting, we add it to the default runlevel.
271	</p>	278	</p>
272		279
273	<pre caption="Adding lircd to the default runlevel">	280	<pre caption="Adding lircd to the default runlevel">
274	# rc-update add lircd default	281	# <i>rc-update add lircd default</i>
275	</pre>	282	</pre>
276		283
277	</body>	284	</body>
278	</section>	285	</section>
279	</chapter>	286	</chapter>
280		287
Lines 286-349 Link Here
286		293
287	<p>	294	<p>
288	To install VDR, we just emerge it.	295	To install VDR, we just emerge it.
289	</p>	296	</p>
290		297
291	<pre caption="Installing VDR">	298	<pre caption="Installing VDR">
292	# emerge vdr	299	# <i>emerge vdr</i>
293	</pre>	300	</pre>
294		301
295	<p>	302	<p>
296	If you want to be able to use your remote control, we have to enable LIRC support	303	If you want to be able to use your remote control, we have to enable LIRC
297	in VDR. Add the following line to the <path>/etc/conf.d/vdr</path>.	304	support in VDR. Add the following line to the <path>/etc/conf.d/vdr</path>.
298	</p>	305	</p>
299		306
300	<pre caption="Enabling support for LIRC">	307	<pre caption="Enabling support for LIRC">
301	# echo "IR_CTRL=\"lirc\"" >> /etc/conf.d/vdr	308	# <i>nano /etc/conf.d/vdr</i>
		309	IR_CTRL="lirc"
302	</pre>	310	</pre>
303		311
304	<p>	312	<p>
305	You can start VDR manually by starting <path>/etc/init.d/vdr</path>, or always	313	You can start VDR manually by starting <path>/etc/init.d/vdr</path>, or always
306	the system gets started.	314	the system gets started.
307	</p>	315	</p>
308		316
309	<pre caption="Adding vdr to the default runlevel">	317	<pre caption="Adding vdr to the default runlevel">
310	# /etc/init.d/vdr start	318	# <i>/etc/init.d/vdr start</i>
311	# rc-update add vdr default	319	# <i>rc-update add vdr default</i>
312	</pre>	320	</pre>
313		321
314	<p>	322	<p>
315	The installation has finished so far, to configure VDR, you switch to your	323	The installation has finished so far, to configure VDR, you switch to your
316	output screen and follow the instructions on the screen. VDR asks you to press	324	output screen and follow the instructions on the screen. VDR asks you to press
317	various keys on your remote control to learn the correct keys codes. In case you	325	various keys on your remote control to learn the correct keys codes. In case
318	havn't a remote control unit, you can optionally use the keyboard. If you have	326	you havn't a remote control unit, you can optionally use the keyboard. If you
319	a budget card, we need to <uri link="#softdevice">install a softdevice</uri> now.	327	only have a budget card, we need to <uri link="#softdevice">install a
320	This device decodes the stream and offers a device to access.	328	software-output-plugin</uri> now. This device decodes the stream and offers a
		329	device to access.
321	</p>	330	</p>
322		331
323	</body>	332	</body>
324	</section>	333	</section>
325		334
326	<section id="softdevice">	335	<section id="softdevice">
327	<title>Optional: Installing the softdevice plugin</title>	336	<title>Optional: Installing the softdevice plugin</title>
328	<body>	337	<body>
329		338
		339	<note>
		340	<c>vdr-xineliboutput</c> is also supported via ebuilds
		341	</note>
		342
330	<p>	343	<p>
331	To install a softdevice, we have to emerge <c>vdr-softdevice</c>. Don't forget	344	To install a softdevice, we have to emerge <c>vdr-softdevice</c>. Don't forget
332	to configure the plugin.	345	to configure the plugin.
333	</p>	346	</p>
334		347
335	<pre caption="Installing the softdevice plugin">	348	<pre caption="Installing the softdevice plugin">
336	# emerge vdr-softdevice	349	# <i>emerge vdr-softdevice</i>
337	# emerge --config vdr-softdevice	350	# <i>emerge --config vdr-softdevice</i>
338	</pre>	351	</pre>
339		352
340	<p>	353	<p>
341	To select the proper video- and audio output, edit	354	To select the proper video- and audio output, edit
342	<path>/etc/conf.d/vdr.softdevice</path>. To switch to the output screen, press	355	<path>/etc/conf.d/vdr.softdevice</path>.
343	Ctrl, Alt and F8.
344	</p>	356	</p>
345		357
346	</body>	358	</body>
347	</section>	359	</section>
348	</chapter>	360	</chapter>
349		361