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.
Hi, is there a way to get the sound to load at startup automatically so I don't have to run alsaconf each time I boot up linux? I am not sure if changing modules.conf works, as there is nothing in my modules.conf, and the alsa group said that it was a depracated file. If that is the solution, could you tell me what I need to add in? Thanks!
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 22.214.171.124, KDE 3.5.8 and KDE 4.0 beta, Plu
There is several ways that this can be done. Create a file either as etc/aumixrc or in your own home directory. Change settings if to low or loud. There are serveral other paramaters that can be here like pcm, bass, etc. read man pages on aumix for more help.
Contents of /etc/aumixrc.
Then edit your /etc/rc.local file and add this to it
bin/aumix-minimal -f /etc/aumixrc -L
Or start it in your /etc/modprobe.conf file. Example below. You may have something close to this.
At the moment, I am having the same problem. All was well for a while, and then it started. I am not sure when or how, because I didn't notice it at first. The problem is NOT with the mixer, which is what gets stored and restored using alsactl store / restore. The problem is in the actual configuration of alsa. I suspect that it is a bug, either in alsa itself, or in one of the drivers.
The symptons are:
* /dev/dsp is not recognised as a device
* running /etc/init.d/alsa start produces an error message saying:
"no state present for card ..." (in my case bt878)
*KDE can't find device (see first point)
Running alsaconf fixes this, it does something which forces alsa to detect the card. If anyone is familiar with the innermost workings of alsaconf, and can think of some way of automating it, this would work, at least as a temporary fix, by adding it to /etc/init.d/alsa before the bit which runs alsactl.
Any help you can offer would be great, and I hope that this information helps to clarify the problem we are having. I don't think dmesg etc. would be much use, but let me know if you want it, I just didn't want to clutter the page too much.
I am using a Via onboard sound card, I'm not sure of the model no, I think it's 82 something, but as I said, I've had it working before, I went throuogh the steps in one of the other threads to set it up in the first place, which involved blacklisting certain stuff.
As for the version of alsa, I am running 1.0.8 at the moment.
Thanks for any help anyone can offer.
Ok, I just had a closer look at dmesg:
* My sound card is via 8233
* It's having a failure when it loads:
VIA 82xx Audio: probe of 0000:00:11.5 failed with error -12
via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker
* Also, I think that the bt878 I mentioned before might be my DVB TV card, why would alsa suddenly start trying to interface with this?
Ok, I tried what you said, but it didn't work, thanks for trying. That module has been loading, even when the sound was working, so I don't think it was that. As I said, I did have teething problems with the sound, (here's what I did) but these were resolved. I believe that the problem lies somewhere in an alsa configuration file, since it tries at startup to use bt878, which I think is something to do with my TV card. If anyone knows how to automate the steps in alsaconf, so I can make a startup script, this would suffice, at least as a temporary fix.