I always have to install soundcard drivers after restart. [SOLVED]

[Asound]

Hello everyone,

as the subjects says, I always have to install the soundcard drivers after every restart. My soundcard is an "Creative X-Fi Xtreme Gaming". Iam using Vectorlinux 5.9.
The installation works very well and Iam having sound, but after a restart its like i never installed the drivers and I have to install them again. Thank god that I dont have to make a restart after the install 
Could it be that the drivers arent loaded with the bootup? If yes what can i do?

Hope that someone can help me, because im very new to Linux.

thanks

[rbistolfi]

A guessing, do you have more than a soundcard? maybe a webcam with mic or similar?
That could be one cause for your problem. If you do, follow this: http://forum.vectorlinux.com/index.php?topic=4888.0

[wcs]

How are these drivers installed? Do you compile them?
Maybe you just need to load a kernel module at boot, with "modprobe <modulename>".
(just guessing here...)

[Asound]

First of all thanks.

@rbistolfi: My onboard soundcard is disabled but Iam also having an tv-card. When the drivers arent installed, the file ist empty. So it seems that there is no soundcard detectet. After the install of the drivers there appears "0 ctalsa".

@wcs: Well, I have just installed them by running an script thats included, so Iam not sure. But the script self runs an "make" and "make install".

[wcs]

Maybe you'll find the name of a module in the documentation of the drivers.
Then you can type "lsmod" to see if the module is loaded.
It shouldn't be after a reboot, but you can load it by typing "modprobe <module name>"

If it works after the modprobe command, then you can put the command at the end of /etc/rc.d/rc.modules and it should start at boot.

Or this procedure might not apply, but give it a try.

[wcs]

Also you might want to look at the driver's Makefile in the source directory to see what it is doing when it does "make install". Search for an "install" instruction in that Makefile.
There must be something there that doesn't stick (in the previous post, I'm guessing it's a modprobe command). Whatever it is, then it can be made to run at boot.

[wcs]

Duh!...

Of course, the module name is "ctalsa" ! You had said that already (from the /proc/asound/modules file, right?) 

Just try rebooting and doing "modprobe ctalsa".

[Asound]

Setting the command "modprobe ctalsa" at the end of the rc.modules worked!
Booting takes a little bit longer but its still much faster then installing the drivers all again.
Thank you so much!

[wcs]

Cool.
You can edit the title of this thread to put [SOLVED] in in, so that it can be easily found.