hi there,

i'm having a problem with the alsa drivers...
I install the kernel 2.6.7 include on the 2º cd and the alsa-driver too, when i reboot my system with the new kernel the alsa wasn't working i trie to do alsaconf and dectect sucefully my audio card but when i tried to start alsamixer gives me a stupid misktake.

Then i search for a problem near mine on forums and then i compile my on alsa-driver and run snddevices to create the links /dev/dsp /dev/mixe , etc and give the right permissions. Everything went fine, the sound was working perfectly until i rebbot . Everytime i rebbot the links i created before disappear i i need to run snddevices again and give the permissions.

Does anyone know whats happening? How can i fix this

Thanks

That's because of the udev package. When using a 2.6 kernel Slackware uses udev to create devices that are in your system at boot. Basicly it is a matter of configuration of udev (located in /etc/udev) and a few days ago I did read a threat how to solve it ,
http://www.linuxquestions.org/questi...a+udev+devices

Hmm.. Interesting. Yet another reason why I dislike 2.6...... 3.2 will be out and I'll still be happy with 2.4.....

I had the same problem, also, when I upgraded to 2.6.7 on one of my boxes and after I recompiled the kernel.

Solution was very simple, using pkgtool, removed all four of the alsa packages. Obtained Patrick's alsa source code packages and used his build scripts to (re)build the packages and install them, while running under 2.6.7. All worked fine, then.

I usually have problem with alsamixer too after a new kernel install, I used to fix that by :
rm /etc/asound.state

After that a new /etc/asound.state is generated and all work fine

alsamixer segfaults on me sometimes...it's temperamental..it segfaults in the default install and also in my compiled-from-source install.

I found that after I compiled the kernel (we are speaking 2.4.26 on one of my other boxes) I solved my alsa sound problems by re-installing it.