Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: alsa-devel@alsa-project.org
Cc: "tiwai >> Takashi Iwai" <tiwai@suse.de>
Subject: Re: hda-intel: no codecs found
Date: Fri, 01 Jan 2010 20:00:58 +0200	[thread overview]
Message-ID: <4B3E385A.6000606@pardus.org.tr> (raw)
In-Reply-To: <4B3886EC.2050905@pardus.org.tr>

Ozan Çağlayan wrote:

(Takashi CC'ed)
> Hi,
>
> Does that warning can be interpreted as a hardware failure? I'm reverting to older alsa-driver snapshots that I'm sure was working OK but still having this warning. I'm suspecting the power outage that the system suffered on Friday.
>
> Is there a way to understand whether it's driver related or HW related?
>
> Thanks,
> Ozan
>   

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-01-01 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 10:22 hda-intel: no codecs found Ozan Çağlayan
2010-01-01 18:00 ` Ozan Çağlayan [this message]
2010-01-12  6: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=4B3E385A.6000606@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=alsa-devel@alsa-project.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