Fedora Core 4

[glassman324]

Hello all. First off I am a noob to Linux and its a little different from my Winblows machine so just bare with me. I'm running Fedora Core 4 right now and cannot get the TS server to start. I have done everything in this thread (http://forum.goteamspeak.com/showthread.php?t=19204) up to the point of actually getting the server to run. I was looking around and found this thread (http://forum.goteamspeak.com/showthread.php?t=22090) for the client side. Not sure if that helps at all. Anyway, I have the same problem, just related to the server instead of the client. Any input would be appreciated. Thanks.

- glassman324

~~We're all n00bs before we become l33t.~~

[wasabi]

Well, I've got Fedora Core 4 installed on my box last evening and can't get my TS2 Client working properly. The client ist working fine. I can hear everything from other participants but I'm unable to get my microphone working...

Sorry, that's not a Answer to your question, I'm just using your thread to concentrate the Fedora Core 4 problems and keep it together. :rolleyes:

Does anyone know what to do? :confused:

Thanks in advance!

[Bob Loblaw]

Try the tips found in thread:
http://forum.goteamspeak.com/showthread.php?t=23860

Which came from thread:
http://forum.goteamspeak.com/showthread.php?t=16460

It seems that the TS2 server needs some legacy work-arounds to get past the exec-shield stuff in the Fedora kernels.

[Bob Loblaw]

Well, I've got Fedora Core 4 installed on my box last evening and can't get my TS2 Client working properly. The client ist working fine. I can hear everything from other participants but I'm unable to get my microphone working...

Sorry, that's not a Answer to your question, I'm just using your thread to concentrate the Fedora Core 4 problems and keep it together. :rolleyes:

Does anyone know what to do? :confused:

Thanks in advance!

What you are doing is thread-hijacking. It is generally better to start a new thread with your particular problem. Please do that in the future.

But to answer your question there are a few things that you can check:
1) Does your microphone work? Commonly mics are broken and it wastes a lot of debugging time before that is finally checked.
2) Is it plugged into the microphone port vs. the line-in port? Microphones need a DC bias voltage to power them and this isn't present on most line-in jacks.
3) Do you have the correct capture device selected? Go into your mixer controls (right click on the volume control in Gnome and click the capture checkbox under the mic slider, or in a text console type "alsamixer" and use the tab key to switch to capture devices, arrow to mic and spacebar to toggle on/off and esc to exit) and make sure that the capture flag is selected for the microphone control.
4) Use the +20dB mic boost. Sometimes microphones and the input sensitivity just suck and this helps.
5) Don't bother messing with the mute button under the mic slider. That will just mute/unmute whether you hear the mic input out of your speakers or not. Generally having this unmuted just causes feedback and is only good for home-made karaoke :]

Hope these tips help.