Here is a snippet of the relevant conversation: mksoft wrote: You need to set the ALSA_CARDS env var before emerging alsa. Search for ALSA_CARDS in the forums for more info. Ahem...now why wasn't that in the desktop configuration document!!! and...uhm....feel a little dumb...let's just say that Code: cat /proc/pci |grep sound printed out Code: Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 0). Soooooo...I've been trying to use the WRONG driver since the begining!!!
Zh, Take care of this please, it seems relevant. //ZhEN
I never had to set an env var before I emerged ALSA. Any ideas Spanky? //ZhEN
There a new ALSA guide. It cover this issue. see alsa-guide.xml. but maybe changes in the build.xml are needed to point to new guide.
you dont *have* to set the environment variable ... if you read the ebuild, it tells you that ... as for using the wrong driver, thats your fault ;) zhware says he has new alsa docs, so basically all that needs to be done is have a link inserted by ZhEN into the desktop config guide # By default, drivers for all supported cards will be compiled. # If you want to only compile for specific card(s), set ALSA_CARDS # environment to a space-separated list of drivers that you want to build. # For example: # # env ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver # [ x"${ALSA_CARDS}" = x ] && ALSA_CARDS=all
I will take this because it involves build.. ;-) //ZhEN
I modified the desktop guide to use this guide. Excellent work on that new ALSA guide ;-) //ZhEN
