[alsa-devel] Fedora 10 x86_64 alsa problem: Realtek ALC889A Audio Codec(ATI azalia) not detected on alsa

[Vedran Miletić]

On Sat, Mar 14, 2009 at 7:50 PM, Emmanuel Chanel
<emmanuelchanel at gmail.com> wrote:
> I wrote this on
> https://bugzilla.redhat.com/show_bug.cgi?id=489828
> I've used the driver of kernel package. And Mr. Jaroslav Kysela replied me that I could try snapshot source. (Thx, Mr. Jaroslav Kysela.
> And on #alsa on Freenode, Thingol and gnubien advised me much. Thank you!)
> But I couldn't get sound back none of both: stable(alsa-driver-1.0.19) and snapshot (alsa-driver-1.0.19.34.g70f78.363.g0ec3b).
> My alsa info is on
> http://www.alsa-project.org/db/?f=af6a6e787d4bd5212bf766bf5d09fda1ab5e2300
> I use desktop. Its mother board is GA-MA69H-S3H . The soundcard is
> onboard. Realtek ALC889A Audio Codec.
> # lspci |grep -i "multi\|audio\|040[0-3]"
> # Audio device: ATI Technologies Inc SB600 Azalia (Intel HDA)
> When I installed stable release of alsa-driver --with-debug=verbose ,
> dmesg says
> HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> ALSA /home/emmanuel/Softwares/alsa-driver-1.0.19/pci/hda/hda_intel.c:2218: chipset global capabilities = 0x4401
> ALSA /home/emmanuel/Softwares/alsa-driver-1.0.19/pci/hda/hda_intel.c:786: codec_mask = 0x8
> ALSA /home/emmanuel/Softwares/alsa-driver-1.0.19/pci/hda/hda_intel.c:1214: hda_intel: codec #3 probed OK
> ALSA /home/emmanuel/Softwares/alsa-driver-1.0.19/pci/hda/../../alsa-kernel/pci/hda/hda_codec.c:788: hda_codec: no AFG or MFG node found
> ALSA /home/emmanuel/Softwares/alsa-driver-1.0.19/pci/hda/hda_intel.c:1298: hda-intel: no codecs initialized
> HDA Intel 0000:00:14.2: PCI INT A disabled
>
> --
> Emmanuel Chanel <emmanuelchanel at gmail.com>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel at alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

I'm like 99% sure that this board is working. A friend of mine had
Gigabyte 690G, and I believe it was this one and it was working fully.
Are you sure everything is enabled (not auto) in BIOS properly and
that you have lastest BIOS?

Vedran Miletić