DebianThis forum is for the discussion of Debian 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.
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.
My wife's computer has two microphones, one hardware mic with a 3.5mm plug and a USB camera with integrated mic. Since the camera stands on top of het screen, she prefers the hardware mic which she can hold close to her mouth. Skype is very important to her so she can talk with the kids which are overseas.
Debian installs pulseaudio server by default. This is what happens when pulseaudio is installed:
KDE mixer only shows one volume control for the output and one for each input, no other controls.
It is not possible to select which sound source to use as default
The input source is invariably put back after a reboot to line while this must be front mic
The only way I can get the sound setup working properly is using alsamixer
At reboot these settings are lost, despite of having them saved with alsactl store
Running alsactl restore does restore all settings, except setting the input source correctly
Once I set up everything in alsamixer, I can use the hardware mic with Skype.
In Skype I can only choose pulseaudio server as sound input. All other settings I have to do with alsamixer.
The problem is the settings are not retained and I can't ask my wife to open a terminal and check 17 settings in alsamixer.
So following a recommendation on the KDE forum I removed pulseaudio. Now this is what happens:
KMixer shows all my volume controls, and I can select the audio source that I want. Yeah!
I can tell Skype to use the USB microphone, and this actually works when all inputs are selected the correct way in alsamixer or KMix.
When I restart KDE, the previous settings are being lost, despite I told KMix to store my settings.
alsactldoes store my settings correctly and restores them correctly at system boot.
But then KDE comes and adjusts everything to whatever it likes, not what I saved in KDE, not what alsactl tells.
The trick is that I have to setup the audio correctly in alsamixer, use alsactl store, and tell KMixernot to restore the settings when starting KDE (go figure...)
This would all be very nice if I could get the front mic actually working. It is selected all right, but I only hear static and buzzing sounds. Arecord records correctly, but Skype refuses to use this microphone. While it did when pulseaudio was still installed.
Sigh... so using the hardware microphone and have all adjustments being saved on startup is mutually exlusive.
I have no idea if it would really help, but when I was having issues with sound on Squeeze (I'm now on Wheezy) I've installed the liquorix kernel and they vanished away. Possibly unrelated, my card is some intel onboard, and there's no guarantee that the liquorix kernel will happen to have the module of your card. That is, if that's really a matter of kernel modules, I don't know.
Distribution: Debian Wheezy/Jessie/Sid, Linux Mint DE
Originally Posted by the trooper
Could you use something other than Kde?.
I should. But I like the window effects. It is a high price to pay.
Since this problem I have been upgrading my T61 laptop which was another bad KDE experience. The sound problem is exactly the same as described in this post. For the rest KDE is like a mystery game. Settings change where you don't expect it, can't be adjusted where you do expect it, many things are hidden and has to be taken care of in the CLI and sometimes get adjusted by KDE -- or not, some settings are saved over KDE restarts, others are not, you never know which those are.... etc, etc.
Upgrading this laptop has taken me over 24 hours now, the most of them being taken by KDE oddities.
Distribution: Debian Wheezy/Jessie/Sid, Linux Mint DE
Originally Posted by Caravel
A kernel update may/may not make a difference, but it's worth a try. Rather than liquorix, go with the 2.6.38 from the testing branch - if it doesn't fix it, boot into 2.6.32 and remove it again.
I have no idea whether this is a kernel problem. Last week I upgraded this Lenovo T61 laptop and I have exactly the same problem with selection of the internal mic. I didn't even bother to try the pulseaudio thing etc. Since this is my own laptop I can use Alsamixer when I start Skype.
When I select internal mic as input I do a alsactl store. When I restart KDE, the input setting is back to mic, and alsactl restore does not restore it. Now is this a alsactl problem (not restoring all settings) or is it a KDE problem (screwing up what was set correctly)