From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001453]: 2.6.14-rc2 "Unknown model for ALC880"
Date: Mon, 19 Dec 2005 02:22:33 +0100 [thread overview]
Message-ID: <1ebdc688592a615df2f0c42a45f82bae@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1453>
======================================================================
Reported By: honschu
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1453
Category: PCI - hda-intel
Reproducibility: always
Severity: block
Priority: normal
Status: resolved
Distribution: Debian sarge
Kernel Version: 2.6.14-rc2
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 09-24-2005 17:22 CEST
Last Modified: 12-19-2005 02:22 CET
======================================================================
Summary: 2.6.14-rc2 "Unknown model for ALC880"
Description:
I have a Aopen i915Gm-HFS Motherboard with intel-hda chipset.
Sound output (input not) works in kernel 2.6.12.
For Kernel 2.6.14-rc2 I get error on boottime (see below)
If you want me to do tests, feel free to ask.
[...]
hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...
hda_codec: num_steps = 0 for NID=0x8
hda_codec: num_steps = 0 for NID=0x8
hda_codec: num_steps = 0 for NID=0x8
[...]
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
[...]
hda_codec: num_steps = 0 for NID=0x8
hda_codec: num_steps = 0 for NID=0x8
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0xb
hda_codec: num_steps = 0 for NID=0x8
hda_codec: num_steps = 0 for NID=0x8
[...]
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0001429 hda_codec: Unknown model for ALC880
======================================================================
----------------------------------------------------------------------
rlrevell - 11-23-05 20:24
----------------------------------------------------------------------
Re: the "unknown model" and "num_steps = 0 for NID" errors, see the patch
in bug #1563.
----------------------------------------------------------------------
rlrevell - 12-19-05 02:22
----------------------------------------------------------------------
The "num_steps = 0" bug is fixed. Open another bug if position_fix is
still needed with 1.0.11rc1
Issue History
Date Modified Username Field Change
======================================================================
09-24-05 17:22 honschu New Issue
09-24-05 17:22 honschu Distribution => Debian sarge
09-24-05 17:22 honschu Kernel Version => 2.6.14-rc2
09-24-05 22:06 rlrevell Relationship added duplicate of 0001429
10-05-05 18:34 tiwai Note Added: 0006430
10-10-05 18:35 honschu Note Added: 0006449
10-11-05 16:29 tiwai Note Added: 0006452
10-14-05 13:17 honschu Note Added: 0006479
11-22-05 19:19 rlrevell Relationship added duplicate of 0000790
11-22-05 19:29 rlrevell Relationship deleted duplicate of 0000790
11-22-05 21:41 mbab Issue Monitored: mbab
11-23-05 20:24 rlrevell Note Added: 0006826
12-19-05 02:22 rlrevell Status assigned => resolved
12-19-05 02:22 rlrevell Resolution open => fixed
12-19-05 02:22 rlrevell Note Added: 0007080
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-19 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 1:22 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 19:24 [ALSA - driver 0001453]: 2.6.14-rc2 "Unknown model for ALC880" bugtrack
2005-11-22 18:29 bugtrack
2005-11-22 18:19 bugtrack
2005-10-14 11:17 bugtrack
2005-10-11 14:29 bugtrack
2005-10-10 16:35 bugtrack
2005-10-05 16:34 bugtrack
2005-09-24 20:06 bugtrack
2005-09-24 15:22 bugtrack
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=1ebdc688592a615df2f0c42a45f82bae@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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