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

Re: [alsa-devel] Boot failure with 2.6.21 with snd-maestro3
by Giridhar Pemmasani 02 May '07

02 May '07

--- Adrian Bunk <bunk(a)stusta.de> wrote: > On Sun, Apr 29, 2007 at 09:55:18AM -0700, Giridhar Pemmasani wrote: > > When snd-maestro3 (ESS Maestro 3 driver) is enabled, kernel 2.6.21 fails > to > > boot - it seems to stop at various points depending on what other modules > are > > enabled. Disabling snd-maestro3 fixes all issues. Moreover, with > everything > > else being same, using maestro3.c from 2.6.20 kernel and using it in > 2.6.21 > > kernel also works - i.e., system boots fine. I will try to isolate the > issue > > and follow up. > > There were only the two attached patches between 2.6.20 and 2.6.21 to > this driver: > - maestro3: add request_firmware() > - maestro3 - Use quirk list helper function > > 2.6.21 + 2.6.20 maestro3.c works for you. > > Does 2.6.21 + 2.6.20 maestro3.c + patch-maestro3-1 work? 2.6.21 with 2.6.20's maestro3.c with patch-maestro3-1 exhibited the same issue. However, I identified the cause: maestro3 driver in 2.6.21 (even just patch-maestro3-1) tries to load firmware file from user space. But each time request_firmware is called it takes about 1 minute to timeout (because I don't have the firmware installed?). If I let the system take its time, even with maestro3.c from 2.6.21, it boots after timing out twice. So after about 2 minutes of no activity, system does boot. Following are trace messages I added to identify the issue: [ 17.004000] input: TPPS/2 IBM TrackPoint as /class/input/input5 [ 70.904000] sound/pci/maestro3.c (snd_m3_create:2763): -2 [ 70.920000] sound/pci/maestro3.c (snd_m3_create:2774): -2 [ 130.940000] sound/pci/maestro3.c (snd_m3_create:2777): -2 [ 130.956000] sound/pci/maestro3.c (snd_m3_create:2788): -2 [ 130.972000] sound/pci/maestro3.c (snd_m3_create:2794): 0 [ 130.992000] sound/pci/maestro3.c (snd_m3_create:2797): 0 [ 131.012000] sound/pci/maestro3.c (snd_m3_create:2802): 0 [ 131.044000] sound/pci/maestro3.c (snd_m3_create:2804): 0 [ 131.580000] sound/pci/maestro3.c (snd_m3_create:2807): 0 [ 131.596000] sound/pci/maestro3.c (snd_m3_create:2810): 0 [ 131.612000] sound/pci/maestro3.c (snd_m3_create:2814): 0 [ 131.628000] sound/pci/maestro3.c (snd_m3_create:2821): 0 [ 132.364000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-d evel(a)redhat.com Giri __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[alsa-devel] porter wanted: AMD Geode SCx200 driver OSS to ALSA
by Martin-Éric Racine 02 May '07

02 May '07

Greetings, I work for a company that develops hardware using the AMD Geode chipset. While our current product line is based on the Geode LX model (which is very well supported in ALSA), our legacy products are based on the earlier Geode SC1200 and SC2200, for which no ALSA support exists. However, AMD has OSS driver source code available at: http://www.amd.com/us-en/ConnectivitySolutions/TechnicalResources/0,,50_233… We basically need this ported to an ALSA snd-scx200 module to replace it. (Would now also be a good time to ask for snd-sc5535audio to be renamed snd-sc5535 for consistence with other driver names?) We could provide a sample SC2200-based unit to whoever volunteers for porting AMD's old OSS code to ALSA, Please contact me for details. The resulting code will be directly submitted to the ALSA project for inclusion in the mainstream kernel, to make sure that everyone can benefit from it. Best Regards, -- Martin-Éric Racine http://q-funk.iki.fi

1 1

[alsa-devel] Possible bug in snd_mixer_selem_set_playback_switch_all
by Tim Burrell 30 Apr '07

30 Apr '07

Hi there, I've encountered a situation where if I very quickly, and repeatedly make calls to snd_mixer_selem_set_playback_switch_all I get some strange undefined behavior. The situation is I'm looping over all mixer elements (on all sound cards) to do a system wide mute / unmute. If I make numerous calls to this function it ends up that some mixers only toggle switches on specific channels (right or left), and sometimes the volume on certain (random) channels gets set to some also random (usually 0, but can be anywhere between 0 and max) level. I've been able to remedy the situation by inserting a 10ms delay in between calls to snd_mixer_selem_set_playback_switch_all. Clearly though this is undesirable. I don't have more than one sound card to test on so I can't be sure if it's a problem with all drivers or just mine (hda-intel). I can certainly provide more information if requested, just let me know what I can do. Or if I'm doing something wrong I'd love to be made aware of something I can do to fix this behavior. Thanks, Tim.

1 0

[alsa-devel] List of all Apple Mac's hda-intel pin configurations
by Ivan N. Zlatev 30 Apr '07

30 Apr '07

I have attached all windows drivers' .ini files (taken from latest windows drivers cd of Boot Camp), which include all pin configuration as well as probably some more useful information (GPIO and stuff). I hope this will help you to make a nice update. [Subsystem ID - configuration] 106B0800 - Board1.ini 106B0600 - Board2.ini 106B0700 - Board2.ini 106B0E00 - Board3.ini 106B0F00 - Board3.ini 106B1600 - Board3.ini 106B1700 - Board3.ini 106B0200 - Board3.ini 106B1E00 - Board3.ini 106B0400 - Board4.ini 106B1A00 - Board4.ini 106B0A00 - Board5.ini 106B2200 - Board5.ini 00000100 - Board4.ini Regards. -- Ivan N. Zlatev Web: http://www.i-nZ.net "It's all some kind of whacked out conspiracy."

1 0

Re: [alsa-devel] [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work? [Solved]
by Cody Jung 30 Apr '07

30 Apr '07

On 4/29/07, Rene Herman <rene.herman(a)gmail.com> wrote: > On 04/29/2007 09:31 AM, Rene Herman wrote: > > > I've attached (to try and avoid linewrap) the lines that you will need in > > /etc/modprobe.conf. > > No I haven't. > > Rene. > > alias snd-card-0 snd-cs4231 > alias sound-slot-0 snd-cs4231 > > options snd-cs4231 index=0 port=0x534 irq=5 dma1=1 dma2=0 > > install snd-cs4231 echo activate >/sys/bus/pnp/devices/01\:01.00/resources &&\ > sleep 1 &&\ > /sbin/modprobe --ignore-install snd-cs4231 > > remove snd-cs4231 /sbin/modprobe -r --ignore-remove snd-cs4231 &&\ > echo disable >/sys/bus/pnp/devices/01\:01.00/resources > > Wahoo! Thank you, thank you! I ended up not going the /etc/modules way, partially because it wasn't working and partially because I didn't know what I was doing. Instead I added the following 4 lines to a file and included it in my init scripts. echo activate > /sys/bus/pnp/devices/01\:01.00/resources sleep 1 modprobe snd modprobe snd-cs4231 port=0x534 irq=5 dma1=1 dma2=0 And it works great! Thanks again for putting up with my incompetence. ~Cody Jung

2 1

Re: [alsa-devel] Boot failure with 2.6.21 with snd-maestro3
by Michal Piotrowski 29 Apr '07

29 Apr '07

Hi, On 29/04/07, Giridhar Pemmasani <pgiri(a)yahoo.com> wrote: > When snd-maestro3 (ESS Maestro 3 driver) is enabled, kernel 2.6.21 fails to > boot - it seems to stop at various points depending on what other modules are > enabled. Disabling snd-maestro3 fixes all issues. Moreover, with everything > else being same, using maestro3.c from 2.6.20 kernel and using it in 2.6.21 > kernel also works - i.e., system boots fine. I will try to isolate the issue > and follow up. Please revert this patches http://www.stardust.webpages.pl/files/patches/alsa_revert/ and test kernel after each revert. Takashi, I'll add this to known regressions for -stable team. > > Giri Regards, Michal -- Michal K. K. Piotrowski Kernel Monkeys (http://kernel.wikidot.com/start)

1 0

[alsa-devel] Can't record sound on Aser Aspire 5100. ATI SB450, RelTek ALC 883
by xinyun liu 29 Apr '07

29 Apr '07

hi, I have an Acer Aspire 5100. I can play sound but with the build in mic, I can't record sound. The driver is the latest HG code. http://pastebin.ca/464406 [root@localhost ~]# lspci -nnv -d1002:437b 00:14.2 0403: 1002:437b (rev 01) Subsystem: 1025:009f Flags: bus master, slow devsel, latency 64, IRQ 19 Memory at c0000000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- [root@localhost ~]# dmesg | fgrep ALSA > /tmp/1 [root@localhost ~]# vi /tmp/1 ALSA ~/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:698: codec_mask = 0xb ALSA ~/alsa-driver/pci/hda/hda_codec.c:1820: hda_codec: model 'acer' is selected for config 1025:0 (Acer laptop) ALSA ~/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:698: codec_mask = 0xb ALSA ~/alsa-driver/pci/hda/hda_codec.c:1820: hda_codec: model 'acer' is selected for config 1025:0 (Acer laptop) ALSA ~/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1188: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 ALSA ~/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1188: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x8, stream=0x1, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x8, stream=0x0, channel=0, format=0x0 ALSA ~/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1188: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 ALSA ~/alsa-driver/pci/hda/hda_codec.c:630: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0

1 1

Re: [alsa-devel] [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work?
by Rene Herman 29 Apr '07

29 Apr '07

On 04/29/2007 04:18 AM, Cody Jung wrote: > Er...that appears to be a .diff file. Do I have to do something with it > for it to be workable, or...? Yes. You'd have to apply the patch (as it's called) to a recent kernel source tree, reconfigure the kernel adding this new VIVO driver to your config and then recompile and reinstall that kernel. Oh well, you posting to alsa-user and not alsa-devel should've been a hint. Rest assured the driver would've worked nicely :-/ There is another thing you can do. What was posted was just a wrapper around cs4231-lib in much the same way that the existing snd-cs4231 module is and that module you _will_ already have installed. That one doesn't do anything automatic though, so you will have to know how to manually enable your card first. First, open a root shell and look through the /sys/bus/pnp/devices directory for your VIVO. Under the "xx:yy.zz" sub-directories there you will find "id" files, and one of them will say "ENS1011". Example: # cat /sys/bus/pnp/devices/01\:01.00/id ENS1011 After having found it in there, activate the card: # echo activate >/sys/bus/pnp/devices/01\:01.00/resources and look at what resources were assigned to it by the PnP layer: # cat /sys/bus/pnp/devices/01\:01.00/resources state = active io 0x330-0x33f io 0x530-0x537 io 0x2100-0x213f irq 5 irq 9 dma 1 dma 0 You can now load the snd-cs4231 module specifying those card resources manually: # modprobe snd-cs4231 port=0x534 irq=5 dma1=1 dma2=0 Yes, 0x534. The second io resource + 4. This should've loaded without problem. Start up alsamixer: # alsamixer and up and unmute the PCM volume. With -> and <- you can walk through the sliders; ^ ups the one you're on, and "m" toggles the mute (the "MM" at the bottom should turn to a highlighted "OO"). PCM is the first slider. 90 seems to be an okay value. Quit alsamixer again with Alt-Q and now you should be able to hear things. If you have a plain "wav" file around somewhere, that makes for the quickest test: # aplay foo.wav No, I'm not going to tell you to plug in your speakers. If anything in the above doesn't work as expected, your system is not as expected and there's isn't much I can help with. If everything does work, you can automate it for the next time. I've attached (to try and avoid linewrap) the lines that you will need in /etc/modprobe.conf. Ubuntu has no doubt found a way to make that dark and muddy again so you might need to add it to an /etc/modprobe/whatever file instead. Please ask a fellow ubuntu victim for advice about translating this generic linux advice to your install. Once you do have that all setup, sound should "Just Work". You probably need to adjust the volume as specified above once only after which ubuntu will save it for the next boot, but if you don't hear anything ater rebooting, please check that first. Rene.

1 1

Re: [alsa-devel] [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work?
by Rene Herman 29 Apr '07

29 Apr '07

On 04/28/2007 07:06 AM, Cody Jung wrote: > As it suggests in the subject, I'm both a Linux-newbie and an > ALSA-newbie. I have an old clunker of a machine running Ubuntu Feisty > that I built out of parts left on curbs during spring cleanup, and that's > how I came across my sound card. It's an Ensoniq SoundscapeVivo (Not a > Vivo90, AFAIK). As far as I'm aware, there are no other VIVO's than the VIVO90. > I've gone through install and troubleshooting guides galore, but I can't > seem to get ALSA to recognize my card, and I'm confused and rather tired > of it all. > > Do you think you can help, and if so, what information do you need from > me? I probably can; I have both a Soundscape VIVO90 and a much older Soundscape S-2000. My VIVO90 is an ISA-PnP card and has a Ensoniq MARK5-RO, an OTTOR2C and a Analog Devices AD1845 codec: http://en.wikipedia.org/wiki/Ensoniq_Soundscape_VIVO90 I tested that when I acquired it a while ago and if I remember correctly, it just worked... mmm. come to think of it, it might be the case that I needed to add its PnP ID to the driver. Not sure anymore. Could you confirm whether or not your Soundscape is an ISA-PnP card and if so (that's also a way to find out if you don't know if it is) run "pnpdump" with it installed and look for a PnP-ID for the card in it? Something of the form "ENSxxxx". If your card is one of the older non-PnP soundscapes it's going to be a bit harder; they also need firmware and all that and I haven't tested that card myself yet. (please use the @alsa-project.org list addresses by the way; in the case of alsa-devel, the sourceforge one is gone even). Rene.

3 4

[alsa-devel] Apple iMac pin configs
by Ivan N. Zlatev 28 Apr '07

28 Apr '07

Hello, I have a 20'' iMac machine with a hda-intel (SigmaTel 9221 A1 codec) and I have successfully been using the mac mini pin config, but there is one problem - the microphone doesn't work. The machine has a built-in microphone, built-in speakers, 1 digitial out jack and 1 for headphones. With the mac mini pin config I get 2 mics: "Front Mic" and "Mic" but none of those works. (alsamixer-macmini.gz for info). Today I spent some time on the search for the the correct pin configuration and it should be this [1] according to the windows drivers. This configuration causes amixer.gz, basically 1 "Mic" (which again doesn't record), but also "Mic as Output" and "Line in as output" (I don't have a line in as far as i know). I have also tried the macbook-pro and macbook introduced with 1.0.14rc3, but the mic doesn't work. I have attached * cat /proc/asound/card0/codec#0 * Mac OS X's complete dump of information of the audio driver - imac20-ioreg-audio.gz * amixer with the below config and the one with the macmini pin config Can you possible assist me to get the below pin config in tune, so that everything works? Regards. [1] ========== [HKR\Settings\pin] [HKR\Settings\Pin\0A] CfgDflt = dword: 0x0121E230 Action = hex: 01,0A,81,0C,81,10 [HKR\Settings\Pin\0B] CfgDflt = dword: 0x90A70120 [HKR\Settings\Pin\0C] CfgDflt = dword: 0x9017E110 [HKR\Settings\Pin\0D] CfgDflt = dword: 0x400000FE [HKR\Settings\Pin\0E] CfgDflt = dword: 0x400000FD Action = hex: 01,10,81,0A,81,0C [HKR\Settings\Pin\0F] CfgDflt = dword: 0x0181E02E Action = hex: 09,0F [HKR\Settings\Pin\10] CfgDflt = dword: 0x1145E240 [HKR\Settings\Pin\11] CfgDflt = dword: 0x500000FA [HKR\Settings\Pin\15] CfgDflt = dword: 0x400000FC [HKR\Settings\Pin\1B] CfgDflt = dword: 0x400000FB -- Ivan N. Zlatev Web: http://www.i-nZ.net "It's all some kind of whacked out conspiracy."

1 1