On Wed, 24 Oct 2001 12:27:07 -0400
Duke <[EMAIL PROTECTED]> wrote:
> I'm using a Turtle Beach Santa Cruz, which uses the CS46xx
> chipset/driver, and I can't seem to get any sound. I did *once*, but
> have no idea how.
> The modules seem to load without a hitch, and I set all playback volumes
> to max and unmute. There also doesn't seem to be any conflicts with
> IO/IRQ when I check /proc/interrupts and /proc/ioports. I'm testing my
> soundcard with aplay and a wav file from my windows partition -- "aplay
> beeper.wav" -- aplay outputs some info about the file to the screen,
> and seems to play, but there's no sound. I've tried all output jacks on
> my soundcard.
> Here is the info in /proc/asound/sndstat:
>
> Sound Driver:3.8.1a-980706 (ALSA v0.9.0beta8a emulation code)
> Kernel: Linux mobius 2.4.12 #2 Fri Oct 12 16:15:23 EDT 2001 i686
> Config options: 0
>
> Installed drivers:
> Type 10: ALSA emulation
>
> Card config:
> Sound Fusion CS46xx at 0xdf102000/0xdf000000, irq 9
>
> Audio devices: NOT ENABLED IN CONFIG
>
> Synth devices: NOT ENABLED IN CONFIG
>
> Midi devices:
> 0: CS46XX
>
> Timers:
> 7: system timer
>
> Mixers: NOT ENABLED IN CONFIG
>
> The "NOT ENABLED IN CONFIG" makes me wonder if that's the problem.
> I'm using Linux kernel 2.4.12, with Alsa drivers 0.9.0beta8.
> Any tips? (let me know if more info is needed.)
> Thanks,
>
> -- Duke.
The info in /proc/asound/sndstat is about OSS emulation and
'NOT ENABLED IN CONFIG' is no problem for a native ALSA
application like aplay. Does aplay give you back the command
prompt after a 'reasonable' amount of time?
-Frans
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
