On 02/01/2008, Lee Revell <rlrevell@xxxxxxxxxxx> wrote: > On Jan 2, 2008 12:44 PM, Adrian McMenamin <lkmladrian@xxxxxxxxx> wrote: > > > > Yes, it worked very well! I think this is some sort of > > userland/alsa-lib problem. The driver hasn't changed, but alsa-lib has > > > > But cat file > /dev/dsp does not touch alsa-lib at all. > Doesn't it? Hmmm. Does it touch any of the alsa userland stuff or is the oss emulation completely in the kernel? > Did anything else change on the system? > > Maybe an interaction with the GD-ROM driver you recently added? > Not loaded so don't think that can be it. In any case was working with it before I upgraded the buildroot set up. Maybe I am still getting the cross compile wrong, this what I have now: ./configure --prefix=/tftpboot/192.168.61.55/usr --oldincludedir=/tftpboot/192.168.61.55/usr/include --host=sh4-linux CC=/home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc LDFLAGS=-L/tftpboot/192.168.61.55/lib --disable-python and now aplay etc gives me this: $ aplay -l **** List of PLAYBACK Hardware Devices **** ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL hw:0 aplay: device_list:213: control open (0): No such file or directory while aplay -L reports nothing at all All of which makes me think this is a configuration error of some sort ------------------------------------------------------------------------- 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
