- Alsa-devel - mailman.alsa-project.org

[alsa-devel] HDA - Change default configuration for Fujitsu Si3515.
by Tobin Davis 21 Jun '07

21 Jun '07

This patch changes the default configuration for the Fujitsu Siemens Si3515 Laptop. Signed off by Tobin Davis <tdavis(a)dsl-only.net>

1 0

[alsa-devel] Help with SoC alsa.conf
by Paul Kavan 21 Jun '07

21 Jun '07

I am trying to determine an appropriate conf file for my AT91SAM9260ek running linux-2.6.22-rc1 and the following alsa drivers: <6>Advanced Linux Sound Architecture Driver Version 1.0.14rc4 (Wed May 09 09:51:39 2007 UTC). <6>ASoC version 0.13.0 <4>AT91SAM9260EK W6811 Driver <1> <6>w6811: W6811 PCM SoC Audio 0.1 <6>asoc: W6811 <-> at91-ssc0 mapping ok <6>grh_ek_w6811: W6811 PCM in Slave Mode <6>ALSA device list: <6> #0: GRH_EK_W6811 (W6811) I have installed alsa-lib-1.0.14a and alsa-utils-1.0.14 on the at91sam9260. The default conf file produces sound using speaker-test and aplay, but will not record using arecord. Frank Mandarino has been kind enough to lend me a barebones conf that worked for him: pcm.!default { type hw card 0 } pcm.hw { type hw card 0 device 0 subdevice 0 } ctl.!default { type hw card 0 } ctl.hw { type hw card 0 } but produces the following for me: /usr/share/alsa $ aplay -l **** List of PLAYBACK Hardware Devices **** ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL hw:0 aplay: device_list:213: control open (0): Invalid argument ALSA is *very* new to me and I am unsure how to interpret any of this. I am using a dumb W6811 pcm codec. I am fairly confident the machine/codec driver is working as expected, so I need to determine what I can do to get alsa to play nice with it as well. When I use the default alsa.conf produced from making alsa-libs, I get the following: /usr/share/alsa $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: GRHEKW6811 [GRH_EK_W6811], device 0: W6811 W6811-PCM-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 record and playing do not seem to work. When I try: /usr/share/alsa $ arecord -d5 test.wav Recording WAVE 'test.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono Aborted by signal Interrupt... It does not stop at 5 seconds....I have to interrupt it manually. Furthermore, it does not appear to record anything as when I: /usr/share/alsa $ aplay test.wav Playing WAVE ' test.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono The speaker pops once, but no audio. Finally, when I use speaker-test, I get some weird results. Doing: /usr/share/alsa $ speaker-test -r8000 -c1 -f1000 -tsine -l1 speaker-test 1.0.14 Playback device is default Stream parameters are 8000Hz, S16_LE, 1 channels Sine wave rate is 1000.0000Hz Rate set to 8000Hz (requested 8000Hz) Buffer size range from 64 to 32768 Period size range from 32 to 8192 Using max buffer size 32768 Periods = 4 was set period_size = 8192 was set buffer_size = 32768 0 - Front Left Time per period = 5.086305 Gives me a wave composed of both the 1k sine and likely a 2k sine. If I go much below 1k, I get a periodic wave, but it looks more like a heart beat. My codec expects u-law, so that may be the problem with speaker-test. However, the fact the aplay and arecord are not working give me pause. I would be greatly appreciative of any insights, pointers, etc. If there is more information that would be helpful, please ask. Thanks. Paul -- *************************************** Paul David Kavan Project Engineer GRH Electronics, Inc. 402-734-4900 pkavan(a)gmail.com ***************************************

1 3

Re: [alsa-devel] OSS/4Front
by Ash Willis 21 Jun '07

21 Jun '07

Hi Clemens, > You could compare <http://manuals.opensound.com/devlists/Linux.html> > with ALSA's sound card matrix, but the latter tends to be out of date. > Yeah, that thing is oooooold. Hopefully the new wiki on't be too bad. > > With the recent open sourcing of OSS, it would be nice to port code > > to ALSA for devices that are only currently covered by OSS. > > AFAICS all devices supported by the open-source OSS are also supported > by ALSA. > Ah, looks can be deceiving. Although both systems have 'geode' support, it seems that the OSS driver supports the CS5530 VSA2 and the SC1200. Also, there's an open bug for the Neomagic 256 driver, which may have a solution hiding away in OSS somewhere (someone with the hardware is hopefully going to help me look into that). There's a couple of things right off the bat and I don't know ALSA very well at all compared to most of you. And yeah, I know this stuff isn't in great demand, but it'd be nice if people weren't able to say that OSS can do XYZ and ALSA can't. Ash -- Get a Free E-mail Account at Mail.com! Choose From 100+ Personalized Domains Visit http://www.mail.com today

1 0

[alsa-devel] OSS/4Front
by Ash Willis 21 Jun '07

21 Jun '07

Hi, Does anyone know if there's any kind of list showing a comparison of hardware support between ALSA and OSS/4Front? With the recent open sourcing of OSS, it would be nice to port code to ALSA for devices that are only currently covered by OSS. There has to be at least a few devices that we can grab support for, right? It may at least provide us with insight into a few bugfixes. Ash -- Get a Free E-mail Account at Mail.com! Choose From 100+ Personalized Domains Visit http://www.mail.com today

4 3

[alsa-devel] Yamaha Cards
by derek＠darlingsong.net 21 Jun '07

21 Jun '07

Hi all, first post for me. I have a Yamaha DS2416 mixer card and Yamaha SW1000XG sound card that I would like to use onLinux (Fedora 6). I have used them on the "other" OS, along with ProTools, etc. Does anyone know if Linux drivers are available? I have looked around, and it seems not to be the case. any help would bve appreciated. Derekd Vancouver, BC

2 1

[alsa-devel] No time for cs4624
by chris＠idlelion.net 21 Jun '07

21 Jun '07

I really wanted to work on the cs4624 suspend resume bug (#305), but there is no time, especially given the lack of technical information. I'm wondering if I were to lend or give a laptop that exhibits the problem to one of you alsa developers, if that would be useful and provide some impetus to fix the bug, or if it would just be a big pain? Opinions? Chris

1 0

[alsa-devel] [1/2] 2.6.22-rc5: known regressions
by Michal Piotrowski 21 Jun '07

21 Jun '07

Hi all, Here is a list of some known regressions in 2.6.22-rc5. Feel free to add new regressions/remove fixed etc. http://kernelnewbies.org/known_regressions Unclassified Subject : Kernel hang on CMOS_READ References : http://lkml.org/lkml/2007/6/3/138 Submitter : Rodrigo Luiz <troops.of.doom(a)gmail.com> Status : Unknown Subject : Device hang when offlining a CPU due to IRQ misrouting References : http://lkml.org/lkml/2007/5/31/419 Submitter : Darrick J. Wong <djwong(a)us.ibm.com> Handled-By : Siddha, Suresh B <suresh.b.siddha(a)intel.com> Status : problem is being debugged ALSA Subject : snd-aoa causes badness in lib/kref.c:33 References : http://bugzilla.kernel.org/show_bug.cgi?id=8513 Submitter : Ben Collins <bcollins(a)ubuntu.com> Handled-By : Takashi Iwai <tiwai(a)suse.de> Status : Unknown FS Subject : 2.6.22-rc4-git5 reiserfs: null ptr deref. References : http://lkml.org/lkml/2007/6/13/322 Submitter : Randy Dunlap <randy.dunlap(a)oracle.com> Handled-By : Vladimir V. Saveliev <vs(a)namesys.com> Status : problem is being debugged PCI Subject : PCI setup hangs on Asus Notebook (nolapic helps) References : http://lkml.org/lkml/2007/6/14/161 Submitter : Malte Cornils <malte(a)cornils.net> Status : unknown Regards, Michal -- LOG http://www.stardust.webpages.pl/log/

3 5

Re: [alsa-devel] Using aplay and arecord on an ARM
by Paul Kavan 20 Jun '07

20 Jun '07

On 6/20/07, Paul Kavan <pkavan(a)gmail.com> wrote: > > Okay: > > Here is where I ran into troubles yesterday. I am working on configuring > alsa-utils. When I do: > > CC=arm-linux-gcc ./configure --target=arm-linux --with-versioned=no > --prefix=/usr --host=i686-pc-linux-gnu > > I get the error: > > grhuser@pcL7:$ CC=arm-linux-gcc ./configure --target=arm-linux > --with-versioned=no --prefix=/usr --host=i686-pc-linux-gnu > configure: WARNING: If you wanted to set the --build type, don't use > --host. > If a cross compiler is detected then cross compile mode will be used. > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking for i686-pc-linux-gnu-strip... no > checking for strip... strip > checking whether NLS is requested... yes > checking for msgfmt... /usr/bin/msgfmt > checking for gmsgfmt... /usr/bin/msgfmt > checking for xgettext... /usr/bin/xgettext > checking for msgmerge... /usr/bin/msgmerge > checking for style of include used by make... GNU > checking for i686-pc-linux-gnu-gcc... arm-linux-gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... yes > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether arm-linux-gcc accepts -g... yes > checking for arm-linux-gcc option to accept ISO C89... none needed > checking dependency style of arm-linux-gcc... gcc3 > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for ld used by GCC... > /home/grhuser/Linux_Builds/buildroot/build_arm/staging_dir/arm-linux-uclibc/bin/ld > checking if the linker > (/home/grhuser/Linux_Builds/buildroot/build_arm/staging_dir/arm-linux-uclibc/bin/ld) > is GNU ld... yes > checking for shared library run path origin... done > checking for CFPreferencesCopyAppValue... no > checking for CFLocaleCopyCurrent... no > checking for GNU gettext in libc... no > checking for iconv... no, consider installing GNU libiconv > checking for GNU gettext in libintl... no > checking whether to use NLS... no > checking for i686-pc-linux-gnu-gcc... (cached) arm-linux-gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether arm-linux-gcc accepts -g... (cached) yes > checking for arm-linux-gcc option to accept ISO C89... (cached) none > needed > checking dependency style of arm-linux-gcc... (cached) gcc3 > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for ALSA CFLAGS... > checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread > checking for libasound headers version >= 1.0.12... not present. > configure: error: Sufficiently new version of libasound not found. > > I know there has to be a flag or something here I need to set. Does anyone > know what that might be? > > Paul > I think what occurs here is that the configure script is using my cross-compilers and associated libs in $HOME/Linux_Builds/buildroot/build_arm/staging_dir/ while the libs are actually given in $HOME/Linux_Builds/buildroot/build_arm/root/usr/lib/ I am looking at the README and INSTALL and do not see a solution to this. Does anyone have a solution to this? Thanks. Paul

4 11

[alsa-devel] Kernel 2.6.21 M-Audio Delta 1010L
by Suso Comesaña 20 Jun '07

20 Jun '07

Hello... My name is Suso Comesaña...I have 2 computers with a M-Audio card Delta 1010L...the problem is the following one: With kernel 2.6.17-2-multimedia-486... I can record sounds perfectly... but, kernel 2.6.21... I cannot record nothing... You have some idea?... You need that she sends some information to you? Tanks... Suso Comesaña. Peatón. susobaco(a)yahoo.es Usuario de Musix, GNU-Linux, basada en Debian/Knoppix. 100% Software Libre. ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ____________________________________________________________________________________ ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. http://es.answers.yahoo.com/info/welcome

2 1

[alsa-devel] Output levels on SBLive! 5.1 on ALSA vs WIndows
by ChernYue Kwok 20 Jun '07

20 Jun '07

Hello, I am using an SBLive! 5.1 sound card (emu10k1 chipset) with 6 channel output. Due to the nature of my work, I need to be able to play sound through all 6 channels at the same output level to an amplifier. Using Linux and the emu10k1 ALSA driver, I measured output voltage levels on an oscilloscope while playing a sine wave on all 6 channels, and I got three different output voltage amplitudes for the front, rear and center/subwoofer channels. Repeating the same test with the same card on WIndows using the Creative SBLive drivers from their website, I am able to get the same output voltage amplitude on all 6 channels. For both tests, all output levels in the relevant mixers were set to their maximum levels. I would like to know if this output normalizing 'feature' of the SBLive Windows driver can be found in the emu10k1 ALSA driver, or in any other ALSA driver. Failing that, is there any other solution to set output levels in the driver, or am I doomed to twiddle in alsamixer to get the output levels that I want? Thanks in advance.

2 3