Bug 221705 - Alsa: no sound in right channel for AD1988 (hda-intel)
Alsa: no sound in right channel for AD1988 (hda-intel)
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2007-01-06 08:33 EST by Per Thomas Jahr
Modified: 2009-01-09 02:03 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 02:03:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Per Thomas Jahr 2007-01-06 08:33:16 EST
Description of problem:

There is no sound in right channel when I use the built-in soundcard on my Asus 
P5B. I have reported this issue in the Alsa bug database:

But I also report it here, since it could be a FC6 problem only (I have only 
tested FC6).

Version-Release number of selected component (if applicable):
alsa: 1.0.14rc1
kernel: 2.6.18-1.2849.fc6

How reproducible:

Steps to Reproduce:
1. play wav/ogg/mp3 or try speaker-test

Actual results:
No sound in right channel, left channel seems to be ok.

Expected results:
Sound in both channels.

Additional info:
More detailed info at: https://bugtrack.alsa-project.org/alsa-bug/
Comment 1 Per Thomas Jahr 2007-10-19 03:19:46 EDT
Bug still present in F8test3.
Comment 2 Jon Stanley 2007-12-30 00:20:18 EST

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.


I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Comment 3 Jon Stanley 2008-01-07 18:58:33 EST
Closing per previous comment.  If you can provide the requested information,
please feel free to re-open this bug.
Comment 4 Per Thomas Jahr 2008-04-21 17:06:39 EDT
I can still reproduce this with the latest kernel for F8 (
Comment 5 Bug Zapper 2008-11-26 02:08:29 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 6 Bug Zapper 2009-01-09 02:03:04 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.