alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Subject: Re: no audio output with TYAN S7025 motherboard and Realtek ALC262
Date: Thu, 04 Mar 2010 10:15:59 +0100	[thread overview]
Message-ID: <1267694159.9133.7.camel@mattotaupa> (raw)
In-Reply-To: <20100303185454.4D36231781@vis06.nas.nasa.gov>


[-- Attachment #1.1: Type: text/plain, Size: 2551 bytes --]

Dear Bryan,


Am Mittwoch, den 03.03.2010, 10:54 -0800 schrieb Bryan Green:
> I have several systems with a TYAN S7025 motherboard and Realtek ALC262 chipset.
> I have not been able to produce any audio output.  Well, that is except for
> one of the systems: after a variety of tweeks and tests, I got sound working
> on one system, but I do not know what change enabled sound to start working,
> and I have not been able to reproduce the effect on the other systems.

Can you give list of what tweeks you did (even incomplete).

> I have tested with kernels up to 2.6.33, and with ALSA version 1.0.22.1.
> For a non-working system, 'alsaconf' gives the following output:
> Unknown hardware: "HDA-Intel" "Realtek ALC262"
> "HDA:10ec0262,10ec0262,00100202" "0x8086" "0x3a3e"
> 
> And dmesg gives the following:
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> HDA Intel 0000:00:1b.0: irq 89 for MSI/MSI-X
> HDA Intel 0000:00:1b.0: setting latency timer to 64
> hda_codec: ALC262: BIOS auto-probing.
> autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0)
>    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
>    hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
>    mono: mono_out=0x0
>    dig-out=0x1e/0x0
>    inputs: mic=0x18, fmic=0x19, line=0x1a, fline=0x0, cd=0x1c, aux=0x0
>    dig-in=0x1f
> realtek: No valid SSID, checking pincfg 0x411111f0 for NID 0x1d
> realtek: Enable default setup for auto mode as fallback
> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
> 
> For the working system, the dmesg output is the same except for two lines:
> autoconfig: line_outs=1 (0x1b/0x0/0x0/0x0/0x0)
>    inputs: mic=0x18, fmic=0x19, line=0x1a, fline=0x0, cd=0x1c, aux=0x14
> 
> Is there a method for tweaking these values on the non-working system to match
> the working system, to see if that works?

Have you tried different values for the model parameter [1]? If I am not
mistaken you can use HDA-Analyzer [2] to change such values. But I never
used it myself.

> I've uploaded the alsa-info output from a non-working system here:
> http://www.alsa-project.org/db/?f=91057bfc12790688f1d257743e53d5d0ec2ce1e2
> 
> I've uploaded the alsa-info output from the working system here:
> http://www.alsa-project.org/db/?f=198420f14cd0062713636408640636e6d474cf94


Thanks,

Paul


[1] http://alsa-project.org/main/index.php/Help_To_Debug_Intel_HDA#.27model.27_parameter
[2] http://alsa-project.org/main/index.php/Help_To_Debug_Intel_HDA#Try_a_lowlevel_GUI_tool_to_control_your_codec

[-- Attachment #1.2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 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

  reply	other threads:[~2010-03-04  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 18:54 no audio output with TYAN S7025 motherboard and Realtek ALC262 Bryan Green
2010-03-04  9:15 ` Paul Menzel [this message]
2010-03-10 19:37   ` Bryan Green
2010-03-24 18:26     ` Bryan Green
2010-06-19 23:37       ` mirix
2010-06-20  9:09         ` mirix

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=1267694159.9133.7.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).