Troubleshooting

2.Verify the JACK and ALSA components are installed and configured properly on the receiver system. To see if the modules are present, as root, type /sbin/lsmod. The modules show up as snd-*-* names. They usually appear by either direct loading or system initialization in the /etc/modules.conf [2.4 kernel] and /etc/modprobe.conf [2.6 kernel]. Examine these files for extraneous or duplicate configuration lines.

3.Unset the channel "mute" and increasing "volume" settings with volume controls such as /usr/bin/alsamixer - channels are un- muted with the "m" command and volume is increased by using arrow keys in a terminal window.

4.Check alternate audio ports on your workstation with audio earphones (in case the speaker is not active or provided).

5.The chipset was unrecognized by the provided source bundles - visit the project sites to update your systems (after updating the script rgs_audio_support).

6.On some sound hardware, ALSA mixer controls do not work as expected. Try running alsamixer in a terminal window or your favorite sound mixer application. Manually adjust the volume sliders in conjunction with the volume slider in the Receiver's Control Panel. Sometimes a sound device “Master Volume” will get mapped to the wrong slider.

7.If you have a sound card installed in your system with multiple line- outs, be sure you are plugged into the correct one.

8.On some hardware, the headphones JACK might be inactive when running ALSA sound drivers. Try plugging into the line-out in the back of your machine.

5.Validating the JACK/ALSA installation on a Linux Receiver:

When the RGS Receiver starts it invokes the jack sound server (jackd) in the background. When JACK is running it has control of the ALSA drivers on your system and prevents other applications from being able to access the ALSA drivers. Attempting to use another audio application that uses ALSA while the RGS Receiver is active may cause unknown behavior. The behavior could be observed as the audio from an application appearing to stop or causing the application to hang. The rgreceiver.sh script attempts to minimize the use of the jackd sound server.

Users can check the state of the ALSA sound drivers by playing any WAV file. On most Linux installations there are WAV files in /usr/share/sounds. Use the simple ALSA player /usr/bin/aplay to test the audio. Be sure to try this when rgreceiver.sh is not in use and the RGS Receiver application has halted.

The script hprgsaudio can determine the state of the JACK sound server (jackd). Users who own the jackd process can inquire:

∙/opt/hpremote/rgreceiver/hprgsaudio status

123