From: Daniel F. <dmf...@gm...> - 2007-12-02 21:04:34
|
Does anyone have any input on this issue? Thanks, Dan Original Message: ============= I am trying to get ALSA setup as my sound driver. I believe I have all the modules loaded correctly, however ALSA fails to initialize. I get this error when I try to list out the devices: # aplay -l **** List of PLAYBACK Hardware Devices **** ALSA lib control.c:817:(snd_ctl_open_noupdate) Invalid CTL hw:0 aplay: device_list:231: control open (0): No such file or directory aplay: conf.c: 3108: snd_config_update_free: Assertion `update->count > 0 && update->finfo' failed. Aborted Thanks for any help. Dan |
From: Daniel F. <dmf...@gm...> - 2007-12-03 00:00:07
|
I think I found the problem. When I do an strace on aplay -l, it appears to be trying to load the alsa.conf from /usr/share/alsa, but it is prefixed with the path to the staging directory. I would assume then, that there is a problem with the paths in package/alsa-lib/alsa- lib.mk and package/alsa-utils/alsa-utils.mk. Dan |
From: Toner, B. <ben...@ro...> - 2007-12-03 10:13:12
|
Search the mailing list archives for "c++ and sound compatibility <http://news.gmane.org/find-root.php?message_id=3D%3c2181C5F19DD0254692452 BFF3EAF1D680357AB78%40rsys005a.comm.ad.roke.co.uk%3e> " =20 I posted a work around some time ago - see below =20 > > I have now also got the Alsa sound library working in r1183. > > Firstly buildroot needs to be compiled after making a small change in > > /package/alsa-lib and alsa-utils > > change the config.in to read BR2_PACKAGE_ALSA_LIB or _UTILS in line 1 > > > > Then you'll find in ./gumstix > > -buildroot/build_arm_nofpu/staging_dir/usr/share/alsa all the required > > files. Copy the whole alsa directory into the gumstix, into a directory > > with an identical path to the directory on you build environment > > > > so in my case I created a dir /home/bt/gumstix/gumstix > > -buildroot/build_arm_nofpu/staging_dir/usr/share/alsa on the gumstix and > > copied everything in. > > > > This needs to be fixed in the install path in the config files that come > > down from buildroot - any takers? > > > > then, > > modprobe snd-pxa2xx-ac97 > > > > run aplay -l and you should see your device. =20 =20 ________________________________ From: gum...@li... [mailto:gum...@li...] On Behalf Of Daniel Frey Sent: 03 December 2007 00:00 To: gum...@li... Subject: Re: [Gumstix-users] How to use ALSA on Connex 400 + AudioStix2 I think I found the problem. When I do an strace on aplay -l, it appears to be trying to load the alsa.conf from /usr/share/alsa, but it is prefixed with the path to the staging directory. I would assume then, that there is a problem with the paths in package/alsa-lib/alsa- lib.mk and package/alsa-utils/alsa-utils.mk. Dan --=20 Roke Manor Research Ltd, Romsey, Hampshire, SO51 0ZN, United Kingdom A Siemens company Registered in England & Wales at: Siemens plc, Faraday House, Sir William Siemens Square, Frimley, Camberley, GU16 8QD. Registered No: 267550 ------------------------------------------------------------------------ Visit our website at www.roke.co.uk ------------------------------------------------------------------------ The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Ltd and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. ------------------------------------------------------------------------ Please consider the environment before printing this email |
From: Daniel F. <dmf...@gm...> - 2007-12-04 03:07:20
|
Thanks for the work around. I am interested in trying to fix this issue but may need some help doing so.. I have reviewed the alsa-lib.mk and I believe the error exists in this section of the code: # Install into target dir, for utils using shared libraries on target. $(TARGET_DIR)/lib/$(ALSA_LIB_BINARY): $(STAGING_DIR)/lib/$(ALSA_LIB_BINARY) install -D -v -m 0644 $< $@ $(STRIP) $@ (cd $(TARGET_DIR)/lib; \ rm -f libasound.so libasound.so.2 libasound.so.2.0; \ ln -s libasound.so.2.0.0 libasound.so; \ ln -s libasound.so.2.0.0 libasound.so.2.0; \ ln -s libasound.so.2.0.0 libasound.so.2) There is no code that moves staging_dir/usr/shar/alsa to target_dir. I pulled the latest buildroot and review its alsa-lib.mk as well. The two processes are performed differently. Here, the result of the install are to a destination with all paths explicitly from the root, but in the gumstix alsa-lib.mk, the library is installed to the prefix, which happens to be under the staging_dir. The comments seem to indicate that this is so other packages can resolve dependencies, but it never moves the installed files to the target_dir. I am looking for some pointers on how to proceed. Thanks for any help. Dan Original Message ============= Search the mailing list archives for "c++ and sound compatibility <http://news.gmane.org/find-root.php?message_id=%3c2181C5F19DD0254692452 BFF3EAF1D680357AB78%40rsys005a.comm.ad.roke.co.uk%3e> " I posted a work around some time ago - see below > > I have now also got the Alsa sound library working in r1183. > > Firstly buildroot needs to be compiled after making a small change in > > /package/alsa-lib and alsa-utils > > change the config.in to read BR2_PACKAGE_ALSA_LIB or _UTILS in line 1 > > > > Then you'll find in ./gumstix > > -buildroot/build_arm_nofpu/staging_dir/usr/share/alsa all the required > > files. Copy the whole alsa directory into the gumstix, into a directory > > with an identical path to the directory on you build environment > > > > so in my case I created a dir /home/bt/gumstix/gumstix > > -buildroot/build_arm_nofpu/staging_dir/usr/share/alsa on the gumstix and > > copied everything in. > > > > This needs to be fixed in the install path in the config files that come > > down from buildroot - any takers? > > > > then, > > modprobe snd-pxa2xx-ac97 > > > > run aplay -l and you should see your device. |