OK this is kind of nit-picky but, during boot up slack displays a bunch of errors relating to the module for my audio. error is something to the effect of, insmod ......nvaudio audio device failed blah blah blah. i have a nvidia nforce 2 motherboard and the drivers are correctly installed. i know they are correctly installed because my sound works fine. so the problem basically is the error, not my sound. now i would assume just leave it alone, because i couldnt think of any way to get rid of the error without changing my configuration somewhat, which i dont want to do, since it works fine, any suggestions to get rid of just the error?

Maybe it would help if you post the error message here

ismod /lib/modules/2.4.20/kernel/drivers/sound/i810_audio.o.gz
ismod /lib/modules/2.4.20/kernel/drivers/sound/i810_audio.o.gz audio device failed
ismod /lib/modules/2.4.20/kernel/drivers/sound/i810_audio.o.gz
ismod /lib/modules/2.4.20/kernel/drivers/sound/i810_audio.o.gz
no such device
ok, the modules its supposed to be loading is nvaudio.o, but the sound still works, so, is it loading both and the old one, that ^ one, not need to be there anymore or what? also nvaudio is the only one in the directory thats not gunzipped, does it need to be?
this is the directory:
ac97.o.gz cs46xx.o.gz msnd.o.gz sgalaxy.o.gz
ac97_codec.o.gz emu10k1/ msnd_classic.o.gz sonicvibes.o.gz
aci.o.gz es1370.o.gz msnd_pinnacle.o.gz sound.o.gz
ad1816.o.gz es1371.o.gz nm256_audio.o.gz soundcore.o.gz
ad1848.o.gz esssolo1.o.gz nvaudio.o sscape.o.gz
adlib_card.o.gz forte.o.gz opl3.o.gz trident.o.gz
aedsp16.o.gz gus.o.gz opl3sa.o.gz trix.o.gz
ali5455.o.gz i810_audio.o.gz opl3sa2.o.gz uart401.o.gz
awe_wave.o.gz mad16.o.gz pas2.o.gz uart6850.o.gz
btaudio.o.gz maestro.o.gz pss.o.gz v_midi.o.gz
cmpci.o.gz maestro3.o.gz rme96xx.o.gz via82cxxx_audio.o.gz
cs4232.o.gz maui.o.gz sb.o.gz wavefront.o.gz
cs4281/ mpu401.o.gz sb_lib.o.gz ymfpci.o.gz

The gzipped state shouldn't make a difference,
if sound works fine just remove the i810_audio
from where ever you load it :)

Cheers,
Tink

not too sure how to remove it from the booting process, any help?

Depends on how it got there :)

I tend to put my modules that I need in
/etc/rc.d/rc.modules ...

In Slack 9, it might be grabbed because
of a stale modules.dep file. Maybe just
a function of /etc/modules.devfs ..

Cheers,
Tink

its there from the slack install. any ideas now?