Peter Hugosson-Miller wrote: > Has anybody managed to get the above sound chip working under > Debian 2.2? > > I've browsed the archives for two hours now. Plenty of people have > had problems, nobody has posted with a solution. I won't bother > with posting my symptoms, they are identical with most of the > posts in the archive, concerning this chip.
FWIW, I have compiled and installed the latest driver for the chip in question, and found the strangest thing: the Crystal CS4236B-104 on-board sound chip thinks it is _two_ soundcards - CS4231 and CS4236! I say this because with snd_cards_limit=2 in /etc/modutils/alsa, then update-modules, /etc/init.d/alsa restart, then all the relevant modules are loaded. If I put it back to 1, then I get that good ole fashioned "card is busy" message that everyone else gets. Now if I could just figure out which bits of the chip belong to which of its two "virtual" cards, I might be on to something. Right now I get the well-known message: "/dev/dsp: No such device" if I try to do anything with sound. Before anyone asks, I _have_ unmuted all the channels, and set the volume to 50% everywhere, and I have followed the FAQ suggestion to the above question. No dice. I reckon this "two cards in one chip" scenario is the one to sort out. It's just that there are so many ways to split it up, and each variation takes time to evaluate. > Any success story gratefully received... This still holds true, of course... > To unsubscribe from <[EMAIL PROTECTED]> mailing > list send message 'unsubscribe' in the body of message to > <[EMAIL PROTECTED]>. > BUG REPORTING SYSTEM: > http://www.alsa-project.org/cgi-bin/bugs The alsa BRS seems to have a bug! I filed a report yesterday, and it tried to forward it to the maintainer - who has a bouncy e-mail address. The BRS was filling up at a rate of xx e-mails a minute, and today the whole site was down :-( -- .~. /V\ // \\ /( )\ ^`~'^ < hugge >
