Bug 497596 - Sound not working properly on VT1708s with ICH10 chipset
Summary: Sound not working properly on VT1708s with ICH10 chipset
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-oss
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Patrick Laughton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-24 22:03 UTC by Mike Reeves
Modified: 2009-12-18 09:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 09:20:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike Reeves 2009-04-24 22:03:43 UTC
Description of problem: Speaker shows sound on and NOT muted but no sound. Sound test seems as though it should be playing but no sound.

I installed Fedora 11 Alpha (could not get beta to install using RAID-6 configuration and Fedora 10.92 detected the VT1708 controller and the sound worked fine. 


Version-Release number of selected component (if applicable):
[root@swamplnx ~]# uname -a
Linux swamplnx 2.6.27.21-170.2.56.fc10.x86_64 #1 SMP Mon Mar 23 23:08:10 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@swamplnx ~]# 

[root@swamplnx ~]# alsactl init
Unknown hardware: "HDA-Intel" "VIA ID 397" "HDA:11060397" "" ""
Hardware is initialized using a guess method

Should be VT1708

How reproducible: very


Steps to Reproduce: try to play sound
1.Select "System" -> "Preferences" -> "Hardware" -> "Sound"
2.Click on any "Test" button
3.
  
Actual results: Acts like it is playing but no sound


Expected results: Expect to hear sound


Additional info:

Comment 1 Mike Reeves 2009-04-24 22:26:37 UTC
forgot to add script output url
http://www.alsa-project.org/db/?f=71d65d14f180267b85db03232706aa869a5d9ca0

Comment 2 Patrick Laughton 2009-04-24 22:51:44 UTC
How does this pertain to alsa-oss?  Misfile?

Comment 3 Mike Reeves 2009-05-01 10:21:57 UTC
That was the best choice in the list. If you have a suggestion as to how to file this I am open.

Comment 4 Mike Reeves 2009-05-01 10:23:26 UTC
P.S. It is also the driver that Fedora 10 chooses to use. Fedora 11 used the VT1708.

Comment 5 Bug Zapper 2009-11-18 11:51:11 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2009-12-18 09:20:05 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.