LMAO yes I knew that from Windows BUT one of the big things you hear about linux is that you don't have to reboot after installing software/making changes so I was assuming any changes made would be immediate. My bad

You don't HAVE to reboot. For just about everything short of running a new kernel, there is a way to avoid rebooting.

That said, I like rebooting on the desktop machine. I make frequent changes. I could skip rebooting, but six months from now when I have trouble rebooting, I'll know it's something that I recently changed. Without frequent reboots on a system that is constantly being tweaked, you are gonna end up with a long list of places to start looking for your problems.

Servers are another matter. I set them up and let them run. I may make updates and such, but I usually leave the basic configuration alone. Therefore, not as likely to have some change from awhile back come bite me when I need to reboot.

I have a problem also, i have to run aslsaconf each time i reboot to hear music.

Is your rc.alsa script executable ? (ls -l /etc/rc.d/rc.alsa)
Do you use hotplug ?

Also, did you run "alsactl store" after setting your volumes?

Did you allow alsaconf to write /etc/modules.conf or /etc/modprobe.conf?

It rights to modules.conf

and no i tried everything still dont work when i run alsaconf it says this for brief second

/usr/sbin/alsaconf: line 35 [: too many arguments
/usr/sbin/alsaconf: line 37 [: too many arguments
could not find module snd
could not find module snd
could not find module snd

The problem with Windows is that there's no explanation for most of its problems and, since it's closed source, much of the knowledge required to fix it is locked up somewhere in Redmond, WA.

Isn't it ironic how MS's address is "One Microsoft Way"? Like they're suggesting that the Microsoft way is the only way or something. . .