SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Did you try running alsaconf as root to configure alsa for your sound card?
Then run alsamixer as a regular user to set your sound levels.
Then run alsactl store as root to save these settings.
Do you have more than one audio-device i.e. does your laptop have HDMI?
As you know, with the command
the modules are shown which are in use a device. I'd recommend to check this in the following way: When you don't have sound, don't run alsaconf but "lspci -k" and look if the module for the soundcard is loaded. If it's not, load it with modprobe and find out if the sound is working now. alsaconf loads the modules for the sound-device, so if that's the problem you'll don't have to use alsaconf.
You may as a first step (when the sound is working) check which module is used. Then (the next time it doesn't work) check for the module. It may be, that the module isn't loaded automatically. The you can load it "manually" with modprobe.
If this is the problem, you can load the module at boot-time with modprobe in the /etc/modprobe.d directory. Be sure that the module isn't blacklisted.
I will try to compile the 38.4 with the /proc/config.gz of the 33.4 to see if my sound works =D
So, if the kernel 33.4 works sound(at this time...), so using this kernel configuration I can did it works on 38.4 too?? Or just copy the .config of the /usr/src/linux...33.4 to 38.4 and make a oldconfig ?
So, if the kernel 33.4 works sound(at this time...), so using this kernel configuration I can did it works on 38.4 too?? Or just copy the .config of the /usr/src/linux...33.4 to 38.4 and make a oldconfig ?...
Yes, this will work, and it is what I do in such cases.
What I meant in my first post was: if the sound does not work, you may check the modules and if they are not loaded, load them and check if the sound then works. In fact it is only one module to load.
I did not understand if you've checked this.
The KDE message may result from a missing HDMI-driver in your graphics-driver. I have a Radeon HD 5470 graphics-adapter and when I use the kerneldriver (radeon) instead of ATI's fglrx driver I have always this message of KDE. As you know HDMI is a Video/Audio-port.