Dominic-Luc Webb wrote:
> On Mon, 3 Mar 2008, Olive wrote:
>> (it was www.slackbuilds.org sorry...)
>>
>> Olive
>
> I went here and all I found was a file clearly indicating it
> was Ekiga,

This site only provide build scripts. You have to download the source
(mentioned in the .info file; this file can be sourced so you can easily
write a script that automate the process) and launch xxx.SlackBuild to
build the package (dependencies are indicated in the README file: in the
case of ekiga it is opal and pwlib).

but was actually just an ASCII file pointing to
> some website. Anyway, this may be besides that point. I
> suspect that even your build might end up giving the same
> problem anyway. From what I can find so far, this looks like
> a kernel configuration issue or maybe a bug that needs to be
> fixed by those writing drivers. I would most be interested
> in hearing from someone who has encountered this problem
> and figured out how to fix it. Have you encountered this
> yourself or maybe have some idea where it is coming from?

I have not experienced it but I would try the following in order to
debug it. Can you play sound files with aplay (try aplay <somefile>.wav)
and can you record something from the micro with arecord? These tests
should tell you if the problem come from the kernel/hardware or not.

What have you configured in audio devices of ekiga? What are the options
available? If aplay works; try to use ALSA as the audio plugin and your
specific card in Audio Devices (I can choose between Default and HDA
Intel: my sound card; do not use the default but your specific sound card).

In case ekiga is misconfigured; try to delete its configuration file
(the non gnome build store it in ~/.config/ekiga but I beleive the Gnome
build use gconf).

Olive