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

[alsa-devel] question on hda_codec.c behavior
by randall 18 Jun '08

18 Jun '08

I've not yet been able to get the Nvidia MCP61 (RealTek ALC662) onboard sound working (EliteGroup Computer Systems) on the Athlon 64 3200+ motherboard. A hwinfo is enclosed: 21: PCI 05.0: 0403 Audio device [Created at pci.301] UDI: /org/freedesktop/Hal/devices/pci_10de_3f0 Unique ID: CvwD.9hpqWdunz16 SysFS ID: /devices/pci0000:00/0000:00:05.0 SysFS BusID: 0000:00:05.0 Hardware Class: sound Model: "Elitegroup MCP61 High Definition Audio" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x03f0 "MCP61 High Definition Audio" SubVendor: pci 0x1019 "Elitegroup Computer Systems" SubDevice: pci 0x2151 Revision: 0xa2 Driver: "HDA Intel" Driver Modules: "snd_hda_intel" Memory Range: 0xfe028000-0xfe02bfff (rw,non-prefetchable) IRQ: 22 (409 events) Module Alias: "pci:v000010DEd000003F0sv00001019sd00002151bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=no, avail=yes, need=no, active=unknown and the pastebin is http://pastebin.ca/1048637 for all the information on the sound setup. YaST2 does the typical sound card editing, and you can hear the speakers click when the card is (de)activated. But no sound is available, even using the speaker-test command or running alsaconf. I've gradually worked my way up from v1.0.14 to the current v1.0.17rl1 but have no success yet in getting the sound modules to work for the Nvidia MCP61 setup. After posting in the install newsgroup one of the persons trying to help me out suggested that I send a note to the developer's group for the following reason, the /var/log/message file contains the following upon booting up > hda_codec: Unknown model for ALC662, trying auto-probe from BIOS... > ALSA sound/pci/hda/hda_codec.c:2333: autoconfig: line_outs=1 > (0x14/0x0/0x0/0x0/0x0) > ALSA sound/pci/hda/hda_codec.c:2337: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) > ALSA sound/pci/hda/hda_codec.c:2341: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) > ALSA sound/pci/hda/hda_codec.c:2349: inputs: mic=0x18, fmic=0x19, > line=0x1a, fline=0x0, cd=0x0, aux=0x0 > hda_codec: num_steps = 0 for NID=0xc And the thought was that "Unknown model" should not be occurring. The /etc/modprobe.d/sound file has one of the allowed models for this codec. Any ideas? Does hda_codec.c need a patch? Randall

1 0

Re: [alsa-devel] Listing raw midi devices "The Right Way"?
by Clemens Ladisch 18 Jun '08

18 Jun '08

Jacob Ole Juul Kolding wrote: > I already found a code example that reads raw midi packages form a > specified device but I need to have a complete list of ALL raw midi > capable devices and ports on the system. > > What is the "Right Way" for an app to build such a list? See the source code of amidi. You probably should be using the sequencer instead of the raw MIDI interface, in which case look at the source code of arecordmidi. HTH Clemens

2 2

[alsa-devel] Listing raw midi devices "The Right Way"?
by Jacob Ole Juul Kolding 18 Jun '08

18 Jun '08

Hello all I'm working on an app that used to run on Linux but then moved to OS X and gained MIDI capabilities. Now it's moving back to Linux so I need to be able to read midi events from devices. I already found a code example that reads raw midi packages form a specified device but I need to have a complete list of ALL raw midi capable devices and ports on the system. What is the "Right Way" for an app to build such a list? Sincerely Jacob Kolding Juvul Tech

1 0

[alsa-devel] [PATCH] ASoC: fix PM=n build
by Mark Brown 17 Jun '08

17 Jun '08

From: Randy Dunlap <randy.dunlap(a)oracle.com> Fix sound/soc build failure when CONFIG_PM=n: linux-next-20080617/sound/soc/soc-core.c:829: error: 'soc_resume_deferred' undeclared (first use in this function) soc3.out:make[3]: *** [sound/soc/soc-core.o] Error 1 Signed-off-by: Randy Dunlap <randy.dunlap(a)oracle.com> Signed-off-by: Mark Brown <broonie(a)opensource.wolfsonmicro.com> --- sound/soc/soc-core.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c index b931039..bdbbc6a 100644 --- a/sound/soc/soc-core.c +++ b/sound/soc/soc-core.c @@ -825,8 +825,10 @@ static int soc_probe(struct platform_device *pdev) /* DAPM stream work */ INIT_DELAYED_WORK(&socdev->delayed_work, close_delayed_work); +#ifdef CONFIG_PM /* deferred resume work */ INIT_WORK(&socdev->deferred_resume_work, soc_resume_deferred); +#endif return 0; -- 1.5.2.5

1 0

[alsa-devel] hda-intel on Asus M2N-X Plus NVIDIA GeForce 6100/nForce 430 mobo
by Nigel Henry 17 Jun '08

17 Jun '08

I've just built a new machine, and expected problems with the onboard soundcard, and also have problems with the onboard NIC, but that's another problem, which is resolved by installing my last remaining realtek 8139 PCI card. Anyway the mobo is an Asus M2N-X Plus NVIDIA GeForce 6100/nForce 430, and the Southbridge (which appears to handle allsorts of stuff) is MCP61. the specs for the soundcard from the Asus site are below. ALC662 6-Channel High Definition Audio Azalia CODEC Support Jack-Sensing, Enumeration, Multi-streaming S/PDIF out on back I/O port This is using the Fedora 8 distro, which has alsa driver 1.0.15, and is probably a bit old. The card is not detected at bootup, but I did a modprobe snd-hda-intel, using various model options. the modules were loaded, but a cat /proc/asound/cards showed "no soundcards detected" I don't want to waste too much time on this onboard card, and will probably buy a cheap well supported card, just to get some sounds on this new machine. All the same I've run the alsa-info.sh script, and the link is below. http://pastebin.ca/1048647 Any comments, as always welcome. Btw: My other machines use Audigy2 soundblaster (emu10k1) on the first machine, and Ensoniq (ens1371) on the other machine, and no problems with these cards at all. I cannot repeat my opinions/thoughts about hda-intel cards. Thanks for all your work you folks. Nigel.

2 4

[alsa-devel] Thoughts on ASOC v2 driver architecture
by Jon Smirl 17 Jun '08

17 Jun '08

I'm trying to sort out an architecture that will let all of the code used in my ASOC drivers to be automatically loaded by the kernel. So if I'm confused and have some of this wrong please explain where I've gone astray. First, what are the physical hardware devices present? From the device tree it says I have two i2s controllers each with an i2c controlled codec. It also says I have a system wide DMA controller. And finally there is the "fabric" which represent the specific pcb (populated jacks, etc) used by the system (the root of the device tree). Upon booting the kernel it will find the five open firmware devices (two i2s, two codecs, one DMA) and load the appropriate of drivers for them. Note that this is the system wide DMA driver, not the ASOC one. Three drivers will be loaded and five devices will be created. The codec devices will each register one codec and multiple codec DAIs. Each i2c channel will register a platform_dai. The next part, the platform device, is where I'm having trouble. Why is the DMA subsystem in it's own ASOC device? I already have a separate system wide device for my DMA hardware. Looking at the implementations of a couple of the ASOC DMA drivers, there is nothing global about the driver, everything is done with per channel instances. Should the DMA code instead simply be a library that is linked to by the i2s drivers? And then move the entry points registered by the DMA driver up into the platform_dai? It seems to me like implementation of the DMA code should be a private matter for the platform_dai/i2s driver. Note that I'm not saying that there shouldn't be modularized ASOC DMA code, instead, why should ASOC be aware of this shared code? To see if this model would work I tried to visualize a system where one i2s controller is using DMA and the second is doing programmed IO. So if the DMA API is pushed into the platform_dai that would free up the platform device. It could then be used to support the fabric code (fabric is the motherboard specific bits of code). It should probably be renamed to the machine device instead of platform device. To handle the case of HDA not needing a fabric driver, ASOC would have a default internal machine driver that a fabric driver could override. This also implies that the fabric driver can't be the last driver registered with ASOC. There would be one global fabric driver, but it would get called on a per instance basis. You could implement (made up scenarios) two amps on the motherboard and only enough power to turn one of them on. Or maybe a front panel switch that switches which channel the front panel controls act on. I'd end up with this object model generic machine (optional machine specific fabric override) platform i2s (platform_dai, soc_snd_card) generic codec (choice of codec dai) platform i2s (platform_dai, soc_snd_card) generic codec (choice of codec dai) The platform specific i2s drivers are linked to a shared library of platform DMA code. -- Jon Smirl jonsmirl(a)gmail.com

4 22

[alsa-devel] git-http interface to ALSA git repositories?
by Timur Tabi 17 Jun '08

17 Jun '08

My company's firewall blocks the git protocol, so I need to use http:// to clone git repositories. What is the http path for the ALSA git repository? -- Timur Tabi Linux kernel developer at Freescale

3 2

[alsa-devel] Mute sound
by Jorge Peixoto de Morais Neto 17 Jun '08

17 Jun '08

Hi. Under kernel 2.6.23, I could get sound from the alsa device created by the module snd_bt87x. In kernel 2.6.24, there is no sound. Also, in kernel 2.6.23 the device would only appear if I modprobed the module with the option load_all=1. In kernel 2.6.24, the option load_all=1 is unnecessary for the device to appear. This is probably because I have in 2007 sent an email to this list with information about my board (it was responded by Takashi). If you need any addition other than what I provide below, ask at any time. jorge@jorge ~ $ uname -a Linux jorge 2.6.24-gentoo-r8d #4 Mon Jun 16 17:58:17 BRT 2008 i686 AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux jorge@jorge ~ $ sudo lspci -v 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge Subsystem: VIA Technologies, Inc. Unknown device 0000 Flags: bus master, 66MHz, medium devsel, latency 8 Memory at e0000000 (32-bit, prefetchable) [size=128M] Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: dde00000-dfefffff Prefetchable memory behind bridge: cdc00000-ddcfffff Capabilities: [80] Power Management version 2 00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at ec00 [size=256] Memory at dfffff00 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Kernel driver in use: 8139too 00:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) Subsystem: PROLINK Microsystems Corp Unknown device 4011 Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at dddfe000 (32-bit, prefetchable) [size=4K] Capabilities: [44] Vital Product Data <?> Capabilities: [4c] Power Management version 2 Kernel driver in use: bttv Kernel modules: bttv 00:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) Subsystem: PROLINK Microsystems Corp Unknown device 4011 Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at dddff000 (32-bit, prefetchable) [size=4K] Capabilities: [44] Vital Product Data <?> Capabilities: [4c] Power Management version 2 Kernel driver in use: Bt87x Kernel modules: snd-bt87x 00:0c.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: Micro-Star International Co., Ltd. Unknown device 5900 Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e800 [size=256] Capabilities: [c0] Power Management version 2 Kernel driver in use: C-Media PCI Kernel modules: snd-cmipci 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at dc00 [size=32] Capabilities: [80] Power Management version 2 Kernel driver in use: uhci_hcd 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e000 [size=32] Capabilities: [80] Power Management version 2 Kernel driver in use: uhci_hcd 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at e400 [size=32] Capabilities: [80] Power Management version 2 Kernel driver in use: uhci_hcd 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at dffffe00 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2 Kernel driver in use: ehci_hcd 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge Subsystem: VIA Technologies, Inc. Unknown device 0000 Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE Flags: bus master, medium devsel, latency 32, IRQ 255 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1] [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1] I/O ports at fc00 [size=16] Capabilities: [c0] Power Management version 2 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3) (prog-if 00 [VGA controller]) Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11 Memory at de000000 (32-bit, non-prefetchable) [size=16M] Memory at d0000000 (32-bit, prefetchable) [size=128M] Memory at ddc80000 (32-bit, prefetchable) [size=512K] Expansion ROM at dfee0000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 2.0 jorge@jorge ~ $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2600+ stepping : 1 cpu MHz : 2133.528 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow ts bogomips : 4271.41 clflush size : 32 jorge@jorge /proc/asound $ ls Bt878 card0 card1 cards CMI8738 devices hwdep oss pcm timers version jorge@jorge /proc/asound $ cat cards 0 [CMI8738 ]: CMI8738-MC6 - C-Media CMI8738 C-Media CMI8738 (model 55) at 0xe800, irq 11 1 [Bt878 ]: Bt87x - Brooktree Bt878 Brooktree Bt878 at 0xdddff000, irq 5 jorge@jorge /proc/asound $ cat devices 0: [ 0] : control 4: [ 0- 0]: hardware dependent 8: [ 0- 0]: raw midi 16: [ 0- 0]: digital audio playback 17: [ 0- 1]: digital audio playback 18: [ 0- 2]: digital audio playback 24: [ 0- 0]: digital audio capture 26: [ 0- 2]: digital audio capture 32: [ 1] : control 33: : timer 56: [ 1- 0]: digital audio capture 57: [ 1- 1]: digital audio capture jorge@jorge /proc/asound $ cat hwdep 00-00: OPL3 FM jorge@jorge /proc/asound $ cat pcm 00-02: CMI8738-MC6 : C-Media PCI IEC958 : playback 1 : capture 1 00-01: CMI8738-MC6 : C-Media PCI 2nd DAC : playback 1 00-00: CMI8738-MC6 : C-Media PCI DAC/ADC : playback 1 : capture 1 01-01: Bt87x Analog : Bt87x Analog : capture 1 01-00: Bt87x Digital : Bt87x Digital : capture 1 jorge@jorge /proc/asound $ cat version Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC). -- Software is like sex: it is better when it is free - Linus Torvalds

1 1

Re: [alsa-devel] Problem regarding CA0106
by Travis Place 16 Jun '08

16 Jun '08

On Mon, 2008-06-16 at 18:00 +0200, Takashi Iwai wrote: > At Tue, 17 Jun 2008 01:52:08 +1000, > Travis Place wrote: > > > > On Mon, 2008-06-16 at 12:38 +0200, Takashi Iwai wrote: > > > At Sat, 14 Jun 2008 03:18:33 +1000, > > > Travis Place wrote: > > > > > > > > Just been speaking with a guy in #alsa about the problems with his "MSI > > > > K8N Diamond MB" which has an onboard "SB Live 24bit" or "Audigy". > > > > > > > > While looking through ca0106_main.c in GIT, i saw the following section: > > > > > > > > /* MSI K8N Diamond Motherboard with onboard SB Live 24bit without AC97 > > > > */ > > > > /* SB0438 > > > > * CTRL:CA0106-DAT > > > > * ADC: WM8775SEDS > > > > * DAC: CS4382-KQZ > > > > */ > > > > { .serial = 0x10091462, > > > > .name = "MSI K8N Diamond MB [SB0438]", > > > > .gpio_type = 2, > > > > .i2c_adc = 1 } , > > > > > > > > For this guys sound to work, we had to change the serial line to: > > > > > > > > { .serial = 0x10091102, > > > > > > Does it mean that this number 1009:1102 is missing, or a wrong > > > 1009:1462 entry matches with his hardware? > > > > > Well, it appears to me (due to another report filed previously) that > > the motherboard is a 'newer revision' and has a different ID for the > > soundcard. > > Hm, so you didn't receive alsa-info.sh or "lspci -nv" output? > Of course I got alsa-info.sh output :) (asks himself why he didnt include it though) http://pastebin.ca/1048644 > > > In the former case, it happens often. We just need to add a new entry > > > for the newer model. In the latter case, it's odd. > > > > > > > I think that adding the new ID to the driver wont cause any immediate > > problems. The old value (1009:1462) should remain, until we can confirm > > it against another K8N Diamond motherboard (although im not sure how > > common these boards are). > > Yeah, I guess so, too. But just to be sure... > Well, we'll just have to see what happens, I guess. For the record, in both older ALSA versions, and 1.0.16, changing only the serial seems to be sufficient. So adding another serial should be an easy fix. Thanks, Travis > > Takashi

1 0

[alsa-devel] [Fwd: Re: Problem regarding CA0106]
by Travis Place 16 Jun '08

16 Jun '08

1 0