Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm having a few problems and I was hoping someone could help me out. First of all, I'm running FC1 with the regular kernel. I installed ALSA and it seems to be working for the most part... However, everytime I turn on my computer the left channel is mute (not in the mixer, just hearing it) and playing around with the volumes unmutes it. I guess it's not so much of a problem as it is an inconvenience.
Second thing, more of a problem, I can't run WineX. It gives me a:
For the loading/muting problem:
make sure you have a startup script for ALSA in your /etc/rc#.d directory, where # is your default runlevel. The script that comes with alsa should take care of saving/restoring volumes. If not, the commands are:
alsactl store <-- this stores current settings
alsactl restore <-- loads previous settings from file
Try setting the output of XMMS or some other program to OSS. If it works, the problem is with WINE. If it doesn't, the problem is with ALSA.
I think the scripts are executing fine, when I run alsactl restore it puts the volumes back where they were when I started the computer but the audio channels are fine. It seems the only time they're off are when I first power on the computer. As for the OSS thing, I set xine to OSS and it seems to work fine. What else should I try?
If you can understand the scripts at all, read through the alsa one, and make sure it's calling alsactl store/restore at the proper places (stop/start).
Otherwise, just add a simple script to your default runlevel:
If xine is working fine on OSS emulation, then it's 99% likely that the problem is in WINE, and its handling of sound. Check your WINE config - I've got 0 experience with it at this point, so I can't be of much help. search this forum and the WINE forums for a solution.
ok, ill try the script thing, i just dont understand how so im hoping someone can explain it to me. i see in each runlevel theres a file S or K##service, im assuming i just make one called (S/K##)alsa but i dont under the S## and K## thing. any kind of explanation would help. thanks.
thanks to everybody who replied. i figured both out, and for anyone else who is having similar problems, here's how. for the balance problem, you guys said to make scripts for saving and restoring the volumes. well, there was already an alsa script in runlevels 0 and 6 (but not 5), so i looked at it and it said:
# It will save the ALSA settings, to restore them you will need to add
# the following to your /etc/modules.conf file :
# post-install snd-card-0 /usr/sbin/alsactl restore >/dev/null 2>&1 || :
# pre-remove snd-card-0 /usr/sbin/alsactl store >/dev/null 2>&1 || :
# The second line does the same as this script, for when the module is
I already had a similar line in my modules.conf but it wasn't running /usr/sbin/alsactl... so all i had to do was replace the two lines there with these two lines... no scripts necessary. what i don't get is why alsaconf would create a script in the shutdown/reboot runlevels and add the right modules to modules.conf but not automatically put those two lines in there as well.
anyways, the winex3 problem. did a little searching around, and it turns out it had nothing to do with the oss drivers. fedora core 1 has some problem with winex3 and error=21 is due to pre-linking. so all i had to do was edit /etc/sysconfig/prelink and set PRELINKING to no, then run /etc/cron.daily/prelink and after that was done winex worked fine. the only question i have remaining is what does prelinking do, and what do i lose by disabling it?
thanks to everybody who responded and i hope this helps someone else who is having similar troubles.