On Jan 3, 2008 3:04 PM, Adrian McMenamin <lkmladrian@xxxxxxxxx> wrote: > On 03/01/2008, Jonathan Stowe <jns@xxxxxxxxxxxxx> wrote: > > On Thu, 2008-01-03 at 19:48 +0000, Adrian McMenamin wrote: > > > On 03/01/2008, Erik Slagter <erik@xxxxxxxxxxxx> wrote: > > > > > > > Please try "aplay -Dhw0,0 file" the device syntax is mandatory afaik. If > > > > that works you can start building a proper alsa config file with all > > > > kinds of useful stuff on top of that. > > > > > > > > > > > > > > Does this > > > > > > $ aplay -Dhw0,0 /aine-email.wav > > > ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM hw0,0 > > > aplay: main:545: audio open error: No such file or directory > > > > that'll be "-dhw:0,0" > > > > Getting this > > > $ aplay -dhw:0,0 /aine-email.wav > Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono > ALSA lib pcm_plug.c:773:(snd_pcm_plug_hw_refine_schange) Unable to > find an usable access for '(null)' > aplay: set_params:895: Access type not available The problem is almost certainly an incorrect cross compile that causes ALSA to look for config files in the build host path rather than the target path. But I don't know how to verify this without strace. Is it possible for you to compile ALSA on the target? Lee ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
