narrowed down but still not working (Re: Having problems with 'pcm' and on-board Crystal Sound)

[pseniura at techie.com]

Thank you for helping.  I'm getting this problem narrowed down.  I'm using the custom kernel w/o any sound drivers compiled-in.

Having loader.conf do both (and only these):
snd_csa_load="YES"
snd_pcm_load="YES"
dmesg shows these getting loaded ahead of the kernel booting, but the sound chips do not get detected at all
e.g. those "unknown <WSS/SB>" lines in dmesg I included in my previous e-mail.

When I have loader.conf do snd_driver_load="YES", I see that 'mss' is saying 0x530 is busy while booting (I know about the old-style 4-bytes-before i/o port address it is trying to find), but later on we see 'pcm' can detect the sound chips.
At this time 'cat /dev/sndstat' shows:
>>>>
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: <CS423x-PCI> at io 0x534 irq 11 drq 1:0 bufsz 4096 (1p/1r/0v channels duplex default)
<<<<
which agrees with IBM's specs for this model 300PL.
I then use the 'play' app to test this with a .wav file (say, one that SDL installs), and we get the msg on the console:
>>>>
pcm0:play:0: play interrupt timeout, channel dead
<<<<

Okay at least I know what to put into loader.conf now:
snd_mss_load="YES"
snd_pcm_load="YES"
'cat /dev/sndstat' still shows the same info as above.
But the console also shows the timeout problem each & every time something wants to play thru it.

There is no man page for mss, but the man for pcm suggests that these particular Crystal Audio chips are directly supported, and now it seems I need mss also to get the hooks in right.

OSS works with the same 'play' app and SDL .wav file, so I'm quite sure we have a problem in mss/pcm somewhere.

I'm not afraid of hacking some code if someone can give me some hints.  ;)
I really appreciate it.

  --  Paul Seniura
      System Specialist
      State of Okla. D.O.T.