[alsa-devel] hda-intel: no codecs initialized with Teradici sound card and ALSA 1.0.17
I'm using CentOS 5.3 (which uses ALSA 1.0.17) and a Teradici KVM over IP extender - which has an hda_intel type sound chipset
However, when the snd_hda_intel module is loaded, dmesg reports:
PCI: Enabling device 0000:04:00.1 (0000 -> 0002) ACPI: PCI Interrupt 0000:04:00.1[A] -> GSI 16 (level, low) -> IRQ 177 PCI: Setting latency timer of device 0000:04:00.1 to 64 hda-intel: no codecs initialized ACPI: PCI interrupt for device 0000:04:00.1 disabled
... and /proc/asound/cards reports:
--- no soundcards ---
I've tried loading the snd-hda-intel module with various 'model=' options (including basic and auto), but it makes no difference
However, we also have CentOS 4.7 on machines with same Teradici card using ALSA 1.0.15 (that replaces the ALSA version that ships with CentOS 4) patched to support the Teradici card - using a patch based on the one that went into ALSA 1.0.17 to support the Teradici card. In this case the audio works - dmesg reports:
ACPI: PCI Interrupt 0000:82:00.1[A] -> GSI 47 (level, high) -> IRQ 233 PCI: Setting latency timer of device 0000:82:00.1 to 64 hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
And in this case, /proc/asound/cards reports:
0 [Teradici ]: HDA-Intel - HDA Teradici HDA Teradici at 0xd0100000 irq 233
and playback works fine.
Any idea why ALSA 1.0.17 doesn't work with the Teradici card?
I don't really want to replace the the ALSA kernel code with a more up to date version if at all possible ... is there a way of 'forcing' the 1.0.17 code 'to work' ?
lspci -vv for this card reports
04:00.1 Audio device: Teradici Corp. Unknown device 1200 Subsystem: Unknown device e49c:040b Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 177 Region 0: Memory at fbbf8000 (64-bit, non-prefetchable) [disabled] [size=16K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [70] Express Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <2us, L1 <8us Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0 Link: Latency L0s <64ns, L1 <16us Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x1
aplay -l (using ALSA 1.0.15 on CentOS 4) reports
**** List of PLAYBACK Hardware Devices **** card 0: Teradici [HDA Teradici], device 0: ALC883 Analog [ALC883 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0
Thanks
James Pearson
At Mon, 09 Nov 2009 17:22:54 +0000, James Pearson wrote:
I'm using CentOS 5.3 (which uses ALSA 1.0.17) and a Teradici KVM over IP extender - which has an hda_intel type sound chipset
However, when the snd_hda_intel module is loaded, dmesg reports:
PCI: Enabling device 0000:04:00.1 (0000 -> 0002) ACPI: PCI Interrupt 0000:04:00.1[A] -> GSI 16 (level, low) -> IRQ 177 PCI: Setting latency timer of device 0000:04:00.1 to 64 hda-intel: no codecs initialized
This means that the driver is loaded but the codec wasn't found on the hardware. It's rather a hardware issue, as it seems.
Takashi
Takashi Iwai wrote:
At Mon, 09 Nov 2009 17:22:54 +0000, James Pearson wrote:
I'm using CentOS 5.3 (which uses ALSA 1.0.17) and a Teradici KVM over IP extender - which has an hda_intel type sound chipset
However, when the snd_hda_intel module is loaded, dmesg reports:
PCI: Enabling device 0000:04:00.1 (0000 -> 0002) ACPI: PCI Interrupt 0000:04:00.1[A] -> GSI 16 (level, low) -> IRQ 177 PCI: Setting latency timer of device 0000:04:00.1 to 64 hda-intel: no codecs initialized
This means that the driver is loaded but the codec wasn't found on the hardware. It's rather a hardware issue, as it seems.
But the same card works with ALSA 1.0.15 - patched to support the Teradici controller - using a patch based on:
http://marc.info/?l=git-commits-head&m=121607380317261&w=2
So how can it be a hardware issue?
I'm going to see if a more recent version of ALSA works ...
James Pearson
At Tue, 10 Nov 2009 10:32:57 +0000, James Pearson wrote:
Takashi Iwai wrote:
At Mon, 09 Nov 2009 17:22:54 +0000, James Pearson wrote:
I'm using CentOS 5.3 (which uses ALSA 1.0.17) and a Teradici KVM over IP extender - which has an hda_intel type sound chipset
However, when the snd_hda_intel module is loaded, dmesg reports:
PCI: Enabling device 0000:04:00.1 (0000 -> 0002) ACPI: PCI Interrupt 0000:04:00.1[A] -> GSI 16 (level, low) -> IRQ 177 PCI: Setting latency timer of device 0000:04:00.1 to 64 hda-intel: no codecs initialized
This means that the driver is loaded but the codec wasn't found on the hardware. It's rather a hardware issue, as it seems.
But the same card works with ALSA 1.0.15 - patched to support the Teradici controller - using a patch based on:
http://marc.info/?l=git-commits-head&m=121607380317261&w=2
So how can it be a hardware issue?
Well, if exactly the same machine works, then it's hardly.
I'm going to see if a more recent version of ALSA works ...
Yes please. 1.0.17 is way too old to debug.
Takashi
Takashi Iwai wrote:
Well, if exactly the same machine works, then it's hardly.
I'm going to see if a more recent version of ALSA works ...
Yes please. 1.0.17 is way too old to debug.
Strangely, using a generic 1.0.17 alsa-driver - and the card works fine ...
So I guess it something strange in what RedHat do to their version of the ALSA drivers ...
James Pearson
participants (2)
-
James Pearson
-
Takashi Iwai