ALSA modules missing after reinstall

gamehack · 04-22-2004, 08:33 AM

I have compiled the latest kernel 2.4.26 and when I type alsaconf the modules are gone.How to fix this ?

Thanks in advance

flyfishin · 04-22-2004, 09:10 AM

If you compiled your own kernel then you will need to recompile the alsa drivers for your kernel. Get the alsa-driver source from a Slackware mirror and simply run the alsa-driver.SlackBuild script in the directory. It will create a Slackware package in your /tmp directory that you can install.

gamehack · 04-22-2004, 11:41 AM

I updated alsa-* with swaret and the things aren't working.But can you describe how to

Quote:

simply run the alsa-driver.SlackBuild script in the directory. It will create a Slackware package in your /tmp directory that you can install.

Thanks in advance

P.S. Isn't there another way to do this ?

flyfishin · 04-22-2004, 01:36 PM

In your first message you say that you compiled the 2.4.26 kernel. Did you actually compile it yourself or did you download a Slackware package of kernel 2.4.26? If you actually compiled it yourself then you have to compile the alsa drivers to match your exact kernel.

To build your own alsa drivers go to your favorite Slackware mirror. I'm assuming you are running 9.1. Go into the slackware-9.1 directory and into the patches/source subdirectory. Download the alsa-driver directory to your box. Now on your box go into the alsa-driver directory you downloaded and edit the alsa-driver.SlackBuild package. Look for the line that starts with KVERSION= at the top of the file. Change it to KVERSION=$(uname -r). Then, as root, type 'sh alasa-driver.SlackBuild', no quotes. That will create a package, alsa-driver-0.9.8-i486-2.tgz in /tmp. Use upgradepkg to upgrade your alsa then rerun /etc/rc.d/rc.alsa by simply typing it in at a command line as root and all should be well again.

gamehack · 04-23-2004, 05:27 AM

It doesn't work

After I finish the instructions and type alsaconf nothing happens,it's like I have run a program that does nothing(alsaconf)

Nichole_knc · 04-23-2004, 05:49 AM

OK... Answer to common problem 101

When you build your kernel AND you are using alsa you MUST NOT compile the sound drivers into the kernel....

When you are in the kernel make *config you must answer (y) Enable Sound Support
ALL others must be (m) or (n) as required.....

Once you have made the kernel, installed it and the mods... THEN you must build alsa for that kernel. Download as explained above and cd to the untar-ed directory
./configure
make
make install
make clean

Once you have done this THEN
alsaconf (configure your sound card)
alsamixer (set your volumes)
alsaconf store (write /etc/asound)

Then once in X run your favorite mixer there.. i.e. aumixer
set your desired levels and save....

If all went well AND you have read the HOWTOs to help yourself - Things should be just PEACHIEE

gamehack · 04-23-2004, 06:59 AM

I did that and everthing went fine.BUT there isn't the command alsaconf ? Why ? I started alsamixer and the sound card was selected and I unmuted the sounds,but there's no sound.Thanks

EDIT: I installed the packaga alsa-driver.tgz after compiling and make install of the source of ALSA.So now sound is running,but the sound icon in GNOME is showing that there isn't sound.When I click on it,it says Cannot Open mixer device /dev/sound/mixer . Isn't there a way to install alsaconf without installing two times the alsa package(one time from source,one time from package.Could this make some problems ?) ?

EDIT 2: I fixed everything!!! Thank you guys

Cheers

nixel · 04-23-2004, 02:27 PM

flyfishin: i did everything you said in that post but i still get an error and im stumped on what to do next

heres the error

Code:

# ./rc.alsa 
Loading ALSA mixer settings:  /usr/sbin/alsactl restore
/usr/sbin/alsactl: load_state:1134: No soundcards found...
Loading OSS compatibility modules for ALSA.
FATAL: Module snd_pcm_oss already in kernel.
FATAL: Module snd_mixer_oss already in kernel.

i got as far as running the rc.alsa. thanks in advance.

Nichole_knc · 04-23-2004, 03:52 PM

Looks like you compiled your sound card into the kernel.. Which is a nono for using alsa... go back a couple of post and read that one...

flyfishin · 04-23-2004, 07:43 PM

Quote:

Originally posted by Nichole_knc
Looks like you compiled your sound card into the kernel.. Which is a nono for using alsa... go back a couple of post and read that one...

In my kernel compiling I copied the .config file from the original Slackware kernel source directory, /usr/src/linux-2.4.24, and copied it into my new 2.4.26 source directory. I then made the few tweaks I needed for my platform like support for 4 GB of memory and proper CPU selection. That's why I've never hit the problems others have with recompiling sound support. Hope this little nugget helps someone. Also, for kernel compiles I just followed the sticky at the top of this forum.

Nichole_knc · 04-23-2004, 08:21 PM

Ok...
Did you do..
make oldconfig
prior to doing the make *config for your kernel????

As it is indicating above the pcm and mixer is complied into the kernel..
I would suggest cd -ing to the /usr/scr/<kernel> and having a look at the .config file with less..
at about line 1092 you reach the sound section... The only one that should have a (y) is the first one CONFIG_SOUND=y
any others listed here should be (m) i.e.
CONFIG_SOUND_<yoursoundcard>=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_ACI_MIXER=m
CONFIG_SOUND_VMIDI=m
CONFIG_SOUND_MSS=m
CONFIG_SOUND_<yoursoundcardchiptype> # from alsa HOWTOs
Depending on your card other settings may be required BUT only as (m)

That is just about all

flyfishin · 04-23-2004, 10:08 PM

Sorry, I meant my reply as a general post to help others see why mine worked and they were having issues. I realized after reading your posts that my methods were working because I was using the default Slackware kernel which configures sound correctly.

nixel · 04-24-2004, 07:21 PM

Quote:

Originally posted by flyfishin
In my kernel compiling I copied the .config file from the original Slackware kernel source directory, /usr/src/linux-2.4.24, and copied it into my new 2.4.26 source directory. I then made the few tweaks I needed for my platform like support for 4 GB of memory and proper CPU selection. That's why I've never hit the problems others have with recompiling sound support. Hope this little nugget helps someone. Also, for kernel compiles I just followed the sticky at the top of this forum.

i think ill just try to recompile 2.4.26 with the old .config file from 2.4.22.
does proper cpu selection make a BIG difference? and as far as swapping the .config files this will work for 2.4.22 -> 2.4.26 right?

flyfishin · 04-26-2004, 06:22 AM

Quote:

Originally posted by nixel
i think ill just try to recompile 2.4.26 with the old .config file from 2.4.22.
does proper cpu selection make a BIG difference? and as far as swapping the .config files this will work for 2.4.22 -> 2.4.26 right?

I used the config file from 2.4.24 since that is the most recent kernel in the patches for 9.1.