|
|
||
A Slackware Desktop Enhancement GuideConfiguring Sound© Copyright Darrell Anderson. A common request by many new Slackware users is to configure sound. For many users the solution is simple and straightforward. Slackware is packaged with the Advanced Linux Sound Architecture (ALSA).
Running alsaconf will modify the /etc/modules.conf file. A typical entry will look like this: # --- BEGIN: Generated by ALSACONF, do not edit. --- Running alsactl store is important to create a permanent configuration file at /etc/asound.state. Without that configuration file you likely will have to repeat this process every boot. Additionally, be sure to run an appropriate sound mixer device from within your GUI. For KDE that tool is KMix. Remember to plug in your speakers! You can test ALSA without booting into X. Determine the location of a wave file and then from the command line type: aplay /location/of/the/wave/fileTroubleshooting is beyond the scope of this short How-To, but after performing the previous steps a common malady is with on-board sound chips. Sometimes those kernel modules need to be added to the hotplug blacklist. Additionally, although Slackware and ALSA works fine with most standard sound cards, you might need to download some additional modules from the ALSA web site. Caveats: Every time you update Slackware and the new release includes an updated ALSA package, you need to reconfigure sound. Dumb, yes, but that’s the way things are. Similarly, if you change from the 2.4.x series of kernels to the 2.6.x series, or vice-versa, you need to install the ALSA package for that series. Lastly, if you begin experimenting with compiling the kernel, know that the process of updating the kernel modules will delete the /lib/modules/linux/kernel/drivers/sound directory. That means you will need to reinstall the ALSA package. Dumb, yes, but that’s the way things are. Finis. |
||