As noted, this is not difficult, with some experience. The first time will be fun. First of all, you need to install the tools to do this. Go to YAST > SOFTWARE > SOFTWARE MANAGEMENT and change “filter” to “patterns”. Then under “Development” select “Base Developement”. That will install a bunch of applications you need to compile.
Then change “filters” back to “search” and search for “checkinstall” and install that (we will use checkinstall to create some custom rpms). Also ensure you have libtar and tar installed.
Then go to that repository where you obtained your kernel, and install kernel-source. Note kernel-source must match your running kernel.
Then go here, and download the tarballs for each of the following (a tarball has a .tar.bz2 extension in this case) :
- alsa-driver-1.0.18 (ie alsa-driver-1.0.18.tar.bz2)
- alsa-lib-1.0.18 … etc …
- alsa-utils-1.0.18
- alsa-tools-1.0.18
- alsa-firmware-1.0.17
- alsa-plugins-1.0.18
- alsa-oss-1.0.17
I don’t know if all need be compiled to get your alsa working, but its possible. But once you get the 1st successful compile, I suspect the others will be easy.
Download those to a directory /home/yourusername/tars or something like that. Uncompress those. I can do this on my kde by selecting the file and right clicking to uncompress.
Then open a gnome-terminal or a konsole and change into the directory where alsa-driver-1.0.18 is uncompressed (when you untar it will create its own directory).
Then read the readme.txt and install.txt for any special instructions. There may or may not be. The type the following in that konsole or gnome-terminal:
./configure
make
su [size=]#enter root password when prompted
checkinstall[/size]
That will create an rpm, and checkinstall will tell you where the rpm is located. You could try installing that rpm now, or you could try making the other rpms and install all at once. Note these rpms are poor quality rpms. They are for use on your pc only and they don’t have all the checks , … etc … that a normal rpm will have.
If “checkinstall” fails, then replace “checkinstall” with the following sequence (ie after ./configure, make, su):
make install
checkinstall
In this later case, “make install” will install alsa on your PC. But by then running checkinstall, it will take the successful “make install” activity and create an rpm. Install that rpm. It will then enter the install information in to your rpm database, making it easier to remove the alsa version later, if so desired.
Then proceed to the other tarballs and do the same.
Do not remove the tar compilation directories, as another method to remove the tarballs (besides the rpm method with checkinstall) is to type “make uninstall”. You can also start an tarball compilation afresh with “make clean”. But you need that directory still in place for “make uninstall” to work.
You can post here any compilation errors you get.
But before you try to compile, I recommend we investigate more about your audio config (hardware/software) in case this is a simple mixer problem.