Got any quick thoughts on this?
 

Ok, I was complaining abooot my sound and computer all fartin' out. Well, i've reinstalled, reconfigured Slack. Result, almost shooting myself, and getting everything to work well enough. Sound works the way it should, everything does really, i'm all happy and feeling 80%. I had no errors when I couldn't get sound, likewise using pppd in console. Now i think i'm good, but now have error messgs. Which are:

Mar 23 19:15:04 loonybin modprobe: modprobe: Can't locate module sound-slot-1
Mar 23 19:15:04 loonybin modprobe: modprobe: Can't locate module sound-service-1-0
Mar 23 19:15:04 loonybin modprobe: modprobe: Can't locate module sound-slot-1
Mar 23 19:15:04 loonybin modprobe: modprobe: Can't locate module sound-service-1-0
Mar 23 19:16:08 loonybin modprobe: modprobe: Can't locate module ppp0
Mar 23 19:16:17 loonybin modprobe: modprobe: Can't locate module ppp-compress-21
Mar 23 19:16:17 loonybin modprobe: modprobe: Can't locate module ppp-compress-21

From syslog...Please tell me i've missed something stupid, tell me i'm dumb or that you don't know, but just tell me SOMETHING! :)

Are you saying you dont have a problem with your sound or you do? You do have your sound module uncommented in /etc/rc.d/rc.modules right? I guess, or it wouldnt say cant find module sound-slot-1, Sure you got the right one uncommented.

Yep...my sound is fine, i just get those errors. I have an SB Live! and use the emu10k1 module which is correct. It's weird, I only get the error actually, when I start X, likewise with pppd, only get the error when logging in with the ppp0 device. I'm baffled...

What generates that file?

If it's done by one of the makes in kernel compile. I would backup rc.modules. Run any predesesors to that make then run that make. I guessing it may require a make mrproper. One thought is to also backup .config for make xconfig After doing make mrproper you could restore the newly generated .config from old then make menuconfig of xconfig save and exit. make dep , bzwhatever, modules, modules_install. ect

Something like this might happen if you have modules config where you have MODULES for sound and ppp and in your new kernel you have this INSIDE kernel. Maybe it's not your case, but I've seen a similar one.

That makes some sense, and really it's the only answer i've got to go on. I'm assuming something is trying to load the modules when they are clearly built into the kernel...I'm having some luck at themoment with no errors, but i've gone through 5 different kernel configs in two days to get here. Now i'm trying to get a basic iptables script to run for my inet/ppp0 interface. Fun stuff... ;)