Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)

Bug #1641028 reported by Barry Price
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK.

$ dmesg | egrep -i 'audio|sound'
[ 22.315357] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
[ 22.346211] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 22.346212] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 22.346212] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 22.346213] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12
[ 22.360623] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
[ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
[ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
$ lspci | egrep -i 'audio|sound'
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)

The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute.

Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel.

Individual applications with their own volume controls work fine.

Plugging in a USB headset and adjusting the volume levels for that device works fine.
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: barryprice 4775 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d
InstallationDate: Installed on 2016-11-08 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: ASUSTeK COMPUTER INC. UX390UAK
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-27-generic N/A
 linux-backports-modules-4.8.0-27-generic N/A
 linux-firmware 1.161
Tags: yakkety
Uname: Linux 4.8.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/31/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX390UAK.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX390UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX390UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Barry Price (barryprice) wrote :
Revision history for this message
Barry Price (barryprice) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1641028

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Barry Price (barryprice) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Barry Price (barryprice) wrote : CRDA.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : IwConfig.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : JournalErrors.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : Lspci.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : Lsusb.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcEnviron.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcModules.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : PulseList.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : RfKill.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : UdevDb.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : WifiSyslog.txt

apport information

Barry Price (barryprice)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Barry Price (barryprice) wrote :

Confirmed with upstream kernel 4.9.0-040900rc5-generic #201611131431.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Barry Price (barryprice) wrote :

Sorry, missed the questions in #19.

This is a fresh install on a brand-new laptop, the bug has been present since the initial install and has persisted with each kernel upgrade since then.

Revision history for this message
Nightbringer (nightbringer4ever) wrote :

Hi, here is a workaround and its works for me:
https://forums.linuxmint.com/viewtopic.php?t=91453

Revision history for this message
Chris D'Italia (chrisditalia) wrote :

I am having a very similar issue with my computer see Bug #1649668. Please let me know if there is anything I can do to assist in resolving this bug.

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.