From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002213]: hda-intel: no sound on nForce ALC880 (10de:026c)
Date: Wed, 21 Jun 2006 19:46:27 +0200 [thread overview]
Message-ID: <31dae27699a62a4b3d6f0000da382c06@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2213>
======================================================================
Reported By: gmaynard
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2213
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution:
Kernel Version: 2.6.16.20
======================================================================
Date Submitted: 06-16-2006 20:55 CEST
Last Modified: 06-21-2006 19:46 CEST
======================================================================
Summary: hda-intel: no sound on nForce ALC880 (10de:026c)
Description:
aplay says: "underrun!!! (at least 0.033 ms long)" continuously. First
sound played causes:
hda-intel: Invalid position buffer, using LPIB read method instead.
in kmsg. Dumping the results of azx_pcm_pointer shows pos to always be 0,
even after that. No change with model, position_fix, single_cmd
parameters, or either 2.6.12rc3 and 2.6.16.20 kernels (always using ALSA
1.0.11).
(The motherboard is Gigabyte "GA-K8N51PVM9-RH", nForce 430 based.)
Similar to #2174, but that has no mention of aplay messages or kernel
logs, and is Intel.
======================================================================
----------------------------------------------------------------------
tiwai - 06-20-06 19:56
----------------------------------------------------------------------
It's likely a hardware or a BIOS problem.
----------------------------------------------------------------------
gmaynard - 06-21-06 19:46
----------------------------------------------------------------------
I'm seeing it on a second motherboard, from a different manufacturer. This
one's a FoxConn 6150BK8MC-KRSH. aplay and kmsg show the same.
Issue History
Date Modified Username Field Change
======================================================================
06-16-06 20:55 gmaynard New Issue
06-16-06 20:55 gmaynard Kernel Version => 2.6.16.20
06-16-06 20:55 gmaynard File Added: codec#0
06-16-06 20:55 gmaynard File Added: lspci
06-20-06 19:56 tiwai Note Added: 0010352
06-21-06 19:46 gmaynard Note Added: 0010404
======================================================================
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
next reply other threads:[~2006-06-21 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 17:46 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 17:56 [ALSA - driver 0002213]: hda-intel: no sound on nForce ALC880 (10de:026c) bugtrack
2006-06-16 18:55 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=31dae27699a62a4b3d6f0000da382c06@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