From: James Pearson <james-p@moving-picture.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: hda-intel: no codecs initialized with Teradici sound card and ALSA 1.0.17
Date: Tue, 10 Nov 2009 10:32:57 +0000 [thread overview]
Message-ID: <4AF94159.6010601@moving-picture.com> (raw)
In-Reply-To: <s5hd43qg6rv.wl%tiwai@suse.de>
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
next prev parent reply other threads:[~2009-11-10 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 17:22 hda-intel: no codecs initialized with Teradici sound card and ALSA 1.0.17 James Pearson
2009-11-10 7:48 ` Takashi Iwai
2009-11-10 10:32 ` James Pearson [this message]
2009-11-10 10:41 ` Takashi Iwai
2009-11-10 16:46 ` James Pearson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF94159.6010601@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.