Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: fab <fab@gnux.info>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Medion + intel hda tests
Date: Thu, 12 May 2005 16:25:02 +0200	[thread overview]
Message-ID: <s5h8y2kzflt.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050510220238.GA28417@blackmilk.localzone.fr>

At Wed, 11 May 2005 00:02:38 +0200,
fab wrote:
> 
> Hi,
> since I reported bugs as well as I can and gave no answers,

Since I've been in vacation and had no net access ;)

>  I started to
> do some very basic tests and sourcecode reading.
> I tried to modprobe snd-hda-intel with different "model" option and then
> tested all the outputs, I only marked the working ones :
> 
> Availables inputs:
>  [front] [surround] [center] , [headphone]
> tested model :
>  3stack        : front
>  3stack-digout : front
>  5stack        : front
>  5stack-digout : front
>  w810          : front surround

This implies that the pin assignment is different from what the normal
models suppose.

I added the "test" model for debugging such cases to ALSA CVS.
Try ALSA CVS version (driver and lib), and set "model=test" module
option to snd-hda-intel module.  Then you'll have fully controllable
volumes and switches.

The noisy output may be fixed by setting "position_fix=1" or
"position_fix=2" module option.

Anyway, please show the content of /proc/asound/card0/codec#* file.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click

      reply	other threads:[~2005-05-12 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 22:02 Medion + intel hda tests fab
2005-05-12 14:25 ` Takashi Iwai [this message]

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=s5h8y2kzflt.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=fab@gnux.info \
    /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