From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?T3phbiDDh2HEn2xheWFu?= Subject: hda-intel: no codecs found Date: Mon, 28 Dec 2009 12:22:36 +0200 Message-ID: <4B3886EC.2050905@pardus.org.tr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from lider.pardus.org.tr (lider.pardus.org.tr [193.140.100.216]) by alsa0.perex.cz (Postfix) with ESMTP id 04FC7103876 for ; Mon, 28 Dec 2009 11:16:25 +0100 (CET) Received: from [192.168.3.203] (uekae-subnet-out.ume.tubitak.gov.tr [194.27.222.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ozan) by lider.pardus.org.tr (Postfix) with ESMTPSA id E61D7A7A217 for ; Mon, 28 Dec 2009 12:09:37 +0200 (EET) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org 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