public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@debian.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ALSA HDA Intel stoped to work in 2.6.16-*
Date: Tue, 28 Feb 2006 17:28:36 -0300	[thread overview]
Message-ID: <87fym3w7m3.fsf@nurf.casa> (raw)
In-Reply-To: <s5hu0ajrbxv.wl%tiwai@suse.de> (Takashi Iwai's message of "Tue, 28 Feb 2006 11:54:04 +0100")

Takashi Iwai <tiwai@suse.de> writes:

> At Tue, 28 Feb 2006 05:51:26 -0300,
> Otavio Salvador wrote:
>> 
>> > This kind of problem is likely due to a broken BIOS.  The current code
>> > parses the default pin configuration set up via BIOS while the older
>> > version used  the fixed pin assignment (depending on the codec chip,
>> > though).
>> > In most cases, it can be recovered by specifying a proper model module
>> > option.  See ALSA-Configuration.txt for details.
>> 
>> I wasn't able to do it.
>
> Didn't it worked?  Which module parameter did you use?

I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did
it work.

>> I hope it helps.
>
> I need more detail of the hardware -- what model of a laptop or a
> desktop from which vendor.

http://www.ctlnotebooks.com/v2/notebook_spec.aspx?id=21&hdr=Products

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

  reply	other threads:[~2006-02-28 20:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 13:15 ALSA HDA Intel stoped to work in 2.6.16-* Otavio Salvador
2006-02-27 14:49 ` Diego Calleja
2006-02-28  8:34   ` Otavio Salvador
2006-02-27 15:02 ` Takashi Iwai
2006-02-28  8:51   ` Otavio Salvador
2006-02-28 10:54     ` Takashi Iwai
2006-02-28 20:28       ` Otavio Salvador [this message]
2006-03-01 10:29         ` Takashi Iwai
2006-03-02  2:24           ` Otavio Salvador
2006-03-03 18:11             ` Takashi Iwai
2006-03-04  5:29               ` Otavio Salvador
2006-03-04 14:51                 ` Adrian Bunk
2006-03-06 14:16                   ` Takashi Iwai
2009-03-07 16:50                     ` [PATCH] " Daniel Gimpelevich
2009-03-07 18:00                       ` Rafael J. Wysocki
2009-03-08 10:26                         ` Takashi Iwai
2009-03-08 23:21                           ` Daniel Gimpelevich
2009-03-11  8:33                             ` Takashi Iwai
2009-03-11 13:07                               ` Daniel Gimpelevich
2009-03-11 13:27                                 ` Takashi Iwai
2009-03-11 13:53                                   ` Daniel Gimpelevich
2006-03-04 15:00           ` [2.6 patch] ALSA-Configuration.txt: snd-hda-intel: document model=basic Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-02-27 15:00 ALSA HDA Intel stoped to work in 2.6.16-* S. Umar
2006-02-27 16:00 ` Takashi Iwai
2006-03-04 14:46   ` Adrian Bunk
2006-03-06 14:14     ` Takashi Iwai
2006-03-06 16:19       ` Otavio Salvador
2006-03-06 16:23         ` Takashi Iwai
2006-03-12  8:11           ` Parag Warudkar
2006-02-27 15:20 S. Umar
2006-02-27 15:58 ` Takashi Iwai

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=87fym3w7m3.fsf@nurf.casa \
    --to=otavio@debian.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox