Created attachment 583419 [details] smolt profile Description of problem: Sound wasn't working by default on f17 (it works in f16, but I need to add some lines in /etc/modprobe.d to get it to work with the headphone sockets). I've added a file called dist-alsa.conf and after restarting sound works using the laptop speakers, or I should say, it worked for a while. The volume icon appeared in the panel at the top and I could listen to things. Sadly, the icon has gone and sound no longer plays (after a suspend/resume cycle). dist-alsa.conf contains: --------------- install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-seq options snd-hda-intel model=dell-m6-amic options snd-hda-intel enable_msi=1 --------------- lspci shows: $ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 18) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06) 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06) 02:00.0 VGA compatible controller: ATI Technologies Inc Device 9488 02:00.1 Audio device: ATI Technologies Inc RV710/730 04:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) 07:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01) 07:00.1 System peripheral: Ricoh Co Ltd Memory Stick Host Controller (rev 01) 07:00.2 System peripheral: Ricoh Co Ltd Device e852 (rev 01) 07:00.3 FireWire (IEEE 1394): Ricoh Co Ltd FireWire Host Controller (rev 01) 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe (rev 10) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05) ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05) ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
Sound works again after logging out and in. Sound icon appeared in panel at log in screen. I've tried a suspend and resume and sound didn't stop working, so not convinced that this triggered it.
Is this still causing issues with 3.5.3?
Hmmm, sorry for the slow reply. Obviously the kernel version has moved on a bit, but I haven't tried for a while. I'll check it out tonight when I get home.
Not sure about 3.5.3, but it's still a problem with 3.6.1 (and I'm downloading 3.6.2) If I open the Sound Settings, I don't even see a second item listed in the Hardware tab. I'm pretty sure I saw this on my last laptop, but that had an ATI video card instead of a Intel. I'm rambling at this point, what more would you like to know?
okay, I've got some more information. I've seen this problem in a number of places and it's to do with a short coming in pulseaudio, but still probably needs addressing in f17, f18 until it's fixed. You can read more information about it here: https://wiki.archlinux.org/index.php/PulseAudio/Examples On one system, I've used pavucontrol to set the HDMI output as default and then added the following lines to the bottom of /etc/pulse/default.pa to setup the analog as a secondary source: ### Load analog device load-module module-alsa-sink device=hw:0,0 load-module module-combine-sink sink_name=combined set-default-sink combined I can no see both my analog and digital (HDMI) outputs. Analog audio isn't working, but at least it's appearing. It's a start and maybe someone with more no how can get this working out of the box.
I am also having this problem in f18.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.