| 1 |
Duncan wrote: |
| 2 |
> |
| 3 |
> This sounds to me like one of the sound modules isn't loaded. ALSA has |
| 4 |
> always started muted, until it's unmuted, but that can't be it, as xine |
| 5 |
> should then play, it'd just be muted. But if one of the necessary |
| 6 |
> modules wasn't loaded, xine would presumably detect that by the failure |
| 7 |
> to open the device at all, thus the xine-out.wav. |
| 8 |
|
| 9 |
All modules are loaded. In fact I just rebuilt my kernel yesterday and |
| 10 |
repopulated the modules that are to load on startup, and still the same |
| 11 |
problem. |
| 12 |
|
| 13 |
As a regular user, if I start alsamixer and see basically a display with |
| 14 |
no channels, I need to rerun alsaconf as root. |
| 15 |
Once done, alsamixer looks proper with all the channels. |
| 16 |
The only channel that is muted after this, is the mic channel. |
| 17 |
|
| 18 |
|
| 19 |
> |
| 20 |
> But running the config loads the modules, which apparently are NOT auto- |
| 21 |
> loaded by the alsa service or whatever you have running at start to bring |
| 22 |
> back sound -- that's assuming that you DO have something running to load |
| 23 |
> sound at start. |
| 24 |
|
| 25 |
Alsa is set to run on boot, and "save on top" as in the Gentoo |
| 26 |
instructions is set. |
| 27 |
If I try to add it to the boot up I get the message that it is already |
| 28 |
loaded. |
| 29 |
|
| 30 |
> |
| 31 |
> FWIW, I've never had an issue of that nature here. |
| 32 |
|
| 33 |
I have not had this issue before either, this started some time ago, now |
| 34 |
out of frustration I am trying to figure out why. It use to work fine |
| 35 |
on this system. |
| 36 |
|
| 37 |
|
| 38 |
> |
| 39 |
> BUT, my kernel policy has for YEARS been to build-in everything possible |
| 40 |
> that I use enough to keep loaded. |
| 41 |
|
| 42 |
I build alsa as modules since the instructions recommend that it is the |
| 43 |
best method. |
Archives