Duncan wrote: > > This sounds to me like one of the sound modules isn't loaded. ALSA has > always started muted, until it's unmuted, but that can't be it, as xine > should then play, it'd just be muted. But if one of the necessary > modules wasn't loaded, xine would presumably detect that by the failure > to open the device at all, thus the xine-out.wav.
All modules are loaded. In fact I just rebuilt my kernel yesterday and repopulated the modules that are to load on startup, and still the same problem. As a regular user, if I start alsamixer and see basically a display with no channels, I need to rerun alsaconf as root. Once done, alsamixer looks proper with all the channels. The only channel that is muted after this, is the mic channel. > > But running the config loads the modules, which apparently are NOT auto- > loaded by the alsa service or whatever you have running at start to bring > back sound -- that's assuming that you DO have something running to load > sound at start. Alsa is set to run on boot, and "save on top" as in the Gentoo instructions is set. If I try to add it to the boot up I get the message that it is already loaded. > > FWIW, I've never had an issue of that nature here. I have not had this issue before either, this started some time ago, now out of frustration I am trying to figure out why. It use to work fine on this system. > > BUT, my kernel policy has for YEARS been to build-in everything possible > that I use enough to keep loaded. I build alsa as modules since the instructions recommend that it is the best method.
