SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is for those who reguraly uses swaret or slapt-get and got the sound broken since a few days.
Well guys, I've just updated my system (a few weeks without doing it) and I saw that ALSA broke up, what I saw is that the ALSA package comes compiled for 2.4.27 kernel, so instead of installing drivers to /lib/modules/2.4.26 it installs them to /lib/modules/2.4.27 (Don't try to move them, they're compiled for different version).
How to get over this? Well I'd recommend to compile the drivers manually (download the source from alsa-project.org, uncompress and type: ./configure && make && make install), be sure to remove the current alsa packages before
Those who compile their own 2.6 kernel should also compile them manually.
You could also upgrade your kernel to 2.4.27 and you'll be able to use these packages
Last choice, downgrade to a alsa package compiled for your kernel (like the ones that comes in slack's cds that are for 2.4.26) and add alsa to your update utility exclude list.
Well, i've just discovered that I compiled alsa-utils and didn't remove the old alsa-utils package I had. What happens if you remove it before is that you will loose the /etc/rc.d/rc.alsa file causing alsa mixer settings (what you store using alsactl) won't be loaded at startup.
To solve this, you can extract the file /etc/rc.d/rc.alsa from alsa-utils package and copy it to /etc/rc.d.
I'll paste here a copy of rc.alsa in case you don't want to get the package just to extract that file (remember to make it executable by typing: chmod +x /etc/rc.d/rc.alsa).
Code:
#!/bin/sh
# Load the mixer settings and OSS compatibility for ALSA.
# (the Advanced Linux Sound Architecture)
# A function to load the ALSA mixer settings:
load_alsa_mixer() {
if [ -r /etc/asound.state ]; then
echo "Loading ALSA mixer settings: /usr/sbin/alsactl restore"
/usr/sbin/alsactl restore
else
echo "ALSA warning: No mixer settings found in /etc/asound.state."
echo " Sound may be muted. Use 'alsamixer' to unmute your sound card,"
echo " and then 'alsactl store' to save the default ALSA mixer settings"
echo " to be loaded at boot."
fi
}
# A function to load the ALSA OSS compat modules:
load_alsa_oss_modules() {
if ! cat /proc/modules | grep -w snd-pcm-oss 1> /dev/null 2> /dev/null ; then
echo "Loading OSS compatibility modules for ALSA."
modprobe snd-pcm-oss
modprobe snd-mixer-oss
fi
}
# If hotplug or something else has loaded the ALSA modules, then
# simply load the mixer settings and make sure the OSS compat
# modules are loaded:
if [ -d /proc/asound ]; then
load_alsa_mixer
load_alsa_oss_modules
else
# If there are ALSA modules defined in /etc/modules.conf, but
# ALSA is not yet loaded, then load the modules now:
DRIVERS=`modprobe -c | grep -E "^[[:space:]]*alias[[:space:]]+snd-card-[[:digit:]]" | awk '{ print $3 }'`
if [ ! "$DRIVERS" = "" ]; then
echo "Loading ALSA kernel modules."
for module in $DRIVERS; do
modprobe $module
done
fi
# If ALSA is now up, then load the mixer settings and OSS modules:
if [ -d /proc/asound ]; then
load_alsa_mixer
load_alsa_oss_modules
fi
fi
I really don't know, I don't own a nvidia based motherboard (I'm still happy with my SB Live Value! :P)
Search LQ forums, i'm pretty sure there's a answer inside
I know some people do that chbin, I made this thread because there was a "crack" in Slackware current where all people suddenly lost their sound when updating to it and were filling this forum with threads about it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.