Lines 24-31
Link Here
|
24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
25 |
<license/> |
25 |
<license/> |
26 |
|
26 |
|
27 |
<version>2.22</version> |
27 |
<version>3</version> |
28 |
<date>2007-05-07</date> |
28 |
<date>2007-06-27</date> |
29 |
|
29 |
|
30 |
<chapter> |
30 |
<chapter> |
31 |
<title>Introduction</title> |
31 |
<title>Introduction</title> |
Lines 51-69
Link Here
|
51 |
|
51 |
|
52 |
</body> |
52 |
</body> |
53 |
</section> |
53 |
</section> |
54 |
<section> |
|
|
55 |
<title>ALSA on Gentoo</title> |
56 |
<body> |
57 |
|
58 |
<p> |
59 |
One of Gentoo's main strengths lies in giving the user maximum control over |
60 |
how a system is installed/configured. ALSA on Gentoo follows the same |
61 |
principle. There are two ways you can get ALSA support up and running on your |
62 |
system. We shall look at them in detail in the next chapter. |
63 |
</p> |
64 |
|
65 |
</body> |
66 |
</section> |
67 |
</chapter> |
54 |
</chapter> |
68 |
|
55 |
|
69 |
<chapter> |
56 |
<chapter> |
Lines 72-170
Link Here
|
72 |
<title>Options</title> |
59 |
<title>Options</title> |
73 |
<body> |
60 |
<body> |
74 |
|
61 |
|
75 |
<warn> |
|
|
76 |
The methods shown below are mutually exclusive. You cannot have ALSA compiled |
77 |
in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail. |
78 |
</warn> |
79 |
|
80 |
<p> |
62 |
<p> |
81 |
The two options are: |
63 |
Gentoo has always been offering two ways to get ALSA up and running for its |
82 |
</p> |
64 |
users, the <e>in-kernel method</e> and the <c>media-sound/alsa-driver</c> |
83 |
|
65 |
package. Having two packages essentially doing the same thing proved to be |
84 |
<ol> |
66 |
pretty hard and time consuming. Therefore, in June 2006 it was decided to |
85 |
<li> |
67 |
discontinue support for the <c>media-sound/alsa-driver</c> package which was |
86 |
Use ALSA provided by your kernel. This is the preferred/recommended method. |
68 |
added to the list of packages slotted for removal from the tree. If you still |
87 |
</li> |
69 |
require the <c>alsa-driver</c> package, please mail <mail |
88 |
<li>Use Gentoo's <c>media-sound/alsa-driver</c> package.</li> |
70 |
link="alsa-bugs@gentoo.org">Gentoo ALSA maintainers</mail> with details about |
89 |
</ol> |
71 |
why the in-kernel drivers don't work for you. |
90 |
|
|
|
91 |
<p> |
92 |
The in-kernel drivers and the <c>alsa-driver</c> package can vary a little; it's |
93 |
possible that features and fixes found in one might not yet be incorporated into |
94 |
the other. The upstream developers are aware of this, but the two drivers are |
95 |
effectively separate branches of the ALSA project; they are not entirely |
96 |
identical. You should be aware that they might function slightly differently, so |
97 |
if one doesn't work for you, try the other! We shall take a peek into both |
98 |
before finally deciding on one. |
99 |
</p> |
100 |
|
101 |
<p> |
102 |
If you were to use ALSA provided by the kernel, the following are the pros and |
103 |
cons: |
104 |
</p> |
105 |
|
106 |
<table> |
107 |
<tr> |
108 |
<th>Kernel ALSA</th> |
109 |
<th>Pros and Cons</th> |
110 |
</tr> |
111 |
<tr> |
112 |
<th>+</th> |
113 |
<ti> |
114 |
No need to emerge yet another package; drivers are integrated into kernel. |
115 |
</ti> |
116 |
</tr> |
117 |
<tr> |
118 |
<th>+</th> |
119 |
<ti>One shot solution, no repeating emerges.</ti> |
120 |
</tr> |
121 |
<tr> |
122 |
<th>-</th> |
123 |
<ti>Might be a slightly different version than <c>alsa-driver</c>.</ti> |
124 |
</tr> |
125 |
</table> |
126 |
|
127 |
<p> |
128 |
And, if you were to use <c>alsa-driver</c>, |
129 |
</p> |
130 |
|
131 |
<table> |
132 |
<tr> |
133 |
<th>alsa-driver</th> |
134 |
<th>Pros and Cons</th> |
135 |
</tr> |
136 |
<tr> |
137 |
<th>+</th> |
138 |
<ti>Possibly the latest drivers from the ALSA Project.</ti> |
139 |
</tr> |
140 |
<tr> |
141 |
<th>+</th> |
142 |
<ti>Useful if you intend to develop audio drivers.</ti> |
143 |
</tr> |
144 |
<tr> |
145 |
<th>-</th> |
146 |
<ti>Every kernel recompile requires a re-emerge of <c>alsa-driver</c>.</ti> |
147 |
</tr> |
148 |
<tr> |
149 |
<th>-</th> |
150 |
<ti>Needs certain kernel config options disabled to work correctly.</ti> |
151 |
</tr> |
152 |
</table> |
153 |
|
154 |
</body> |
155 |
</section> |
156 |
<section> |
157 |
<title>So...</title> |
158 |
<body> |
159 |
|
160 |
<p> |
161 |
The differences between <c>alsa-driver</c> and the in-kernel ALSA drivers are |
162 |
quite subtle, as mentioned earlier. Since there are not any huge differences, |
163 |
you are encouraged to go through the process of using the ALSA provided by the |
164 |
kernel <e>first</e> for ease of use. Before reporting any sound related issues |
165 |
to <uri link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to |
166 |
reproduce them using <c>alsa-driver</c> and file the bug report no matter what |
167 |
the result. |
168 |
</p> |
72 |
</p> |
169 |
|
73 |
|
170 |
</body> |
74 |
</body> |
Lines 174-180
Link Here
|
174 |
<body> |
78 |
<body> |
175 |
|
79 |
|
176 |
<p> |
80 |
<p> |
177 |
Whichever method of install you choose, you need to know what drivers your |
81 |
At first, you need to know what drivers your |
178 |
sound card uses. In most cases, sound cards (onboard and otherwise) are PCI |
82 |
sound card uses. In most cases, sound cards (onboard and otherwise) are PCI |
179 |
based and <c>lspci</c> will help you in digging out the required information. |
83 |
based and <c>lspci</c> will help you in digging out the required information. |
180 |
Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it |
84 |
Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it |
Lines 236-245
Link Here
|
236 |
<title>Using ALSA provided by your Kernel</title> |
140 |
<title>Using ALSA provided by your Kernel</title> |
237 |
<body> |
141 |
<body> |
238 |
|
142 |
|
239 |
<p> |
|
|
240 |
If you're a person who likes to keep things simple, then this is the way to go. |
241 |
</p> |
242 |
|
243 |
<note> |
143 |
<note> |
244 |
Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Please |
144 |
Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Please |
245 |
check that your kernel is a 2.6 series kernel. This method will <e>not</e> work |
145 |
check that your kernel is a 2.6 series kernel. This method will <e>not</e> work |
Lines 338-348
Link Here
|
338 |
</body> |
238 |
</body> |
339 |
</section> |
239 |
</section> |
340 |
<section id="alsa-driver"> |
240 |
<section id="alsa-driver"> |
|
|
241 |
<!-- |
242 |
This section will be removed when the alsa-driver package leaves the tree. It's |
243 |
been left in for a transition period as it's still possible that some people |
244 |
might require it for sound to work. |
245 |
--> |
341 |
<title>Using the ALSA Driver package</title> |
246 |
<title>Using the ALSA Driver package</title> |
342 |
<body> |
247 |
<body> |
343 |
|
248 |
|
|
|
249 |
<impo> |
250 |
The <c>alsa-driver</c> package is not supported by Gentoo developers. If your |
251 |
soundcard doesn't work with in-kernel drivers, it's a bug that should be fixed. |
252 |
Please let the <mail link="alsa-bugs@gentoo.org">Gentoo ALSA maintainers</mail> |
253 |
know about your issues. If you don't, this package will be removed from the tree |
254 |
and sound will stop working for you. |
255 |
</impo> |
256 |
|
344 |
<p> |
257 |
<p> |
345 |
So you've decided to go the <c>alsa-driver</c> way. Let's get started then. |
|
|
346 |
There are a few minor things to be done to ensure only the drivers for your |
258 |
There are a few minor things to be done to ensure only the drivers for your |
347 |
sound card are compiled. Although this is not really necessary, it cuts down |
259 |
sound card are compiled. Although this is not really necessary, it cuts down |
348 |
on the unnecessary drivers that will be compiled otherwise. |
260 |
on the unnecessary drivers that will be compiled otherwise. |
Lines 735-740
Link Here
|
735 |
0: SigmaTel STAC9721/23 |
647 |
0: SigmaTel STAC9721/23 |
736 |
</pre> |
648 |
</pre> |
737 |
|
649 |
|
|
|
650 |
<!-- TODO: this should be probably removed after a few months after the |
651 |
alsa-driver leaves the tree --> |
652 |
|
738 |
<p> |
653 |
<p> |
739 |
The other most common issue users face is the dreaded "Unknown symbol in module" |
654 |
The other most common issue users face is the dreaded "Unknown symbol in module" |
740 |
error. An example of the same is shown below. |
655 |
error. An example of the same is shown below. |
Lines 825-830
Link Here
|
825 |
that should take care of this issue. |
740 |
that should take care of this issue. |
826 |
</p> |
741 |
</p> |
827 |
|
742 |
|
|
|
743 |
<!-- end of removal notice --> |
744 |
|
828 |
</body> |
745 |
</body> |
829 |
</section> |
746 |
</section> |
830 |
</chapter> |
747 |
</chapter> |
Lines 969-976
Link Here
|
969 |
|
886 |
|
970 |
<p> |
887 |
<p> |
971 |
You can have more than one sound card in your system simultaneously, provided |
888 |
You can have more than one sound card in your system simultaneously, provided |
972 |
that you have built ALSA as modules in your kernel (or have installed |
889 |
that you have built ALSA as modules in your kernel. You just need to specify |
973 |
<c>alsa-driver</c> instead). You just need to specify which should be started |
890 |
which should be started |
974 |
first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their |
891 |
first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their |
975 |
driver names inside this file. 0 is the first card, 1 is the second, and so on. |
892 |
driver names inside this file. 0 is the first card, 1 is the second, and so on. |
976 |
Here's an example for a system with two sound cards. |
893 |
Here's an example for a system with two sound cards. |