I've found this link:

http://www.linux-thinkpad.org/cgi-bin/fom?_recurse=1&file=5#file_36

I run 'modprobe sound dmabuf=1' and get 'FATAL: Module off not found'

I run 'modprobe cs4236 irq=5 io=0x534 dma=1 dma2=0 mpuio=0x330
mpuirq=9' and I get 'FATAL: module cs4236 not found'

Which makes me then realise that the tutorial missed the 'snd-' part
of the module, so I retype 'modprobe snd-cs4236 irq=5 io=0x534 dma=1
dma2=0 mpuio=0x330 mpuirq=9' and I get '
CS4236+ soundcard not found or device busy
FATAL: Error inserting snd_cs4236
(/lib/modules/2.6.7-1-386/kernel/sound/isa/cs423x/snd-cs4236.ko): No
such device
FATAL: Error running install command for snd_cs4236
'

I then run 'modprobe op13 io=0x388' and get 'FATAL: Module op13 not found'

... I remember trying like that before, and I'm still confused about
the actual individual steps. Shouldn't I stop after the first error -
aren't these commands successive? Don't they all need to work? Anyway
- I'm not sure about that part.

That tutorial pointed out that Redhat has a 'sndconfig' program that
works - but I'm not sure if that's available for Debian. I've looked,
and to my knowledge it isn't.

If I run 'dmesg' (BTW - what the heck does that command stand for?
I'll look it up later...)

I get 5 lines at the very end that all say 'CS4236+ soundcard not
found or device busy'

I'm not sure what that means - if anything at all.

I also found this forum post...
http://www.linuxquestions.org/questions/showthread.php?threadid=199348
...(but I don't think it matters, since it's for a 600 series
thinkpad, and I'm on a 380).

I know that I've given a lot of information, and it's ok if nobody
wants to keep trying... I guess at this point I'm hoping for a
miracle.

Thanks to everyone who's helped so far.

-Rich


On Wed, 29 Dec 2004 07:36:21 -0700, Byron Clark <[EMAIL PROTECTED]> wrote:
> 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
> 
> 
> --------------------
> 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
> 
> 
>

--------------------
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

Reply via email to