From: Aivils S. <ai...@un...> - 2006-01-16 07:25:58
|
> Hugo Vanwoerkom wrote: > >--- ludovic pollet <pl...@nn...> wrote: > > > > =A0 > > > >>Hello, > >> > >>For most alsa application, correctly setting the > >>following environment > >>variable will do the trick : > >> > >>ALSA_CARD=3D1 > >>ALSA_CTL_CARD=3D1 > >>ALSA_PCM_CARD=3D1 > >> > >>You can force SDL games to use alsa with : > >> > >>SDL_AUDIODRIVER=3Dalsa > >> > >> > >>But applications which use the OSS API will cause > >>problems (mozilla plugins, > >>openoffice, old games, ...) > >> > >>For those, you will need to make the device entries > >>point to different files > >>depending on the DISPLAY : I do that at home. Have a > >>look at > >>http://www.nnx.com/~pludov/sessiond/ SDL driver is one , which have hardcoded /dev/sound/dsp Please use Ludovic recomendations. Create a user login script: SDL_AUDIODRIVER=3D"oss" AUDIODEVICE=3D"/dev/dsp" export $SDL_AUDIODRIVER $AUDIODEVICE I am not udev expert, but that /dev/sound is artifical, created by udev config scripts - so is _not_ forced to create /dev/sound at all. Edit udev scripts and You have dspXX where You want. Under Mandriva edit /etc/udev/rules.d/50-mdk.rules =46or appliaction , which does suspicious things # strace -oapp.log application-bin Analyze app.log or simpler method # strings application-bin | grep dsp or # strings lib-plugin.so | grep dsp Aivils |