* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-07-12 19:17 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2005-07-12 19:17 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/07/12 19:17:38
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
#95574, #98429 - Updates + Fixes to the guide. Added sections on the Audio Group and more info regarding USB + ISA sound cards. #92711 went to RESO FIXED, so genkernel information was updated to reflect the corresponding changes. Thanks to Daniel Drake(dsd), Arun Raghavan (for ISA input), Miles Lubin, Jason Bucata, Deathwing00, alin, rane, LinuxBlues on IRC for helping with proofing and corrections.
Revision Changes Path
1.54 +136 -38 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.54&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.54&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.53&r2=1.54&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- alsa-guide.xml 8 Jun 2005 19:54:07 -0000 1.53
+++ alsa-guide.xml 12 Jul 2005 19:17:38 -0000 1.54
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.53 2005/06/08 19:54:07 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.54 2005/07/12 19:17:38 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -15,11 +15,11 @@
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.2</version>
-<date>2005-06-09</date>
+<version>2.3</version>
+<date>2005-07-12</date>
<chapter>
<title>Introduction</title>
@@ -71,13 +71,6 @@
in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail.
</warn>
-<impo>
-<c>genkernel</c> users have their config built such a way that the ALSA
-sub-system in the kernel is active. Therefore <c>genkernel</c> users can
-proceed to the <uri link="#alsa-utilities">ALSA Utilities</uri> section
-directly.
-</impo>
-
<p>
The two options are :
</p>
@@ -164,10 +157,37 @@
<p>
Whichever method of install you choose, you need to know what drivers your
-sound card uses. <c>lspci</c> will help you in digging out the required
-information. Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if
-you don't have it installed already. We now proceed to find out details about
-the sound card.
+sound card uses. In most cases, sound cards (onboard and otherwise) are PCI
+based and <c>lspci</c> will help you in digging out the required information.
+Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it
+installed already. In case you have a USB sound card, <c>lsusb</c> from
+<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using
+<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users
+with ISA based sound cards.
+</p>
+
+<ul>
+ <li>
+ <uri link="http://www.roestock.demon.co.uk/isapnptools/">The ISAPNPTOOLS
+ Page</uri>
+ </li>
+ <li>
+ <uri link="http://www2.linuxjournal.com/article/3269">LinuxJournal PnP
+ Article</uri>
+ </li>
+ <li>
+ <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/x320.html">TLDP Sound
+ HowTo</uri>
+ </li>
+</ul>
+
+<note>
+For ease of use/explanation, we assume the user has a PCI based sound card for
+the remainder of this guide.
+</note>
+
+<p>
+We now proceed to find out details about the sound card.
</p>
<pre caption="Soundcard Details">
@@ -208,6 +228,11 @@
Let us now configure the kernel to enable ALSA.
</p>
+<impo>
+<c>genkernel</c> users should now run <c>genkernel --menuconfig</c> and then follow
+the instructions in <uri link="#doc_chap2_pre3">Kernel Options for ALSA</uri>.
+</impo>
+
<pre caption="Heading over to the source">
# <i>cd /usr/src/linux</i>
# <i>make menuconfig</i>
@@ -223,13 +248,14 @@
kernel to ensure proper ALSA support for our sound card.
</p>
-<note>
-Please note that for the sake of ease, all examples show a modular kernel. It
-is advisable to follow the same. Please do <e>not</e> skip the
-<uri link="#alsa-config">Configuration</uri> section of this document. If
-you still like to have options built-in, ensure that you make changes to your
-config accordingly.
-</note>
+<p>
+Please note that for the sake of ease, all examples show ALSA built as modules.
+It is advisable to follow the same as it then allows the use of <c>alsaconf</c>
+which is a boon when you want to configure your card. Please do <e>not</e> skip the <uri
+link="#alsa-config">Configuration</uri> section of this document. If you still
+like to have options built-in, ensure that you make changes to your config
+accordingly.
+</p>
<pre caption="Kernel Options for ALSA">
Device Drivers --->
@@ -318,6 +344,12 @@
fail. The next code listing gives you one way of performing the checks.
</p>
+<note>
+<c>genkernel</c> users can proceed with <uri link="#doc_chap2_pre6">Installing
+alsa-driver</uri> as their configuration is in sync with the one shown below by
+default.
+</note>
+
<ol>
<li>
<c>CONFIG_SOUND</c> is set. (Basic Sound support enabled)
@@ -347,7 +379,7 @@
</pre>
<p>
-Now all you have to do is type the magic words...and no, its not abracadabra.
+Now all you have to do is type the magic words... and no, it's not abracadabra.
</p>
<pre caption="Installing alsa-driver">
@@ -412,10 +444,9 @@
your devices and try to find out your sound card. You will be asked to pick
your sound card from a list. Once that's done, it will ask you permission to
automatically make required changes to <path>/etc/modules.d/alsa</path>.
-It will then adjust your volume settings to optimum levels and run
-<c>modules-update</c> and starts the <path>/etc/init.d/alsasound</path>
-service. Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA
-initscript.
+It will then adjust your volume settings to optimum levels, run
+<c>modules-update</c> and start the <path>/etc/init.d/alsasound</path> service.
+Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA initscript.
</p>
</body>
@@ -432,8 +463,8 @@
</p>
<pre caption="Adding ALSA to default">
-# <i>rc-update add alsasound default</i>
- * alsasound added to runlevel default
+# <i>rc-update add alsasound boot</i>
+ * alsasound added to runlevel boot
* rc-update complete.
</pre>
@@ -446,6 +477,29 @@
</body>
</section>
<section>
+<title>Audio Group</title>
+<body>
+
+<p>
+Before we move on to testing, there's one last <e>important</e> thing that needs
+to be setup. Rule of thumb in a *nix OS : Do not run as root unless needed.
+This applies here as well ;) How? Well, most of the times you should be logged
+in as a user and would like to listen to music or access your soundcard. For
+that to happen, you need to be in the "audio" group. At this point, we'll add
+users to the audio group, so that they won't have any issues when they want to
+access sound devices. We'll use <c>gpasswd</c> here and you need to be logged in
+as root for this to work.
+</p>
+
+<pre caption="Adding users to the audio group">
+<comment>(Substitute <username> with your user)</comment>
+# <i>gpasswd -a <username> audio </i>
+Adding user <username> to group audio
+</pre>
+
+</body>
+</section>
+<section>
<title>Volume Check!</title>
<body>
@@ -456,7 +510,7 @@
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-07-14 9:05 Sven Vermeulen
0 siblings, 0 replies; 26+ messages in thread
From: Sven Vermeulen @ 2005-07-14 9:05 UTC (permalink / raw
To: gentoo-doc-cvs
swift 05/07/14 09:05:36
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
When you add something to the boot run level, you add it to the boot run level :)
Revision Changes Path
1.55 +4 -4 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.55&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.55&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.54&r2=1.55&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- alsa-guide.xml 12 Jul 2005 19:17:38 -0000 1.54
+++ alsa-guide.xml 14 Jul 2005 09:05:36 -0000 1.55
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.54 2005/07/12 19:17:38 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.55 2005/07/14 09:05:36 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.3</version>
-<date>2005-07-12</date>
+<version>2.4</version>
+<date>2005-07-14</date>
<chapter>
<title>Introduction</title>
@@ -459,7 +459,7 @@
We're now almost all setup. Whichever method you chose to install ALSA, you'll
need to have something load your modules or initialize ALSA and restore your
volume settings when your system comes up. The ALSA Initscript handles all of
-this for you and is called <c>alsasound</c>. Add it to the default run-level.
+this for you and is called <c>alsasound</c>. Add it to the boot run-level.
</p>
<pre caption="Adding ALSA to default">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-07-14 9:11 Xavier Neys
0 siblings, 0 replies; 26+ messages in thread
From: Xavier Neys @ 2005-07-14 9:11 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 05/07/14 09:11:02
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
When you add something to the boot run level, you add it to the boot run level :)
Indeed!
Revision Changes Path
1.56 +4 -4 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.56&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.56&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.55&r2=1.56&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- alsa-guide.xml 14 Jul 2005 09:05:36 -0000 1.55
+++ alsa-guide.xml 14 Jul 2005 09:11:02 -0000 1.56
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.55 2005/07/14 09:05:36 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.56 2005/07/14 09:11:02 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,7 +18,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.4</version>
+<version>2.5</version>
<date>2005-07-14</date>
<chapter>
@@ -459,10 +459,10 @@
We're now almost all setup. Whichever method you chose to install ALSA, you'll
need to have something load your modules or initialize ALSA and restore your
volume settings when your system comes up. The ALSA Initscript handles all of
-this for you and is called <c>alsasound</c>. Add it to the boot run-level.
+this for you and is called <c>alsasound</c>. Add it to the boot runlevel.
</p>
-<pre caption="Adding ALSA to default">
+<pre caption="Adding ALSA to the boot runlevel">
# <i>rc-update add alsasound boot</i>
* alsasound added to runlevel boot
* rc-update complete.
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-07-14 19:22 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2005-07-14 19:22 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/07/14 19:22:54
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
#98772 - Addition of stuff to appease the sound team ;)
Revision Changes Path
1.57 +7 -3 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.57&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.57&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.56&r2=1.57&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- alsa-guide.xml 14 Jul 2005 09:11:02 -0000 1.56
+++ alsa-guide.xml 14 Jul 2005 19:22:54 -0000 1.57
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.56 2005/07/14 09:11:02 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.57 2005/07/14 19:22:54 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,7 +18,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.5</version>
+<version>2.6</version>
<date>2005-07-14</date>
<chapter>
@@ -146,7 +146,11 @@
The main difference between using <c>alsa-driver</c> and ALSA that comes with
the kernel is that <c>alsa-driver</c> is generally more up to date than the
version in the kernel. Since this does not make any huge difference as
-such, you are encouraged to use the ALSA provided by the kernel.
+such, you are encouraged to use the ALSA provided by the kernel for ease of use.
+Before reporting any sound related issues to <uri
+link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to reproduce
+them using <c>alsa-driver</c> and file the bug report no matter what the
+result.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-07-16 11:45 Alin Dobre
0 siblings, 0 replies; 26+ messages in thread
From: Alin Dobre @ 2005-07-16 11:45 UTC (permalink / raw
To: gentoo-doc-cvs
alin 05/07/16 11:45:41
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
- killing a program with KILL (-9) signal is recommended only when it's
really necesarry. Instead, using the default signal (TERM) should kill
[in this case] udevd without any problems. Also, -9 may cause an unclean
exit for the program (if it does not handle the signal properly).
- surrounded /dev with <path>
Revision Changes Path
1.58 +6 -6 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.58&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.58&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.57&r2=1.58&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- alsa-guide.xml 14 Jul 2005 19:22:54 -0000 1.57
+++ alsa-guide.xml 16 Jul 2005 11:45:41 -0000 1.58
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.57 2005/07/14 19:22:54 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.58 2005/07/16 11:45:41 alin Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.6</version>
-<date>2005-07-14</date>
+<version>2.7</version>
+<date>2005-07-16</date>
<chapter>
<title>Introduction</title>
@@ -543,9 +543,9 @@
<impo>
If you have issues starting up <c>alsamixer</c> and get errors such as
alsamixer: function snd_ctl_open failed for default: No such file or directory,
-this is usually an issue with udev setting up the devices. Run <c>killall -9
-udevd; udevstart</c> to reload /dev entries and fire up <c>alsamixer</c>. It
-should solve the issue.
+this is usually an issue with udev setting up the devices. Run <c>killall
+udevd; udevstart</c> to reload <path>/dev</path> entries and fire up
+<c>alsamixer</c>. It should solve the issue.
</impo>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-07-26 17:28 Marcelo Goes
0 siblings, 0 replies; 26+ messages in thread
From: Marcelo Goes @ 2005-07-26 17:28 UTC (permalink / raw
To: gentoo-doc-cvs
vanquirius 05/07/26 17:28:11
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
fix a couple of typos
Revision Changes Path
1.59 +6 -6 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.59&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.59&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.58&r2=1.59&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- alsa-guide.xml 16 Jul 2005 11:45:41 -0000 1.58
+++ alsa-guide.xml 26 Jul 2005 17:28:11 -0000 1.59
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.58 2005/07/16 11:45:41 alin Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.59 2005/07/26 17:28:11 vanquirius Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,7 +19,7 @@
<license/>
<version>2.7</version>
-<date>2005-07-16</date>
+<date>2005-07-26</date>
<chapter>
<title>Introduction</title>
@@ -338,7 +338,7 @@
<pre caption="Adding ALSA_CARDS to make.conf">
<comment>(For one sound card)</comment>
ALSA_CARDS="emu10k1"
-<comment>(For more than one, seperate names with spaces)</comment>
+<comment>(For more than one, separate names with spaces)</comment>
ALSA_CARDS="emu10k1 via82xx"
</pre>
@@ -489,7 +489,7 @@
to be setup. Rule of thumb in a *nix OS : Do not run as root unless needed.
This applies here as well ;) How? Well, most of the times you should be logged
in as a user and would like to listen to music or access your soundcard. For
-that to happen, you need to be in the "audio" group. At this point, we'll add
+that to happen, you need to be in the "audio" group. At this point, we'll add
users to the audio group, so that they won't have any issues when they want to
access sound devices. We'll use <c>gpasswd</c> here and you need to be logged in
as root for this to work.
@@ -607,7 +607,7 @@
configured and working.
</p>
-<pre caption="Bring on th static">
+<pre caption="Bring on the static">
# <i>cat /dev/urandom > /dev/dsp</i>
</pre>
@@ -672,7 +672,7 @@
</body>
</section>
<section>
-<title> ALSA and USE</title>
+<title>ALSA and USE</title>
<body>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-08-30 11:38 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2005-08-30 11:38 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/08/30 11:38:03
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
Fixed genkernel command options. genkernel --menuconfig is wrong.
Revision Changes Path
1.60 +4 -4 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.60&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.60&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.59&r2=1.60&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- alsa-guide.xml 26 Jul 2005 17:28:11 -0000 1.59
+++ alsa-guide.xml 30 Aug 2005 11:38:02 -0000 1.60
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.59 2005/07/26 17:28:11 vanquirius Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.60 2005/08/30 11:38:02 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.7</version>
-<date>2005-07-26</date>
+<version>2.8</version>
+<date>2005-08-30</date>
<chapter>
<title>Introduction</title>
@@ -233,7 +233,7 @@
</p>
<impo>
-<c>genkernel</c> users should now run <c>genkernel --menuconfig</c> and then follow
+<c>genkernel</c> users should now run <c>genkernel --menuconfig all</c> and then follow
the instructions in <uri link="#doc_chap2_pre3">Kernel Options for ALSA</uri>.
</impo>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-09-09 6:49 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2005-09-09 6:49 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/09/09 06:49:31
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
#102891 - Added info about the Unknown Symbol in module error thanks to dsd. Added another location to get soundfont file (from the SB CD), thanks to Robert Millan for the hint.
Revision Changes Path
1.61 +76 -4 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.61&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.61&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.60&r2=1.61&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- alsa-guide.xml 30 Aug 2005 11:38:02 -0000 1.60
+++ alsa-guide.xml 9 Sep 2005 06:49:31 -0000 1.61
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.60 2005/08/30 11:38:02 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.61 2005/09/09 06:49:31 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.8</version>
-<date>2005-08-30</date>
+<version>2.9</version>
+<date>2005-09-09</date>
<chapter>
<title>Introduction</title>
@@ -739,6 +739,76 @@
0: SigmaTel STAC9721/23
</pre>
+<p>
+The other most common issue users face is the dreaded "Unknown symbol in module"
+error. An example of the same is shown below.
+</p>
+
+<pre caption="Unknown Symbol in module error">
+# <i>/etc/init.d/alsasound start</i>
+ * Loading ALSA modules ...
+ * Loading: snd-card-0 ... [ ok ]
+ * Loading: snd-pcm-oss ...
+WARNING: Error inserting snd_mixer_oss
+(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown
+symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting
+snd_pcm_oss
+(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-pcm-oss.ko): Unknown
+symbol in module, or unknown parameter (see dmesg)
+ [ !! ]
+ * Loading: snd-mixer-oss ...
+FATAL: Error inserting snd_mixer_oss
+(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown
+symbol in module, or unknown parameter (see dmesg)
+ [ !! ]
+ * Loading: snd-seq ... [ ok ]
+ * Loading: snd-emu10k1-synth ... [ ok ]
+ * Loading: snd-seq-midi ... [ ok ]
+ * Restoring Mixer Levels ... [ ok ]
+</pre>
+
+<p>
+And when you take a look at <c>dmesg</c> as suggested, you're quite likely to
+see:
+</p>
+
+<pre caption="dmesg output">
+<comment>(Only relevant portions are shown below)</comment>
+# <i>dmesg | less</i>
+ACPI: PCI Interrupt 0000:02:06.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 209
+snd_mixer_oss: Unknown symbol snd_unregister_oss_device
+snd_mixer_oss: Unknown symbol snd_register_oss_device
+snd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback
+snd_mixer_oss: Unknown symbol snd_oss_info_register
+snd_pcm_oss: Unknown symbol snd_unregister_oss_device
+snd_pcm_oss: Unknown symbol snd_register_oss_device
+snd_pcm_oss: Unknown symbol snd_mixer_oss_ioctl_card
+snd_pcm_oss: Unknown symbol snd_oss_info_register
+snd_mixer_oss: Unknown symbol snd_unregister_oss_device
+snd_mixer_oss: Unknown symbol snd_register_oss_device
+snd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback
+snd_mixer_oss: Unknown symbol snd_oss_info_register
+</pre>
+
+<p>
+The above issue is caused when you switch from <c>alsa-driver</c> to in-kernel
+ALSA because when you unmerge <c>alsa-driver</c> the module files are config
+protected and hence get left behind. So, when you switch to in-kernel
+drivers, running <c>modprobe</c> gives you a mix of <c>alsa-driver</c> and
+in-kernel modules thus causing the above errors.
+</p>
+
+<p>
+The solution is quite easy. We just need to manually remove the problem causing
+directory after you unmerge <c>alsa-driver</c>. Be sure to remove the correct
+kernel version and not the current one!
+</p>
+
+<pre caption="Removing the alsa-driver modules">
+<comment>(Replace KERNELVER with your kernel version)</comment>
+# <i>rm -rf /lib/modules/KERNELVER/alsa-driver</i>
+</pre>
+
</body>
</section>
</chapter>
@@ -783,7 +853,9 @@
<pre caption="Loading Soundfonts">
<comment>(First, copy the Soundfont)</comment>
-# <i>cp /mnt/win2k/Program\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
+# <i>cp /mnt/win2k/Program\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
+<comment>(Or get it from your SoundBlaster CD)</comment>
+# <i>cp /mnt/cdrom/AUDIO/ENGLISH/SFBANK/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
<comment>(We load the specific Soundfont)</comment>
# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i>
</pre>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-09-10 18:02 swift
0 siblings, 0 replies; 26+ messages in thread
From: swift @ 2005-09-10 18:02 UTC (permalink / raw
To: gentoo-doc-cvs
swift 05/09/10 18:02:53
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
Update grub config after building a new kernel; reported by Rasmus Lerchedahl Petersen
Revision Changes Path
1.62 +5 -4 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.62&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.62&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.61&r2=1.62&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- alsa-guide.xml 9 Sep 2005 06:49:31 -0000 1.61
+++ alsa-guide.xml 10 Sep 2005 18:02:53 -0000 1.62
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.61 2005/09/09 06:49:31 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.62 2005/09/10 18:02:53 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.9</version>
-<date>2005-09-09</date>
+<version>2.10</version>
+<date>2005-09-10</date>
<chapter>
<title>Introduction</title>
@@ -310,7 +310,8 @@
<p>
Now that your options are set, you can (re)compile the kernel and ALSA support
-for your card should be functional once you reboot into the new kernel.
+for your card should be functional once you reboot into the new kernel. Don't
+forget to update your GRUB configuration to use the newly built kernel.
You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
see if everything is working as it should.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2005-10-30 16:02 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2005-10-30 16:02 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/10/30 16:02:55
Modified: xml/htdocs/doc/en alsa-guide.xml
Log:
Testing YosWink's repodoc, found a few wrapping issues...and fixed them. No content change.
Revision Changes Path
1.63 +10 -8 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.63&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.63&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.62&r2=1.63&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- alsa-guide.xml 10 Sep 2005 18:02:53 -0000 1.62
+++ alsa-guide.xml 30 Oct 2005 16:02:55 -0000 1.63
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.62 2005/09/10 18:02:53 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.63 2005/10/30 16:02:55 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -233,8 +233,9 @@
</p>
<impo>
-<c>genkernel</c> users should now run <c>genkernel --menuconfig all</c> and then follow
-the instructions in <uri link="#doc_chap2_pre3">Kernel Options for ALSA</uri>.
+<c>genkernel</c> users should now run <c>genkernel --menuconfig all</c> and
+then follow the instructions in <uri link="#doc_chap2_pre3">Kernel Options for
+ALSA</uri>.
</impo>
<pre caption="Heading over to the source">
@@ -255,10 +256,10 @@
<p>
Please note that for the sake of ease, all examples show ALSA built as modules.
It is advisable to follow the same as it then allows the use of <c>alsaconf</c>
-which is a boon when you want to configure your card. Please do <e>not</e> skip the <uri
-link="#alsa-config">Configuration</uri> section of this document. If you still
-like to have options built-in, ensure that you make changes to your config
-accordingly.
+which is a boon when you want to configure your card. Please do <e>not</e> skip
+the <uri link="#alsa-config">Configuration</uri> section of this document. If
+you still like to have options built-in, ensure that you make changes to your
+config accordingly.
</p>
<pre caption="Kernel Options for ALSA">
@@ -451,7 +452,8 @@
automatically make required changes to <path>/etc/modules.d/alsa</path>.
It will then adjust your volume settings to optimum levels, run
<c>modules-update</c> and start the <path>/etc/init.d/alsasound</path> service.
-Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA initscript.
+Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA
+initscript.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-01-01 11:51 Xavier Neys
0 siblings, 0 replies; 26+ messages in thread
From: Xavier Neys @ 2006-01-01 11:51 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 06/01/01 11:51:44
Modified: xml/htdocs/doc/en alsa-guide.xml colinux-howto.xml
cron-guide.xml distcc.xml gentoo-sparc-faq.xml
gentoolkit.xml home-router-howto.xml
kernel-upgrade.xml power-management-guide.xml
quick-samba-howto.xml rsync.xml source_mirrors.xml
Log:
Removed some tabs (blame rane) **No Content Change**
Revision Changes Path
1.64 +5 -5 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.64&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.64&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.63&r2=1.64&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- alsa-guide.xml 30 Oct 2005 16:02:55 -0000 1.63
+++ alsa-guide.xml 1 Jan 2006 11:51:43 -0000 1.64
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.63 2005/10/30 16:02:55 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.64 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -85,7 +85,7 @@
</li>
</ol>
-<p>
+<p>
We shall take a peek into both before finally deciding on one.
</p>
@@ -522,9 +522,9 @@
* Loading ALSA modules ...
* Loading: snd-card-0 ... [ ok ]
* Loading: snd-pcm-oss ... [ ok ]
- * Loading: snd-seq ... [ ok ]
- * Loading: snd-emu10k1-synth ... [ ok ]
- * Loading: snd-seq-midi ... [ ok ]
+ * Loading: snd-seq ... [ ok ]
+ * Loading: snd-emu10k1-synth ... [ ok ]
+ * Loading: snd-seq-midi ... [ ok ]
* Restoring Mixer Levels ... [ ok ]
<comment>(ALSA compiled in)</comment>
# <i>/etc/init.d/alsasound start</i>
1.9 +2 -2 xml/htdocs/doc/en/colinux-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/colinux-howto.xml?rev=1.9&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/colinux-howto.xml?rev=1.9&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/colinux-howto.xml.diff?r1=1.8&r2=1.9&cvsroot=gentoo
Index: colinux-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/colinux-howto.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- colinux-howto.xml 26 Jul 2005 17:48:26 -0000 1.8
+++ colinux-howto.xml 1 Jan 2006 11:51:43 -0000 1.9
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/colinux-howto.xml,v 1.8 2005/07/26 17:48:26 vanquirius Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/colinux-howto.xml,v 1.9 2006/01/01 11:51:43 neysx Exp $ -->
<guide link="colinux-howto.xml">
<title>HOWTO setup coLinux to run Gentoo</title>
@@ -323,7 +323,7 @@
</p>
<pre caption="Add to /etc/fstab">
-/dev/cobd1 none swap sw 0 0
+/dev/cobd1 none swap sw 0 0
</pre>
<p>
1.6 +4 -4 xml/htdocs/doc/en/cron-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/cron-guide.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/cron-guide.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/cron-guide.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo
Index: cron-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- cron-guide.xml 24 Jul 2005 23:00:30 -0000 1.5
+++ cron-guide.xml 1 Jan 2006 11:51:43 -0000 1.6
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.5 2005/07/24 23:00:30 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/cron-guide.xml,v 1.6 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/cron-guide.xml">
@@ -554,7 +554,7 @@
22 2 * * 1 /usr/bin/updatedb
30 6 * * * /usr/bin/emerge --sync
<comment>(if you're using anacron, add this line)</comment>
-30 7 * * * /usr/sbin/anacron -s
+30 7 * * * /usr/sbin/anacron -s
</pre>
<p>
@@ -589,12 +589,12 @@
<li>
<b>Is your command working?</b><br/>
Try: * * * * * /bin/foobar > /file_you_own 2>&1, look for errors
- in /file_you_own
+ in /file_you_own
</li>
<li>
<b>Can cron run your job?</b><br/>
Check the cron log, usually <path>/var/log/cron.log</path> or
- <path>/var/log/messages</path> for errors
+ <path>/var/log/messages</path> for errors
</li>
<li>
<b>Are there any dead.letter's?</b><br/>
1.31 +2 -2 xml/htdocs/doc/en/distcc.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml?rev=1.31&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml?rev=1.31&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml.diff?r1=1.30&r2=1.31&cvsroot=gentoo
Index: distcc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- distcc.xml 3 Jul 2005 17:33:01 -0000 1.30
+++ distcc.xml 1 Jan 2006 11:51:43 -0000 1.31
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.30 2005/07/03 17:33:01 alin Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.31 2006/01/01 11:51:43 neysx Exp $ -->
<guide link="/doc/en/distcc.xml">
@@ -327,7 +327,7 @@
# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
<comment>An example: <i>/usr/bin/distcc-config --set-hosts "localhost
192.168.0.4 192.168.0.6"</i></comment>
-</pre>
+</pre>
<p>
Distcc is now set up to bootstrap! Continue with the official installation
1.8 +2 -2 xml/htdocs/doc/en/gentoo-sparc-faq.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-faq.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-faq.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-faq.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo
Index: gentoo-sparc-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-faq.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- gentoo-sparc-faq.xml 27 Oct 2005 19:41:57 -0000 1.7
+++ gentoo-sparc-faq.xml 1 Jan 2006 11:51:43 -0000 1.8
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-faq.xml,v 1.7 2005/10/27 19:41:57 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-faq.xml,v 1.8 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gentoo-sparc-faq.xml">
@@ -260,7 +260,7 @@
<comment># Solaris options</comment>
other = /sbus/espdma/esp/sd@1,0;1
- label = solaris
+ label = solaris
</pre>
</body>
1.22 +6 -6 xml/htdocs/doc/en/gentoolkit.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoolkit.xml?rev=1.22&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoolkit.xml?rev=1.22&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoolkit.xml.diff?r1=1.21&r2=1.22&cvsroot=gentoo
Index: gentoolkit.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- gentoolkit.xml 7 Jun 2005 06:26:26 -0000 1.21
+++ gentoolkit.xml 1 Jan 2006 11:51:43 -0000 1.22
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.21 2005/06/07 06:26:26 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.22 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gentoolkit.xml">
@@ -221,9 +221,9 @@
`-- sys-apps/gawk-3.1.3-r1
`-- sys-apps/util-linux-2.12-r4
`-- sys-apps/sed-4.0.9
- `-- sys-libs/ncurses-5.4-r4
- `-- sys-apps/pam-login-3.14
- `-- sys-libs/pam-0.77-r1
+ `-- sys-libs/ncurses-5.4-r4
+ `-- sys-apps/pam-login-3.14
+ `-- sys-libs/pam-0.77-r1
`-- sys-libs/cracklib-2.7-r10
`-- sys-apps/miscfiles-1.3-r1
`-- app-arch/gzip-1.3.5-r1
@@ -369,8 +369,8 @@
<pre caption="Package Size">
# <i>equery size openoffice-bin</i>
* app-office/openoffice-bin-1.1.2
- Total Files : 2908
- Total Size : 223353.31 KiB
+ Total Files : 2908
+ Total Size : 223353.31 KiB
</pre>
<p>
1.41 +4 -4 xml/htdocs/doc/en/home-router-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.41&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.41&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.40&r2=1.41&cvsroot=gentoo
Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- home-router-howto.xml 21 Dec 2005 11:12:59 -0000 1.40
+++ home-router-howto.xml 1 Jan 2006 11:51:43 -0000 1.41
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.40 2005/12/21 11:12:59 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.41 2006/01/01 11:51:43 neysx Exp $ -->
<guide link="/doc/en/home-router-howto.xml" lang="en">
<title>Home Router Guide</title>
@@ -734,9 +734,9 @@
address = 192.168.0.1
[gentoo-portage]
- path = /mnt/space/portage
- comment = Gentoo Linux Portage tree
- exclude = /distfiles /packages
+ path = /mnt/space/portage
+ comment = Gentoo Linux Portage tree
+ exclude = /distfiles /packages
</pre>
<p>
1.12 +2 -2 xml/htdocs/doc/en/kernel-upgrade.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.12&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml.diff?r1=1.11&r2=1.12&cvsroot=gentoo
Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- kernel-upgrade.xml 11 Oct 2005 03:48:06 -0000 1.11
+++ kernel-upgrade.xml 1 Jan 2006 11:51:43 -0000 1.12
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.11 2005/10/11 03:48:06 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.12 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/kernel-upgrade.xml">
<title>Gentoo Linux Kernel Upgrade Guide</title>
<author title="Author">
- <mail link="dsd@gentoo.org">Daniel Drake</mail>
+ <mail link="dsd@gentoo.org">Daniel Drake</mail>
</author>
<abstract>
1.16 +7 -7 xml/htdocs/doc/en/power-management-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.16&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.16&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml.diff?r1=1.15&r2=1.16&cvsroot=gentoo
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- power-management-guide.xml 28 Oct 2005 14:48:06 -0000 1.15
+++ power-management-guide.xml 1 Jan 2006 11:51:43 -0000 1.16
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.15 2005/10/28 14:48:06 so Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.16 2006/01/01 11:51:43 neysx Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -532,12 +532,12 @@
<ti>N.A.</ti>
<ti>N.A.</ti>
<ti>
- Unlike the ondemand governor, conversative doesn't jump to maximum
- frequency when CPU load is high, but increases the frequency step by
- step. Further tuning through files in
- <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still
- requires userland tools (programs, scripts) if governor switching or
- similar is desired.
+ Unlike the ondemand governor, conversative doesn't jump to maximum
+ frequency when CPU load is high, but increases the frequency step by step.
+ Further tuning through files in
+ <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still requires
+ userland tools (programs, scripts) if governor switching or similar is
+ desired.
</ti>
</tr>
<tr>
1.20 +2 -2 xml/htdocs/doc/en/quick-samba-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.20&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.20&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/quick-samba-howto.xml.diff?r1=1.19&r2=1.20&cvsroot=gentoo
Index: quick-samba-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- quick-samba-howto.xml 2 Oct 2005 21:26:32 -0000 1.19
+++ quick-samba-howto.xml 1 Jan 2006 11:51:43 -0000 1.20
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.19 2005/10/02 21:26:32 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.20 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="quick-samba-howto.xml">
<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
@@ -687,7 +687,7 @@
ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
LogLevel debug <comment># only while isntalling and testing, should later be
- # changed to 'info'</comment>
+ # changed to 'info'</comment>
MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
# there seemed to be a bug in CUPS' controlling of the web interface,
1.46 +3 -3 xml/htdocs/doc/en/rsync.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/rsync.xml?rev=1.46&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/rsync.xml?rev=1.46&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/rsync.xml.diff?r1=1.45&r2=1.46&cvsroot=gentoo
Index: rsync.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/rsync.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- rsync.xml 12 Dec 2005 16:04:32 -0000 1.45
+++ rsync.xml 1 Jan 2006 11:51:43 -0000 1.46
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/rsync.xml,v 1.45 2005/12/12 16:04:32 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/rsync.xml,v 1.46 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/rsync.xml">
@@ -266,8 +266,8 @@
</p>
<ol>
- <li>:00 to :10</li>
- <li>:30 to :40</li>
+ <li>:00 to :10</li>
+ <li>:30 to :40</li>
</ol>
<p>
1.28 +10 -10 xml/htdocs/doc/en/source_mirrors.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/source_mirrors.xml?rev=1.28&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/source_mirrors.xml?rev=1.28&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/source_mirrors.xml.diff?r1=1.27&r2=1.28&cvsroot=gentoo
Index: source_mirrors.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/source_mirrors.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- source_mirrors.xml 12 Apr 2005 17:52:20 -0000 1.27
+++ source_mirrors.xml 1 Jan 2006 11:51:43 -0000 1.28
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/source_mirrors.xml,v 1.27 2005/04/12 17:52:20 alin Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/source_mirrors.xml,v 1.28 2006/01/01 11:51:43 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/source_mirrors.xml">
@@ -110,11 +110,11 @@
</p>
<ul>
- <li>/releases</li>
- <li>/experimental</li>
- <li>/distfiles</li>
- <li>/snapshots</li>
- <li>/grp</li>
+ <li>/releases</li>
+ <li>/experimental</li>
+ <li>/distfiles</li>
+ <li>/snapshots</li>
+ <li>/grp</li>
</ul>
<p>
@@ -122,8 +122,8 @@
</p>
<ul>
- <li>/distfiles</li>
- <li>/snapshots</li>
+ <li>/distfiles</li>
+ <li>/snapshots</li>
</ul>
<p>
@@ -219,8 +219,8 @@
</p>
<ul>
- <li>/distfiles</li>
- <li>/snapshots</li>
+ <li>/distfiles</li>
+ <li>/snapshots</li>
</ul>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-03-25 6:59 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2006-03-25 6:59 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 06/03/25 06:59:01
Modified: alsa-guide.xml
Log:
Removed stupid section on catting /dev/urandom. Closes bug #119019 as well.
Revision Changes Path
1.65 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.65&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.65&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.64&r2=1.65&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -r1.64 -r1.65
--- alsa-guide.xml 1 Jan 2006 11:51:43 -0000 1.64
+++ alsa-guide.xml 25 Mar 2006 06:59:01 -0000 1.65
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.64 2006/01/01 11:51:43 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.65 2006/03/25 06:59:01 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.10</version>
-<date>2005-09-10</date>
+<version>2.11</version>
+<date>2006-03-25</date>
<chapter>
<title>Introduction</title>
@@ -605,29 +605,6 @@
<body>
<p>
-The irritating way to check your soundcard is to see if you can hear static on
-the speakers. This isn't exactly fun, but hey, it tells you the card is
-configured and working.
-</p>
-
-<pre caption="Bring on the static">
-# <i>cat /dev/urandom > /dev/dsp</i>
-</pre>
-
-<note>
-<path>/dev/dsp</path> is a symlink to <path>/dev/sound/dsp</path> and should be
-automatically created. Try re-directing the output to
-<path>/dev/sound/dsp</path> in case you don't get a "No such file or directory"
-error.
-</note>
-
-<p>
-You should hear static. Press <c>Ctrl + C</c> to stop. If you don't hear
-anything, now is a good time to go back and check/trace out the issue and
-rectify it.
-</p>
-
-<p>
Finally. Some music. If everything above is perfect, you should now be able to
listen to some good music. A quick way to test is to use a command line tool
like <c>media-sound/madplay</c>. You could also use something more well known
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-05-01 5:52 Shyam Mani
0 siblings, 0 replies; 26+ messages in thread
From: Shyam Mani @ 2006-05-01 5:52 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 06/05/01 05:52:31
Modified: alsa-guide.xml
Log:
Fixes for Bug 111387
Revision Changes Path
1.66 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.66&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.66&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.65&r2=1.66&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- alsa-guide.xml 25 Mar 2006 06:59:01 -0000 1.65
+++ alsa-guide.xml 1 May 2006 05:52:31 -0000 1.66
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.65 2006/03/25 06:59:01 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.66 2006/05/01 05:52:31 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.11</version>
-<date>2006-03-25</date>
+<version>2.12</version>
+<date>2006-05-01</date>
<chapter>
<title>Introduction</title>
@@ -789,6 +789,27 @@
# <i>rm -rf /lib/modules/KERNELVER/alsa-driver</i>
</pre>
+<p>
+Another reason for error messages similar to the ones above could be a file in
+<path>/etc/modules.d</path> supplying a <c>device_node</c> parameter when it
+isn't required. Confirm that this is indeed the issue and find out which file
+is the culprit.
+</p>
+
+<pre caption="Confirming and searching for device_node">
+<comment>(Check dmesg to confirm)</comment>
+# <i>dmesg | grep device_mode</i>
+snd: Unknown parameter `device_mode'
+<comment>(Now, to get to the source of the issue)</comment>
+# <i>grep device_mode /etc/modules.d/*</i>
+</pre>
+
+<p>
+Usually it is a file called <path>alsa</path> with the line <c>options snd
+device_mode=0666</c>. Remove this line and restart the alsasound service and
+that should take care of this issue.
+</p>
+
</body>
</section>
</chapter>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-05-27 13:59 Xavier Neys
0 siblings, 0 replies; 26+ messages in thread
From: Xavier Neys @ 2006-05-27 13:59 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 06/05/27 13:59:35
Modified: alsa-guide.xml
Log:
s/device_node/device_mode/
Revision Changes Path
1.67 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.67&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.67&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.66&r2=1.67&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -r1.66 -r1.67
--- alsa-guide.xml 1 May 2006 05:52:31 -0000 1.66
+++ alsa-guide.xml 27 May 2006 13:59:35 -0000 1.67
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.66 2006/05/01 05:52:31 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.67 2006/05/27 13:59:35 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.12</version>
-<date>2006-05-01</date>
+<version>2.13</version>
+<date>2006-05-27</date>
<chapter>
<title>Introduction</title>
@@ -791,12 +791,12 @@
<p>
Another reason for error messages similar to the ones above could be a file in
-<path>/etc/modules.d</path> supplying a <c>device_node</c> parameter when it
+<path>/etc/modules.d</path> supplying a <c>device_mode</c> parameter when it
isn't required. Confirm that this is indeed the issue and find out which file
is the culprit.
</p>
-<pre caption="Confirming and searching for device_node">
+<pre caption="Confirming and searching for device_mode">
<comment>(Check dmesg to confirm)</comment>
# <i>dmesg | grep device_mode</i>
snd: Unknown parameter `device_mode'
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-07-06 19:51 Lukasz Damentko
0 siblings, 0 replies; 26+ messages in thread
From: Lukasz Damentko @ 2006-07-06 19:51 UTC (permalink / raw
To: gentoo-doc-cvs
rane 06/07/06 19:51:07
Modified: alsa-guide.xml
Log:
#138845, replaced KERNELVER with more elite 2.6.16-gentoo-r9
Revision Changes Path
1.68 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.68&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.68&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.67&r2=1.68&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- alsa-guide.xml 27 May 2006 13:59:35 -0000 1.67
+++ alsa-guide.xml 6 Jul 2006 19:51:06 -0000 1.68
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.67 2006/05/27 13:59:35 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.68 2006/07/06 19:51:06 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.13</version>
-<date>2006-05-27</date>
+<version>2.14</version>
+<date>2006-06-06</date>
<chapter>
<title>Introduction</title>
@@ -785,8 +785,7 @@
</p>
<pre caption="Removing the alsa-driver modules">
-<comment>(Replace KERNELVER with your kernel version)</comment>
-# <i>rm -rf /lib/modules/KERNELVER/alsa-driver</i>
+# <i>rm -rf /lib/modules/$(uname -r)/alsa-driver</i>
</pre>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-07-07 14:40 Lukasz Damentko
0 siblings, 0 replies; 26+ messages in thread
From: Lukasz Damentko @ 2006-07-07 14:40 UTC (permalink / raw
To: gentoo-doc-cvs
rane 06/07/07 14:40:08
Modified: alsa-guide.xml
Log:
date fix, it's july not june
Revision Changes Path
1.69 xml/htdocs/doc/en/alsa-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.69&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.69&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.68&r2=1.69&cvsroot=gentoo
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- alsa-guide.xml 6 Jul 2006 19:51:06 -0000 1.68
+++ alsa-guide.xml 7 Jul 2006 14:40:08 -0000 1.69
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.68 2006/07/06 19:51:06 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.69 2006/07/07 14:40:08 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,7 +19,7 @@
<license/>
<version>2.14</version>
-<date>2006-06-06</date>
+<date>2006-07-06</date>
<chapter>
<title>Introduction</title>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2006-11-02 18:24 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2006-11-02 18:24 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/11/02 18:24:36
Modified: alsa-guide.xml
Log:
Removed XMMS references, bug 153830
Revision Changes Path
1.70 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.70&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.70&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.69&r2=1.70
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- alsa-guide.xml 7 Jul 2006 14:40:08 -0000 1.69
+++ alsa-guide.xml 2 Nov 2006 18:24:36 -0000 1.70
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.69 2006/07/07 14:40:08 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.70 2006/11/02 18:24:36 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.14</version>
-<date>2006-07-06</date>
+<version>2.15</version>
+<date>2006-11-02</date>
<chapter>
<title>Introduction</title>
@@ -608,14 +608,14 @@
Finally. Some music. If everything above is perfect, you should now be able to
listen to some good music. A quick way to test is to use a command line tool
like <c>media-sound/madplay</c>. You could also use something more well known
-like <c>mpg123</c> or <c>xmms</c>. If you are an ogg fan, you could use
-<c>ogg123</c> provided by <c>media-sound/vorbis-tools</c>. Use any player you
-are comfortable with. As always, <c>emerge</c> what you need.
+like <c>mpg123</c>. If you are an ogg fan, you could use <c>ogg123</c> provided
+by <c>media-sound/vorbis-tools</c>. Use any player you are comfortable with. As
+always, <c>emerge</c> what you need.
</p>
<pre caption="Getting the software">
<comment>(Install the applications you want)</comment>
-# <i>emerge madplay mpg123 xmms</i>
+# <i>emerge madplay mpg123</i>
<comment>(To play .ogg files)</comment>
# <i>emerge vorbis-tools</i>
</pre>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-01-31 15:54 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-01-31 15:54 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 13098 bytes --]
nightmorph 07/01/31 15:54:35
Modified: alsa-guide.xml
Log:
the big alsa guide update to make the whole damn thing more neutral (among other additions), fixes bugs 164573, 164576, 164577, 164578, 164593, 164597, and 164598
Revision Changes Path
1.71 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.71&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.71&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.70&r2=1.71
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- alsa-guide.xml 2 Nov 2006 18:24:36 -0000 1.70
+++ alsa-guide.xml 31 Jan 2007 15:54:35 -0000 1.71
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.70 2006/11/02 18:24:36 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.71 2007/01/31 15:54:35 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -9,6 +9,12 @@
<author title="Author">
<mail link="fox2mike@gentoo.org">Shyam Mani</mail>
</author>
+<author title="Author">
+ <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
+</author>
+<author title="Contributor">
+ <mail link="flameeyes@gentoo.org">Diego Pettenò</mail>
+</author>
<abstract>
This document helps a user setup ALSA on Gentoo Linux.
@@ -18,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.15</version>
-<date>2006-11-02</date>
+<version>2.16</version>
+<date>2007-01-31</date>
<chapter>
<title>Introduction</title>
@@ -76,17 +82,18 @@
</p>
<ol>
- <li>
- Use ALSA provided by your kernel. This is the preferred/recommended
- method.
- </li>
- <li>
- Use Gentoo's <c>media-sound/alsa-driver</c> package.
- </li>
+ <li>Use ALSA provided by your kernel.</li>
+ <li>Use Gentoo's <c>media-sound/alsa-driver</c> package.</li>
</ol>
<p>
-We shall take a peek into both before finally deciding on one.
+The in-kernel drivers and the <c>alsa-driver</c> package can vary a little; it's
+possible that features and fixes found in one might not yet be incorporated into
+the other. The upstream developers are aware of this, but the two drivers are
+effectively separate branches of the ALSA project; they are not entirely
+identical. You should be aware that they might function slightly differently, so
+if one doesn't work for you, try the other! We shall take a peek into both
+before finally deciding on one.
</p>
<p>
@@ -101,7 +108,9 @@
</tr>
<tr>
<th>+</th>
- <ti>Pretty stable as drivers are integrated into kernel.</ti>
+ <ti>
+ No need to emerge yet another package; drivers are integrated into kernel.
+ </ti>
</tr>
<tr>
<th>+</th>
@@ -109,7 +118,7 @@
</tr>
<tr>
<th>-</th>
- <ti>Might be a slightly older version than <c>alsa-driver</c>.</ti>
+ <ti>Might be a slightly different version than <c>alsa-driver</c>.</ti>
</tr>
</table>
@@ -124,7 +133,11 @@
</tr>
<tr>
<th>+</th>
- <ti>Latest drivers from the ALSA Project.</ti>
+ <ti>Possibly the latest drivers from the ALSA Project.</ti>
+</tr>
+<tr>
+ <th>+</th>
+ <ti>Useful if you intend to develop audio drivers.</ti>
</tr>
<tr>
<th>-</th>
@@ -143,11 +156,11 @@
<body>
<p>
-The main difference between using <c>alsa-driver</c> and ALSA that comes with
-the kernel is that <c>alsa-driver</c> is generally more up to date than the
-version in the kernel. Since this does not make any huge difference as
-such, you are encouraged to use the ALSA provided by the kernel for ease of use.
-Before reporting any sound related issues to <uri
+The differences between <c>alsa-driver</c> and the in-kernel ALSA drivers are
+quite subtle, as mentioned earlier. Since there are not any huge differences,
+this guide will go through the process of using the ALSA provided by the kernel
+<e>first</e> for ease of use. However, if you run into problems, try switching
+to <c>alsa-driver</c>. Before reporting any sound related issues to <uri
link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to reproduce
them using <c>alsa-driver</c> and file the bug report no matter what the
result.
@@ -210,6 +223,20 @@
"Details" and that will take you to the <c>emu10k1</c> specific page.
</p>
+<p>
+If you intend to use MIDI, then you should add <c>midi</c> to your USE flags in
+<path>/etc/make.conf</path> before emerging any ALSA packages. Later in the
+guide, we will show you how to set up <uri link="#midi">MIDI support</uri>.
+</p>
+
+<pre caption="MIDI support in /etc/make.conf">
+<comment>(If you want MIDI support)</comment>
+USE="midi"
+
+<comment>(If you don't need MIDI)</comment>
+USE="-midi"
+</pre>
+
</body>
</section>
<section id="kernel">
@@ -254,8 +281,8 @@
</p>
<p>
-Please note that for the sake of ease, all examples show ALSA built as modules.
-It is advisable to follow the same as it then allows the use of <c>alsaconf</c>
+Please note that for ease of use, all examples show ALSA built as modules. It
+is advisable to follow the same as it then allows the use of <c>alsaconf</c>
which is a boon when you want to configure your card. Please do <e>not</e> skip
the <uri link="#alsa-config">Configuration</uri> section of this document. If
you still like to have options built-in, ensure that you make changes to your
@@ -393,8 +420,13 @@
</pre>
<impo>
-Please note that you will have to run <c>emerge alsa-driver</c> after every
-kernel (re)compile, as the earlier drivers are deleted.
+Please note that you will have to run <c>emerge alsa-driver</c> after every
+kernel (re)compile, as the earlier drivers are deleted. To make this task
+easier, you may want to emerge the <c>module-rebuild</c> package, which will
+keep track of module packages and rebuild them for you. First run <c>module
+rebuild populate</c> to create the list, and then after every kernel
+(re)compile, you just run <c>module-rebuild rebuild</c>, and your external
+modules will be rebuilt.
</impo>
</body>
@@ -431,14 +463,21 @@
<title>Configuration</title>
<body>
+<p>
+Recent versions of <c>udev</c> (<c>>=udev-103</c>) provide some degree of
+kernel-level autoconfiguration of your sound card. If possible, try to rely on
+just letting your kernel automatically setup your sound card for you. Otherwise,
+use <c>alsaconf</c> to configure your card, as shown below.
+</p>
+
<note>
Please shut down any programs that <e>might</e> access the sound card while
running <c>alsaconf</c>.
</note>
<p>
-The easiest way to configure your sound card is to run <c>alsaconf</c>. Just
-type <c>alsaconf</c> in a shell as root.
+Another way to configure your sound card is to run <c>alsaconf</c>. Just type
+<c>alsaconf</c> in a shell as root.
</p>
<pre caption="Invoking alsaconf">
@@ -511,25 +550,13 @@
<body>
<p>
-We've completed all the setups and pre-requisites, so let's fire up ALSA. If
+We've completed all the setups and prerequisites, so let's fire up ALSA. If
you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
does this for you.
</p>
<pre caption="Start the service">
-<comment>(ALSA as modules)</comment>
-# <i>/etc/init.d/alsasound start</i>
- * Loading ALSA modules ...
- * Loading: snd-card-0 ... [ ok ]
- * Loading: snd-pcm-oss ... [ ok ]
- * Loading: snd-seq ... [ ok ]
- * Loading: snd-emu10k1-synth ... [ ok ]
- * Loading: snd-seq-midi ... [ ok ]
- * Restoring Mixer Levels ... [ ok ]
-<comment>(ALSA compiled in)</comment>
-# <i>/etc/init.d/alsasound start</i>
- * Loading ALSA modules ...
- * Restoring Mixer Levels ... [ ok ]
+# <i>/etc/init.d/alsasound start</i>
</pre>
<p>
@@ -815,11 +842,27 @@
<chapter>
<title>Other things ALSA</title>
-<section>
+<section id="midi">
<title>Setting up MIDI support</title>
<body>
<p>
+First, check to make sure that you enabled the <c>midi</c> USE flag in
+<path>/etc/make.conf</path>.
+</p>
+
+<pre caption="MIDI support in /etc/make.conf">
+USE="midi"
+</pre>
+
+<p>
+If you didn't previously enable <c>midi</c>, go ahead and add it to
+<path>/etc/make.conf</path> now. You will also need to re-emerge any ALSA
+packages that use the <c>midi</c> flag, such as <c>alsa-lib</c>,
+<c>alsa-utils</c>, and <c>alsa-driver</c>.
+</p>
+
+<p>
If your sound card is one of those that come with on-board MIDI synthesizers
and you would like to listen to some .mid files, you have to install
<c>awesfx</c> which is basically a set of utilities for controlling the AWE32
@@ -895,22 +938,23 @@
</pre>
<p>
-For timidity to play sounds, it needs a sound font. If you do not have any,
-install <c>timidity-eawpatches</c> or <c>timidity-shompatches</c> which will
-give you some sound fonts. You can have multiple sound font configurations
-installed, and you can place your own in <path>/usr/share/timidity/</path>.
-To switch between different timidity configurations, you should use the
-<c>timidity-update</c> tool provided in the timidity++ package.
+For timidity to play sounds, it needs a sound font. Fortunately, the ebuild will
+install some sound font packages for you. There are a few other font packages
+available in Portage, such as <c>timidity-freepats</c> and
+<c>timidity-eawpatches</c>. You can have multiple sound font configurations
+installed, and you can place your own in <path>/usr/share/timidity/</path>. To
+switch between different timidity configurations, you should use the
+<c>timidity-update</c> tool provided in the timidity++ package. In later
+versions of timidity, <c>eselect</c> is used to switch configurations.
</p>
-<pre caption="Installing sound fonts">
-# <i>emerge timidity-eawpatches</i>
+<pre caption="Changing configurations">
+<comment>(replace eawpatches with the name of your sound font package)</comment>
# <i>timidity-update -g -s eawpatches</i>
-<comment>(or)</comment>
-
-# <i>emerge timidity-shompatches</i>
-# <i>timidity-update -g -s shompatches</i>
+<comment>(Use eselect if you have installed >=timidity-2.13.2-r3)</comment>
+# <i>eselect timidity list</i>
+# <i>eselect timidity set eawpatches</i>
</pre>
<p>
@@ -934,28 +978,68 @@
<p>
Some specific sound cards can benefit from certain tools provided by the
-<c>alsa-tools</c> and <c>alsa-firmware</c> packages. If you need
-<c>alsa-tools</c>, be sure to define the ALSA_TOOLS variable in
-<path>/etc/make.conf</path> with the tools you require. For instance:
+<c>alsa-tools</c> and <c>alsa-firmware</c> packages. You may install either with
+a simple <c>emerge</c>.
</p>
-<pre caption="Selecting ALSA Tools in /etc/make.conf">
-ALSA_TOOLS="as10k1 ac3dec"
+<pre caption="Installing ALSA Tools">
+# <i>emerge alsa-tools</i>
</pre>
+</body>
+</section>
+<section>
+<title>Multiple sound cards</title>
+<body>
+
<p>
-If the ALSA_TOOLS variable is not set, all available tools will be built.
-Now, install the <c>alsa-tools</c> (and/or <c>alsa-firmware</c>) package(s):
+You can more than one sound card in your system simultaneously, provided that
+you have built ALSA as modules in your kernel (or have installed
+<c>alsa-driver</c> instead). You just need to specify which should be started
+first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their
+driver names inside this file. 0 is the first card, 1 is the second, and so on.
+Here's an example for a system with two sound cards.
</p>
-<pre caption="Installing ALSA Tools">
-# <i>emerge alsa-tools</i>
+<pre caption="Two sound cards in /etc/modules.d/alsa">
+options snd-emu10k1 index=0
+options snd-via82xx index=1
+</pre>
+
+<p>
+Or, if you have two cards that use the same driver, you specify them on the same
+line, using comma-separated numbers. Here's an example for a system with three
+sound cards, two of which are the same Intel High Definition Audio card.
+</p>
+
+<pre caption="Multiple sound cards in /etc/modules.d/alsa">
+options snd-ymfpci index=0
+options snd-hda-intel index=1,2
+</pre>
+
+</body>
+</section>
+<section>
+<title>Plugins</title>
+<body>
+
+<p>
+You may want to install some plugins for extra functionality.
+<c>alsa-plugins</c> is a collection of useful plugins, which include: PulseAudio
+output, a sample rate converter, jack (a low-latency audio server), and an
+encoder that lets you output 6-channel audio through digital S/PDIF connections
+(both optical and coaxial). You can choose which of its plugins you want
+installed by adding their USE flags to <path>/etc/portage/package.use</path>.
+</p>
+
+<pre caption="Installing alsa-plugins">
+# <i>emerge -avt alsa-plugins</i>
</pre>
</body>
</section>
<section>
-<title>A Big thank you to...</title>
+<title>A big thank you to...</title>
<body>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-01-31 16:39 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-01-31 16:39 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/01/31 16:39:26
Modified: alsa-guide.xml
Log:
typo fix, should have been module-rebuild not module rebuild
Revision Changes Path
1.72 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.72&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.72&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.71&r2=1.72
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- alsa-guide.xml 31 Jan 2007 15:54:35 -0000 1.71
+++ alsa-guide.xml 31 Jan 2007 16:39:26 -0000 1.72
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.71 2007/01/31 15:54:35 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.72 2007/01/31 16:39:26 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -423,8 +423,8 @@
Please note that you will have to run <c>emerge alsa-driver</c> after every
kernel (re)compile, as the earlier drivers are deleted. To make this task
easier, you may want to emerge the <c>module-rebuild</c> package, which will
-keep track of module packages and rebuild them for you. First run <c>module
-rebuild populate</c> to create the list, and then after every kernel
+keep track of module packages and rebuild them for you. First run
+<c>module-rebuild populate</c> to create the list, and then after every kernel
(re)compile, you just run <c>module-rebuild rebuild</c>, and your external
modules will be rebuilt.
</impo>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-02-17 19:03 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-02-17 19:03 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/02/17 19:03:36
Modified: alsa-guide.xml
Log:
only use eselect now that timidity is stable, bug 164578 (again)
Revision Changes Path
1.73 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.73&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.73&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.72&r2=1.73
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -r1.72 -r1.73
--- alsa-guide.xml 31 Jan 2007 16:39:26 -0000 1.72
+++ alsa-guide.xml 17 Feb 2007 19:03:36 -0000 1.73
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.72 2007/01/31 16:39:26 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.73 2007/02/17 19:03:36 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.16</version>
-<date>2007-01-31</date>
+<version>2.17</version>
+<date>2007-02-17</date>
<chapter>
<title>Introduction</title>
@@ -943,16 +943,11 @@
available in Portage, such as <c>timidity-freepats</c> and
<c>timidity-eawpatches</c>. You can have multiple sound font configurations
installed, and you can place your own in <path>/usr/share/timidity/</path>. To
-switch between different timidity configurations, you should use the
-<c>timidity-update</c> tool provided in the timidity++ package. In later
-versions of timidity, <c>eselect</c> is used to switch configurations.
+switch between different timidity configurations, you should use
+<c>eselect</c>.
</p>
<pre caption="Changing configurations">
-<comment>(replace eawpatches with the name of your sound font package)</comment>
-# <i>timidity-update -g -s eawpatches</i>
-
-<comment>(Use eselect if you have installed >=timidity-2.13.2-r3)</comment>
# <i>eselect timidity list</i>
# <i>eselect timidity set eawpatches</i>
</pre>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-03-10 13:02 Jan Kundrat
0 siblings, 0 replies; 26+ messages in thread
From: Jan Kundrat @ 2007-03-10 13:02 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 07/03/10 13:02:28
Modified: alsa-guide.xml
Log:
no point in adding an example about how to add a USE flag to /etc/make.conf -- most likely thay already have customized it and blindly adding USE="foo" overwrites existing values
Revision Changes Path
1.75 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.75&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.75&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.74&r2=1.75
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- alsa-guide.xml 4 Mar 2007 10:35:58 -0000 1.74
+++ alsa-guide.xml 10 Mar 2007 13:02:28 -0000 1.75
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.74 2007/03/04 10:35:58 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.75 2007/03/10 13:02:28 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,7 +24,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.17</version>
+<version>2.18</version>
<date>2007-02-17</date>
<chapter>
@@ -229,14 +229,6 @@
guide, we will show you how to set up <uri link="#midi">MIDI support</uri>.
</p>
-<pre caption="MIDI support in /etc/make.conf">
-<comment>(If you want MIDI support)</comment>
-USE="midi"
-
-<comment>(If you don't need MIDI)</comment>
-USE="-midi"
-</pre>
-
</body>
</section>
<section id="kernel">
@@ -848,18 +840,9 @@
<p>
First, check to make sure that you enabled the <c>midi</c> USE flag in
-<path>/etc/make.conf</path>.
-</p>
-
-<pre caption="MIDI support in /etc/make.conf">
-USE="midi"
-</pre>
-
-<p>
-If you didn't previously enable <c>midi</c>, go ahead and add it to
-<path>/etc/make.conf</path> now. You will also need to re-emerge any ALSA
-packages that use the <c>midi</c> flag, such as <c>alsa-lib</c>,
-<c>alsa-utils</c>, and <c>alsa-driver</c>.
+<path>/etc/make.conf</path>. If you didn't, go ahead and add it now. You will
+also need to re-emerge any ALSA packages that use the <c>midi</c> flag, such as
+<c>alsa-lib</c>, <c>alsa-utils</c>, and <c>alsa-driver</c>.
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-05-03 6:21 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-05-03 6:21 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/05/03 06:21:01
Modified: alsa-guide.xml
Log:
alsa priority, bug 172490
Revision Changes Path
1.77 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.77&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.77&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.76&r2=1.77
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- alsa-guide.xml 16 Apr 2007 05:39:54 -0000 1.76
+++ alsa-guide.xml 3 May 2007 06:21:01 -0000 1.77
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.76 2007/04/16 05:39:54 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.77 2007/05/03 06:21:01 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.19</version>
-<date>2007-04-15</date>
+<version>2.20</version>
+<date>2007-05-02</date>
<chapter>
<title>Introduction</title>
@@ -82,7 +82,9 @@
</p>
<ol>
- <li>Use ALSA provided by your kernel.</li>
+ <li>
+ Use ALSA provided by your kernel. This is the preferred/recommended method.
+ </li>
<li>Use Gentoo's <c>media-sound/alsa-driver</c> package.</li>
</ol>
@@ -123,7 +125,7 @@
</table>
<p>
-And, if you were to use alsa-driver,
+And, if you were to use <c>alsa-driver</c>,
</p>
<table>
@@ -158,12 +160,11 @@
<p>
The differences between <c>alsa-driver</c> and the in-kernel ALSA drivers are
quite subtle, as mentioned earlier. Since there are not any huge differences,
-this guide will go through the process of using the ALSA provided by the kernel
-<e>first</e> for ease of use. However, if you run into problems, try switching
-to <c>alsa-driver</c>. Before reporting any sound related issues to <uri
-link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to reproduce
-them using <c>alsa-driver</c> and file the bug report no matter what the
-result.
+you are encouraged to go through the process of using the ALSA provided by the
+kernel <e>first</e> for ease of use. Before reporting any sound related issues
+to <uri link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to
+reproduce them using <c>alsa-driver</c> and file the bug report no matter what
+the result.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-05-06 23:27 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-05-06 23:27 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/05/06 23:27:46
Modified: alsa-guide.xml
Log:
updated alsa matrix link; old matrix is no longer maintained. bug 177384
Revision Changes Path
1.78 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.78&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.78&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.77&r2=1.78
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -r1.77 -r1.78
--- alsa-guide.xml 3 May 2007 06:21:01 -0000 1.77
+++ alsa-guide.xml 6 May 2007 23:27:46 -0000 1.78
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.77 2007/05/03 06:21:01 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.78 2007/05/06 23:27:46 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.20</version>
-<date>2007-05-02</date>
+<version>2.21</version>
+<date>2007-05-06</date>
<chapter>
<title>Introduction</title>
@@ -214,14 +214,14 @@
</pre>
<p>
-We now know that the sound card on the machine is a Sound Blaster Live! and
-the card manufacturer is Creative Labs. Head over to the
-<uri link="http://www.alsa-project.org/alsa-doc/"> ALSA Soundcard Matrix</uri>
-page and select Creative Labs from the drop down menu. You will be taken to
-the Creative Labs matrix page where you can see that the SB Live! uses the
-<c>emu10k1</c> module. That is the information we need for now. If you are
-interested in detailed information, you can click on the link next to the
-"Details" and that will take you to the <c>emu10k1</c> specific page.
+We now know that the sound card on the machine is a Sound Blaster Live! and the
+card manufacturer is Creative Labs. Head over to the <uri
+link="http://bugtrack.alsa-project.org/main/index.php/Matrix:Main">ALSA
+Soundcard Matrix</uri> page and select Creative Labs from the drop down menu.
+You will be taken to the Creative Labs matrix page where you can see that the SB
+Live! uses the <c>emu10k1</c> module. That is the information we need for now.
+If you are interested in detailed information, you can click on the link next to
+the "Details" and that will take you to the <c>emu10k1</c> specific page.
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-05-07 7:08 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-05-07 7:08 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/05/07 07:08:24
Modified: alsa-guide.xml
Log:
misc. fixes suggested by pva on IRC, as well as removing 2.4 kernel notices (no longer in the tree)
Revision Changes Path
1.79 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.79&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.79&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.78&r2=1.79
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- alsa-guide.xml 6 May 2007 23:27:46 -0000 1.78
+++ alsa-guide.xml 7 May 2007 07:08:24 -0000 1.79
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.78 2007/05/06 23:27:46 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.79 2007/05/07 07:08:24 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.21</version>
-<date>2007-05-06</date>
+<version>2.22</version>
+<date>2007-05-07</date>
<chapter>
<title>Introduction</title>
@@ -78,7 +78,7 @@
</warn>
<p>
-The two options are :
+The two options are:
</p>
<ol>
@@ -100,7 +100,7 @@
<p>
If you were to use ALSA provided by the kernel, the following are the pros and
-cons :
+cons:
</p>
<table>
@@ -237,15 +237,13 @@
<body>
<p>
-If you're a person who likes to keep things simple like I do, then this is
-the way to go.
+If you're a person who likes to keep things simple, then this is the way to go.
</p>
<note>
-Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Unless
-you are specifically using the 2.4 profile, <c>gentoo-sources</c> will be a
-2.6 kernel on <e>most</e> architectures. Please check that your kernel is a
-2.6 series kernel. This method will <e>not</e> work on a 2.4 kernel.
+Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Please
+check that your kernel is a 2.6 series kernel. This method will <e>not</e> work
+on a 2.4 kernel.
</note>
<p>
@@ -521,7 +519,7 @@
<p>
Before we move on to testing, there's one last <e>important</e> thing that needs
-to be setup. Rule of thumb in a *nix OS : Do not run as root unless needed.
+to be setup. Rule of thumb in a *nix OS: Do not run as root unless needed.
This applies here as well ;) How? Well, most of the times you should be logged
in as a user and would like to listen to music or access your soundcard. For
that to happen, you need to be in the "audio" group. At this point, we'll add
@@ -707,8 +705,7 @@
0 [Live ]: EMU10K1 - Sound Blaster Live!
Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11
-<comment>(If you run ALSA off the kernel like I do and wonder how far behind
-you are from alsa-driver, this displays current running ALSA version)</comment>
+<comment>(This displays the current running ALSA version)</comment>
# <i>cat /proc/asound/version</i>
Advanced Linux Sound Architecture Driver Version 1.0.8 (Thu Jan 13 09:39:32 2005 UTC).
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2007-05-19 3:00 Josh Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Josh Saddler @ 2007-05-19 3:00 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/05/19 03:00:29
Modified: alsa-guide.xml
Log:
spacing fixes by pva, bug 177969. no content change.
Revision Changes Path
1.80 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.80&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.80&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.79&r2=1.80
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- alsa-guide.xml 7 May 2007 07:08:24 -0000 1.79
+++ alsa-guide.xml 19 May 2007 03:00:29 -0000 1.80
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.79 2007/05/07 07:08:24 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.80 2007/05/19 03:00:29 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -34,18 +34,18 @@
<body>
<p>
-ALSA, which stands for <e>Advanced Linux Sound Architecture</e>, provides
-audio and MIDI (<e>Musical Instrument Digital Interface</e>) functionality to
-the Linux operating system. ALSA is the default sound subsystem in the 2.6
-kernel thereby replacing OSS (<e>Open Sound System</e>), which was used in the
+ALSA, which stands for <e>Advanced Linux Sound Architecture</e>, provides
+audio and MIDI (<e>Musical Instrument Digital Interface</e>) functionality to
+the Linux operating system. ALSA is the default sound subsystem in the 2.6
+kernel thereby replacing OSS (<e>Open Sound System</e>), which was used in the
2.4 kernels.
</p>
<p>
-ALSA's main features include efficient support for all types of audio
-interfaces ranging from consumer sound cards to professional sound
-equipment, fully modularized drivers, SMP and thread safety, backward
-compatibility with OSS and a user-space library <c>alsa-lib</c> to make
+ALSA's main features include efficient support for all types of audio
+interfaces ranging from consumer sound cards to professional sound
+equipment, fully modularized drivers, SMP and thread safety, backward
+compatibility with OSS and a user-space library <c>alsa-lib</c> to make
application development a breeze.
</p>
@@ -56,9 +56,9 @@
<body>
<p>
-One of Gentoo's main strengths lies in giving the user maximum control over
-how a system is installed/configured. ALSA on Gentoo follows the same
-principle. There are two ways you can get ALSA support up and running on your
+One of Gentoo's main strengths lies in giving the user maximum control over
+how a system is installed/configured. ALSA on Gentoo follows the same
+principle. There are two ways you can get ALSA support up and running on your
system. We shall look at them in detail in the next chapter.
</p>
@@ -73,7 +73,7 @@
<body>
<warn>
-The methods shown below are mutually exclusive. You cannot have ALSA compiled
+The methods shown below are mutually exclusive. You cannot have ALSA compiled
in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail.
</warn>
@@ -99,7 +99,7 @@
</p>
<p>
-If you were to use ALSA provided by the kernel, the following are the pros and
+If you were to use ALSA provided by the kernel, the following are the pros and
cons:
</p>
@@ -174,14 +174,14 @@
<body>
<p>
-Whichever method of install you choose, you need to know what drivers your
+Whichever method of install you choose, you need to know what drivers your
sound card uses. In most cases, sound cards (onboard and otherwise) are PCI
-based and <c>lspci</c> will help you in digging out the required information.
+based and <c>lspci</c> will help you in digging out the required information.
Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it
installed already. In case you have a USB sound card, <c>lsusb</c> from
<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using
<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users
-with ISA based sound cards.
+with ISA based sound cards:
</p>
<ul>
@@ -217,10 +217,10 @@
We now know that the sound card on the machine is a Sound Blaster Live! and the
card manufacturer is Creative Labs. Head over to the <uri
link="http://bugtrack.alsa-project.org/main/index.php/Matrix:Main">ALSA
-Soundcard Matrix</uri> page and select Creative Labs from the drop down menu.
-You will be taken to the Creative Labs matrix page where you can see that the SB
-Live! uses the <c>emu10k1</c> module. That is the information we need for now.
-If you are interested in detailed information, you can click on the link next to
+Soundcard Matrix</uri> page and select Creative Labs from the list. You will
+be taken to the Creative Labs matrix page where you can see that the SB Live!
+uses the <c>emu10k1</c> module. That is the information we need for now. If
+you are interested in detailed information, you can click on the link next to
the "Details" and that will take you to the <c>emu10k1</c> specific page.
</p>
@@ -272,7 +272,7 @@
</p>
<p>
-Please note that for ease of use, all examples show ALSA built as modules. It
+Please note that for ease of use, all examples show ALSA built as modules. It
is advisable to follow the same as it then allows the use of <c>alsaconf</c>
which is a boon when you want to configure your card. Please do <e>not</e> skip
the <uri link="#alsa-config">Configuration</uri> section of this document. If
@@ -301,10 +301,10 @@
<M> OSS PCM (digital audio) API
<comment>(You now have a choice of devices to enable support for. Generally,
-you will have one type of device and not more. If you have more than one
+you will have one type of device and not more. If you have more than one
sound card, please enable them all here.)</comment>
-<comment>(Mostly for testing and development purposes, not needed for normal
+<comment>(Mostly for testing and development purposes, not needed for normal
users unless you know what you are doing.)</comment>
Generic devices --->
@@ -313,7 +313,7 @@
<comment>(IF you had the Gravis, you would select this option)</comment>
<M> Gravis UltraSound Extreme
-<comment>(Move one level back and into PCI devices. Most sound cards today are
+<comment>(Move one level back and into PCI devices. Most sound cards today are
PCI devices)</comment>
PCI devices --->
<comment>(We now select the emu10k1 driver for our card)</comment>
@@ -331,7 +331,7 @@
Now that your options are set, you can (re)compile the kernel and ALSA support
for your card should be functional once you reboot into the new kernel. Don't
forget to update your GRUB configuration to use the newly built kernel.
-You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
+You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
see if everything is working as it should.
</p>
@@ -342,16 +342,16 @@
<body>
<p>
-So you've decided to go the <c>alsa-driver</c> way. Let's get started then.
-There are a few minor things to be done to ensure only the drivers for your
-sound card are compiled. Although this is not really necessary, it cuts down
+So you've decided to go the <c>alsa-driver</c> way. Let's get started then.
+There are a few minor things to be done to ensure only the drivers for your
+sound card are compiled. Although this is not really necessary, it cuts down
on the unnecessary drivers that will be compiled otherwise.
</p>
<p>
-If you don't have an idea of what drivers your sound card might need, please
-take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once
-you have your driver name (<c>emu10k1</c> in our example), edit
+If you don't have an idea of what drivers your sound card might need, please
+take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once
+you have your driver name (<c>emu10k1</c> in our example), edit
<path>/etc/make.conf</path> and add a variable, <c>ALSA_CARDS</c>.
</p>
@@ -363,8 +363,8 @@
</pre>
<p>
-If you have compiled your kernel and want to use <c>alsa-driver</c>, please
-ensure the following before proceeding, else <c>alsa-driver</c> is likely to
+If you have compiled your kernel and want to use <c>alsa-driver</c>, please
+ensure the following before proceeding, else <c>alsa-driver</c> is likely to
fail. The next code listing gives you one way of performing the checks.
</p>
@@ -431,8 +431,8 @@
<body>
<p>
-<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of
-programs that are highly useful, including the ALSA Initscripts. Hence we
+<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of
+programs that are highly useful, including the ALSA Initscripts. Hence we
strongly recommend that you install <c>alsa-utils</c>
</p>
@@ -441,10 +441,10 @@
</pre>
<note>
-If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did
-not compile ALSA as modules, please proceed to the
-<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need
-to configure ALSA. This is made very easy by the existence of the
+If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did
+not compile ALSA as modules, please proceed to the
+<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need
+to configure ALSA. This is made very easy by the existence of the
<c>alsaconf</c> tool provided by <c>alsa-utils</c>.
</note>
@@ -462,13 +462,12 @@
</p>
<note>
-Please shut down any programs that <e>might</e> access the sound card while
+Please shut down any programs that <e>might</e> access the sound card while
running <c>alsaconf</c>.
</note>
<p>
-Another way to configure your sound card is to run <c>alsaconf</c>. Just type
-<c>alsaconf</c> in a shell as root.
+To configure your sound card just type <c>alsaconf</c> in a shell as root.
</p>
<pre caption="Invoking alsaconf">
@@ -476,10 +475,10 @@
</pre>
<p>
-You will now see a neat menu guided interface that will automatically probe
-your devices and try to find out your sound card. You will be asked to pick
-your sound card from a list. Once that's done, it will ask you permission to
-automatically make required changes to <path>/etc/modules.d/alsa</path>.
+You will now see a neat menu guided interface that will automatically probe
+your devices and try to find out your sound card. You will be asked to pick
+your sound card from a list. Once that's done, it will ask you permission to
+automatically make required changes to <path>/etc/modules.d/alsa</path>.
It will then adjust your volume settings to optimum levels, run
<c>update-modules</c> and start the <path>/etc/init.d/alsasound</path> service.
Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA
@@ -493,9 +492,9 @@
<body>
<p>
-We're now almost all setup. Whichever method you chose to install ALSA, you'll
-need to have something load your modules or initialize ALSA and restore your
-volume settings when your system comes up. The ALSA Initscript handles all of
+We're now almost all setup. Whichever method you chose to install ALSA, you'll
+need to have something load your modules or initialize ALSA and restore your
+volume settings when your system comes up. The ALSA Initscript handles all of
this for you and is called <c>alsasound</c>. Add it to the boot runlevel.
</p>
@@ -506,8 +505,8 @@
</pre>
<p>
-Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that
-SAVE_ON_STOP variable is set to yes. This saves your sound settings when you
+Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that
+SAVE_ON_STOP variable is set to yes. This saves your sound settings when you
shutdown your system.
</p>
@@ -541,17 +540,17 @@
<body>
<p>
-We've completed all the setups and prerequisites, so let's fire up ALSA. If
-you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
+We've completed all the setups and prerequisites, so let's fire up ALSA. If
+you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
does this for you.
</p>
<pre caption="Start the service">
-# <i>/etc/init.d/alsasound start</i>
+# <i>/etc/init.d/alsasound start</i>
</pre>
<p>
-Now that the required things have been taken care of, we need to check up on
+Now that the required things have been taken care of, we need to check up on
the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this
purpose.
</p>
@@ -570,9 +569,9 @@
</impo>
<p>
-This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay
-attention to the Master and PCM channels which both have an MM below them.
-That means they are muted. If you try to play anything with <c>alsamixer</c>
+This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay
+attention to the Master and PCM channels which both have an MM below them.
+That means they are muted. If you try to play anything with <c>alsamixer</c>
in this state, you will not hear anything on your speakers.
</p>
@@ -589,28 +588,28 @@
<ul>
<li>
- To move between channels, use your left and right arrow keys. (<-
+ To move between channels, use your left and right arrow keys. (<-
& ->)
</li>
<li>
- To toggle mute, move to the specific channel, for example Master and press
- the <e>m</e> key on the keyboard.
+ To toggle mute, move to the specific channel, for example Master and press
+ the <e>m</e> key on the keyboard.
</li>
<li>
- To increase and decrease the volume levels, use the up and down arrow keys
+ To increase and decrease the volume levels, use the up and down arrow keys
respectively.
</li>
</ul>
<note>
-Be careful when setting your Bass and Treble values. 50 is usually a good
-number for both. Extremely high values of Bass may cause <e>jarring</e>
+Be careful when setting your Bass and Treble values. 50 is usually a good
+number for both. Extremely high values of Bass may cause <e>jarring</e>
on speakers that are not designed to handle them.
</note>
<p>
-After you're all done, your ALSA Mixer should look similar to the one below.
-Note the 00 instead of the MM and also the volume levels for some optimum
+After you're all done, your ALSA Mixer should look similar to the one below.
+Note the 00 instead of the MM and also the volume levels for some optimum
settings.
</p>
@@ -686,20 +685,20 @@
<body>
<p>
-If for some reason you're unable to hear sound, the first thing to do would
-be to check your <uri link="#doc_chap3_pre6">alsamixer</uri> settings. 80% of
-the issues lie with muted channels or low volume. Also check your Window
+If for some reason you're unable to hear sound, the first thing to do would
+be to check your <uri link="#doc_chap3_pre6">alsamixer</uri> settings. 80% of
+the issues lie with muted channels or low volume. Also check your Window
Manager's sound applet and verify that volumes are set to audible levels.
</p>
<p>
-<path>/proc</path> is your friend. And in this case, <path>/proc/asound</path>
-is your best friend. We shall just take a short look at how much info is made
+<path>/proc</path> is your friend. And in this case, <path>/proc/asound</path>
+is your best friend. We shall just take a short look at how much info is made
available to us there.
</p>
<pre caption="Fun with /proc/asound">
-<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has
+<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has
picked up your sound card fine.)</comment>
# <i>cat /proc/asound/cards</i>
0 [Live ]: EMU10K1 - Sound Blaster Live!
@@ -844,11 +843,11 @@
</p>
<p>
-If your sound card is one of those that come with on-board MIDI synthesizers
-and you would like to listen to some .mid files, you have to install
-<c>awesfx</c> which is basically a set of utilities for controlling the AWE32
-driver. We need to install it first. If you don't have a hardware synthesizer,
-you can use a virtual one. Please see the section on
+If your sound card is one of those that come with on-board MIDI synthesizers
+and you would like to listen to some .mid files, you have to install
+<c>awesfx</c> which is basically a set of utilities for controlling the AWE32
+driver. We need to install it first. If you don't have a hardware synthesizer,
+you can use a virtual one. Please see the section on
<uri link="#vsynth">Virtual Synthesizers</uri> for more information.
</p>
@@ -857,21 +856,21 @@
</pre>
<note>
-You will need to copy over SoundFont (SF2) files from your sound card's driver
-CD or a Windows installation into <path>/usr/share/sounds/sf2/</path>. For
+You will need to copy over SoundFont (SF2) files from your sound card's driver
+CD or a Windows installation into <path>/usr/share/sounds/sf2/</path>. For
example a sound font file for the Creative SBLive! card would be 8MBGMSFX.SF2.
</note>
<p>
After copying over the Soundfont files, we can then play a midi file as shown.
-You can also add the <c>asfxload</c> command to
-<path>/etc/conf.d/local.start</path>, so that the sound font is loaded
+You can also add the <c>asfxload</c> command to
+<path>/etc/conf.d/local.start</path>, so that the sound font is loaded
every time the system starts up.
</p>
<note>
-<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</e>
-be the same in your machine. They are just an example. Please be careful to
+<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</e>
+be the same in your machine. They are just an example. Please be careful to
change the path to suit your machine.
</note>
@@ -885,8 +884,8 @@
</pre>
<p>
-You can now play midi files using a program like <c>aplaymidi</c>. Run
-<c>aplaymidi -l</c> to get a list of available ports and then pick one
+You can now play midi files using a program like <c>aplaymidi</c>. Run
+<c>aplaymidi -l</c> to get a list of available ports and then pick one
to play the file on.
</p>
@@ -923,7 +922,7 @@
install some sound font packages for you. There are a few other font packages
available in Portage, such as <c>timidity-freepats</c> and
<c>timidity-eawpatches</c>. You can have multiple sound font configurations
-installed, and you can place your own in <path>/usr/share/timidity/</path>. To
+installed, and you can place your own in <path>/usr/share/timidity/</path>. To
switch between different timidity configurations, you should use
<c>eselect</c>.
</p>
@@ -971,7 +970,7 @@
<p>
You can have more than one sound card in your system simultaneously, provided
that you have built ALSA as modules in your kernel (or have installed
-<c>alsa-driver</c> instead). You just need to specify which should be started
+<c>alsa-driver</c> instead). You just need to specify which should be started
first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their
driver names inside this file. 0 is the first card, 1 is the second, and so on.
Here's an example for a system with two sound cards.
@@ -1020,7 +1019,7 @@
<p>
Everyone who contributed to the earlier version of the Gentoo ALSA Guide:
-Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston,
+Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston,
John P. Davis, Sven Vermeulen, Benny Chuang, Tiemo Kieft and Erwin.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
* [gentoo-doc-cvs] cvs commit: alsa-guide.xml
@ 2008-03-05 9:16 Joshua Saddler
0 siblings, 0 replies; 26+ messages in thread
From: Joshua Saddler @ 2008-03-05 9:16 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 08/03/05 09:16:49
Modified: alsa-guide.xml
Log:
removed alsa-driver steps from the guide, per bug 183418, bug 207427 and other showstopper/regression bugs, and requests from the alsa & kernel teams. no one maintains or wants to maintain alsa-driver. it is the weakest link.
Revision Changes Path
1.81 xml/htdocs/doc/en/alsa-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.81&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?rev=1.81&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/alsa-guide.xml?r1=1.80&r2=1.81
Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- alsa-guide.xml 19 May 2007 03:00:29 -0000 1.80
+++ alsa-guide.xml 5 Mar 2008 09:16:49 -0000 1.81
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.80 2007/05/19 03:00:29 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.81 2008/03/05 09:16:49 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.22</version>
-<date>2007-05-07</date>
+<version>2.23</version>
+<date>2008-03-05</date>
<chapter>
<title>Introduction</title>
@@ -56,132 +56,39 @@
<body>
<p>
-One of Gentoo's main strengths lies in giving the user maximum control over
-how a system is installed/configured. ALSA on Gentoo follows the same
-principle. There are two ways you can get ALSA support up and running on your
-system. We shall look at them in detail in the next chapter.
+Historically, Gentoo offered two ways to get ALSA up and running: the
+<e>in-kernel</e> driver and the external <c>alsa-driver</c> package. The two
+solutions essentially do the same thing; this made supporting the external
+package extremely difficult and time-consuming. The Gentoo maintainers decided
+to discontinue support for the <c>alsa-driver</c> package, concentrating their
+resources on the ALSA drivers available within the Linux kernel. This guide will
+focus solely on configuring ALSA via the in-kernel driver.
</p>
-</body>
-</section>
-</chapter>
-
-<chapter>
-<title>Installing ALSA</title>
-<section>
-<title>Options</title>
-<body>
-
-<warn>
-The methods shown below are mutually exclusive. You cannot have ALSA compiled
-in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail.
-</warn>
-
<p>
-The two options are:
+If you still require the <c>alsa-driver</c> package, please email the <mail
+link="alsa-bugs@gentoo.org">Gentoo ALSA maintainers</mail> with why the
+in-kernel drivers don't work for you. Be sure to include detailed error logs.
</p>
-<ol>
- <li>
- Use ALSA provided by your kernel. This is the preferred/recommended method.
- </li>
- <li>Use Gentoo's <c>media-sound/alsa-driver</c> package.</li>
-</ol>
-
-<p>
-The in-kernel drivers and the <c>alsa-driver</c> package can vary a little; it's
-possible that features and fixes found in one might not yet be incorporated into
-the other. The upstream developers are aware of this, but the two drivers are
-effectively separate branches of the ALSA project; they are not entirely
-identical. You should be aware that they might function slightly differently, so
-if one doesn't work for you, try the other! We shall take a peek into both
-before finally deciding on one.
-</p>
-
-<p>
-If you were to use ALSA provided by the kernel, the following are the pros and
-cons:
-</p>
-
-<table>
-<tr>
- <th>Kernel ALSA</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- No need to emerge yet another package; drivers are integrated into kernel.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>One shot solution, no repeating emerges.</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>Might be a slightly different version than <c>alsa-driver</c>.</ti>
-</tr>
-</table>
-
-<p>
-And, if you were to use <c>alsa-driver</c>,
-</p>
-
-<table>
-<tr>
- <th>alsa-driver</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>Possibly the latest drivers from the ALSA Project.</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Useful if you intend to develop audio drivers.</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>Every kernel recompile requires a re-emerge of <c>alsa-driver</c>.</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>Needs certain kernel config options disabled to work correctly.</ti>
-</tr>
-</table>
-
</body>
</section>
-<section>
-<title>So...</title>
-<body>
-
-<p>
-The differences between <c>alsa-driver</c> and the in-kernel ALSA drivers are
-quite subtle, as mentioned earlier. Since there are not any huge differences,
-you are encouraged to go through the process of using the ALSA provided by the
-kernel <e>first</e> for ease of use. Before reporting any sound related issues
-to <uri link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to
-reproduce them using <c>alsa-driver</c> and file the bug report no matter what
-the result.
-</p>
+</chapter>
-</body>
-</section>
+<chapter>
+<title>Installing ALSA</title>
<section id="lspci">
<title>Before you proceed</title>
<body>
<p>
-Whichever method of install you choose, you need to know what drivers your
-sound card uses. In most cases, sound cards (onboard and otherwise) are PCI
-based and <c>lspci</c> will help you in digging out the required information.
-Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it
-installed already. In case you have a USB sound card, <c>lsusb</c> from
-<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using
-<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users
-with ISA based sound cards:
+First, you need to know what drivers your sound card uses. In most cases, sound
+cards (onboard and otherwise) are PCI based and <c>lspci</c> will help you in
+digging out the required information. Please <c>emerge sys-apps/pciutils</c> to
+get <c>lspci</c>, if you don't have it installed already. In case you have a USB
+sound card, <c>lsusb</c> from <c>sys-apps/usbutils</c> <e>might</e> be of help.
+For ISA cards, try using <c>sys-apps/isapnptools</c>. Also, the following pages
+<e>may</e> help users with ISA based sound cards:
</p>
<ul>
@@ -233,13 +140,9 @@
</body>
</section>
<section id="kernel">
-<title>Using ALSA provided by your Kernel</title>
+<title>Configuring the kernel</title>
<body>
-<p>
-If you're a person who likes to keep things simple, then this is the way to go.
-</p>
-
<note>
Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Please
check that your kernel is a 2.6 series kernel. This method will <e>not</e> work
@@ -337,91 +240,6 @@
</body>
</section>
-<section id="alsa-driver">
-<title>Using the ALSA Driver package</title>
-<body>
-
-<p>
-So you've decided to go the <c>alsa-driver</c> way. Let's get started then.
-There are a few minor things to be done to ensure only the drivers for your
-sound card are compiled. Although this is not really necessary, it cuts down
-on the unnecessary drivers that will be compiled otherwise.
-</p>
-
-<p>
-If you don't have an idea of what drivers your sound card might need, please
-take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once
-you have your driver name (<c>emu10k1</c> in our example), edit
-<path>/etc/make.conf</path> and add a variable, <c>ALSA_CARDS</c>.
-</p>
-
-<pre caption="Adding ALSA_CARDS to make.conf">
-<comment>(For one sound card)</comment>
-ALSA_CARDS="emu10k1"
-<comment>(For more than one, separate names with spaces)</comment>
-ALSA_CARDS="emu10k1 via82xx"
-</pre>
-
-<p>
-If you have compiled your kernel and want to use <c>alsa-driver</c>, please
-ensure the following before proceeding, else <c>alsa-driver</c> is likely to
-fail. The next code listing gives you one way of performing the checks.
-</p>
-
-<note>
-<c>genkernel</c> users can proceed with <uri link="#doc_chap2_pre6">Installing
-alsa-driver</uri> as their configuration is in sync with the one shown below by
-default.
-</note>
-
-<ol>
- <li>
- <c>CONFIG_SOUND</c> is set. (Basic Sound support enabled)
- </li>
- <li>
- <c>CONFIG_SOUND_PRIME</c> is not set. (In-built OSS support disabled)
- </li>
- <li>
- <c>CONFIG_SND</c> is not set. (In-built ALSA support disabled)
- </li>
- <li>
- <path>/usr/src/linux</path> points to the kernel you want ALSA working on.
- </li>
-</ol>
-
-<pre caption=".config checks">
-<comment>(Assuming the linux symlink points to the correct kernel)</comment>
-# <i>cd /usr/src/linux</i>
-# <i>grep SOUND .config</i>
-<comment>(1. is true)</comment>
-CONFIG_SOUND=y
-<comment>(2. is true)</comment>
-CONFIG_SOUND_PRIME is not set
-# <i>grep SND .config</i>
-<comment>(and 3. is true)</comment>
-CONFIG_SND is not set
-</pre>
-
-<p>
-Now all you have to do is type the magic words... and no, it's not abracadabra.
-</p>
-
-<pre caption="Installing alsa-driver">
-# <i>emerge alsa-driver</i>
-</pre>
-
-<impo>
-Please note that you will have to run <c>emerge alsa-driver</c> after every
-kernel (re)compile, as the earlier drivers are deleted. To make this task
-easier, you may want to emerge the <c>module-rebuild</c> package, which will
-keep track of module packages and rebuild them for you. First run
-<c>module-rebuild populate</c> to create the list, and then after every kernel
-(re)compile, you just run <c>module-rebuild rebuild</c>, and your external
-modules will be rebuilt.
-</impo>
-
-</body>
-</section>
</chapter>
<chapter>
@@ -441,11 +259,10 @@
</pre>
<note>
-If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did
-not compile ALSA as modules, please proceed to the
-<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need
-to configure ALSA. This is made very easy by the existence of the
-<c>alsaconf</c> tool provided by <c>alsa-utils</c>.
+If you did <e>not</e> compile ALSA as modules, please proceed to the <uri
+link="#initscript">ALSA Initscript</uri> section. The rest of you need to
+configure ALSA. This is made very easy by the existence of the <c>alsaconf</c>
+tool provided by <c>alsa-utils</c>.
</note>
</body>
@@ -735,6 +552,8 @@
0: SigmaTel STAC9721/23
</pre>
+<!-- TODO: remove this a few months after alsa-driver leaves the tree -->
+
<p>
The other most common issue users face is the dreaded "Unknown symbol in module"
error. An example of the same is shown below.
@@ -787,7 +606,7 @@
</pre>
<p>
-The above issue is caused when you switch from <c>alsa-driver</c> to in-kernel
+The above issue is caused when you switch from the <c>alsa-driver</c> to in-kernel
ALSA because when you unmerge <c>alsa-driver</c> the module files are config
protected and hence get left behind. So, when you switch to in-kernel
drivers, running <c>modprobe</c> gives you a mix of <c>alsa-driver</c> and
@@ -821,10 +640,12 @@
<p>
Usually it is a file called <path>alsa</path> with the line <c>options snd
-device_mode=0666</c>. Remove this line and restart the alsasound service and
-that should take care of this issue.
+device_mode=0666</c>. Remove this line and restart the <c>alsasound</c> service
+and that should take care of this issue.
</p>
+<!-- End of removal notice -->
+
</body>
</section>
</chapter>
@@ -839,7 +660,7 @@
First, check to make sure that you enabled the <c>midi</c> USE flag in
<path>/etc/make.conf</path>. If you didn't, go ahead and add it now. You will
also need to re-emerge any ALSA packages that use the <c>midi</c> flag, such as
-<c>alsa-lib</c>, <c>alsa-utils</c>, and <c>alsa-driver</c>.
+<c>alsa-lib</c> and <c>alsa-utils</c>.
</p>
<p>
@@ -969,11 +790,10 @@
<p>
You can have more than one sound card in your system simultaneously, provided
-that you have built ALSA as modules in your kernel (or have installed
-<c>alsa-driver</c> instead). You just need to specify which should be started
-first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their
-driver names inside this file. 0 is the first card, 1 is the second, and so on.
-Here's an example for a system with two sound cards.
+that you have built ALSA as modules in your kernel. You just need to specify
+which should be started first in <path>/etc/modules.d/alsa</path>. Your cards
+are identified by their driver names inside this file. 0 is the first card, 1 is
+the second, and so on. Here's an example for a system with two sound cards.
</p>
<pre caption="Two sound cards in /etc/modules.d/alsa">
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2008-03-05 9:16 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-19 3:00 [gentoo-doc-cvs] cvs commit: alsa-guide.xml Josh Saddler
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 9:16 Joshua Saddler
2007-05-07 7:08 Josh Saddler
2007-05-06 23:27 Josh Saddler
2007-05-03 6:21 Josh Saddler
2007-03-10 13:02 Jan Kundrat
2007-02-17 19:03 Josh Saddler
2007-01-31 16:39 Josh Saddler
2007-01-31 15:54 Josh Saddler
2006-11-02 18:24 Josh Saddler
2006-07-07 14:40 Lukasz Damentko
2006-07-06 19:51 Lukasz Damentko
2006-05-27 13:59 Xavier Neys
2006-05-01 5:52 Shyam Mani
2006-03-25 6:59 Shyam Mani
2006-01-01 11:51 Xavier Neys
2005-10-30 16:02 Shyam Mani
2005-09-10 18:02 swift
2005-09-09 6:49 Shyam Mani
2005-08-30 11:38 Shyam Mani
2005-07-26 17:28 Marcelo Goes
2005-07-16 11:45 Alin Dobre
2005-07-14 19:22 Shyam Mani
2005-07-14 9:11 Xavier Neys
2005-07-14 9:05 Sven Vermeulen
2005-07-12 19:17 Shyam Mani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox