Rene Herman wrote: > Okay, that's fine. I wasn't aware though that your CS4237 was onboard > and more importantly, neither was snd-cs4236. It appears to not have > support for onboard CS4236+ chips -- the CSC0000 device is driven only > by snd-cs4232. Does "modprobe snd-cs4232" work? If not, does it fail > with just the same "no devices" message as snd-cs4236 did, or does > something more interesting appear at the end of "dmesg" (typing "dmesg" > displays the kernel message buffer)?
Crap, I see in your original message that you already tried snd-cs4232 as well. I'm not suite sure why that wouldn't work though, so please retry and check that "dmesg" if failed. One more thing to try; let's take PnP out of the picture. Does it work to do: modprobe snd-cs4236 isapnp=0 port=0x534 cport=0x538 irq=5 dma1=1 dma2=0 If not, that same line with snd-cs4232 instead? If both do not work, please try upgrading your kernel (how to do that is dependent on the distribution -- you can probably update through some update tool). I see it's 2.6.12 and that's fairly old. I'm looking at 2.6.16 kernels here. And a last resort for now: modprobe snd-sb8 port=0x220 irq=5 dma8=1 That will probably work, but we should get the crystal driver working instead. Rene. _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
