From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001678]: nForce (10de:026c) left channel squeals, right channel mostly okay
Date: Fri, 6 Jan 2006 19:22:45 +0100 [thread overview]
Message-ID: <fa2c226830d9ccf6ed26b696642f132e@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1678>
======================================================================
Reported By: kees
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1678
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Ubuntu Breezy
Kernel Version: 2.6.15-rc6-git4
======================================================================
Date Submitted: 12-25-2005 02:29 CET
Last Modified: 01-06-2006 19:22 CET
======================================================================
Summary: nForce (10de:026c) left channel squeals, right
channel mostly okay
Description:
This is an integrated chipset on an ASUS A8N-VM-UAYGZ mobo. Marketing info
is this is an "nForce410" board, with "6-channel HD audio".
Both the ALSA in 2.6.15-rc6-git4 and the 1.0.11rc1 ALSA driver for
snd-hda-intel load fine, but during playback, the left channel squeals,
while the right seems to play things okay.
I'm happy to dig around and try whatever needs trying to get this fixed.
Thanks!
======================================================================
----------------------------------------------------------------------
adel - 01-06-06 18:14
----------------------------------------------------------------------
Hi,
I would like to confirm this bug on my ASUS A7N-VM CSM
with SoundMax ADI AD1986A 5.1 integrated with the motherboard.
I'm using Ubuntu Breezu, with kernel 2.6.14 .
The system make a horrible noise (trying to play de gdm "welcome" sound)
and after the sound driver seems to crash. However there is no messages in
/var/log/messages or dmesg. But the modules are still loaded :
snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss, snd_pcm and
snd_timer
I applied successfully the patch :
http://www.nabble.com/Intel-HDA-AD1986A-without-surround-t595968.html
on alsa-driver-1.0.10.
Now the sound seems stable with some litte strange noise (perhaps my
speakers).
this is the lspci -nvv :
0000:00:10.1 0403: 10de:026c (rev a2)
Subsystem: 10de:cb84
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin B routed to IRQ 5
Region 0: Memory at febd8000 (32-bit, non-prefetchable)
[size=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [6c] #08 [a802]
----------------------------------------------------------------------
kees - 01-06-06 19:22
----------------------------------------------------------------------
adel:
If what you're hearing sounds like static, I found notes here:
http://lists.us.dell.com/pipermail/linux-precision/2005-September/000687.html
Adding this to my modules.conf file fixed the problem:
options snd-hda-intel position_fix=1
Issue History
Date Modified Username Field Change
======================================================================
12-25-05 02:29 kees New Issue
12-25-05 02:29 kees Distribution => Ubuntu Breezy
12-25-05 02:29 kees Kernel Version => 2.6.15-rc6-git4
12-26-05 11:02 kees Note Added: 0007149
12-30-05 23:43 morgoth666 Issue Monitored: morgoth666
12-30-05 23:43 morgoth666 Issue End Monitor: morgoth666
12-30-05 23:44 morgoth666 Issue Monitored: morgoth666
12-30-05 23:50 morgoth666 Note Added: 0007300
12-31-05 05:47 Dr Hotdog Issue Monitored: Dr Hotdog
12-31-05 10:16 kees Note Added: 0007355
12-31-05 17:12 Dr Hotdog Note Added: 0007357
12-31-05 17:30 Dr Hotdog Note Edited: 0007357
01-04-06 17:40 tiwai Note Added: 0007446
01-04-06 17:56 kees Note Added: 0007449
01-06-06 18:14 adel Note Added: 0007490
01-06-06 19:22 kees Note Added: 0007494
======================================================================
-------------------------------------------------------
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:[~2006-01-06 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 18:22 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-15 14:47 [ALSA - driver 0001678]: nForce (10de:026c) left channel squeals, right channel mostly okay bugtrack
2006-01-31 20:43 bugtrack
2006-01-12 8:57 bugtrack
2006-01-06 17:14 bugtrack
2006-01-04 16:56 bugtrack
2006-01-04 16:40 bugtrack
2005-12-31 16:12 bugtrack
2005-12-31 9:16 bugtrack
2005-12-30 22:50 bugtrack
2005-12-26 10:02 bugtrack
2005-12-25 1:29 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=fa2c226830d9ccf6ed26b696642f132e@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