Red Hat Bugzilla – Bug 122953
Can't hear sound with FC2-Test 3
Last modified: 2007-11-30 17:10:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Description of problem:
I have intel 8x0 (onboard soundcard), the module are loaded (lsmod)
the sound in the mixer is up (alsamixer)
No error message, the speaker work (tested with other os)
Note: in Fedora Core 2 Test 2 my sound work perfectly. Iï¿½ve updated
with Fresh install of Test3 and now no sound! I log this problem on
system-config-soundcard but if I try to play "test sound" i can't hear
I test on another computer (again with intel 8x0 onboard) same
problem! My two computer have now no sound!
If I check in vu meters and I play soundï¿½ seem work (bar up and down)
but nothing in speakerï¿½
The sound card detection is ok, kudzu write good information about
sound cardï¿½ all seem ok!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install Fedora Core 2 Test 3 on intel 8x0
2.Check if module are loaded, sound mixer is un-mute and up
3.Try to play sound, test sound, or music
Actual Results: no sound, but seem to work
I have exactly the same bug as this one with the Core 2 release.
snd-intel8x0, module is loaded properly, un-mute, no error, vu meters
show bars moving normally, but no sound. Souds was working great on
new observation : with my speakers and the mixer to the maximum
volume, I can hear sound from an audio CD playing through /dev/cdrom
with gnome CD Player... but this is the only way to make noise coming
from thoses speakers! ... no wav or sound system
Seems to be a problem with alsa drivers, i've compile "deprecated" oss
kernel modules and remove alsa settings... now it's working
I think is ALSA problem too!
I want test with ALSA driver in fedora dev tree this evening
I don't know if problem is fixed in this version
If you have news tell me!
I've tried with alsa-lib-1.0.5 RC1 and the problem was still there, so
I'll be using old OSS drivers until alsa fix that problem...
Do you have to report this problem to ALSA ?
Bug 122557, 122953, bug 123389, bug 123586, bug 123631, and bug 124497
all seem to be describing the same problem. Some of these are already
assigned. Bug 123631 seems to be the best-documented, so I am putting
additional diagnostic info there. Someone with the right permissions
should probably mark the others as duplicates as appropriate.
*** This bug has been marked as a duplicate of 123631 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.