My PC is Epox 9NPA+ Ultra Motherboard based (NForce 4Ultra Chipset, ALC850 Sound). I can hear sound, play songs. After I have installed Skype to my system, i could not pass the "ECHO123" test. Though I have tried many variations, I could not send my voice to the other side. There must be something wrong with my headset or mic settings! I have been using Plantronic Skype Headset and it works fine at XP. On the other hand i have tried to plug front and back mic jack but there is no change. Any comment or instruction to figure out this problem?

Thanx, Ufuk

were you playing any sounds while using Skype?

Be sure to turn off all other programs before doing so.

xboxrulz

yes i am sure all other sounds are closed. I have also checked the setting with Kmix and other variation tools. All the mic sound is open to high and the rest of sounds as well. I could not understand why the system doesnt sense the microphone! please help... :(

try testing your mic with another applications such as krecord. If your mic doesn't work with that that either then it's nothing to do with skype!

Also, check if you have the levels set up correctly incl 10dB boost setup

this is ridiculous, there must be a solution of the problem. i think we skip (miss) a very easy point from our eyes and i dont know what it is but i'd like to solve this problem and use skype in my suse 10 linux. please any other suggest or comment.
p.s i have tried the krecord, kmix and all other tools to sense the mic and get the sound but there is still no change. I am expecting a professional solution from skype team. my computer is very updated has the latest chips (nforce 4 ultra + alc850 sound) and my headset is the "plantronics skype headset" . Please help !!! :roll:

I recently upgraded to KDE3.5 on SuSE 10 and now have exactly the same problem as ufkisk. If I boot Windows XP and run Skype the mic works fine and the people I call can hear me. As soon as I go back into SuSE nobody can hear me even though I can hear them so it is not the mic. It is something in the Linux or KDE sound config. I've followed the sound setup advice for aRTs but still no joy.

The KDE Control Centre - Sound System seems a bit buggy. If I try and test sound or test midi nothing happens or it crashes. Current KDE settings are:

Enable sound system: set
Sound buffer: 185msec
Autosuspend if idle after: 5sec
Select the audio device: Autodetect
Full duplex: set
Quality: default
Select the MIDI device: Emu10k1 WaveTable Emu10k1 Port0 - ALSA device

I'm in the process of looking for the config files so I can check the duplex setting and others are actually set.

As per the post for Mandrake 10.1, ran alsaconf as root and it works. Have since used amaroK for streaming radio, stopped it and the mic still works with Skype. It will be interesting to see if any other audio apps kill it.

Magically i have configured the microphone now it sense my sound then i may record through krecord and i can replay it. there is nothing wrong the rest of the proccess since i try the skype echo123 service, i put a message but still could not hear my own sound back. it s really pissing me off, i really get bored this ridiculous bug! :?
can anyone describe me if there is anything i can do after this step? i checked the other post of the forum and i have seen it may be misconfiguration of alsa! since i am not so bright in linux configuration please explain me step by step after this step!

thanks,

All I did was open Konsole as root, type alsaconf and answered yes to all the prompts. Be aware that doing this seems to kill artsd and amaroK and mute sound in Kmix so you may have to restart them, artsd first (root Konsole). You are probably better off closing amaroK before running alsaconf.

i did as ou described but the result is unfortunately the same. :(

I've found that KDE doesn't automatically start artsd (use Cntl + Esc). If this is the case in your system you need to go into the KDE Control - Multimedia - Sound and turn sound off and then back on again. I currently have to do this every time KDE starts but it is a known bug and the KDE and SuSE developers are aware of it so a fix should be forthcoming soon.