I am running a new install of Suse 10.2. Since I could not get my sound working, I decided to update my ALSA driver to version 1.0.14rc4. When I run the
./configure I get the following:
I read the install notes:


and I can tell that the problem is where I highlighted it in blue concerning the --with-kernel=dir option and from what research I have done believe that there will probably be a problem with the --with-build=<kernel_build also.

I have been doing some research where I could find it but much of what I have found on this same issue was resolved without an explanation on what was done. I have kernel 2.6.18 which is using ALSA 1.0.13. There has been significant changes to the driver that I need in the later 1.0.14rc4 version, so I think it necessary to install it.

I would appreciate any help I can in finding the proper directory to point this to. I am new to Linux so I would appreciate as clear an explanation as possible.

edit: oh, I noticed that some people ran a script to post the required info needed to determine what the problem might be. I will be glad to do that if needed. Please just let me know the best way to run the script. I am sure it is simple, but as I am new I don't want to mess anything up.

Thanks

even if you do not intend to rebuild your kernel you need to get the kernel source and at least run make oldconfig and make (no need to install anything) because alsa-driver needs the full kernel source to build against...

Hi,

Just to clarify, at the minimum, Suse needs the kernel-source package and the kernel-headers package installed for a program to build its modules.

Sam

oh, I can't believe I forgot to install the source. I went into Yast and installed the source for 2.6.18.2-34 and ./configure ran all the way through. I am running make now. I left it at default so it is running all of the drivers. I guess maybe I should have put in the one I needed.

So samstar is the kernel-headers package included in the source package or in its dependencies?

...and Okie I need to run make oldconfig? Since I am already running make did I mess something up?

edit: ALSA modules were successfully compiled!!!

So, before I go any further and run make install please recommend what I should do now.

No, kernel-headers is a separate package to install so that you don't have to use the 'make' command in your source tree and modify it.

thanks samstar!

I was still wondering if it is necessary to run make oldconfig before I run make install.

As I mentioned before my ALSA modules were successfully compiled!!!

I will wait to run make install until I get some more info on make oldconfig.

Any assistance would be much appreciated!

if you don't actually need to rebuild your kernel dont do it, i am sure SuSE has some specific patches that are not included in a plain jane vanilla kernel so just downloading kernel source and installing will cause some things to possibly break, but dont just delete the kernel source as sometimes in order to compile certain packages it will require the kernel source to build against (as a reference)...

what make oldconfig does is setup the kernel source to have the same configuration as the kernel presently installed & running, also you can run make menuconfig and scroll to the bottom and load an alternate config file, there is a pretty good README and other documentation in the kernel source - i suggest you read it (twice even) as one day you may need to rebuild & install a kernel, this is good knowledge that never hurts to know...

Yes, suse distributes an installable source, but they recommend not to mess with the source at all (using make, make oldconfig, any of that). That's what the kernel-headers package is for. Just install that, and don't make any changes to the source.

You can revert the source to its original state by deleting the source code's directory and re-installing the kernel-source package from yast.

Sam

Now I am confused...

I have Kernel 2.6.18.2-34 and am installing ALSA driver version 1.0.14rc4. I guess since ALSA is part of the Kernel that it makes changes to the kernel when the updates are made to it?

I understood that when I ran /configure that the 1.0.14rc4 Alsa update was being changed to work with my 2.6.18 kernel. I thought that when I ran "make" that it put together the driver packages I would need to work with my present kernel.

I thought that "make install" would just install those packages.

Now my confusion is pretty much complete. I guess I understood something wrong in what I was reading.

So you are saying that when I run make that my kernel is being modified?

If you could explain this better or refer me to something specific that I can read to explain this I would greatly appreciate it.

Thanks


...back to the books!

When I was saying 'make' or 'make oldconfig' I was talking about doing so inside the kernel sources. I was referring to Okie's advice. That you don't need to rebuild the kernel source for Alsa to detect 'version.h'. You just need the kernel-source, and the kernel-headers packages for upgrading your Alsa. Then just install Alsa how you planned to.

Sam

Ohhhhhhhhhhhhh, sorry samstar... I get it now
Sorry I was so thick there, I had it all confused there for a bit! Thanks for straightening it out for me!

I will continue with my install then and post how it goes!

Thanks again for the help!

I followed the ASLA install instructions as closely as I could. I got down to where I am supposed to run modprobe snd-card.

Well, I ran modprobe -v snd-riptide:

I wanted to know what it was doing so I used the -v (verbose) option and it seemed to do nothing. Do you know what directory I would have to be in to run this?

I understand that modprobe is a program that is used to add and remove modules from the Linux Kernel. Does this mean that after it runs successfully that I should be able to see the sound driver in YAST? It has never shown up there, nor is it listed in the add list.

Note: I know it is built into the kernel and the updates in ALSA should be the ones to fix my problem. I am really just using this thread to determine how to install the ALSA update properly. I already have another thread started discussing other problems concerning the sound issue in general.

This Linux learning curve has really got me flummoxed!

Any help would be most welcome!

I'm assuming you know that modprobe has to be run as root. Otherwise, modprobe is pretty much silent unless it has a problem or an error occurs. Check your module list (run 'lsmod') to see if the module is installed and in the list.

Thanks Sam!

I ran alsaconf and it tested to see if I had sound, but there was none.

I found that when I rebooted a second time that I had an icon in my tray! I removed the mute on the sound and turned up the volume, so I am further than I have ever gotten!

When I try to play a music cd, it seems to play fine as far as watching the screen goes, but I get no sound. The software is actually going through the motions of playing sound, though I do not hear it. I made sure that the cd sound was turned up too!

Now this has got to be something simple! I will check out a few things and post what I find!

Ok, use alsamixer at the console to get the best control over your volume levels. Use <tab> key to switch between playback, capture, and 'all', and use <esc> key to . . . guess what.

Sam