Hi Mohapi.

Did you solve this :- 'My new Knoppix system tells me this when I try to configure my soundcards;

x You don't seem to be running a kernel with modular sound enabled. x
x (soundcore.o was not found in the module search path). x
x To use sndconfig, you must be running a kernel with modular x
x sound, such as the kernel shipped with Debian GNU/Linux or a 2.2 x
x kernel, and sound must be compiled as modules.

How do I enable the necessary modules?'

Thanks in advance.

I solved it by reading another post. As soon as I can remember where that post was, I'll let you know. I use the kernel from CCRMA for my FC3 harddrive.
http://ccrma.stanford.edu/planetccrm...anetccrma.html

I believe that this is the
sequence I used with the CCRMA kernel to get my sound going, but I'll post something different if I find more. My memory [human] sucks.
Configuring multiple sound cards

If you have multiple sound cards (including external usb MIDI controllers, which also count as a soundcard) you most probably want to define which one is going to be the default. For that you will have to (carefully) edit the "/etc/modprobe.conf" file. Otherwise cards whose kernel modules are loaded by the hotplug subsystem early in the boot process - such as usb soundcards - will automatically become the first card, probably not what you want if that soundcard is just a MIDI interface with no audio capabilities.

You can use the following template as an inspiration for what you have to add to modprobe.conf. Be aware that there will be more lines in your modules.conf file, including ``install'' and ``remove'' lines for the soundcards that Kudzu has configured, leave those lines alone:

alias snd-card-0 snd-CARD_0
options snd-CARD_0 index=0
...
alias snd-card-N snd-CARD_N
options snd-CARD_N index=N

In this template ``...'' stands for more lines here, one for each extra card (don't copy the dots! :-) ``CARD_N'' is the name of the kernel module that corresponds to the card you want in position ``N'' (N=0 is the first card, usually the default device used by all programs).

In the case of USB soundcards you will have to add the ``alias'' line manually as kudzu does not include it in modprobe.conf:

alias snd-card-N snd-usb-audio
options snd-usb-audio index=N

Here is a filled in example that includes three cards (this ommits the ``install'' and ``remove'' lines):

alias snd-card-0 snd-ice1712
options snd-ice1712 index=0
alias snd-card-1 snd-ens1370
options snd-ens1370 index=1
alias snd-card-2 snd-usb-audio
options snd-usb-audio index=2

And this is how the audio part of modprobe.conf looks like in my laptop configuration (wrapping of the install and remove lines added to better fit the width of this page):

alias snd-card-0 snd-intel8x0
options snd-intel8x0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && \
/usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; \
/sbin/modprobe -r --ignore-remove snd-intel8x0
alias snd-card-1 snd-usb-audio
options snd-usb-audio index=1

After you are done editing the file, use depmod to parse it again and determine module dependencies:

/sbin/depmod -a

You can now restart the sound driver to test it. If you are logged in into X you probably want to logout first and do this from a text console, as stopping the alsa system will kill the audio control panel in Gnome. Note: this will not test what happens when hotplug find an audio device early in the boot sequence, you will have to reboot to test that.

/etc/rc.d/init.d/alsasound stop

Then start it again:

/etc/rc.d/init.d/alsasound start

It should load all the modules for all your soundcards in the specified order.

The ALSA sequencer kernel module

The ALSA sequencer kernel module is not automatically loaded. As a workaround you can enable the old alsasound startup script, it will force the load of the sequencer module:

/sbin/chkconfig alsasound on

Hi, I also am a newbie. A very new bie, so sorry for asking evtl. basics, too... I found this forum after googling this special issue and registered just now. After posting this I immediately go and begin reading basics. But I dare to ask my question, for I found this problem very often in google - w/o solution.

Here my details on this issue:

I got a Knoppix V5 DVD and put it in my Windows box... and loved it. (I always wanted to go Unix/Linux at last, never had the time... this "accident" made me start now). I quickly set up another box and installed the Knoppix DVD on it via knx2hd. Went fine. Now the problem comes.

Booting off the live DVD my sound was OK. Installed on the hda there is no sound, with the same results as stated in the above postings.

Kernel says to be 2.6.15 (means definitely >2.2). sndconfig is v0.57 installed from this DVD. The file soundcore.o *is* there, under /usr/lib..../2.4.26.3um/...

/dev/dsp cannot be opened (no such device)

Alsaconfig goes through w/o errors and wishes me fun which I do not have with no sound

It finds my coundcard as

ENSONIQ ES1371 [AudioPCI] (Rev-08)

This soundcard sounds (as I said) if booting off the DVD! So I do not really understand why I had to recompile the kernel (whatever that is, I can learn it I am sure) - for there must be some kernel on the DVD which is capable to sound that card...

I also have an older version of Knoppix, a live CD V4.2 I think? It sounds booting off the CD. I installed it via knx2hd - and it sounded also in the installation!

I think there must be a change perhaps in the kernel? As one of you stated here, Linux is a developer and developing system changig often and building new things in make old things sometimes stop to work. I believe something like this might have happened here - but I far do not have the experience to investigate this: I still have problems with typing commands...

I know this stuff is good, I know there must be a solution, I know if a guru finds and posts it how to do it - I can implement it.

I want to make the step the move away from Redmond, and I know I also have to work for it so no way flaming Linux, being a moron myself! But I still need a helping hand.

Thanks

Nat

Found nothing useful while googling - only that several people with several distributions had this problem.