Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
It happened once with Fedora 9, I upgraded to 10, and now it's happened again. I assume it's the automatic update, because I haven't changed anything else - suddenly no sound. This is kernel 2.6.27.12-170.2.5.fc10.x86_64. If I go back to 2.6.27.5-117.fc10.x86_64, the sound is back again. I'm sure I'm missing something obvious, but would really appreciate some help.
Hi Alan,
/sbin/alsa reload is a command to be typed in a terminal.
Open a terminal window and type 'su -' without the quotes to become root.
Type in the root password when prompted.
Type in '/sbin/alsa reload' without the quotes to restart the alsa program.
Others have also had this problem. If the reload doesn't help you can boot with the old kernal until a fix comes along.
Thanks, Laserman,
I don't have /sbin/alsa, all that seems close is /sbin/alsactl, and reload doesn't work with that. I guess I'll stick to the older kernel, but should I refuse updates, and how will I know when a fix comes along?
Sorry to spout so many questions. Good to know I'm not alone - well, good to know I'm not an only dumb one, and that others get this too.
It's not a good idea to refuse the updates as they may fix things far more serious than missing sound such as security holes.
If alsactl reload didn't work you may want to try
Code:
# alsamixer
which will give you a graphical display of the volume setting.
btw: when posting outputs of things like 'lspci' and 'lsmod' surround the info with:
[ code ] and [ /code ] (without the spaces)
This will format the output nicely and make it much easier to read.
Here is the output of 'lsmod | grep snd' from my system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.