Damned odd and annoying

Jubei · #1 07-12-2002, 05:37

Lo

Someone PLEASE help me.

I am running Linux Red Hat 8.0, KDE 3.03 with arts.

I am using the latest ALSA available for kernel 2.4.18. I have an SBLIVE!

If I use ALSA drivers, TeamSpeak doesn't run. If I run TeamSpeak with TeamSpeak -d I don't see any output to console or /var/log/message (does it send it somewhere else?)

If I use the default kernel driver instead of ALSA, it runs, I can hear what's being said, but it doesn't detect me speaking into my mic. If I bind a push to talk key, no one can hear me. I can hear my output via my speakers, but I have tried muting the mic in the mixer, un muting and playing with the volume. Nothing.

If poss I'd like to find out why TeamSpeak just sits after I run it with no GUI loading with ALSA if poss.

Oh, and when I run TeamSpeak from console with ALSA running and it just sits there, I get this when I CTRL+C:

Runtime error 0 at BFFFF2F8

Please help!

N. Werensteijn · #2 07-12-2002, 11:45

The logs are in /home/<yourdir>/.teamspeak2/TSClient.log

You must make sure the volume on your mic is high enough and that the soundcard is set to capture the microphone. (maybe its set on capturing line in or something like that)

Jubei · #3 07-12-2002, 20:38

Quote:

Originally posted by N. Werensteijn
The logs are in /home/<yourdir>/.teamspeak2/TSClient.log

You must make sure the volume on your mic is high enough and that the soundcard is set to capture the microphone. (maybe its set on capturing line in or something like that)

Thanks for the reply.

About an hour ago a development occurred on this. It was the volume setting on a control called IGain and OGain? wtf?

So that's it working now with the kernel default emu10k1 driver, cool great.

Now, I'd love to find out why it's not working with the ALSA drivers, ie, I run it, say from command prompt and it just sits there. Nuthin, nada.

Jubei · #4 16-12-2002, 11:11

Gah

Someone please help me on this. I just upgraded my alsa rpms today and still no joy, if I run from console it just sits there doing nothing, as if hung. Nothing goes into the debug report either.

Heelllp!!

[alexb@titan alexb]$ rpm -qa | grep alsa
alsa-lib-0.9.0rc3-fr3
alsa-xmms-0.9.7-fr1
alsa-kernel-0.9.0rc3-fr11_2.4.18_14
alsa-lib-devel-0.9.0rc3-fr3
alsa-driver-0.9.0rc3-fr11
alsa-utils-0.9.0rc3-fr2
alsa-kernel-0.9.0-fr0rc6.1_2.4.18_18.8.0
[alexb@titan alexb]$

Jammet · #5 20-12-2002, 00:39

I'll try and help, what's your current problem? The mixer?

Jubei · #6 21-12-2002, 11:57

Quote:

Originally posted by Jammet
I'll try and help, what's your current problem? The mixer?

No...not the mixer....as I said in my post, if I use ALSA TeamSpeak does not run at all. If I start it from a command console, it just sits and does nothing, no program appears. If I start it with debugging on, nothing goes into the debug log.

If I use the default kernel drivers and the emu10k1 module that comes with the Red Hat kernel, it works just fine.

Jammet · #7 21-12-2002, 12:49

In that case, perhaps a stack trace can help. What will strace say?

Jubei · #8 21-12-2002, 16:19

This is the stack trace.

It gets up to the point at the end of the file, and just sits. I've left it 20 minutes and nothing happens.

http://nwahead.dyndns.org/teamspeak-stacktrace.txt

Woulda been a bad idea to paste that little lot

N. Werensteijn · #9 21-12-2002, 18:40

From your log

Quote:

If teamspeak is not running, delete the file "/tmp/.lock_teamspeak2client"

you should get this message if you startup teamspeak in a console.

I suggest you delete /tmp/.lock_teamspeak2client and see what happens

Jubei · #10 22-12-2002, 10:52

Quote:

Originally posted by N. Werensteijn
From your log

you should get this message if you startup teamspeak in a console.

I suggest you delete /tmp/.lock_teamspeak2client and see what happens

Oops.

I did that, and aside from that message the stack trace is the same.

N. Werensteijn · #11 23-12-2002, 14:50

do you have write permission in /tmp ?
did /tmp/.lock_teamspeak2client exist?

Jubei · #12 23-12-2002, 16:38

Quote:

Originally posted by N. Werensteijn
do you have write permission in /tmp ?
did /tmp/.lock_teamspeak2client exist?

Ok, please give me a small amount of credit, I realise you don't know me but I assure you file permissions etc I am well aware of.

And I'd have more problems than just TeamSpeak if I didn't have write access to /tmp

I will reiterate. If I use the normal kernel drivers, TeamSpeak works like a charm. If I use ALSA, it does not, it just stops when I run it.

Krenn · #13 05-02-2003, 22:56

Could the problem be artsd?

I know that I have to shut down artsd to use TS, or I get exactly the same behavior - no GUI comes up at all, and hitting ctrl-c just gets me the "Control C pressed!" popup.

Krenn · #14 05-02-2003, 22:59

I should add, I just tried:

artsdsp TeamSpeak

and the GUI popped up. Haven't tried it for functionality though, as my normal TS host is screwed up at the moment.

heinz! · #15 11-02-2005, 17:37

You have to stop your KDE-Soundsystem because it will take control over your hardware. TS2 dosn't know arts or alsa and can only use OSS properly.