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

[alsa-devel] [HDA Intel/STAC92xx] Alsa 1.0.14: error in stac92xx_auto_fill_dac_nid
by Jan de Mooij 02 Jul '07

02 Jul '07

I have a strange problem with alsa on Ubuntu Gutsy. If I compile and install the Alsa 1.0.14 driver, my sound card is not detected, and sound doesn't work. I also get the following message in dmesg: [ 33.360190] stac92xx_auto_fill_dac_nids: No available DAC for pin 0x15 So the problem seems to be in the stac92xx_auto_fill_dac_nids function. When I copy that function from alsa 1.0.13 into the 1.0.14 source, everything works okay... It looks like the function is rewritten for version 1.0.14, but for me it does not work anymore. I have to do the above steps with each new kernel update in Ubuntu Gutsy... Therefore I would like to fix it, but I don't know where to start. Thanks in advance. Jan

2 6

[alsa-devel] Acer Aspire 9810 hda-intel RealTek ALC883 no sound thru speakers only via SPDIF/Headphones.
by Adrian Grassi 02 Jul '07

02 Jul '07

Hi guys, I have a Acer Aspire 9810 with hda-intel realtek ALC883 chipset and no matter what version of alsa and ditribution I try I only get sound thru the shared SPDIF/Headphone Jack. This laptop has a built in 2.1 power speaker system which works fine under windows but not in any linux distro's I have tried: Ubuntu 7.04 - Kubuntu 7.04 - Suse 10.2 - Ubuntu Gutsy 7.10 Beta - Mandriva Spring 2007.1 I think this is a configuration issue however I can't find any info anywhere on how to fix it, I did find a few posts where several people are having the same issue. Can someone please shed some light on how to fix this issue, if any additional information is needed please let me know, I have been trying to solve this for over 5 days now and is driving me bananas. Here is the aadebug from alsa-wiki: Debug INFO ALSA Audio Debug v0.1.0 - Sat Jun 30 02:01:40 EDT 2007 http://alsa.opensrc.org/aadebug http://www.gnu.org/licenses/gpl.txt Kernel ---------------------------------------------------- Linux XTTG-Mob1 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux Loaded Modules -------------------------------------------- snd_hda_intel 256024 1 snd_pcm_oss 44672 0 snd_mixer_oss 17664 1 snd_pcm_oss snd_pcm 80388 3 snd_hda_intel,saa7134_alsa,snd_pcm_oss snd_seq_dummy 4740 0 snd_seq_oss 33152 0 snd_seq_midi 9600 0 snd_rawmidi 25728 1 snd_seq_midi snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi snd_seq 53232 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 24324 2 snd_pcm,snd_seq snd_seq_device 9228 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 54660 12 snd_hda_intel,saa7134_alsa,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device snd_page_alloc 10888 2 snd_hda_intel,snd_pcm Modprobe Conf --------------------------------------------- Warning: module config file does not exist This means any kernel modules will not be auto loaded See your linux distro docs on how to create this file Proc Asound ----------------------------------------------- Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xd2300000 irq 23 1 [SAA7134 ]: SAA7134 - SAA7134 saa7133[0] at 0xd2005000 irq 16 2: : timer 3: : sequencer 4: [ 1- 0]: digital audio capture 5: [ 1] : control 6: [ 0- 2]: digital audio capture 7: [ 0- 0]: digital audio playback 8: [ 0- 0]: digital audio capture 9: [ 0] : control cat: /proc/asound/hwdep: No such file or directory 01-00: SAA7134 PCM : SAA7134 PCM : capture 1 00-02: ALC883 Analog : ALC883 Analog : capture 2 00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 2 Client info cur clients : 3 peak clients : 3 max clients : 192 Client 0 : "System" [Kernel] Port 0 : "Timer" (Rwe-) Port 1 : "Announce" (R-e-) Connecting To: 15:0 Client 14 : "Midi Through" [Kernel] Port 0 : "Midi Through Port-0" (RWe-) Client 15 : "OSS sequencer" [Kernel] Port 0 : "Receiver" (-we-) Connected From: 0:1 Dev Snd --------------------------------------------------- controlC0 controlC1 pcmC0D0c pcmC0D0p pcmC0D2c pcmC1D0c seq timer CPU ------------------------------------------------------- model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz cpu MHz : 2000.000 model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz cpu MHz : 2000.000 RAM ------------------------------------------------------- MemTotal: 2074528 kB SwapTotal: 1951888 kB Hardware -------------------------------------------------- 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 09:04.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) 09:06.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)

4 3

[alsa-devel] High-pitched noise on output from cmi9739 (snd_intel8x0)
by j t 02 Jul '07

02 Jul '07

Hi all. I have a cmi9739 (sis7012) built into an asus k7s8x motherboard which produces a quiet but noticeable noise on top of the regular output (the noise only occurs during playback). I logged a bug to alsa's bugtrack: (https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2288) about a year ago, but unfortunately I still have the problem with alsa release 1.0.14 To try to find out what's going on, I tried using seven (7) different drivers for this soundcard (both Linux and Windows XP) to find out when the problem occurs. Here's the results: a) Alsa (snd_intel8x0) version 1.0.14 under Ubuntu 7.10 alpha 2. Problem EXISTS. b) OSS 4Front Opensound v4.1 (v4.1test0-070624). Problem EXISTS c) CMedia Linux OSS driver cmaudio-070 (from http://www.cmedia.com.tw). Problem EXISTS. d) Windows XP "built-in" driver for SiS 7012 version 5.10.0.6120. Problem EXISTS. e) Windows XP drivers from Asus website for SiS 7012 version 5.12.1.38. Problem DOES NOT EXIST. f) Windows XP drivers from CMedia website (http://www.cmedia.com.tw) version 5.12.1.39. Problem DOES NOT EXIST. g) Windows XP drivers from CMedia forum (http://www.cmedia.com.tw/forums) version 5.12.1.51. Problem DOES NOT EXIST. Given that the problem does not happen with three out of the seven drivers, I assume it's a driver problem. Is there anything that I can do debug this further? Thank you.

2 1

[alsa-devel] SALSA-Lib versus C++
by J. Scott Merritt 02 Jul '07

02 Jul '07

Dear List, It -appears- to me that the source file headers generated by SALSA-Lib-0.0.5 (for example SALSA:asoundlib.h) are not generally usable from within a C++ program compiled with g++. The first problem that I encountered was a failure in IOC_TYPECHECK from asm-generic/ioctl.h. After much searching, I concluded that this is a component of continuing struggles related to "sanitized linux-kernel-headers". Some of the Debian folks have supplied patches to disable this particular check when the ioctl.h file is included from userland, but these patched headers are not present in my cross-compile environment. This behavior apparently is not a problem with gcc or g++ < 2.3.3 - but shows up in later versions of g++. ... a real mess as best I can tell ... The next problem is that when warnings are enabled, g++ complains vigorously about void pointers that are implicitly cast to typed pointers through-out all of the SALSA-Lib supplied header files. Perhaps SALSA-Lib was never intended from usable from C++ programs - and indeed it could argued that its intended application (embedded systems) should avoid the use of C++. If this is the case, perhaps a mention of this restriction might be appropriate on the SALSA-Lib Website and/or in its README file ? Thanks again for all of your help in trying to get this working. Best regards, Scott.

2 2

[alsa-devel] NVidia AC97 / CK804: arecord hangs in system call poll()
by Rainer Menzner 02 Jul '07

02 Jul '07

Hi, my soundcard is an onboard AC97 CK804 NVidia. I use snd-intel8x0 module. Everything works fine except recording sound. When calling arecord -f cd buffer.wav the program infinitely hangs, and an strace shows that it is a poll() call that does not return. After interrupting, a wave file of 44 bytes which is the header only is left. My setup is Kernel 2.6.21.3, all ALSA-software is updated to the latest version, that is 1.0.14(a). In a previous setup with an older ALSA version and kernel 2.6.16.11 recording did work with the same hardware. Now that I updated all ALSA software, even with that older kernel version the same recording problem came up. From that I concluded that it is somehow related to the ALSA-lib version. I have tried to downgrade ALSA-lib down to 1.0.0 to no avail. I have also made tests appropriate if this would be an interrupt problem (using pci=noroute et al) which also did not solve the problem. I have scrolled though the archives of alsa-user and there have been a few posts regarding the same problem (but with other chip sets). However, in those threads no definitive solution of the problem has been discussed. So I tried it again in alsa-user but did not get any feedback ... Now, I finally try this developer list. Your comments and help are much appreciated. Let me know if you need further info. I'm not a Linux system programmer or specialist, but I would be willing to do some debugging if somebody explains what to check. Thanks for any support, -Rainer

2 2

[alsa-devel] hda-Intel Realtek ALC883 chipset support
by Adriano Grassi 30 Jun '07

30 Jun '07

Hi guys I have sound on different linux distro's however only the spdif/headphone share output, no sound from the internal speakers I have been trying to get this work for the last 5 days no success. So i was wondering if the support for this chipset is in place. I even tried the lastest candidate release alsa files 14rc4 with no luck, this is a high definition audio card with multiple outputs analog and digital and i have tried everything i can think of with no success, I tried multiple distro's with the same result, I don't this it is a driver issue is probably more like a configuration issue. Can anyone help me figure this one out. Thanks. 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xd2300000 irq 98 2: : timer 3: [ 0- 2]: digital audio playback 4: [ 0- 1]: digital audio capture 5: [ 0- 0]: digital audio playback 6: [ 0- 0]: digital audio capture 7: [ 0] : control 8: : sequencer cat: /proc/asound/Intel: Is a directory 0 snd_hda_intel cat: /proc/asound/oss: Is a directory 00-02: ALC883 Digital : ALC883 Digital : playback 1 00-01: ALC883 Analog : ALC883 Analog : capture 2 00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 2 cat: /proc/asound/seq: Is a directory G0: system timer : 4000.000us (10000000 ticks) P0-0-0: PCM playback 0-0-0 : SLAVE P0-0-1: PCM capture 0-0-1 : SLAVE P0-0-3: PCM capture 0-0-3 : SLAVE P0-1-1: PCM capture 0-1-1 : SLAVE P0-1-3: PCM capture 0-1-3 : SLAVE P0-2-0: PCM playback 0-2-0 : SLAVE Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).

1 0

[alsa-devel] Digigram VX source code
by Colin Stewart Campbell 30 Jun '07

30 Jun '07

About 5 years ago Digigram released their VX soundcard source for OSX through the alsa project. Is there somewhere I can still get a hold of it? I have in mind a legacy card coreaudio driver for Intel macs. Colin

2 1

[alsa-devel] helping debugging
by Thierry Vignaud 30 Jun '07

30 Jun '07

Hi Here's a suggestion from Dave Airlie: http://airlied.livejournal.com/46087.html "If you are going to have lots of unsigned int sized free running pointers called things like hw_ptr or hw.ptr or anything, for debugging it would be really cool if you started those counters at INT_MAX-100000 or something instead of at zero, 24 hours waiting for a bug to trip in the pcm rate conversion is not fun and I'm guessing it'll be some stupid interger overflow or dumb boundary condition hitting..."

2 1

Re: [alsa-devel] Fwd: Problems with hda_intel, Santa Rosa, and suspend
by albox＠free.fr 30 Jun '07

30 Jun '07

Could this issue be related to the other one with Medion laptops : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3160 Takashi, you said you were going to check the older patch that was working on ALSA 1.0.13, did you have a chance to do that ? Takashi Iwai wrote: > At Mon, 25 Jun 2007 15:16:41 -0500, > Matt Mullins wrote: >> On 6/25/07, Takashi Iwai <tiwai(a)suse.de> wrote: >>>> Yes, single_cmd mode is used always. >>> That's bad. >> I believe we have established that. What can I do about it? *Can* I >> do anything about it? What functions should I start debugging? Has >> this happened with other codecs before? What documentation will I >> need or want other than the Intel HDA and STAC9205 specifications? > > Similar problems have been seen in some laptops, too. I vaguely > remember that they need some ACPI-related boot options to fix it > somehow. I think it's likely irrelevant with the codec chip, but > rather a problem of the controller side. > >> I'm definitely willing to help work on this, as not many people have >> this hardware. I'm just new to the sound system, so I'm still trying >> to figure out what-calls-what. > > > Takashi > _______________________________________________ > Alsa-devel mailing list > Alsa-devel(a)alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > >

2 1

Re: [alsa-devel] Creative Soundblaster X-Fi
by Ash Willis 30 Jun '07

30 Jun '07

Hi all, Sorry for straying a little off topic, but talk of these couple of chips got me thinking about unsupported hardware in general. Does anyone know the legal implications of reverse engineering with regards to producing new drivers? I myself wouldn't mind reversing a certain chip or two but I'm not too aware of the legality of it all, particularly in the case where the vendor is hostile or unwilling to release chip information. In general, is it legally acceptable to reverse engineer for the purposes of interoperability? Are vendors likely to make a noise if their hardware gains support under Linux without or against their consent? or is it more a matter of protecting the original product specification than hiding details of the product's interface? Takashi, may I ask your thoughts on this? What's your position on accepting reverse engineered code? (Let's assume that the driver works as well as one written in a more correct manner ;)) I'm fully aware that uncooperative vendors don't deserve to have their hardware supported, but I think that Linux users and Linux itself deserves the support. Ash -- We've Got Your Name at http://www.mail.com! Get a FREE E-mail Account Today - Choose From 100+ Domains

3 2