/[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.51 Revision 1.66
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.66 2006/05/01 05:52:31 fox2mike Exp $ -->
2 3
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 5
5<guide link="/doc/en/alsa-guide.xml"> 6<guide link="/doc/en/alsa-guide.xml">
6<title>Gentoo Linux ALSA Guide</title> 7<title>Gentoo Linux ALSA Guide</title>
7 8
8<author title="Author"> 9<author title="Author">
9 <mail link="fox2mike@gmail.com">Shyam Mani</mail> 10 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
10</author> 11</author>
11 12
12<abstract> 13<abstract>
13This document helps a user setup ALSA on Gentoo Linux. 14This document helps a user setup ALSA on Gentoo Linux.
14</abstract> 15</abstract>
15 16
16<!-- The content of this document is licensed under the CC-BY-SA license --> 17<!-- The content of this document is licensed under the CC-BY-SA license -->
17<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 18<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
18<license/> 19<license/>
19 20
20<version>2.0</version> 21<version>2.12</version>
21<date>2005-06-07</date> 22<date>2006-05-01</date>
22 23
23<chapter> 24<chapter>
24<title>Introduction</title> 25<title>Introduction</title>
25<section> 26<section>
26<title>What is ALSA?</title> 27<title>What is ALSA?</title>
68<warn> 69<warn>
69The methods shown below are mutually exclusive. You cannot have ALSA compiled 70The methods shown below are mutually exclusive. You cannot have ALSA compiled
70in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail. 71in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail.
71</warn> 72</warn>
72 73
73<impo>
74<c>genkernel</c> users have their config built such a way that the ALSA
75sub-system in the kernel is active. Therefore <c>genkernel</c> users can
76proceed to the <uri link="#alsa-utilities">ALSA Utilities</uri> section
77directly.
78</impo>
79
80<p> 74<p>
81The two options are : 75The two options are :
82</p> 76</p>
83 77
84<ol> 78<ol>
85 <li> 79 <li>
86 Use ALSA provided by your kernel. This is the preferred/recommended 80 Use ALSA provided by your kernel. This is the preferred/recommended
87 method. 81 method.
88 </li> 82 </li>
89 <li> 83 <li>
90 Use Gentoo's <c>media-sound/alsa-driver</c> package. 84 Use Gentoo's <c>media-sound/alsa-driver</c> package.
91 </li> 85 </li>
92</ol> 86</ol>
93 87
94<p> 88<p>
95We shall take a peek into both before finally deciding on one. 89We shall take a peek into both before finally deciding on one.
96</p> 90</p>
97 91
98<p> 92<p>
99If you were to use ALSA provided by the kernel, the following are the pros and 93If you were to use ALSA provided by the kernel, the following are the pros and
150 144
151<p> 145<p>
152The main difference between using <c>alsa-driver</c> and ALSA that comes with 146The main difference between using <c>alsa-driver</c> and ALSA that comes with
153the kernel is that <c>alsa-driver</c> is generally more up to date than the 147the kernel is that <c>alsa-driver</c> is generally more up to date than the
154version in the kernel. Since this does not make any huge difference as 148version in the kernel. Since this does not make any huge difference as
155such, you are encouraged to use the ALSA provided by the kernel. 149such, you are encouraged to use the ALSA provided by the kernel for ease of use.
150Before reporting any sound related issues to <uri
151link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to reproduce
152them using <c>alsa-driver</c> and file the bug report no matter what the
153result.
156</p> 154</p>
157 155
158</body> 156</body>
159</section> 157</section>
160<section id="lspci"> 158<section id="lspci">
161<title>Before you proceed</title> 159<title>Before you proceed</title>
162<body> 160<body>
163 161
164<p> 162<p>
165Whichever method of install you choose, you need to know what drivers your 163Whichever method of install you choose, you need to know what drivers your
164sound card uses. In most cases, sound cards (onboard and otherwise) are PCI
166sound card uses. <c>lspci</c> will help you in digging out the required 165based and <c>lspci</c> will help you in digging out the required information.
167information. Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if 166Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it
168you don't have it installed already. We now proceed to find out details about 167installed already. In case you have a USB sound card, <c>lsusb</c> from
169the sound card. 168<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using
169<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users
170with ISA based sound cards.
171</p>
172
173<ul>
174 <li>
175 <uri link="http://www.roestock.demon.co.uk/isapnptools/">The ISAPNPTOOLS
176 Page</uri>
177 </li>
178 <li>
179 <uri link="http://www2.linuxjournal.com/article/3269">LinuxJournal PnP
180 Article</uri>
181 </li>
182 <li>
183 <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/x320.html">TLDP Sound
184 HowTo</uri>
185 </li>
186</ul>
187
188<note>
189For ease of use/explanation, we assume the user has a PCI based sound card for
190the remainder of this guide.
191</note>
192
193<p>
194We now proceed to find out details about the sound card.
170</p> 195</p>
171 196
172<pre caption="Soundcard Details"> 197<pre caption="Soundcard Details">
173# <i>lspci -v | grep -i audio</i> 198# <i>lspci -v | grep -i audio</i>
1740000:00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06) 1990000:00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
205 230
206<p> 231<p>
207Let us now configure the kernel to enable ALSA. 232Let us now configure the kernel to enable ALSA.
208</p> 233</p>
209 234
235<impo>
236<c>genkernel</c> users should now run <c>genkernel --menuconfig all</c> and
237then follow the instructions in <uri link="#doc_chap2_pre3">Kernel Options for
238ALSA</uri>.
239</impo>
240
210<pre caption="Heading over to the source"> 241<pre caption="Heading over to the source">
211# <i>cd /usr/src/linux</i> 242# <i>cd /usr/src/linux</i>
212# <i>make menuconfig</i> 243# <i>make menuconfig</i>
213</pre> 244</pre>
214 245
220<p> 251<p>
221Now we will look at some of the options we will have to enable in the 2.6 252Now we will look at some of the options we will have to enable in the 2.6
222kernel to ensure proper ALSA support for our sound card. 253kernel to ensure proper ALSA support for our sound card.
223</p> 254</p>
224 255
225<note> 256<p>
226Please note that for the sake of ease, all examples show a modular kernel. It 257Please note that for the sake of ease, all examples show ALSA built as modules.
227is advisable to follow the same. Please do <e>not</e> skip the 258It is advisable to follow the same as it then allows the use of <c>alsaconf</c>
259which is a boon when you want to configure your card. Please do <e>not</e> skip
228<uri link="#alsa-config">Configuration</uri> section of this document. If 260the <uri link="#alsa-config">Configuration</uri> section of this document. If
229you still like to have options built-in, ensure that you make changes to your 261you still like to have options built-in, ensure that you make changes to your
230config accordingly. 262config accordingly.
231</note> 263</p>
232 264
233<pre caption="Kernel Options for ALSA"> 265<pre caption="Kernel Options for ALSA">
234Device Drivers ---&gt; 266Device Drivers ---&gt;
235 Sound ---&gt; 267 Sound ---&gt;
236 268
277USB Devices ---&gt; 309USB Devices ---&gt;
278</pre> 310</pre>
279 311
280<p> 312<p>
281Now that your options are set, you can (re)compile the kernel and ALSA support 313Now that your options are set, you can (re)compile the kernel and ALSA support
282for your card should be functional once you reboot into the new kernel. 314for your card should be functional once you reboot into the new kernel. Don't
315forget to update your GRUB configuration to use the newly built kernel.
283You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and 316You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
284see if everything is working as it should. 317see if everything is working as it should.
285</p> 318</p>
286 319
287</body> 320</body>
305</p> 338</p>
306 339
307<pre caption="Adding ALSA_CARDS to make.conf"> 340<pre caption="Adding ALSA_CARDS to make.conf">
308<comment>(For one sound card)</comment> 341<comment>(For one sound card)</comment>
309ALSA_CARDS="emu10k1" 342ALSA_CARDS="emu10k1"
310<comment>(For more than one, seperate names with spaces)</comment> 343<comment>(For more than one, separate names with spaces)</comment>
311ALSA_CARDS="emu10k1 via82xx" 344ALSA_CARDS="emu10k1 via82xx"
312</pre> 345</pre>
313 346
314<p> 347<p>
315If you have compiled your kernel and want to use <c>alsa-driver</c>, please 348If you have compiled your kernel and want to use <c>alsa-driver</c>, please
316ensure the following before proceeding, else <c>alsa-driver</c> is likely to 349ensure the following before proceeding, else <c>alsa-driver</c> is likely to
317fail. The next code listing gives you one way of performing the checks. 350fail. The next code listing gives you one way of performing the checks.
318</p> 351</p>
352
353<note>
354<c>genkernel</c> users can proceed with <uri link="#doc_chap2_pre6">Installing
355alsa-driver</uri> as their configuration is in sync with the one shown below by
356default.
357</note>
319 358
320<ol> 359<ol>
321 <li> 360 <li>
322 <c>CONFIG_SOUND</c> is set. (Basic Sound support enabled) 361 <c>CONFIG_SOUND</c> is set. (Basic Sound support enabled)
323 </li> 362 </li>
344<comment>(and 3. is true)</comment> 383<comment>(and 3. is true)</comment>
345CONFIG_SND is not set 384CONFIG_SND is not set
346</pre> 385</pre>
347 386
348<p> 387<p>
349Now all you have to do is type the magic words...and no, its not abracadabra. 388Now all you have to do is type the magic words... and no, it's not abracadabra.
350</p> 389</p>
351 390
352<pre caption="Installing alsa-driver"> 391<pre caption="Installing alsa-driver">
353# <i>emerge alsa-driver</i> 392# <i>emerge alsa-driver</i>
354</pre> 393</pre>
409<p> 448<p>
410You will now see a neat menu guided interface that will automatically probe 449You will now see a neat menu guided interface that will automatically probe
411your devices and try to find out your sound card. You will be asked to pick 450your devices and try to find out your sound card. You will be asked to pick
412your sound card from a list. Once that's done, it will ask you permission to 451your sound card from a list. Once that's done, it will ask you permission to
413automatically make required changes to <path>/etc/modules.d/alsa</path>. 452automatically make required changes to <path>/etc/modules.d/alsa</path>.
414It will then adjust your volume settings to optimum levels and run 453It will then adjust your volume settings to optimum levels, run
415<c>modules-update</c> and starts the <path>/etc/init.d/alsasound</path> 454<c>modules-update</c> and start the <path>/etc/init.d/alsasound</path> service.
416service. Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA 455Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA
417initscript. 456initscript.
418</p> 457</p>
419 458
420</body> 459</body>
421</section> 460</section>
425 464
426<p> 465<p>
427We're now almost all setup. Whichever method you chose to install ALSA, you'll 466We're now almost all setup. Whichever method you chose to install ALSA, you'll
428need to have something load your modules or initialize ALSA and restore your 467need to have something load your modules or initialize ALSA and restore your
429volume settings when your system comes up. The ALSA Initscript handles all of 468volume settings when your system comes up. The ALSA Initscript handles all of
430this for you and is called <c>alsasound</c>. Add it to the default run-level. 469this for you and is called <c>alsasound</c>. Add it to the boot runlevel.
431</p> 470</p>
432 471
433<pre caption="Adding ALSA to default"> 472<pre caption="Adding ALSA to the boot runlevel">
434# <i>rc-update add alsasound default</i> 473# <i>rc-update add alsasound boot</i>
435 * alsasound added to runlevel default 474 * alsasound added to runlevel boot
436 * rc-update complete. 475 * rc-update complete.
437</pre> 476</pre>
438 477
439<p> 478<p>
440Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that 479Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that
443</p> 482</p>
444 483
445</body> 484</body>
446</section> 485</section>
447<section> 486<section>
487<title>Audio Group</title>
488<body>
489
490<p>
491Before we move on to testing, there's one last <e>important</e> thing that needs
492to be setup. Rule of thumb in a *nix OS : Do not run as root unless needed.
493This applies here as well ;) How? Well, most of the times you should be logged
494in as a user and would like to listen to music or access your soundcard. For
495that to happen, you need to be in the "audio" group. At this point, we'll add
496users to the audio group, so that they won't have any issues when they want to
497access sound devices. We'll use <c>gpasswd</c> here and you need to be logged in
498as root for this to work.
499</p>
500
501<pre caption="Adding users to the audio group">
502<comment>(Substitute &lt;username&gt; with your user)</comment>
503# <i>gpasswd -a &lt;username&gt; audio </i>
504Adding user &lt;username&gt; to group audio
505</pre>
506
507</body>
508</section>
509<section>
448<title>Volume Check!</title> 510<title>Volume Check!</title>
449<body> 511<body>
450 512
451<p> 513<p>
452We've completed all the setups and pre-requisites, so let's fire up ALSA. If 514We've completed all the setups and pre-requisites, so let's fire up ALSA. If
453you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already 515you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
454does this for you. 516does this for you.
455</p> 517</p>
456 518
457<pre caption="Start the service"> 519<pre caption="Start the service">
458<comment>(Modular Kernels)</comment> 520<comment>(ALSA as modules)</comment>
459# <i>/etc/init.d/alsasound start</i> 521# <i>/etc/init.d/alsasound start</i>
460 * Loading ALSA modules ... 522 * Loading ALSA modules ...
461 * Loading: snd-card-0 ... [ ok ] 523 * Loading: snd-card-0 ... [ ok ]
462 * Loading: snd-pcm-oss ... [ ok ] 524 * Loading: snd-pcm-oss ... [ ok ]
463 * Loading: snd-seq ... [ ok ] 525 * Loading: snd-seq ... [ ok ]
464 * Loading: snd-emu10k1-synth ... [ ok ] 526 * Loading: snd-emu10k1-synth ... [ ok ]
465 * Loading: snd-seq-midi ... [ ok ] 527 * Loading: snd-seq-midi ... [ ok ]
466 * Restoring Mixer Levels ... [ ok ] 528 * Restoring Mixer Levels ... [ ok ]
467<comment>(ALSA compiled in)</comment> 529<comment>(ALSA compiled in)</comment>
468# <i>/etc/init.d/alsasound start</i> 530# <i>/etc/init.d/alsasound start</i>
469 * Loading ALSA modules ... 531 * Loading ALSA modules ...
470 * Restoring Mixer Levels ... [ ok ] 532 * Restoring Mixer Levels ... [ ok ]
471</pre> 533</pre>
472 534
473<p> 535<p>
474Now that the required things have been take care of, we need to check up on 536Now that the required things have been taken care of, we need to check up on
475the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this purpose. 537the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this
538purpose.
476</p> 539</p>
477 540
478<pre caption="Starting alsamixer"> 541<pre caption="Starting alsamixer">
479<comment>(Opens up a console program. Only required settings are shown)</comment> 542<comment>(Opens up a console program. Only required settings are shown)</comment>
480# <i>alsamixer</i> 543# <i>alsamixer</i>
481</pre> 544</pre>
545
546<impo>
547If you have issues starting up <c>alsamixer</c> and get errors such as
548alsamixer: function snd_ctl_open failed for default: No such file or directory,
549this is usually an issue with udev setting up the devices. Run <c>killall
550udevd; udevstart</c> to reload <path>/dev</path> entries and fire up
551<c>alsamixer</c>. It should solve the issue.
552</impo>
482 553
483<p> 554<p>
484This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay 555This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay
485attention to the Master and PCM channels which both have an MM below them. 556attention to the Master and PCM channels which both have an MM below them.
486That means they are muted. If you try to play anything with <c>alsamixer</c> 557That means they are muted. If you try to play anything with <c>alsamixer</c>
492<p> 563<p>
493Now, we shall unmute the channels, and set volume levels as needed. 564Now, we shall unmute the channels, and set volume levels as needed.
494</p> 565</p>
495 566
496<warn> 567<warn>
497Both Master <e>and</e> PCM need to be unmuted and set to audible volume levels if 568Both Master <e>and</e> PCM need to be unmuted and set to audible volume levels
498you want to hear some output on your speakers. 569if you want to hear some output on your speakers.
499</warn> 570</warn>
500 571
501<ul> 572<ul>
502 <li> 573 <li>
503 To move between channels, use your left and right arrow keys. (&lt;- 574 To move between channels, use your left and right arrow keys. (&lt;-
532<section> 603<section>
533<title>Sound Check!</title> 604<title>Sound Check!</title>
534<body> 605<body>
535 606
536<p> 607<p>
537Finally. Some music. If everything above is perfect, you should be able to now 608Finally. Some music. If everything above is perfect, you should now be able to
538listen to some good music. A quick way to test is to use a command line tool 609listen to some good music. A quick way to test is to use a command line tool
539like <c>media-sound/madplay</c>. You could also use something more well known 610like <c>media-sound/madplay</c>. You could also use something more well known
540like <c>mpg123</c> or <c>xmms</c>. If you are an ogg fan, you could use 611like <c>mpg123</c> or <c>xmms</c>. If you are an ogg fan, you could use
541<c>ogg123</c> provided by <c>media-sound/vorbis-tools</c>. Use any player you 612<c>ogg123</c> provided by <c>media-sound/vorbis-tools</c>. Use any player you
542are comfortable with. As always, <c>emerge</c> what you need. 613are comfortable with. As always, <c>emerge</c> what you need.
543</p> 614</p>
544 615
579</pre> 650</pre>
580 651
581</body> 652</body>
582</section> 653</section>
583<section> 654<section>
655<title>ALSA and USE</title>
656<body>
657
658<p>
659You can now add the <c>alsa</c> use flag to <path>/etc/make.conf</path> to
660ensure that your applications that support ALSA get built with it. Some
661architectures like x86 and amd64 have the flag enabled by default.
662</p>
663
664</body>
665</section>
666<section>
584<title>Issues?</title> 667<title>Issues?</title>
585<body> 668<body>
586 669
587<p> 670<p>
588If for some reason you're unable to hear sound, the first thing to do would 671If for some reason you're unable to hear sound, the first thing to do would
589be to check your <uri link="#doc_chap3_pre5">alsamixer</uri> settings. 80% of 672be to check your <uri link="#doc_chap3_pre6">alsamixer</uri> settings. 80% of
590the issues lie with muted channels or low volume. Also check your Window 673the issues lie with muted channels or low volume. Also check your Window
591Manager's sound applet and verify that volumes are set to audible levels. 674Manager's sound applet and verify that volumes are set to audible levels.
592</p> 675</p>
593 676
594<p> 677<p>
634 717
635Mixers: 718Mixers:
6360: SigmaTel STAC9721/23 7190: SigmaTel STAC9721/23
637</pre> 720</pre>
638 721
722<p>
723The other most common issue users face is the dreaded "Unknown symbol in module"
724error. An example of the same is shown below.
725</p>
726
727<pre caption="Unknown Symbol in module error">
728# <i>/etc/init.d/alsasound start</i>
729 * Loading ALSA modules ...
730 * Loading: snd-card-0 ... [ ok ]
731 * Loading: snd-pcm-oss ...
732WARNING: Error inserting snd_mixer_oss
733(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown
734symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting
735snd_pcm_oss
736(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-pcm-oss.ko): Unknown
737symbol in module, or unknown parameter (see dmesg)
738 [ !! ]
739 * Loading: snd-mixer-oss ...
740FATAL: Error inserting snd_mixer_oss
741(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown
742symbol in module, or unknown parameter (see dmesg)
743 [ !! ]
744 * Loading: snd-seq ... [ ok ]
745 * Loading: snd-emu10k1-synth ... [ ok ]
746 * Loading: snd-seq-midi ... [ ok ]
747 * Restoring Mixer Levels ... [ ok ]
748</pre>
749
750<p>
751And when you take a look at <c>dmesg</c> as suggested, you're quite likely to
752see:
753</p>
754
755<pre caption="dmesg output">
756<comment>(Only relevant portions are shown below)</comment>
757# <i>dmesg | less</i>
758ACPI: PCI Interrupt 0000:02:06.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 209
759snd_mixer_oss: Unknown symbol snd_unregister_oss_device
760snd_mixer_oss: Unknown symbol snd_register_oss_device
761snd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback
762snd_mixer_oss: Unknown symbol snd_oss_info_register
763snd_pcm_oss: Unknown symbol snd_unregister_oss_device
764snd_pcm_oss: Unknown symbol snd_register_oss_device
765snd_pcm_oss: Unknown symbol snd_mixer_oss_ioctl_card
766snd_pcm_oss: Unknown symbol snd_oss_info_register
767snd_mixer_oss: Unknown symbol snd_unregister_oss_device
768snd_mixer_oss: Unknown symbol snd_register_oss_device
769snd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback
770snd_mixer_oss: Unknown symbol snd_oss_info_register
771</pre>
772
773<p>
774The above issue is caused when you switch from <c>alsa-driver</c> to in-kernel
775ALSA because when you unmerge <c>alsa-driver</c> the module files are config
776protected and hence get left behind. So, when you switch to in-kernel
777drivers, running <c>modprobe</c> gives you a mix of <c>alsa-driver</c> and
778in-kernel modules thus causing the above errors.
779</p>
780
781<p>
782The solution is quite easy. We just need to manually remove the problem causing
783directory after you unmerge <c>alsa-driver</c>. Be sure to remove the correct
784kernel version and not the current one!
785</p>
786
787<pre caption="Removing the alsa-driver modules">
788<comment>(Replace KERNELVER with your kernel version)</comment>
789# <i>rm -rf /lib/modules/KERNELVER/alsa-driver</i>
790</pre>
791
792<p>
793Another reason for error messages similar to the ones above could be a file in
794<path>/etc/modules.d</path> supplying a <c>device_node</c> parameter when it
795isn't required. Confirm that this is indeed the issue and find out which file
796is the culprit.
797</p>
798
799<pre caption="Confirming and searching for device_node">
800<comment>(Check dmesg to confirm)</comment>
801# <i>dmesg | grep device_mode</i>
802snd: Unknown parameter `device_mode'
803<comment>(Now, to get to the source of the issue)</comment>
804# <i>grep device_mode /etc/modules.d/*</i>
805</pre>
806
807<p>
808Usually it is a file called <path>alsa</path> with the line <c>options snd
809device_mode=0666</c>. Remove this line and restart the alsasound service and
810that should take care of this issue.
811</p>
812
639</body> 813</body>
640</section> 814</section>
641</chapter> 815</chapter>
642 816
643<chapter> 817<chapter>
678change the path to suit your machine. 852change the path to suit your machine.
679</note> 853</note>
680 854
681<pre caption="Loading Soundfonts"> 855<pre caption="Loading Soundfonts">
682<comment>(First, copy the Soundfont)</comment> 856<comment>(First, copy the Soundfont)</comment>
683# <i>cp /mnt/win2k/Program\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i> 857# <i>cp /mnt/win2k/Program\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
858<comment>(Or get it from your SoundBlaster CD)</comment>
859# <i>cp /mnt/cdrom/AUDIO/ENGLISH/SFBANK/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
684<comment>(We load the specific Soundfont)</comment> 860<comment>(We load the specific Soundfont)</comment>
685# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i> 861# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i>
686</pre> 862</pre>
687 863
688<p> 864<p>
723For timidity to play sounds, it needs a sound font. If you do not have any, 899For timidity to play sounds, it needs a sound font. If you do not have any,
724install <c>timidity-eawpatches</c> or <c>timidity-shompatches</c> which will 900install <c>timidity-eawpatches</c> or <c>timidity-shompatches</c> which will
725give you some sound fonts. You can have multiple sound font configurations 901give you some sound fonts. You can have multiple sound font configurations
726installed, and you can place your own in <path>/usr/share/timidity/</path>. 902installed, and you can place your own in <path>/usr/share/timidity/</path>.
727To switch between different timidity configurations, you should use the 903To switch between different timidity configurations, you should use the
728<e>timidity-update</e> tool provided in the timidity++ package. 904<c>timidity-update</c> tool provided in the timidity++ package.
729</p> 905</p>
730 906
731<pre caption="Installing sound fonts"> 907<pre caption="Installing sound fonts">
732# <i>emerge timidity-eawpatches</i> 908# <i>emerge timidity-eawpatches</i>
733# <i>timidity-update -g -s eawpatches</i> 909# <i>timidity-update -g -s eawpatches</i>

Legend:
Removed from v.1.51  
changed lines
  Added in v.1.66

  ViewVC Help
Powered by ViewVC 1.1.20