Normal Linux event sounds (opening, closing windows etc) work OK, as do "test" sounds using aplay. No sounds whatsoever using FlightGear. How do I manage to "attach" FlightGear sounds to alsamixer? Where do I look for info? I have read/studied all I can find; no luck so far. Any help appreciated. SBM

>Normal Linux event sounds (opening, closing windows etc) work>OK, as do "test" sounds using aplay. No sounds whatsoever>using FlightGear. How do I manage to "attach" FlightGear>sounds to alsamixer? Where do I look for info? I have>read/studied all I can find; no luck so far. Any help>appreciated.There is a whole variety of potential sources for the problem you are experiencing, but based on what you have told us so far, we cannot really come up with a good guess.So, you need to provide some more information about your system's setup (hardware and OS/software!), also details about your sound card, FlightGear version and other things may be relevant. You can get a good impression about what sort of data is required by looking into some of the other threads. Additionally, it would also be good to know if you are using a pre-compiled binary or if you have compiled FlightGear from scratch. As an aside, FlightGear itself uses OpenAL for its sound, so you will want to make sure that there are not any sound/OpenAL related warnings or even errors during initialization. Thus, it may make sense to also run FlightGear with a more verbose log-level, such as --log-level=bulk and redirect the output to a file to allow you to further investigate the output. Also, you need to realize that hardware/software mixing is still only rarely seen to work properly under Linux due to the board manufacturers not releasing proper technical documentation for opensource driver development, meaning you might have to make sure that no other software (i.e. xmms) is using (=possibly blocking!) the sound device when you start up FlightGear, otherwise FlightGear may not be able to allocate the sound device exclusively. So, you see there are really many possible reasons for your problems and you will probably want to provide some more information about your setup, otherwise the only thing we could do is to keep guessing.

Thanks for the insight. I'll investigate and supply any needed info. SBM

>Thanks for the insight. I'll investigate and supply any>needed info.> SBMMy guess is, the artsd sound server from KDE is blocking the soundcard device.So to circumvent this open a console and enter the following command:"artsshell terminate"This will stop your artsd sound server.After that start FlightGear.

Thanks, but I note that I don't have OpenAL. I'm trying to get it either through RPM's or compiling it through CVS. SBM

Here's a summary of progress to date:1) OpenAL installed OK, but but not the alut portion. "Make" says missing references in the hello_world.c file. Trying to follow the procedure in the README file, but no luck so far. Is alut required in order to provide sound in FlightGear?2) So far, the only executable binary found under openal is "openal-configure". Is this correct? I would have expected something like "OpenAL" to start the application.3) The docs say that I should have a ".openalrc" file, which requires an added statement, but all I can find is "sample.openalrc". It would seem that I'm still missing something, don't know how to start OpenAL or still need alut. If I had some idea of where to look, I could at least investigate before "dumping" the numerous files required for a pro to analyze it.