If I reboot my computer and log in, xmms will complain about ALSA not working ("check if your sound card is enabled", or something like that), and the xfce4 volume control will not function. Xine will be quiet. Now if, instead, I log in and start by running "aplay sound.wav", not only will I get sound, but xmms and the rest of the programs will function. Almost as if aplay does something magic which unlocks or loads some alsa component. I have not been able to reproduce this "unlocking" _after_ having run xmms. It seems it has to be done directly after boot-up (preferably outside of X, as to not load a non-working volume control). Reproducible: Always Steps to Reproduce: 1. Compile and install development-sources 2.6.9_rc1 with ALSA and emu10k1 (I think it works with modules as well as built-in). 2. Follow the Gentoo ALSA setup guide. 3. Reboot and log in. 4. To get sound: "aplay sound.wav" 5. Start xmms (for instance). If 4 was performed, xmms will play with the ALSA driver. If it wasn't, xmms will complain about ALSA not working. Actual Results: Quietness; ALSA unaccessable (as were it not loaded) Expected Results: Audio through ALSA kernel 2.6.9_rc1 from development-sources with ALSA and emu10k1 built-in
do you have 'alsasound' in the boot runlevel? does it work with an older kernel?
Yes, alsasound is in boot. I've folded back to 2.6.8 now, and it's working, but I had to add myself to the audio group -- which makes this even more strange. I did not have to be in the audio group when doing all of the stuff mentioned in the original post.
ok, then this is a problem with alsa in a specific kernel which is not maintained by the sound herd... reassigning...
We don't modify development-sources - this must be an upstream bug. Please file a bug at http://bugzilla.kernel.org
