Can't Locate Sound Modules
 

Every day I get these dam messages repeated over and over again in my log file:

Mar 2 11:21:01 domain modprobe: modprobe: Can't locate module sound-service-1-0
Mar 2 11:21:01 domain modprobe: modprobe: Can't locate module sound-slot-1

I'm running Linux on a laptop so I'm not surprised its having trouble. All the sound works fine though so thats not the problem.

Can I just give it what it wants and load these modules? If so where do I find them? This should probably go under the newbie forum because I don't know much about getting and installing modules.

<UPDATE>
Doing a little snooping around I found this directory:

/lib/modules/2.4.18-18.8.0/kernel/drivers/sound

In it there is a file called sound.o . Is this what I'm looking for?
</UPDATE>

try
man modules.conf

Okay I did:

man modules.conf

It works very well.:D Now what? What am I looking for in the man pages? How do I identify the modules that are being requested in my log files?

My man says ..modprobe.. can be modified by the (optional) configuration file /etc/modules.conf
Check if there is a sound(snd) entry in modules.conf - comment it out and reboot
also look in /etc/modules

I thought it wasn't necessary to reboot to install modules? I'm confused. Can you read over my original post and tell me how I can find these EXACT modules being reported in the log files.

Thank you.

It's not. You can remove and add modules without rebooting. rmmod and modproble are usually the ones I use to that.

Those are more than likely entries in your /etc/modules.conf file. You can comment them out (#) so that the error will go away. Post up your modules.conf file if you need help determining what to comment.

Cool

Gidday ...

my educated guess is that you're probably
trying to load modules for something that's
compiled into your kernel (since you said
sound is working fine) and thus no modules
to load present ...

My solution would be to edit the file that
RH uses to load modules, and remove the
offending lines ;)

Cheers,
Tink

Here is /etc/modules.conf

alias parport_lowlevel parport_pc
alias eth0 eepro100
alias usb-controller usb-uhci
options ide-cd dma=1
alias sound-slot-0 i810_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

Hmm :)

I'm not using "little red riding hood"
for my daily work, it's been ages since
I had my hands on, and the only box with
it I have access to is running 6.2 :}

But I am fairly certain that RH 8 uses
more than just one config file to actually
pull up the modules system ...

In the old version there's
in /etc
and
in /etc/rc.d

Use the force, Luke!
Errrh, I mean the grep! :}

Cheers,
Tink

grep sound /etc/*

returns the modules.conf and other files that contain the string 'sound' but they are not module related files.

What if you try
?

Cheers,
Tink

It takes a while but it returns nothing.

*sigh*

Sorry mate, you're alone now :)
I always disliked the big distros with Sys V scripts ;)

As for your <UPDATE> ... I don't think it is...
But you certainly know that's a binary.

Cheers,
Tink

Hmmm....

You could try looking at what point the error pops up. Then, go into your init scripts and find the area that most closely matches that string of startups. Then, look for what file it's calling on to probe your sound module, locate that file, comment out the line, and reboot to see if it worked (rebooting is just to see if the error comes up during bootup, not because you need to in order to remove/add the module).

Cool

i said boot because it is the booting process that is attempting to install the modules. The boot is driven from inittab which should have an entry si::sysinit:/etc/rc.d/rc.sysinit - run at boot time.
long story short - modprobe is run from startup scripts, uses modules.conf.

I may be wrong that modules.conf is the cause - only rebooting will tell for sure.

PS your modprobe messages in the log are harmless