Here are some basic troubleshooting tips for working
with new azalia codecs.

The generic driver creates every possible mixer item, so new
codecs can be can be thorougly tested in userland by fiddling
with them.  What follows is an incredibly tedious process, but
I've tried my best to arrange it so that you'll find the
solution as quickly as possible.

Here goes..

   Start up some music sampled at 48000 Hz.  If you don't have
   any, here is a copy of the 3.0 song resampled at that rate.
   I figured that would be best since since many of us know how
   it is supposed to sound (this is also the bsdtalk intro
   music).

   http://freedaemonhosting.com/~deanna/song30_48khz.mp3

If you hate that too much, you can resample anything with sox
(audio/sox)

   sox song.mp3 -r 48000 song48.mp3

   And some lightweight players are 'plaympeg' (devel/smpeg) and
   'madplay' (devel/mad).

1) Run 'mixerctl -v' and take a look at the items.

2) Look for any *.eapd controls, and set them all to 'on'.

If that doesn't work..

3) Look for any volume controls (the number,number values) and
   set them all to something fairly high.  220,220 should do it.

If that doesn't work..

4) Look for mutable items: 'mixerctl -v | grep mute' Now the fun
   really starts!  Mute every single one of these. Make sure the
   music is still playing, then unmute and re-mute each one.

If that doesn't work..

5) All mutable items should still be muted.  Look for an
   'inputs.usingdac' control.  Stop the music, and choose the
   next dacgroup entry.  Start the music back up, and repeat
   step 4.

Still no music?  Repeat step five until you've tried all dac
groups (inputs.usingdac).

If at any point here you manage to produce some sound, save the
output of 'mixerctl -av' and email this plus your dmesg to
deanna@openbsd.org.

I DID NOT WRITE THIS DRIVER.  NONE OF THIS IS MY FAULT! :)

This is just a last resort for the truly desperate.