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!
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.
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 18.104.22.168-170.2.5.fc10.x86_64. If I go back to 22.214.171.124-117.fc10.x86_64, the sound is back again. I'm sure I'm missing something obvious, but would really appreciate some help.
/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.
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.