| 1 |
On Thu, 2009-10-01 at 15:08 +0200, Stefan G. Weichinger wrote: |
| 2 |
> Daniel Troeder schrieb: |
| 3 |
> > On Thu, 2009-10-01 at 06:48 +0200, Stefan G. Weichinger wrote: |
| 4 |
> >> Daniel Troeder schrieb: |
| 5 |
> >> Same here. After booting no sound ... in PA all looks good, after some |
| 6 |
> >> searching I find alsamixer mutes things ... sigh ... but as long as |
| 7 |
> >> there aren't more problems I can live with it. |
| 8 |
> > You can set things with alsamixer, and then (save and) restore them on |
| 9 |
> > (re)boot with /etc/init.d/alsasound |
| 10 |
> > Setup is in /etc/conf.d/alsasound. |
| 11 |
> |
| 12 |
> So I have to have both services running, alsasound AND pulseaudio ? |
| 13 |
> I assumed I would have to disable alsasound when using PA (and disabled |
| 14 |
> it ...) |
| 15 |
ALSA is not a service (it's just drivers and API). There is nothing |
| 16 |
running. It just loads your configuration (modules and volume levels). |
| 17 |
PA on the other hand does not have hardware drivers - it relies on ALSA |
| 18 |
or OSS for that. |
| 19 |
|
| 20 |
-- |
| 21 |
PGP key @ http://pgpkeys.pca.dfn.de/pks/lookup?search=0xBB9D4887&op=get |
| 22 |
# gpg --recv-keys --keyserver hkp://subkeys.pgp.net 0xBB9D4887 |
Archives