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.
On a whim, I decided to give KDE 3.2 a try. I emerged kdelibs and kdebase, and went from there. Everything was going good, until I decided to include kdemultimedia.
Once that was installed, my sound began acting up. I'd hear a bit of static, and the occasional morse code-like beeping. This, combined with a few other things that turned me off about KDE, led me to simply remove the whole damned thing, thinking that would restore the sound. So I unmerge kdemultimedia, kdelibs, and kdebase. No luck.
Every time I restart, I get a big burst of static into my headphones, followed my intermittent bursts every few seconds. It gets worse once I go into X; every time I click on something or try loading a web page, I get static while whatever program I'm using is working.
I've re-emerged alsa-lib, with no luck.
I've stopped, started, and restarted alsasound at least a dozen times. No luck.
I've fiddled with the volumes with alsamixer. No luck.
I haven't changed anything kernel-wise (running 2.6.2 ATM), and I've purged my entire system of anything KDE-related, and still no luck.
If it does I use the following work around, its far from idealy but untill I find a better solution its all that I could get to work
//You need to stop the alsa server copy the backup asound.state file and restart the alsa
//This is how I do it
//add the following
%users ALL=(ALL) NOPASSWD /etc/init.d/alsasound stop
%users ALL=(ALL) NOPASSWD /etc/init.d/alsasound start
%users ALL=(ALL) NOPASSWd /home/username/.alsafix/TextFile
Now save the file by pressing esc and typing :wq
NOTE:above should be %users and not your username
Ok now in a terminal type the following
//CREATING COPY ASOUND FILE
//Type the following
cp /etc/asound.state.new /etc/asound.state
//Now save the file
press esc and then :wq
//CREATING ALSA FIX FILE
//Type the following
sudo /etc/init.d/alsasound stop
sudo /etc/init.d/alsasound start
//Now save the file
press esc and then :wq
//SETTING FILE PERMISSIONS
open konqueror up at /home/username/.alsafix
Right Click on TextFile and go to properties then permissions
Click the make executable
Change the top pull down list to can read only
Right Click on run
And do as above for TextFile
Has the hissing stopped? If it has not check that you have done all of the above
If it has type
cp /home/username/.alsafix/run /home/username/.kde/Autostart/run
//Make sure the file permissions are still ok
Now reboot and login to Kde has the hissing etc stopped does sound work?
WARNING the arts server still seems to be able to muck system settings up, for example my version of xine is a nightmere
To get round this you could run the run command with your xine command for example
Hope this helps you in someway and don't stop using KDE 3.2 its much better than gnome or Kde 3.1 etc: The instructions above are basic I know you prolly know all this having installed kernel 2.6 but some people might not
I am new to bash so sorry. Just added the sleep command as on my system run is run to early and has no effect the sleep command allows arts to mess up then fixes alsa for it
Anyone got a better fix
Last edited by hyperlink1uk; 02-27-2004 at 11:04 AM.
The only further advice i can give you is to run alsaconfig and go to the amplifer section and press M. Some people said that has worked for them. It could just be you need the correct asound.state file for your sound card and thats why mine did not fix it. Just out of interest was it kde3.2 or one of the betas or rc builds. Just to check you did stop alsa before copying the file across? Otherwise alsa will overwrite it when it shuts down or is restarted. What sound card do you have? What distro?
I don't have alsaconfig on my system. Did you mean alasconf?
I ran that, and it doesn't think I have any sound cards installed at all. Is this a 2.6 thing, or is it because I compiled my sound card support into the kernel rather than as a module?
As for KDE, I installed kde-3.2.0. And yes, I did stop alsa (/etc/init.d/alsasound stop) before copying over the new asound.state. My sound card is the onboard nforce2 card using the intel i8x0 driver.
I have never had my sound card driver built into the kernel so not to sure, in your modules.conf file have you still got an entry for your sound card? Also on SuSE 9.0 the file /etc/init.d/alsasound needed to be changed because the script used modprobe -c which does not exist any more, for the new mod-utils for kenerl 2.6.
My advice would be to try using a module, and check the entry in modules.conf matches the name of the driver in kernel 2.6.
At the moment does dmesg give any errors after you have run /etc/init.d/alsasound config, because if it does not believe a sound card is installed it might be giving an error message.
If you do decide to config a module remeber to replace your kernel with the new one as well otherwise you will prolly get problems loading it.
What version of Geneto are you using?