On Thu, Apr 08, 2004 at 07:45:48AM -0500, [EMAIL PROTECTED] wrote:
> * David ([EMAIL PROTECTED]) wrote:
> > On Tue, Apr 06, 2004 at 10:01:17PM -0500, [EMAIL PROTECTED] wrote:
> This does not seem to work?
>
> sarge:~# modinfo cs4236
> modinfo: cs4236: no module by that name found
This would imply that the module cs4236.o is not installed (at least in
the right place). One caveat.. when you issue this command, you _were_
running the correct kernel, aren't you? The command "modinfo" will
look under /lib/modules/<current-running-kernel>/ for this module.
> As has been seen thoough specifying the path does (path problem maybe?)
It shouldn't. As I said above, it will automatically search the
directory under the currently -running kernel.
> > > filename: /lib/modules/2.4.25-1-386/kernel/drivers/sound/es1370.o
^^^^^^^^^^^^
This is the wrong kernel if you're running 2.4.25alsa3
> Well the modprobe snd.... did something!
>
> sarge:~# modinfo cs-4236
> modinfo: cs-4236: no module by that name found
> sarge:~# modinfo cs4236
> modinfo: cs4236: no module by that name found
> sarge:~# modinfo cs4236
> modinfo: cs4236: no module by that name found
> sarge:~# modprobe snd-cs4236
Did you get anything with this command? It appears you have this module
loaded below...
> note just got the command line back, aadebug now shows
>
> Loaded Modules --------------------------------------------
> snd-cs4236 8804 0 (unused)
> snd-pnp 2800 0 [snd-cs4236]
> snd-cs4236-lib 11216 0 [snd-cs4236]
> snd-opl3-lib 6372 0 [snd-cs4236]
> snd-hwdep 5408 0 [snd-opl3-lib]
> snd-cs4231-lib 19020 0 [snd-cs4236 snd-cs4236-lib]
> snd-pcm 61700 0 [snd-cs4236-lib snd-cs4231-lib]
> snd-timer 14724 0 [snd-opl3-lib snd-cs4231-lib snd-pcm]
> snd-page-alloc 6292 0 [snd-cs4231-lib snd-pcm]
> snd-mpu401-uart 3456 0 [snd-cs4236]
> snd-rawmidi 13632 0 [snd-mpu401-uart]
> snd-seq-device 4032 0 [snd-opl3-lib snd-rawmidi]
> snd 34276 0 [snd-cs4236 snd-cs4236-lib
> snd-opl3-lib snd-hwdep snd-cs4231-lib snd-pcm snd-timer snd-mpu401-uart
> snd-rawmidi snd-seq-device]
> Well I am back to where I was before trying the soundblaster card, and
> unfortunatly remote to the machine, however it did not work last time,
> will try tonight.
It appears that you should be set up to make some sounds.
> Tried the same trick with the es1370, no luck with that one
It sounds like you may not have that module compiled - although it
probably would have the name snd-es1370, not sure
One thing you might want to try, if you didn't do this at first. You
might want to go back into your alsa modules directory, maybe 'make
clean', or even delete the alsa modules directory and untar the sources
again. then, in the /usr/src/alsa-driver directory, do
./configure --with-cards=snd-cs4236<,another card if desired><,still
another>
You might issue the command ./configure --help, I use a couple others
--with-synthesizer (I think), and there's a --with-pnp or something,
too. Make-kpkg will configure the modules, but I don't think it allows
you to do these things.
After you compile and re-install, look in your
/lib/modules/<kernel-name>/alsa directory and see if the needed modules
are there.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
