From: Peter A. B. <pa...@pa...> - 2012-11-29 12:38:50
|
On 11/27/2012 07:27 PM, Peter A. Bigot wrote: > I've built gumstix-console-imageusing the instructions at > https://github.com/gumstix/Gumstix-YoctoProject-Repo on the master > (stable) branch, and installed it on an Overo Fire. I can't get sound > out of the speakers using either speaker-test or aplay. It may be just > that amixer is muted, but I'm not having any luck figuring out how to > unmute it since there are 67 controls none of which is named "Volume". > Is there a basic sanity-check audio play validation test I can run on > this image, or another image supported by the stable branch, to ensure > the playback audio path works? The following commands allow aplay to generate sound on more recent kernels: amixer sset 'HeadsetL Mixer AudioL2' on amixer sset 'HeadsetR Mixer AudioR2' on amixer sset 'Headset' 2 amixer cset name="DAC2 Analog Playback Switch" 1 amixer cset name="DAC2 Analog Playback Volume" 12 amixer cset name="DAC2 Digital Coarse Playback Volume" 2 amixer cset name="DAC2 Digital Fine Playback Volume" 50 The thread at http://www.spinics.net/lists/linux-omap/msg48644.html may also be helpful as it includes settings for supporting arecord. > FWIW: The real problem, demonstrated in the 3.0 kernel on Overo (from > the 2012-01-22-1750 development image) and a 3.2 kernel on BeagleBoard > (from Angstrom v2012.12), is an issue where ALSA (aplay) works fine when > fed a fixed-rate file, but generates random clicking sounds when > processing a variable-rate SIP stream received over the network. The > same software/configuration works with ALSA on a Fedora 16 desktop. The > theory is that there's a frame timing bug with variable-rate data, > possibly in omap-mcbsp, and my hope is that it's been fixed as a side > effect of subsequent kernel updates. I can't determine that until basic > sound works, though if others have encountered this and there's a known > solution I'd like to hear the details. This issue is still present in linux-mainline-3.6-3.6.6 from meta-gumstix-community, so it's either not a kernel bug, or it's one that hasn't been fixed. Peter |