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.
Thanks, Drakeo. I will try that and see what happens. Thanks for the reply. I was wondering if maybe I had missed something obvious and should have known what to do. Since I am new to linux, I read a lot of posts and howtos but haven't found a solution that will rid me of my error popping up each boot.
Drakeo, When I type alsaconf I get 'command not found'. I did a search for alsa* and there is a file named alsa.conf in the /etc folder. I also typed 'alsa.conf' but still got "command not found". What should that be telling me?
I assumed the alsaconf was a good command.(It doesn't work on my pc either.) I've found most commands have to have the /sbin/ in front of them. One command that displays a list of pci devices on your pc screen is lspci. It works at the user level or root level for me but only with /sbin/ otherwise you get the error can't find command. /sbin/lspci
Fedora just switched to Pulseaudio for sound server, so maybe this error will be fixed shortly with an automatic update. I have a different sound error. So far I'm just waiting for a Fedora 8 specific update. Think I may have to add my self to some types of "groups" (pulse-rt? or pulse-access? or pulse? or Jack?)on my pc to correct error, but not sure yet. http://pulseaudio.org/
Actually tktim, since I started this thread, I put a check in the box so the error message wouldn't show up any more. My sound is working fine. I think that I have had a sound update. I know that I have had quite a few updates lately. Thanks for efforts by yourself and Drakeo in addressing this issue with me. It helps greatly in my learning process to get ideas and information from others that probably are more knowledgeable than myself. I am basically a newcomer to Linux. Anything that I can add to my computer knowledge is appreciated.
Ok when the sound server crashes it resets. there is a reason for this if it is not used in like 60 seconds it goes down so any other program can use it. go into your sound system and make sure it is set to defaults. if for some reason it may be set for to much stuff. I get the crash onces in awhile during boot up this is caused by KDE the sound server is starting at the exact same time KDE is loading and KDE will try and take the server at that point.it crashes resets and kde is now using it. for the next 60 seconds or until another program like gxine or any other media player wants it. It never really crashes it is just a program that says print this message that there has been two or more programs colliding at the same ram point.the sound server can only be run by one program at a time this is a load bug and will not be fixed so as you can see the messages is correct CRASH
houndhen: You might find this helpful.
Right click “Applications”, click Edit Menus, click System, click Preferences, "check" Control Center, click Close. Then click System from drop down at top of screen, click Preferences, click Control Center. This allows you to control about 30 to 40 items in one spot.
Drakeo: (Thanks for your help.) I've tried the command at both the user lever and root (used my root password to go to root. - I'm sure I'm at root.) Both with and without /sbin/. Always says can't find command. The Control Center has a Sound Icon, Volume Control(Alsa mixer) Icon and a Soundcard Detection Icon, etc. I think the Soundcard Detection Icon may be the same or simular to alsaconf. It allows you to configure your soundcard.
glad you got it going.I have not been using FC8 in a while I am a slackware person and as you know slackware you use the terminal a little more then the GUI so I will have to Bone up on some mor of the Gui distros. But I like to know what comes up when you type als then push the tab button this will show all the comands for als. mine comes up alsaconf alsactl alsamixer alsawizard. just curious how FC8 has edited ther commands
First try with alsacard barfed, got a connection error, used GUI to force reload of drivers and configuration, rebooted. No more error, but now I have no sound. Alsa driver ver 1.0.15, lib- alsa-lib-1.0.15-1.fc.8, utils- alsa-utils-1.0.15-1.fc.8.
Will look to see if these were just updated and maybe try rolling back to previous version if so. I need my sound to listen to a lecture.
Model:82801H (ICH8 Family) HD Audio Controller
ALSA Driver ver 1.0.15,
ALSA Lib package- alsa-lib-1.0.15-1.fc.8,
ALSA Utils package- alsa-utils-1.0.15-1.fc.8.
Under Control Center are 3 Icons 1)"Volume Control" unmute each. 2) "Sound" enable software sound mixing(ESD), also set most to Autodetect, Can test each item here. 3.)"Sound Card Detection" test,settings,etc., can also generate two reports here for trouble shooting. Under(drop down)Applications/Sound&Video/PulseAudio Volume Control unmuted.
as I explained before it was not a sound card issue . now it is. befor it was two programs at startup trying to control the sound system it then crashed reset then used the desk top program. now you will have to go back and enable it in your gui what is F8 using kde or gnome not sure. but at this point you should reconfigure the card module make sure it is loaded the correct one make sure it is the correct one then do a alsactl that is the program that saves your setting and keeps it in your /etc/asoundstate. when you reload the configuration for your module it is kept in the /etc/modprobe.d/sound open that and you should see your card module. if it is incorrect then do a alsacard. this can be done also in gui. what is F8 using yum yeast or some interface program. and make sure it is not muted.