From: Jo Shields <directhex@apebox.org>
To: alsa-devel@alsa-project.org
Subject: Re: ALC889A (Gigabyte EX58-UD5) pin support
Date: Fri, 06 Mar 2009 02:18:49 +0000 [thread overview]
Message-ID: <1236305929.7464.1.camel@desire> (raw)
In-Reply-To: <1236302368.7568.21.camel@desire>
[-- Attachment #1.1: Type: text/plain, Size: 1090 bytes --]
On Fri, 2009-03-06 at 01:19 +0000, Jo Shields wrote:
> I've got a pretty new Gigabyte board, using snd-hda-intel and an ALC889A
> chip. Whilst the chip seems to be detected fine, I have no functional
> audio out - no sound on any of the ports.
>
> dmesg shows that ALSA has no idea about the specific model:
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
>
> If I'm reading the source correctly, the default pin layout is
> 3stack-digout. I tried 6stack-digout, but it didn't help.
>
> Linked is output from the diagnostic script:
> http://www.alsa-project.org/db/?f=3938bc16481f549203e373e303c4b1c1dfb303dd
>
> I'm happy enough to try things out in an effort to get the onboard sound
> to behave
Scratch that - it seems to have decided to start working after I messed
with some of the switches. Oddly, it's identical to one time when it was
merely popping and clicking (plugging something into the front-panel
audio helped, but the fix seems to hold between cold-boots)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-03-06 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 1:19 ALC889A (Gigabyte EX58-UD5) pin support Jo Shields
2009-03-06 2:18 ` Jo Shields [this message]
2009-03-06 9:01 ` Vedran Miletić
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=1236305929.7464.1.camel@desire \
--to=directhex@apebox.org \
--cc=alsa-devel@alsa-project.org \
/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.