SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Well, I was using my computer 1 night and the sound settings worked perfectly.
Then my speakers decided to go off at FULL BLAST in the middle of the night when the computer was OFF. ...woke my whole family up...
So after I was done being scared shitless, I ripped the Surge Protector out of the wall and my computer was unplugged for the rest of the night.
Next morning, I got rid of the demon speakers and unpluged them from everything.
This is where the problem occurred.
When I had the speakers in, I could see the following output devices in System Settings -> Multimedia:
Logitech Premium Stereo USB headset 350
HDA Intel (ALC888 Analog)
(There are more but I don't think they're important)
Now, when I first log in, the list of output devices are:
ALSA default output
OSS default output
(Nothing at all)
Then if I run Amorak, a message pops up saying:
Removed Sound Devices
KDE detected that 1 or more internal sound devices were removed
This is the list of devices KDE thinks can be removed:
Output: HDA ATI HDMI, ATI HDMI (HDMI Audio Output)
Yes No Manage Devices
After I click manage devices, I see that all of my headset information comes back. Now Amorak will play the audio through the headset (Like I want it to) but when I try just about any other program (Firefox), audio does not work.
How can I fix it so the headset always stays in the list like before?
Last edited by Geraldsmod; 09-07-2009 at 08:50 PM.
I suspect people are too scared to help, after all you seem to have a computer that is possessed. I would like to point out that it is impossible for a computer to turn itself on and carry out an independent action. You must of had it on standby, or wake on-lan or something. However that is besides the point. try running the old alsaconfig, alsamixer, alsactl store as root and see if that exorcises your deamon.
I gotta ask: What was blasting out of the speakers while the machine was OFF?? Hopefully not something like a backwards Ozzy Oz recording
Anyhow, I'd be looking at the ALSAmixer settings, especially of your motherboard has automatic jack sensing. The automatic jack sensing might be acting up, and/or not working properly depending on the exact level of support for your hardware by the ALSA driver and other ALSA software installed on the machine.
Maybe look at ALSAMIXER, play with the settings, and see if you can get some semblance of normalcy that way. Also, please tell us what distro you're running, and which version of the ALSA packages, AND what motherboard you're running.