Bug 1384625

Summary: Built-in speakers not listed as outputs
Product: [Fedora] Fedora Reporter: Paddy <paddy>
Component: alsa-firmwareAssignee: Tim Jackson <rpm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 24CC: jkysela, rpm
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-24 07:22:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
alsa-info.txt none

Description Paddy 2016-10-13 17:24:03 UTC 
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36
Build Identifier: 

I went through the guide[1], but couldn't find any advice on what to set the snd_hda_intel property to, so I'm filing a bug as requested on that page.

My basic problem is that the built-in speakers for my laptop are not listed as outputs in the output panel of the sound preferences. My headphone jack is, and works properly. I have been unable to get sound from the speakers.

[1]: https://fedoraproject.org/wiki/How_to_debug_sound_problems

Reproducible: Always

Steps to Reproduce:
1. Try to play a sound
Actual Results:  
No sound is played.

Expected Results:  
Sound is played.

lspci output:

00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d12 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21)
00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
3b:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)
Comment 1 Paddy 2016-10-13 17:25:10 UTC 
Created attachment 1210207 [details]
alsa-info.txt
Comment 2 Tim Jackson 2016-10-24 07:22:41 UTC 
This bug is filed against the alsa-firmware package but doesn't sound like a
problem with alsa-firmware.
alsa-firmware contains firmware drivers for a very small number of specialist 
sound cards only.

Please be aware that problems with sound can be caused by many different
software components within a Fedora system (including ALSA kernel modules,
PulseAudio, desktop volume controls, individual applications and more) and
you may find it easier to get some informal help to track down the problem 
before filing bugs (if necessary), so that you can file them against the 
right component and the appropriate person can help.

Help resources are listed here:
https://fedoraproject.org/wiki/Communicating_and_getting_help

If you still believe that your problem is with alsa-firmware, please
re-open this bug with further details. Alternatively, if you identify the
software causing the problem, you could change the Component accordingly and
re-open it.