On Sat, 8 Jun 2002 14:09:49 +0930
Adam Luchjenbroers <[EMAIL PROTECTED]> wrote:
>
> Here is the sound-initialisation portion of my modules.conf file. I am using
> a SoundBlaster Vibra128 PCI (ens1371).
>
> # Core Sound Drivers
> alias char-major-14 soundcore
> alias char-major-116 snd
>
> # Setup card for ALSA
> alias snd-card-0 snd-ens1371
> options snd-ens1371 snd_index 0 snd_id vibra
This should read: options snd-ens1371 snd_index=0 snd_id=vibra ;)
> # Setup links for OSS
> alias snd-card-0 sound-slot-0
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-12 snd-pcm-oss
>
> The boot process makes no mention of starting ALSA. Alsamixer cannot find the
> device until I type in
>
> ]# modprobe snd-ens1371
> ]# alsadevices
>
> (NB: alsadevices is a copy of the snddevices script that comes with the
> alsa-drivers package).
Check the INSTALL file if you are using DEVFS.
> If I do this and tweak the volume alsaplayer can be run (however it fails to
> use ALSA to do so, resorting to OSS (emulated by ALSA), however I suspect
> this is because alsaplayer is for 0.5.x, aplay reports no errors)
>
> I am also having trouble getting the aRTs soundserver (KDEs soundsystem) to
> detect and use ALSA (or OSS), anyone know how to get it to find it.
>
> Anybody know how to make it load without requiring intervention and/or how to
> make aRTs detect it.
HTH,
-Frans
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
