[alsa-devel] SB0880 X-Fi Titanium Fatal1ty Pro (with codecgraph)
Good evening,
Just wanted to share that this card seems to be HD-Audio compatible (by virtue of its UAA compatibility claim); http://uk.europe.creative.com/products/product.asp?category=1&subcategor...
For a while now, I've been trying to write a skeleton patch_creative.c to hook up some basic playback functions. As this has failed, I will instead post all information I can gather about the card, in the hope that such a basic patch_creative.c can be written that I can then slowly extend. I was unable to set up proper PCM paths (and thus listen to any audio at all), but did manage to get the card detected with a simple addition to hda_intel.c: + /* Creative Labs UAA-compatible */ + { PCI_DEVICE(0x1102, 0x000b), .driver_data = AZX_DRIVER_CREATIVE },
A guess at correct mixer controls would be: HDA_CODEC_VOLUME("PCM Playback Volume", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("PCM Playback Switch", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("Surround Playback Volume", 0x03, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("Surround Playback Switch", 0x03, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_MONO("Center Playback Volume", 0x04, 1, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_MONO("Center Playback Switch", 0x04, 1, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_MONO("LFE Playback Volume", 0x04, 2, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_MONO("LFE Playback Switch", 0x04, 2, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("Side Playback Volume", 0x05, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("Side Playback Switch", 0x05, 0x0, HDA_OUTPUT),
Please find attached the codec details and the resulting codec graph.
It is a PCI-Express card, lspci information follows: 83:00.0 Audio device [0403]: Creative Labs Device [1102:000b] (rev 03) Subsystem: Creative Labs Device [1102:0043] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 505 Region 0: Memory at d0100000 (64-bit, non-prefetchable) [size=64K] Region 2: Memory at d0200000 (64-bit, non-prefetchable) [size=2M] Region 4: Memory at d4000000 (64-bit, non-prefetchable) [size=64M] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000feeff00c Data: 41c9 Capabilities: [58] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Suprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [100] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff Capabilities: [300] Advanced Error Reporting <?> Kernel driver in use: HDA Intel
Regards, Tony V.
At Sun, 13 Jul 2008 22:51:42 +0100, Tony "Chainsaw" Vroon wrote:
Good evening,
Just wanted to share that this card seems to be HD-Audio compatible (by virtue of its UAA compatibility claim); http://uk.europe.creative.com/products/product.asp?category=1&subcategor...
For a while now, I've been trying to write a skeleton patch_creative.c to hook up some basic playback functions. As this has failed, I will instead post all information I can gather about the card, in the hope that such a basic patch_creative.c can be written that I can then slowly extend. I was unable to set up proper PCM paths (and thus listen to any audio at all), but did manage to get the card detected with a simple addition to hda_intel.c:
/* Creative Labs UAA-compatible */{ PCI_DEVICE(0x1102, 0x000b), .driver_data =AZX_DRIVER_CREATIVE },
A guess at correct mixer controls would be: HDA_CODEC_VOLUME("PCM Playback Volume", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("PCM Playback Switch", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("Surround Playback Volume", 0x03, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("Surround Playback Switch", 0x03, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_MONO("Center Playback Volume", 0x04, 1, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_MONO("Center Playback Switch", 0x04, 1, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_MONO("LFE Playback Volume", 0x04, 2, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_MONO("LFE Playback Switch", 0x04, 2, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("Side Playback Volume", 0x05, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("Side Playback Switch", 0x05, 0x0, HDA_OUTPUT),
Please find attached the codec details and the resulting codec graph.
Thanks for reporting. I've had already a test patch on my unstable tree, but it's pending just because of lack of testing with the real hardware.
Could you try the git tree git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git ?
If an external ALSA-driver tarball is preferred, get alsa-driver-unstable from the below: http://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/
thanks,
Takashi
Does this hack only work with the X-Fi Titanium Fatal1ty Pro, or does it include support for all X-Fi based cards from Creative Labs? I have got a Creative X-Fi Extreme Music, that gets infact recognized by my system but modprobing the patched source (modprobe snd-hda-intel, i hope this is the right one) does not work. Here the lspci if this helps:
-- beomuex
Takashi Iwai wrote:
At Sun, 13 Jul 2008 22:51:42 +0100, Tony "Chainsaw" Vroon wrote:
Good evening,
Just wanted to share that this card seems to be HD-Audio compatible (by virtue of its UAA compatibility claim); http://uk.europe.creative.com/products/product.asp?category=1&subcategor...
For a while now, I've been trying to write a skeleton patch_creative.c to hook up some basic playback functions. As this has failed, I will instead post all information I can gather about the card, in the hope that such a basic patch_creative.c can be written that I can then slowly extend. I was unable to set up proper PCM paths (and thus listen to any audio at all), but did manage to get the card detected with a simple addition to hda_intel.c:
/* Creative Labs UAA-compatible */{ PCI_DEVICE(0x1102, 0x000b), .driver_data =AZX_DRIVER_CREATIVE },
A guess at correct mixer controls would be: HDA_CODEC_VOLUME("PCM Playback Volume", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("PCM Playback Switch", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("Surround Playback Volume", 0x03, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("Surround Playback Switch", 0x03, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_MONO("Center Playback Volume", 0x04, 1, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_MONO("Center Playback Switch", 0x04, 1, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_MONO("LFE Playback Volume", 0x04, 2, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_MONO("LFE Playback Switch", 0x04, 2, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("Side Playback Volume", 0x05, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE("Side Playback Switch", 0x05, 0x0, HDA_OUTPUT),
Please find attached the codec details and the resulting codec graph.
Thanks for reporting. I've had already a test patch on my unstable tree, but it's pending just because of lack of testing with the real hardware.
Could you try the git tree git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git ?
If an external ALSA-driver tarball is preferred, get alsa-driver-unstable from the below: http://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/
thanks,
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
At Mon, 14 Jul 2008 15:23:16 +0200, Maximilian Güntner wrote:
Does this hack only work with the X-Fi Titanium Fatal1ty Pro, or does it include support for all X-Fi based cards from Creative Labs?
It's only for X-Fi with HD-audio compatibility. It's not for native Emu20k stuff.
I have got a Creative X-Fi Extreme Music, that gets infact recognized by my system but modprobing the patched source (modprobe snd-hda-intel, i hope this is the right one) does not work. Here the lspci if this helps:
Check "lspci -n". So far, 1102:0009 and 1102:000b are known to be HD-audio compatible.
Takashi
Takashi Iwai wrote:
Does this hack only work with the X-Fi Titanium Fatal1ty Pro, or does it include support for all X-Fi based cards from Creative Labs?
It's only for X-Fi with HD-audio compatibility. It's not for native Emu20k stuff.
HD-audio means what exactly? How can i see whether a card has this feature or not? The cards you mentioned have all 64 MB X-RAM, mine has only 2 MB. Is this a indication of missing HD-Audio support ?
I have got a Creative X-Fi Extreme Music, that gets infact recognized by my system but modprobing the patched source (modprobe snd-hda-intel, i hope this is the right one) does not work. Here the lspci if this helps:
Check "lspci -n". So far, 1102:0009 and 1102:000b are known to be HD-audio compatible.
This is lspci -nn 01:02.0 Multimedia audio controller [0401]: Creative Labs SB X-Fi [1102:0005]
-- beomuex
At Mon, 14 Jul 2008 15:59:53 +0200, Maximilian Güntner wrote:
Takashi Iwai wrote:
Does this hack only work with the X-Fi Titanium Fatal1ty Pro, or does it include support for all X-Fi based cards from Creative Labs?
It's only for X-Fi with HD-audio compatibility. It's not for native Emu20k stuff.
HD-audio means what exactly?
It means that the board has a compatible mode with Intel HD-audio hardwares, which are seen on most of new PCs as on-board sounds. In this mode, you have no emu20k-specific DSP functionalities but acts just as a dumb playback/capture device.
How can i see whether a card has this feature or not?
Try the driver with your PCI ID, and check whether it works.
The cards you mentioned have all 64 MB X-RAM, mine has only 2 MB. Is this a indication of missing HD-Audio support ?
It's irrelevant.
I have got a Creative X-Fi Extreme Music, that gets infact recognized by my system but modprobing the patched source (modprobe snd-hda-intel, i hope this is the right one) does not work. Here the lspci if this helps:
Check "lspci -n". So far, 1102:0009 and 1102:000b are known to be HD-audio compatible.
This is lspci -nn 01:02.0 Multimedia audio controller [0401]: Creative Labs SB X-Fi [1102:0005]
You can add 1102:0005 to hda_intel.c like the above others.
Takashi
Clearly a harder reboot is required, I will power the machine off and unplug it from the AC for a few minutes. A regular powercycle resulted in the following oops report:
ACPI: PCI Interrupt Link [LK2E] enabled at IRQ 47 ACPI: PCI Interrupt 0000:83:00.0[A] -> Link [LK2E] -> GSI 47 (level, high) -> IRQ 47 PCI: Setting latency timer of device 0000:83:00.0 to 64 ALSA sound/pci/hda/hda_intel.c:2022: chipset global capabilities = 0x3500 ALSA sound/pci/hda/hda_intel.c:754: codec_mask = 0x2 ALSA sound/pci/hda/hda_codec.c:3242: autoconfig: line_outs=4 (0xd/0xf/0xe/0x10/0x0) ALSA sound/pci/hda/hda_codec.c:3246: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3250: hp_outs=1 (0x11/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3251: mono: mono_out=0x0 ALSA sound/pci/hda/hda_codec.c:3259: inputs: mic=0x14, fmic=0x0, line=0x13, fline=0x0, cd=0x0, aux=0x0 ALSA sound/pci/hda/hda_codec.c:2336: BUG? (info->nid) Pid: 1, comm: swapper Not tainted 2.6.26-rc7-00240-gfae47c0 #1
Call Trace: [<ffffffff804668ed>] snd_hda_build_pcms+0x1fc/0x29c [<ffffffff804ec225>] azx_probe+0x7ed/0x7fd [<ffffffff804639b5>] azx_send_cmd+0x0/0x130 [<ffffffff80463ae5>] azx_get_response+0x0/0x207 [<ffffffff8046320a>] azx_attach_pcm_stream+0x0/0x1a0 [<ffffffff80462ed4>] azx_power_notify+0x0/0x51 [<ffffffff80324bd1>] pci_device_probe+0xa9/0xf6 [<ffffffff803b138a>] driver_probe_device+0xb5/0x159 [<ffffffff803b1474>] __driver_attach+0x46/0x6d [<ffffffff803b142e>] __driver_attach+0x0/0x6d [<ffffffff803b0c9e>] bus_for_each_dev+0x44/0x78 [<ffffffff803b0630>] bus_add_driver+0xac/0x1e6 [<ffffffff803b1638>] driver_register+0xa2/0x11f [<ffffffff80324e4a>] __pci_register_driver+0x4a/0x7c [<ffffffff80660b68>] alsa_card_azx_init+0x0/0x15 [<ffffffff80644656>] kernel_init+0x146/0x28b [<ffffffff8020cc08>] child_rip+0xa/0x12 [<ffffffff80644510>] kernel_init+0x0/0x28b [<ffffffff8020cbfe>] child_rip+0x0/0x12
ACPI: PCI interrupt for device 0000:83:00.0 disabled HDA Intel: probe of 0000:83:00.0 failed with error -22 ALSA device list: No soundcards found.
Regards, Tony V.
On Tue, 2008-07-15 at 16:56 +0200, Takashi Iwai wrote:
Could you try the git tree git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git ?
Certainly, compiled and running: Linux prometheus 2.6.26-rc7-00240-gfae47c0 #1 SMP Mon Jul 14 22:10:33 BST 2008 x86_64 Quad-Core AMD Opteron(tm) Processor 2354 AuthenticAMD GNU/Linux
The card is detected, and the auto-detection really seems to do quite well: ACPI: PCI Interrupt Link [LK2E] enabled at IRQ 47 ACPI: PCI Interrupt 0000:83:00.0[A] -> Link [LK2E] -> GSI 47 (level, high) -> IRQ 47 PCI: Setting latency timer of device 0000:83:00.0 to 64 ALSA sound/pci/hda/hda_intel.c:2022: chipset global capabilities = 0x3500 ALSA sound/pci/hda/hda_intel.c:754: codec_mask = 0x2 ALSA sound/pci/hda/hda_codec.c:3242: autoconfig: line_outs=4 (0xd/0xf/0xe/0x10/0x0) ALSA sound/pci/hda/hda_codec.c:3246: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3250: hp_outs=1 (0x11/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3251: mono: mono_out=0x0 ALSA sound/pci/hda/hda_codec.c:3259: inputs: mic=0x14, fmic=0x0, line=0x13, fline=0x0, cd=0x0, aux=0x0 ALSA device list: #0: HDA Intel at 0xd0100000 irq 47
Unfortunately, it now reverts to the same "short attention span" problem that I have seen before. This occured when I tried to write a patch_creative.c myself, and I had blamed this on my unfamiliarity with the framework: hda_codec: num_steps = 0 for NID=0x8 (ctl = Line Capture Volume) ALSA sound/pci/hda/hda_intel.c:601: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x101f000a ALSA sound/pci/hda/hda_intel.c:608: hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x101f000a ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0
I provoked this with a simple: cat /proc/asound/card0/codec#1
It produces valid-looking output the first time (that I shared with you in my initial e-mail), and then the card's short attention span gets the better of it. It is dead in the water, and no matter how hard ALSA tries, it gets no response out of it:
ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 __ratelimit: 3 messages suppressed ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 __ratelimit: 85 messages suppressed ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0
Can you perhaps decode the command from the printk to a problematic widget that should be left alone? I will now powercycle the machine and try to use the soundcard without poking at the codec info.
Note that I've tried this card on MSI as well, and the behaviour is exactly the same (only disabling MSI is another troubleshooting step for the framework, which is equally unsuccessful). The card displays various completely broken codec configurations once in this state, occasionally causing an 'Invalid AFG subtree' message but usually settling on a GPIO configuration with 255 I/Os (seemingly caused by reading an area of all ones): GPIO: io=255, o=255, i=255, unsolicited=1, wake=1 IO[0]: enable=1, dir=1, wake=1, sticky=1, data=1 IO[1]: enable=1, dir=1, wake=1, sticky=1, data=1 (and so on)
The mainboard that I'm trying this on is a Tyan Thunder n6650W (S2915-E) on BIOS revision 2.07; the card is in one of the 8-lane PCI-express slots.
Regards, Tony V.
Sorry, I seem unable to reproduce the earlier success even after having the machine without power for over an hour:
ACPI: PCI Interrupt Link [LK2E] enabled at IRQ 47 ACPI: PCI Interrupt 0000:83:00.0[A] -> Link [LK2E] -> GSI 47 (level, high) -> IRQ 47 PCI: Setting latency timer of device 0000:83:00.0 to 64 ALSA sound/pci/hda/hda_intel.c:2022: chipset global capabilities = 0x3500 ALSA sound/pci/hda/hda_intel.c:754: codec_mask = 0x2 ALSA sound/pci/hda/hda_codec.c:3242: autoconfig: line_outs=4 (0xd/0xf/0xe/0x10/0x0) ALSA sound/pci/hda/hda_codec.c:3246: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3250: hp_outs=1 (0x11/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3251: mono: mono_out=0x0 ALSA sound/pci/hda/hda_codec.c:3259: inputs: mic=0x14, fmic=0x0, line=0x13, fline=0x0, cd=0x0, aux=0x0 ALSA sound/pci/hda/hda_codec.c:275: Too many connections ALSA sound/pci/hda/hda_codec.c:2336: BUG? (info->nid) Pid: 1, comm: swapper Not tainted 2.6.26-rc7-00240-gfae47c0 #1
Call Trace: [<ffffffff804668ed>] snd_hda_build_pcms+0x1fc/0x29c [<ffffffff804ec225>] azx_probe+0x7ed/0x7fd [<ffffffff804639b5>] azx_send_cmd+0x0/0x130 [<ffffffff80463ae5>] azx_get_response+0x0/0x207 [<ffffffff8046320a>] azx_attach_pcm_stream+0x0/0x1a0 [<ffffffff80462ed4>] azx_power_notify+0x0/0x51 [<ffffffff80324bd1>] pci_device_probe+0xa9/0xf6 [<ffffffff803b138a>] driver_probe_device+0xb5/0x159 [<ffffffff803b1474>] __driver_attach+0x46/0x6d [<ffffffff803b142e>] __driver_attach+0x0/0x6d [<ffffffff803b0c9e>] bus_for_each_dev+0x44/0x78 [<ffffffff803b0630>] bus_add_driver+0xac/0x1e6 [<ffffffff803b1638>] driver_register+0xa2/0x11f [<ffffffff80324e4a>] __pci_register_driver+0x4a/0x7c [<ffffffff80660b68>] alsa_card_azx_init+0x0/0x15 [<ffffffff80644656>] kernel_init+0x146/0x28b [<ffffffff8020cc08>] child_rip+0xa/0x12 [<ffffffff80644510>] kernel_init+0x0/0x28b [<ffffffff8020cbfe>] child_rip+0x0/0x12
ACPI: PCI interrupt for device 0000:83:00.0 disabled HDA Intel: probe of 0000:83:00.0 failed with error -22 ALSA device list: No soundcards found.
I will power it down now and try again tomorrow. Perhaps you can sprinkle some strategic printk statements? I'm certainly happy to try different configurations. To confirm, this machine is not in production use and repeated reboots are not an issue.
Regards, Tony V.
Being without power for longer reset it properly, it seems: ACPI: PCI Interrupt Link [LK2E] enabled at IRQ 47 ACPI: PCI Interrupt 0000:83:00.0[A] -> Link [LK2E] -> GSI 47 (level, high) -> IRQ 47 PCI: Setting latency timer of device 0000:83:00.0 to 64 ALSA sound/pci/hda/hda_intel.c:2022: chipset global capabilities = 0x3500 ALSA sound/pci/hda/hda_intel.c:754: codec_mask = 0x2 ALSA sound/pci/hda/hda_codec.c:3242: autoconfig: line_outs=4 (0xd/0xf/0xe/0x10/0x0) ALSA sound/pci/hda/hda_codec.c:3246: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3250: hp_outs=1 (0x11/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3251: mono: mono_out=0x0 ALSA sound/pci/hda/hda_codec.c:3259: inputs: mic=0x14, fmic=0x0, line=0x13, fline=0x0, cd=0x0, aux=0x0 ALSA device list: #0: HDA Intel at 0xd0100000 irq 47
The mixer restore script then complained about control #4, saying it was unable to set it; the ALSA mixer state dump contains: control.4 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -3450 comment.dbmax 1200 iface MIXER name 'Mic Playback Volume' value.0 0 value.1 0 }
All seemed normal, until I started mplayer and got no audio: [AO_ALSA] alsa-lib: pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave [AO_ALSA] Playback open error: Invalid argument Could not open/initialize audio device -> no sound. Audio: no sound
Kernel-side, things look like the usual 'short attention span' bug: Pid: 3987, comm: mplayer Not tainted 2.6.26-rc7-00240-gfae47c0 #1
Call Trace: [<ffffffff80453c7e>] snd_pcm_hw_constraints_complete+0xbf/0x2b7 [<ffffffff80453ee8>] snd_pcm_open_substream+0x72/0xb9 [<ffffffff804ee718>] mutex_lock+0xd/0x1e [<ffffffff80453fbe>] snd_pcm_open+0x8f/0x188 [<ffffffff80228d82>] default_wake_function+0x0/0xe [<ffffffff8027f1ec>] exact_lock+0xc/0x14 [<ffffffff804466f8>] snd_open+0x40/0x53 [<ffffffff8027f3f6>] chrdev_open+0x120/0x144 [<ffffffff80285d28>] do_path_lookup+0x1cc/0x1ec [<ffffffff8027f2d6>] chrdev_open+0x0/0x144 [<ffffffff8027b9b1>] __dentry_open+0xe6/0x1e2 [<ffffffff80286e56>] do_filp_open+0x3ac/0x7f6 [<ffffffff8027b740>] get_unused_fd_flags+0x7f/0x10e [<ffffffff8027b815>] do_sys_open+0x46/0xca [<ffffffff8020bdeb>] system_call_after_swapgs+0x7b/0x80
ALSA sound/core/pcm_native.c:2051: snd_pcm_hw_constraints_complete failed ALSA sound/pci/hda/hda_codec.c:774: hda_codec_cleanup_stream: NID=0x2 ALSA sound/pci/hda/hda_codec.c:774: hda_codec_cleanup_stream: NID=0x4 ALSA sound/pci/hda/hda_codec.c:774: hda_codec_cleanup_stream: NID=0x3 ALSA sound/pci/hda/hda_codec.c:774: hda_codec_cleanup_stream: NID=0x5 hda_codec: num_steps = 0 for NID=0x2 (ctl = Front Playback Volume) hda_codec: num_steps = 0 for NID=0x4 (ctl = Surround Playback Volume) hda_codec: num_steps = 0 for NID=0x3 (ctl = Center Playback Volume) hda_codec: num_steps = 0 for NID=0x3 (ctl = LFE Playback Volume) hda_codec: num_steps = 0 for NID=0x5 (ctl = Side Playback Volume) ALSA sound/pci/hda/hda_intel.c:601: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x102ba000 ALSA sound/pci/hda/hda_intel.c:608: hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x102ba000 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 __ratelimit: 455 messages suppressed ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 __ratelimit: 21 messages suppressed ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0 __ratelimit: 155 messages suppressed ALSA sound/pci/hda/hda_intel.c:666: hda-intel: get_response timeout: IRS=0x0
PCM streams are advertised, which is new: prometheus ~ # aplay -L default:CARD=Intel HDA Intel, CA0110 Analog Default Audio Device front:CARD=Intel,DEV=0 HDA Intel, CA0110 Analog Front speakers surround40:CARD=Intel,DEV=0 HDA Intel, CA0110 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Intel,DEV=0 HDA Intel, CA0110 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Intel,DEV=0 HDA Intel, CA0110 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Intel,DEV=0 HDA Intel, CA0110 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Intel,DEV=0 HDA Intel, CA0110 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers null Discard all samples (playback) or generate zero samples (capture) prometheus ~ # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: CA0110 Analog [CA0110 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: CA0110 Digital [CA0110 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0
Sorry to report that I was too late in capturing codec info, this had already reverted to the phantom 255 GPIOs configuration.
Regards, Tony V.
participants (4)
-
Maximilian Güntner -
Takashi Iwai -
Tony "Chainsaw" Vroon -
Tony Vroon