The Gentoo Linux ALSA Guide, Using the ALSA Driver package, tells you to disable all Alsa and OSS options in the kernel, and enable sound card support as built-in module: <*> Sound card support according to: CONFIG_SOUND is set. (Basic Sound support enabled) # grep SOUND .config (1. is true) CONFIG_SOUND=y ..in Code Listing 2.5: .config checks Though as you can see, searching on the forums for alsa-driver, people including myself where having problems, not getting it to work, especially going from the kernel way to the driver way. After lots of testing, trying the solutions from the forums without result, the solution was quite easy: CONFIG_SOUND had to be built as a module instead of built into the kernel, and therefore only 2 minor changes which will keep the small groups of people from having these problems: CONFIG_SOUND is set as module. (Basic Sound support enabled) CONFIG_SOUND=m.
i've always built Sound Card Support into my kernel, left ALSA and OSS disabled, and used alsa-driver without any problem.
Could you elaborate more on what your problem was and also provide us with links to the topics in the forums that are related to this bug?
shyam@trinity /usr/src/linux $ grep SOUND .config CONFIG_SOUND=y # CONFIG_SOUND_PRIME is not set shyam@trinity /usr/src/linux $ eix alsa-driver * media-sound/alsa-driver Available versions: 1.0.10-r2 1.0.11 [M]1.0.12_rc1 Installed: 1.0.11 Homepage: http://www.alsa-project.org/ Description: Advanced Linux Sound Architecture kernel modules WORKSFORME. I guess if you could provide more info like Lukasz suggested, it would help. Thanks!
CONFIG_SOUND=y is not a problem. Probably people had problems with is either CONFIG_SND (ALSA support) or due to not removing the old /lib/modules/`uname -r` after passing from one method (in-kernel vs alsa-driver) to the other.
Well, i can't give more related stuff, cause i solved the problem. I removed the modules as you said in these comments, i updated the modules just like the alsaconf does, i tried everything what i could find on the forums. And the only thing you can link from from the gentoo forums, is one topic at a time. I just searched and found users with similar problems, especially the users that went from in-kernel to alsa-driver (on the page only from alsa-driver to in-kernel is covered). And those people couldn't get it working for a strange reason. As i had the same problem, in the end i came up with the idea that, now it was launching all alsa-driver modules, i made CONDIF_SOUND a module too instead of built-in, copied the kernel to /boot again and restart again, and this time, it simply worked. Thats why i'm advising this.. since building that as a module won't be such a big difference for the users, but will help those few with problems.
Do you have any proof that it was switching to the module that solved your problem? I tried searching the forums and couldn't find anything like this. Maybe it was something else, that was done along with the switch?
I have no prove, nor do i feel like replicating it now. I only wanted to advise it to get people to built it as a module instead of built in, cause for he/she it works for, it will work as a module too.. and the few few people built-in doesn't work for, module might be a solution (especially since you doing everything then as loaded modules). So, if you don't feel like it should be change, thats cool too, but imho it couldn't hurt and doing it the driver module way, should be logical to do it as module too in the kernel.. So, thats all up to you now :)
Thanks for reporting but I confirmed with many people that it works without problem when you have it built-in. As we generally advise people to built their modules into the kernel, i think that this bug should be closed.
