Finally, after several failed attempts, I've managed to get Teamspeak working with ALSA. I'd visited this forum on more than one occasion trying to find some clues and none of the posts I read led to a solution for me. I'm posting the answer I found in the hope that it will be of assistance to other people having problems.

Here's the setup I've got: sound chip is YMF754 which is controlled by the ymfpci driver. Audio applications work with both OSS and ALSA but Teamspeak doesn't play or record at all with OSS and wouldn't record with ALSA. Eventually I had success with ALSA 0.9.5. Previously I had tried 0.9.0 and my system locked up on a few occasions so I would definitely recommend 0.9.5 or later.

The first thing that I found I had to do was ensure that I could record correctly from the mic. ALSA allows you to monitor an input completely separately from actually recording it, so speaking into the mic and hearing your voice played back DOES NOT necessarily mean that everything is working! You need to activate the correct mixer settings using alsamixer. Skip the next paragraph if you know about alsamixer.

alsamixer is a nice little curses program which lets you set the volume of all your various inputs. The dispay is split into a bunch of vertical bars which represent the gain of each channel. At the bottom of the screen is the name of each one and its volume as a percentage. You can change channel with the left and right arrow keys and raise or lower the volume with up and down. Some channels can be muted (by pressing M) in which case they will display MM at the top of the bar. Certain channels also have either five dashes or the word CAPTUR above them. If CAPTUR is displayed it means that that channel is set to record. You can toggle this setting by pressing space.

I found that I needed to set the volume for at least the following: Master, PCM, Wave, ADC Capture and Digital. I also had to mark both Mic and Capture to record (by pressing space). You might want to mute your mic so you don't hear your voice looping back; it will still record.

You can test that your setup works using arecord, which will record from the selected input to a file, and playing the recording back with aplay. For example you could try arecord -f cd -d 3 -t wav -N test.wav which will record for three seconds. Play it back with aplay test.wav. If the combination of arecord and aplay doesn't work you will have to go back and tweak your driver and/or mixer settings some more because Teamspeak definitely won't work!

Don't forget to save your mixer settings with alsactl store. You should then think about making your system bootup scripts load the settings again with alsactl restore...

Once you are satisfied that you can record sound, the final step is to run Teamspeak, for which you need to use OSS emulation. There are two ways you can do this. The easiest way is to load the OSS emulation kernel module: modprobe snd-pcm-oss. You should then be able to run Teamspeak!

If you don't want to use the emulation module you can use the aoss wrapper (from the alsa-oss package; tested with version 0.9.4). You will need to create the file .asoundrc in your home directory and add these lines to it:
Code:
pcm.dsp0 {
    type hw
    card 0
}
ctl.dsp0 {
    type hw
    card 0
}
You might need to change card0 if the card you want to use isn't the first one... Once the above is done you should be able to run Teamspeak with aoss /path/to/Teamspeak and set the output to /dev/dsp. Since /dev/dsp is (probably) a symlink to dsp0, .asoundrc defines pcm.dsp0 and ctl.dsp0. Change as necessary.