/[gentoo]/xml/htdocs/doc/en/alsa-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/alsa-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.25 Revision 1.26
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.25 2004/02/19 14:28:12 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.26 2004/02/23 14:17:05 erwin Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link = "/doc/en/alsa-guide.xml"> 5<guide link = "/doc/en/alsa-guide.xml">
6<title>Gentoo Linux ALSA Guide</title> 6<title>Gentoo Linux ALSA Guide</title>
7<author title="Author"> 7<author title="Author">
11 <mail link="g2boojum@gentoo.org">Grant Goodyear</mail> 11 <mail link="g2boojum@gentoo.org">Grant Goodyear</mail>
12</author> 12</author>
13<author title="Author"> 13<author title="Author">
14 <mail link="agenkin@gentoo.org">Arcady Genkin</mail> 14 <mail link="agenkin@gentoo.org">Arcady Genkin</mail>
15</author> 15</author>
16<author title="Author">
17 <mail link="eradicator@gentoo.org">Jeremy Huddleston</mail>
18</author>
16<author title="Editor"><!-- zhen@gentoo.org --> 19<author title="Editor"><!-- zhen@gentoo.org -->
17 John P. Davis 20 John P. Davis
18</author> 21</author>
19<author title="Editor"> 22<author title="Editor">
20 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 23 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
22<author title="Editor"> 25<author title="Editor">
23 <mail link="bennyc@gentoo.org">Benny Chuang</mail> 26 <mail link="bennyc@gentoo.org">Benny Chuang</mail>
24</author> 27</author>
25<author title="Editor"> 28<author title="Editor">
26 <mail link="blubber@gentoo.org">Tiemo Kieft</mail> 29 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
30</author>
31<author title="Editor">
32 <mail link="erwin@gentoo.org">Erwin</mail>
27</author> 33</author>
28 34
29<abstract> 35<abstract>
30This guide will show you how to set up the Advanced Linux Sound Architecture 36This guide will show you how to set up the Advanced Linux Sound Architecture
31(ALSA) on Gentoo Linux. In addition to the Gentoo Linux Desktop Configuration 37(ALSA) on Gentoo Linux. In addition to the Gentoo Linux Desktop Configuration
32Guide, this guide is supposed to give you more information on this subject. 38Guide, this guide is supposed to give you more information on this subject.
33</abstract> 39</abstract>
34 40
35<license/> 41<license/>
36 42
37<version>1.3.5</version> 43<version>1.4.0</version>
38<date>December 31, 2003</date> 44<date>February 22, 2003</date>
39 45
40<chapter> 46<chapter>
41<title>Introduction</title> 47<title>Introduction</title>
42<section> 48<section>
43<title>What is ALSA?</title> 49<title>What is ALSA?</title>
44<body> 50<body>
45 51
46<p> 52<p>
47The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux 53The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux
48sound subsystem by rewriting large chunks of it. It is anticipated that ALSA 54sound subsystem by rewriting large chunks of it. It has replaced the Open
49will make it into Linux kernel 2.6.x (or 3.x.x -- whichever comes first) as it 55Sound System (OSS) as the default sound subsystem in the 2.6 kernel, but it
50becomes ready. 56can be used with either 2.4 or 2.6 kernels.
51</p> 57</p>
52 58
53<p> 59<p>
54ALSA provides audio and MIDI functionality for Linux. 60ALSA provides audio and MIDI functionality for Linux.
55</p> 61</p>
87<section> 93<section>
88<title>Why use ALSA?</title> 94<title>Why use ALSA?</title>
89<body> 95<body>
90 96
91<p> 97<p>
92If your soundcard is supported by the Linux kernel sound system or the 98Your sound card may be supported by modules available in the 2.4 kernel (these
93commercial OSS/4Front sound driver system, which can be found in all 2.4.x 99are also provided in the 2.6 kernel under the 'Open Sound System (DEPRECATED)'
94Linux kernels, you could just aswell build <e>those modules</e> for use with 100option). Additionally, you might be able to use the commercial OSS/4Front sound
95your soundcard. If you want this, just read through the <uri 101driver system. If you wish to use either of these systems, then you should read
96link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri>. 102through the <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux
103Sound HOWTO</uri>.
97</p> 104</p>
98 105
99<p> 106<p>
100However, those OSS/4Front drivers have some limitations -- being commercial is 107The OSS/4Front drivers have some limitations, however. Being commercial is
101one. ALSA is an attempt to go beyond these limitations and to do so in an 108one. ALSA is an attempt to go beyond these limitations with an open source
102open-source fashion. ALSA is a fully GPL and LGPL'ed sound driver system, that 109development model. ALSA is a fully GPL and LGPL'ed sound driver system that
103provides a professional quality system for recording, playback, and MIDI 110provides a professional quality system for recording, playback, and MIDI
104sequencing. 111sequencing.
105</p> 112</p>
106 113
107</body> 114</body>
142<section> 149<section>
143<title>Kernel modules</title> 150<title>Kernel modules</title>
144<body> 151<body>
145 152
146<p> 153<p>
147Since we're still using 2.4.x kernel sources, we'll have to compile kernel 154When using the 2.4 kernels, you'll need to compile the alsa drivers separately
148modules and ALSA modules separately. People who are using a 2.5.x kernel can 155from the rest of the kernel. If you are using a 2.6 kernel, you have the
149do this from within their kernel configuration, since the ALSA modules are 156option of using the ALSA drivers included in the kernel or those provided
150included in the kernel sources and should be built there. 157by the <c>alsa-driver</c> package.
151</p> 158</p>
152 159
153<p> 160<p>
154First we'll make sure that our kernel configuration is ready for use with ALSA. 161First we'll make sure that our kernel configuration is ready for use with ALSA.
155All you need in your kernel configuration is having Sound Card Support set to 162All you need in your kernel configuration is having Sound Card Support set to
156be built as a module (M). This will build <path>soundcore.o</path>. 163be built as a module (M). This will build <path>soundcore.o</path>.
157</p> 164</p>
158 165
159<note> 166<note>
160Possibly, this will also work when you built Sound Card Support in the kernel 167Possibly, this will also work if you build 'Sound Card Support' in the kernel
161(Y) instead of building it as a module (M). However, the official ALSA 168(Y) instead of building it as a module (M). However, the official ALSA
162documentation suggests building it as a module, since ALSA will try loading it. 169documentation suggests building it as a module, since ALSA will try loading it.
163</note> 170</note>
164 171
165<p> 172<p>
176# <i>make menuconfig</i> 183# <i>make menuconfig</i>
177</pre> 184</pre>
178 185
179<p> 186<p>
180Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound 187Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound
181drivers. Exit and say Y to save your kernel configuration. After that, build 188drivers. If you are using 2.6 with the ALSA modules provided by the kernel, select
182the modules: 189the drivers for your sound card as well (look in the <uri
190link="#doc_chap2_sect3">ALSA modules</uri> section below if you need help
191choosing the right drivers). Exit and say Y to save your kernel configuration.
192After that, build the modules:
183</p> 193</p>
184 194
185<pre caption="Kernel compilation"> 195<pre caption="2.4 Kernel compilation">
186# <i>make dep clean</i> 196# <i>make dep clean</i>
187# <i>make modules modules_install</i> 197# <i>make modules modules_install</i>
188</pre> 198</pre>
199
200<pre caption="2.6 Kernel compilation">
201# <i>make</i>
202# <i>make modules_install</i>
203</pre>
204
205<p>
206If you compiled 2.6 with the ALSA modules provided by the kernel, please skip to
207<uri link="#doc_chap2_sect4">Configuration of ALSA</uri> below.
208</p>
189 209
190<p> 210<p>
191Before installing your new modules, this last line will delete all your previous 211Before installing your new modules, this last line will delete all your previous
192modules, even the ones from a previous ALSA installation. 212modules, even the ones from a previous ALSA installation.
193</p> 213</p>
214</pre> 234</pre>
215 235
216<warn> 236<warn>
217If you had a previous sound setup and there are still non-ALSA sound modules 237If you had a previous sound setup and there are still non-ALSA sound modules
218loaded, unload them <e>now</e>. Check with <c>lsmod</c> and use <c>rmmod</c> 238loaded, unload them <e>now</e>. Check with <c>lsmod</c> and use <c>rmmod</c>
219to unload all sound-related modules on your system. 239to unload all sound-related modules on your system. If <c>rmmod</c> complains
240about not being able to unload the modules because they are in use, try using
241<c>/etc/init.c/alsasound stop</c> to remove them.
220</warn> 242</warn>
221 243
222<p> 244<p>
223We could simply do an <c>emerge alsa-driver</c> now, this would compile and 245We could simply do an <c>emerge alsa-driver</c> now, this would compile and
224install <e>all</e> ALSA sound drivers. 246install <e>all</e> ALSA sound drivers.
232since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. We'll set 254since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. We'll set
233ALSA_CARDS environment to the value of the module name before emerging (but 255ALSA_CARDS environment to the value of the module name before emerging (but
234without the snd prefix), so emerge will only compile the drivers we need. 256without the snd prefix), so emerge will only compile the drivers we need.
235</p> 257</p>
236 258
237<pre caption="Compile correct modules"> 259<pre caption="With 2.4 Kernel">
238# <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i> 260# <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i>
239</pre> 261</pre>
262
263<pre caption="With 2.6 Kernel">
264# <i>env ALSA_CARDS='emu10k1' emerge \>=media-sound/alsa-driver-1.0.2c</i>
265</pre>
266
267<note>
2682.6 kernels require alsa-driver to be atl east version 1.0.2c.
269</note>
240 270
241<note> 271<note>
242You can also add this value in <path>/etc/make.conf</path>, so when you have 272You can also add this value in <path>/etc/make.conf</path>, so when you have
243to emerge the alsa-driver later on you can just run <c>emerge alsa-driver</c>. 273to emerge the alsa-driver later on you can just run <c>emerge alsa-driver</c>.
244For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c> 274For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c>
258<note> 288<note>
259If you plan on recompiling your kernels numerous times, it might 289If you plan on recompiling your kernels numerous times, it might
260be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This 290be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This
261will create a binary package for it. Later, after recompiling your kernel, 291will create a binary package for it. Later, after recompiling your kernel,
262you can just do <c>emerge --usepkg alsa-driver</c> which will install the 292you can just do <c>emerge --usepkg alsa-driver</c> which will install the
263binary package instead of recompiling it completely. 293binary package instead of recompiling it completely. If 'depmod -a' ever
294complains about sound drivers having unreferenced symbols when you do this,
295you will need to recompile the alsa-driver package from source.
264</note> 296</note>
265 297
266<p> 298<p>
267After this, the ALSA modules should be installed on your system. 299After this, the ALSA modules should be installed on your system.
268</p> 300</p>
290Hereafter, we need to edit <path>/etc/modules.d/alsa</path>. 322Hereafter, we need to edit <path>/etc/modules.d/alsa</path>.
291</p> 323</p>
292 324
293<warn> 325<warn>
294There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit 326There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit
295files in <path>/etc/modules.d</path>. 327files in <path>/etc/modules.d</path> and run <c>modules-update</c> to generate
328<path>/etc/modules.conf</path> from the updated data.
296</warn> 329</warn>
297
298<p>
299Check the ALSA portion <e>at the bottom of the file</e>. By tweaking this line
300you can specify the max number of soundcards you have (generally, just one).
301</p>
302
303<pre caption="At the bottom of /etc/modules.d/alsa">
304<comment>Set this to the correct number of cards.</comment>
305options snd cards_limit=1
306</pre>
307
308<p>
309Now we'll specify the sounddriver(s) ALSA should use. In the same file, edit
310like this:
311</p>
312 330
313<pre caption="In /etc/modules.d/alsa"> 331<pre caption="In /etc/modules.d/alsa">
314## and then run `modules-update' command. 332## and then run `modules-update' command.
315## Read alsa-driver's INSTALL file in /usr/share/doc for more info. 333## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
316## 334##
317## ALSA portion 335## ALSA portion
318alias snd-card-0 snd-emu10k1 336alias snd-card-0 snd-emu10k1
319<comment>## If you have more than one, add:</comment>
320## alias snd-card-1 snd-intel8x0 337## alias snd-card-1 snd-intel8x0
321## alias snd-card-2 snd-ens1370 338## alias snd-card-2 snd-ens1370
322## OSS/Free portion 339## OSS/Free portion
323## alias sound-slot-0 snd-card-0 340alias sound-slot-0 snd-card-0
324## alias sound-slot-1 snd-card-1 341## alias sound-slot-1 snd-card-1
342## alias sound-slot-2 snd-card-2
325## 343##
326</pre> 344</pre>
327 345
328<note> 346<note>
329If you have more than one soundcard, adjust the <c>cards_limit</c> value and add 347If you have more than one soundcard, add more <c>snd-card</c> and <c>snd-slot</c>
330more snd-card aliases to the file. I don't have experience with this, but you 348aliases and adjust the <c>cards_limit</c> value at the end of the file. You can
331can find examples for configurations with two or more soundcards in <uri 349find examples for configurations with two or more soundcards in <uri
332link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri> 350link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri>
333of the <uri 351of the <uri
334link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA 352link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA
335Howto</uri>. 353Howto</uri>.
336</note> 354</note>
345alias /dev/dsp snd-pcm-oss 363alias /dev/dsp snd-pcm-oss
346alias /dev/midi snd-seq-oss 364alias /dev/midi snd-seq-oss
347</pre> 365</pre>
348 366
349<p> 367<p>
350Now double-check the file <path>/etc/modules.d/alsa</path> and when you're sure 368After double-checking the file <path>/etc/modules.d/alsa</path> to make sure
351everyting is ok, run <c>modules-update</c>. 369everyting is ok, run <c>modules-update</c>.
352</p> 370</p>
353 371
354<pre caption="Running modules-update"> 372<pre caption="Running modules-update">
355# <i>modules-update</i> 373# <i>modules-update</i>
392<section> 410<section>
393<title>Adding alsasound to a runlevel</title> 411<title>Adding alsasound to a runlevel</title>
394<body> 412<body>
395 413
396<p> 414<p>
415An init script is provided for you which will install all neccessary sound drivers
416for your card (including the OSS support drivers if you set USE=oss). The first
397First thing to do now, is to make ALSA startup at boottime. Like this: 417thing to do now is to make ALSA startup at boot time:
398</p> 418</p>
399 419
400<pre caption="Add ALSA to the boot runlevel"> 420<pre caption="Add ALSA to the boot runlevel">
401# <i>rc-update add alsasound boot</i> 421# <i>rc-update add alsasound boot</i>
402</pre> 422</pre>
429 449
430<pre caption = "Running amixer"> 450<pre caption = "Running amixer">
431# <i>amixer</i> 451# <i>amixer</i>
432</pre> 452</pre>
433 453
454<!-- alsasound init script will do this for them now...
434<warn> 455<warn>
435You shouldn't get this, but <e>if</e> you get an error about "amixer: Mixer 456You shouldn't get this, but <e>if</e> you get an error about "amixer: Mixer
436attach default error: No such file or directory", you should manually modprobe 457attach default error: No such file or directory", you should manually modprobe
437<c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again. 458<c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again.
438</warn> 459</warn>
440<pre caption="Only if you get an error when running amixer"> 461<pre caption="Only if you get an error when running amixer">
441# <i>modprobe snd-mixer-oss</i> 462# <i>modprobe snd-mixer-oss</i>
442# <i>modprobe snd-pcm-oss</i> 463# <i>modprobe snd-pcm-oss</i>
443# <i>amixer</i> 464# <i>amixer</i>
444</pre> 465</pre>
466-->
445 467
446<p> 468<p>
447If you got this far, now unmute Master and PCM channels. Some hardware 469If you got this far, now unmute Master and PCM channels. Some hardware
448even requires you to unmute the center channel or even the surround 470even requires you to unmute the center channel or even the surround
449channel. 471channel.
465to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them 487to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them
466"just so". 488"just so".
467</p> 489</p>
468 490
469<p> 491<p>
470You may want to emerge <c>alsa-xmms</c> as that will provide ALSA support for
471XMMS.
472</p>
473
474<p>
475When you reboot your system, the <c>alsasound</c> init script will 492When you reboot your system, the <c>alsasound</c> init script will
476properly save and restore your volume settings. 493properly save and restore your volume settings.
477</p> 494</p>
495
496</body>
497</section>
498</chapter>
499
500<chapter>
501<title>MIDI Support</title>
502<section>
503<title>Hardware Synthesizer</title>
504<body>
505
506<p>
507Some sound cards (SBLive, Audigy, and others) come with onboard MIDI synthesizers.
508To use them, you must first install the <c>awesfx</c> package.
509</p>
510
511<pre caption="Install awesfx">
512# <i>emerge awesfx</i>
513</pre>
514
515<p>
516Now, you should place your sound fonts in <path>/usr/share/sfbank/</path>. You
517can probably get the sound fonts off of the windows driver CD for your sound card.
518With the SBLive, one of the included sound font files is called 8MBGMSFX.SF2.
519</p>
520
521<p>
522After copying over the sound font you want to use, you need to select it for use
523with <c>/usr/bin/sfxload</c>.
524</p>
525
526<pre caption="Selecting the sound font">
527# <i>/usr/bin/sfxload /usr/share/sfbank/8MBGMSFX.SF2</i>
528</pre>
529
530<note>
531You may wish to place this command in /etc/conf.d/local.start or in the startup
532script for your sound card (/etc/alsa.d/emu10k1) to make sure it gets loaded
533at startup.
534</note>
535
536</body>
537</section>
538<section>
539<title>Timidity++ Virtual Synthesizer</title>
540<body>
541
542<p>
543If your sound card does not come with a hardware synthesizer (or you don't
544want to use it), you can use <c>timidity++</c> to provide you with a virtual
545synthesizer. Start by emerging this package:
546</p>
547
548<pre caption="Installing Timidity++">
549# <i>emerge timidity++</i>
550</pre>
551
552<p>
553A sample configuration file will be installed for you in
554<path>/usr/share/timitidy/config/timidity.cfg</path>. If you don't have a
555timidity++ configuration setup yet, you can just use this one.
556</p>
557
558<pre caption="Use the default Timidity++ configuration file">
559# <i>cp /usr/share/timitidy/config/timidity.cfg /usr/share/timidity</i>
560</pre>
561
562<p>
563Now, you need to enable the init script to run when your system boots
564and enable it now.
565</p>
566
567<pre caption="Add timidity to default runlevel and start it now">
568# <i>rc-update add timidity default</i>
569# <i>/etc/init.d/timidity start</i>
570</pre>
571
572<p>
573Note that there is a configuration file for the init script that you can
574modify in <path>/etc/conf.d/timidity</path>, and sane defaults have been
575chosen for you.
576</p>
577
578</body>
579</section>
580<section>
581<title>Testing MIDI Support</title>
582<body>
583
584<p>
585You can use <c>pmidi</c> to test out your MIDI configuration. To do so,
586you need to first emerge its package.
587</p>
588
589<pre caption="Installing pmidi">
590# <i>emerge pmidi</i>
591</pre>
592
593<p>
594The '-l' command line option to pmidi will list all detected MIDI output ports,
595and '-p' can be used to select the one for playback. Check to see what
596MIDI output ports are available on your system:
597</p>
598
599<pre caption="Listed ports when using hardware sythisizer">
600# <i>pmidi -l</i>
601 Port Client name Port name
602 64:0 Rawmidi 0 - EMU10K1 MPU-401 (U EMU10K1 MPU-401 (UART)
603 65:0 Emu10k1 WaveTable Emu10k1 Port 0
604 65:1 Emu10k1 WaveTable Emu10k1 Port 1
605 65:2 Emu10k1 WaveTable Emu10k1 Port 2
606 65:3 Emu10k1 WaveTable Emu10k1 Port 3
607</pre>
608
609<pre caption="Listed ports when using Timidity++">
610# <i>pmidi -l</i>
611 Port Client name Port name
612 64:0 Rawmidi 0 - ES1371 ES1371
613128:0 TiMidity TiMidity port 0
614128:1 TiMidity TiMidity port 1
615128:2 TiMidity TiMidity port 2
616128:3 TiMidity TiMidity port 3
617</pre>
618
619<p>
620Now, try playing a MIDI file to make sure everything works:
621</p>
622
623<pre caption="Play a song">
624# <i>pmidi -p 65:0 Final\ Fantasy\ 7\ -\ Aerith\'s\ Theme.mid</i>
625or
626# <i>pmidi -p 128:0 Final\ Fantasy\ 7\ -\ Aerith\'s\ Theme.mid</i>
627</pre>
478 628
479</body> 629</body>
480</section> 630</section>
481</chapter> 631</chapter>
482 632
502</pre> 652</pre>
503 653
504</body> 654</body>
505</section> 655</section>
506<section> 656<section>
657<title>alsa-tools and alsa-firmware</title>
658<body>
659
660<p>
661The alsa-tools and alsa-firmware packages contain tools useful to only users of
662specific sound cards. Most users will not need these. If you do need alsa-tools,
663you can set the environment variable 'ALSA_TOOLS' to install just the needed tools
664for your card:
665</p>
666
667<pre caption="Installing alsa-tools">
668# <i>env ALSA_TOOLS='as10k1 ac3dec' emerge alsa-tools</i>
669</pre>
670
671</body>
672</section>
673<section>
674<title>Mixing versions</title>
675<body>
676
677<p>
678Often times, different versions of <c>alsa-driver</c>, <c>alsa-lib</c>,
679<c>alsa-utils</c>, <c>alsa-tools</c>, and <c>alsa-oss</c> will work with each
680other, but it is recommended that you try to keep the versions in sync.
681</p>
682
683</body>
684</section>
685<section>
507<title>/etc/modules.autoload</title> 686<title>/etc/modules.autoload</title>
508<body> 687<body>
509 688
510<p> 689<p>
511You won't have to edit this file for use with ALSA. After our <c>rc-update add 690You won't have to edit this file for use with ALSA. After doing <c>rc-update add
512alsasound boot</c>, our system will load the correct modules at startup. 691alsasound boot</c>, the correct modules will be loaded at startup.
513</p> 692</p>
514 693
694<!--
515<p> 695<p>
516It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this 696It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this
517file. Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this 697file. Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this
518FAQ</uri> for more info. 698FAQ</uri> for more info.
519</p> 699</p>
700-->
520 701
521</body> 702</body>
522</section> 703</section>
523<section> 704<section>
524<title>Known bugs</title> 705<title>Known bugs</title>

Legend:
Removed from v.1.25  
changed lines
  Added in v.1.26

  ViewVC Help
Powered by ViewVC 1.1.20