Red Hat Bugzilla – Bug 123586
sound doesn't work (snd-intel8x0)
Last modified: 2015-01-04 17:06:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
Sound doesn't work for new FC2 install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot system
2. play test sound with 'System Settings / Soundcard Detection'
Actual Results: no sound is played
Expected Results: sound is played
I will submit lsmod, lspci and dmesg output as an attachment.
I have tried with and without pci=noacpi
Created attachment 100337 [details]
dmesg with pci=noacpi enabled, accessed alsamixer prior to starting X
Created attachment 100338 [details]
same scenerio as dmesg_pci-noacpi.txt
Created attachment 100339 [details]
lspci with pci=noacpi enabled, same scenario as previous (comment 3 was lsmod)
here is the next round of attachments. These are with the standard
grub boot options that FC2 installed by default. (in other words,
pci=noacpi is not used)
Created attachment 100341 [details]
dmesg acpi enabled
Created attachment 100342 [details]
lsmod acpi enabled
Created attachment 100343 [details]
lspci acpi enabled
I'd also like to mention that if i try to access gnome-volume-control
i get the error "sorry, no mixer elements and/or devices found". Just
so we can rule (atleast partially) that everything is simply muted.
i've also tried enabling and disabling the sound server under
'Preferences / Sound'
ugh. I got it working but this definately needs to be reassigned to
another component. Master and PCM were the only two things enabled in
the amixer (and alsamixer). When I enabled more channels it started
The crazy thing is that it would NOT let me access the
gnome-volume-control until i enabled some of these channels. That
alone makes it a pretty serious bug I'd guess. As serious as no sound
working can be atleast :)
I'm going to reassign this to alsa-lib for the component.
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 is still broken in Fedora Core 3, with the same symptoms.
Can you please describe better your problems? Do you have trouble with
comand-line tools (aplay, alsamixer) or any X programs (xmms, mplayer
and other)? What device for play do you use?
Can you please test simple commands (on console, not under X) like:
"aplay -D plughw:0,0 /usr/share/sounds/error.wav" or
"aplay -D default /usr/share/sounds/error.wav"
Next, try to use alsamixer (from console) and if it doesn't help,
attach please your ~/.asoundrc, /etc/asound.conf, /etc/alsa/alsa.conf
(if exist) and output from amixer.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Same problem here. The soundcard worked correctly with FC3.
I checked the level in alsamixer too.
Should I open a new bug report in FC4 ?
everything works fine in fc4 for me with a clean install.
did you upgrade or reinstall?
Problem solved for me.
I just had to activate <External> in alsamixer (not available in kmix).
Marking "WORKSFORME" as per comment #18.