Wrong audio profile (on a Skylake system), causing volume problems.

Bug #1637107 reported by Saverio Miroddi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have a Skylake system (ASRock Z170 Gaming-ITX/ac) with (x)Ubuntu 16.04.

My speakers are connected via the SPDIF port, but there is a problem.

When I inspect the audio profile (in `pavucontrol`), I see that `Analog Stereo Output (unplugged)` is selected.
The speakers play regularly, even if this profile is wrong, but the volume doesn't work correctly - anything above mute will cause the speakers to play at maximum volume.

If I choose the `Digital Stereo (IEC958)`, the speakers won't receive any signal at all.

Debug info:

~$ lspci -vv # extract
    00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
      Subsystem: ASRock Incorporation Sunrise Point-H HD Audio
      Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
      Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
      Latency: 32
      Interrupt: pin A routed to IRQ 140
      Region 0: Memory at df140000 (64-bit, non-prefetchable) [size=16K]
      Region 4: Memory at df120000 (64-bit, non-prefetchable) [size=64K]
      Capabilities: <access denied>
      Kernel driver in use: snd_hda_intel
      Kernel modules: snd_hda_intel

    ~$ dmesg | grep 00:1f.3
    [ 0.181004] pci 0000:00:1f.3: [8086:a170] type 00 class 0x040300
    [ 0.181034] pci 0000:00:1f.3: reg 0x10: [mem 0xdf140000-0xdf143fff 64bit]
    [ 0.181062] pci 0000:00:1f.3: reg 0x20: [mem 0xdf120000-0xdf12ffff 64bit]
    [ 0.181091] pci 0000:00:1f.3: PME# supported from D3hot D3cold
    [ 0.181176] pci 0000:00:1f.3: System wakeup disabled by ACPI
    [ 0.579846] iommu: Adding device 0000:00:1f.3 to group 8
    [ 3.126041] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915_bpo])
    [ 4.185983] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
    [ 4.186034] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
    [ 4.186081] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
    [ 4.186135] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
    [ 4.186188] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
    [ 4.186228] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
    [ 4.186267] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
    [ 4.186304] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: saverio 3012 F...m pulseaudio
 /dev/snd/controlC0: saverio 3012 F.... pulseaudio
 /dev/snd/controlC1: saverio 3012 F.... pulseaudio
CurrentDesktop: XFCE
Date: Thu Oct 27 10:21:31 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-11 (108 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Microsoft® LifeCam VX-2000 - Microsoft® LifeCam VX-2000
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.10
dmi.board.name: Z170 Gaming-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :
Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

Further information:

    ~$ grep "Codec:" /proc/asound/card*/codec*
    /proc/asound/card0/codec#0:Codec: Realtek ALC1150
    /proc/asound/card0/codec#2:Codec: Intel Skylake HDMI

Revision history for this message
Luke Yelavich (themuso) wrote : Re: [Bug 1637107] Re: Wrong audio profile (on a Skylake system), causing volume problems.

You could try upgrading ALSA drivers, instructions here: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

Thanks, I will try that.

For reference, audio via analog port works fine (it uses the correct profile, `Analog Stereo Output`, which is the same which is inappropriately used when plugging the digital cable).

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

This is fixed by upgrading the kernel to 4.10.

Revision history for this message
Ubfan (ubfan1) wrote :

See bug Bug #1755309 for the mismatched prototype in the 4.4 linux headers for i915_component.h -- preventing building the HDMI audio code. The 4.10 kernel code finally matched the prototype, and the intel_audio.c file compiles.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

Works on 18.04, closing.

Changed in alsa-driver (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.