On Tue, Dec 28, 2004 at 11:31:00PM -0700, me lyman wrote: > Don't you mean snd-cs4236 and not snd-cs4326?
You caught me, late night searching for stuff I don't use usually makes me mistype. snd-cs4236 is the module you should be using. > CS4236+ soundcard not found or device busy > > Wouldn't it need to know where to find the card? IRQ's or DMA's or > something like that?? I feel so clueless... I'm thinking that sound > isn't worth this trouble. You're exactly right that the module needs to find the card. It appears that 'modinfo snd-cs4236' spits out a lot of information; the only lines you'll need are the ones that start with parm. 'modinfo snd-cs4236 | grep ^parm' should show you all the parameters the module will take. Having never used this specific card, the first thing I would try is turning off the alsa isapnp probing by trying the modprobe like this: modprobe snd-cs4236 isapnp=0 If that didn't work I would try to find the port, irq and dma settings for the card and then run a modprobe like this (warning: values taken from a simple soundblaster card, not a cs4236): modprobe snd-cs4236 isapnp=0 port=0x220 irq=5 dma1=1 -- --------------------------------+----------------------------------- Byron Clark | http://www.byronandannie.net [EMAIL PROTECTED] | --------------------------------+----------------------------------- GnuPG Fingerprint: 0365 6979 6C3E BC0C 56C0 FB7F 12B3 75DD 042B EA68
signature.asc
Description: Digital signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
