Sound Problem!

[Mikenell]

I have a Creative SB 128 PCI which uses the es1371 driver. It worked in red hat with the sndconfig program, but I compiled a kernel in Debian, selected sound support as module, the es1371 driver as a module and then compiled the kernel. It works and then I ran modconf and selected to load all of the sound modules at boot time but even though I have the modules I need, it says No Sound Cards Defined when its booting. soundcore was needed by sndconfig which I apt-got in Debian, so I loaded it and the es1731 module but sndconfig said it wasnt supported even tho the same program said it was in red hat!
Does anyone know whats wrong? I'm running Debian woody and my kernel is 2.2.17.
Thanks a lot
Mikenell

[Muzzafarath]

I've got the same card, with the same kernel. Have you tried to do `modprobe es1371`? I didn't use any sndconfig program, I just used modprobe...

[This message has been edited by Muzzafarath (edited 27 October 2000).]

[Mikenell]

Yeah i think I did, but I want it to load automatically.
Mikenell

[teeitup]

Is es1371 listed in /etc/modules?

I would think monconf would take care of it.



------------------
Don't take life to seriously, You'll never get out alive!
-Bugs Bunny-

[fuzzy]

If you used modprobe, you still need it to be added to your modules.conf so it will be loaded on startup.
I'm not sure if this is the best way to do it, but you can edit /etc/modules.conf manually with your sound card added, save it, then run "update-modules". Something along those lines should make the soundcard module load up on startup.
Similar to getting your NIC up and running on startup.

------------------
I spy with my little eye something that begins with "W"... oops, it's gone now.

[Mikenell]

I used modconf and the sound card works now but at startup it says:

Starting sound driver: No sound cards defined.

Hmm, how can I define one?
Thanks
Mikenell

[teeitup]

If it's working you don't need to define one.

Something like alsa is probably trying to start.

There are many ways to get sound, you only need one.

Check you /etc/rc2.d directory, Look for something along the lines of S##alsa
mv it to s##alsa and reboot.

see if the error is still there.

One note on changing capital S to small s:
You may notice errors on shutdown due to something not running. There are K commands in the /etc/rc1.d corresponding to the S files of other run levels. If the errors bother you just mv the capital K to a small k along with the S's.



------------------
Don't take life to seriously, You'll never get out alive!
-Bugs Bunny-