ALC295 codec seems to have Master and PCM channels swapped

[Dylan Borg]

When trying to use pulseaudio to control volume on my ASUS Zenbook Pro UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying the Master ALSA channel. If I vary that channel in alsamixer I get no variation in volume. If I vary the PCM channel instead I get the desired effect that volume buttons should have. Since pulseaudio varies the Master channel by default and does not respect any configuration settings telling it to use other settings, I suggest swapping these two channels so that pulseaudio works out of the box.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic]
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dylan 1532 F.... pulseaudio
CurrentDesktop: GNOME
Date: Wed Oct 4 19:25:38 2017
HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
InstallationDate: Installed on 2017-10-02 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 13d3:5755 IMC Networks
 Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX550VE
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic N/A
 linux-firmware 1.168
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550VE.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550VE
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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX550VE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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.14 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.14-rc3

[Dylan Borg (borgdylan)]

NO, this is a fresh install on brand new hardware. Also I need the nvidia driver to work on thsi system which is impossible for now with the the 4.14 kernel.

[Dylan Borg (borgdylan)]

This is the installtion output:
dylan@zenbook-pro:~/Downloads/kdebs$ sudo dpkg -i *.deb
[sudo] password for dylan:
Selecting previously unselected package linux-headers-4.14.0-041400rc3.
(Reading database ... 288569 files and directories currently installed.)
Preparing to unpack linux-headers-4.14.0-041400rc3_4.14.0-041400rc3.201710011930_all.deb ...
Unpacking linux-headers-4.14.0-041400rc3 (4.14.0-041400rc3.201710011930) ...
Selecting previously unselected package linux-headers-4.14.0-041400rc3-generic.
Preparing to unpack linux-headers-4.14.0-041400rc3-generic_4.14.0-041400rc3.201710011930_amd64.deb ...
Unpacking linux-headers-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Selecting previously unselected package linux-image-4.14.0-041400rc3-generic.
Preparing to unpack linux-image-4.14.0-041400rc3-generic_4.14.0-041400rc3.201710011930_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
Done.
Unpacking linux-image-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Setting up linux-headers-4.14.0-041400rc3 (4.14.0-041400rc3.201710011930) ...
Setting up linux-headers-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
ERROR (dkms apport): kernel package linux-headers-4.14.0-041400rc3-generic is not supported
Error! Bad return status for module build on kernel: 4.14.0-041400rc3-generic (x86_64)
Consult /var/lib/dkms/nvidia-387/387.12/build/make.log for more information.
Setting up linux-image-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
ERROR (dkms apport): kernel package linux-headers-4.14.0-041400rc3-generic is not supported
Error! Bad return status for module build on kernel: 4.14.0-041400rc3-generic (x86_64)
Consult /var/lib/dkms/nvidia-387/387.12/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
update-initramfs: Generating /boot/initrd.img-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.14.0-041400rc3-generic
Found initrd image: /boot/initrd.img-4.14.0-041400rc3-generic
Found linux image: /boot/vmlinuz-4.13.0-15-generic
Found initrd image: /boot...

[Dylan Borg (borgdylan)]

The DKMS isues should be fixable by disabling "AMD Secure Memory Encryption" i.e. SME support in the 4.14 kernel.

[Dylan Borg (borgdylan)]

Ok, this issue can be fixed by modified pulseaudio instead of the kernel. Will mark this as fixed. For anyone else coming across this having the same issue please add:

[Element Master]
switch = mute
volume = ignore

before the PCM settings block in "/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common"

[Kai-Heng Feng (kaihengfeng)]

It's actually a valid bug. The problem is that node 0x06 does not have amp-out capability. Also there's no mixer that can connect 0x06 to another node with amp-out capability.

I'll ask ALSA expert how to solve problem like this.

[Dylan Borg (borgdylan)]

I got a better result by changing "volume=ignore" to "volume=100", that makes ure teh Master channel is stuck to 100% so teh woofers get used.

[Dylan Borg (borgdylan)]

I wish anyone luck when trying to improve the status of the driver for this codec. Some aspects do feel weird such as the interplay between mixer channels.

[Kai-Heng Feng (kaihengfeng)]

Please try the kernel here:

http://people.canonical.com/~khfeng/lp1721345/

[Dylan Borg (borgdylan)]

I cannot do that, the current nvidia drivers do not build against 4.14. If possible I could try a patches 4.13.9 kernel instead.

[Kai-Heng Feng (kaihengfeng)]

Ok, use this one instead,
http://people.canonical.com/~khfeng/lp1721345-4.13/

[Dylan Borg (borgdylan)]

Is it based on a kernel that is 4.13.5 or higher? 4.13 till 4.13.4 lead to hung shutdowns on the machien in question.

[Kai-Heng Feng (kaihengfeng)]

> On 28 Oct 2017, at 1:42 AM, Dylan Borg <email address hidden> wrote:
>
> Is it based on a kernel that is 4.13.5 or higher? 4.13 till 4.13.4 lead
> to hung shutdowns on the machien in question.

Higher. It’s 4.13.8 based.

>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1721345
>
> Title:
> ALC295 codec seems to have Master and PCM channels swapped
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
> UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
> the Master ALSA channel. If I vary that channel in alsamixer I get no
> variation in volume. If I vary the PCM channel instead I get the
> desired effect that volume buttons should have. Since pulseaudio
> varies the Master channel by default and does not respect any
> configuration settings telling it to use other settings, I suggest
> swapping these two channels so that pulseaudio works out of the box.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic]
> ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
> Uname: Linux 4.13.0-12-generic x86_64
> NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
> ApportVersion: 2.20.7-0ubuntu2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: dylan 1532 F.... pulseaudio
> CurrentDesktop: GNOME
> Date: Wed Oct 4 19:25:38 2017
> HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
> InstallationDate: Installed on 2017-10-02 (1 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 8087:0a2b Intel Corp.
> Bus 001 Device 002: ID 13d3:5755 IMC Networks
> Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: ASUSTeK COMPUTER INC. UX550VE
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.13.0-12-generic N/A
> linux-backports-modules-4.13.0-12-generic N/A
> linux-firmware 1.168
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/05/2017
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: UX550VE.300
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: UX550VE
> 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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX55...

[Dylan Borg (borgdylan)]

The provided kernel has swapped the speaker and headphone channels. The Headphone channel in alsamixer is controlling the laptop speakers! If you need some alsa dumps to aid in correctly mapping the channels do not hesitate to ask.

[Dylan Borg (borgdylan)]

The provided kernel requires all three of Headphone,Master and PCM to be raised for sound to come put of the speakers. The stock kernel needs only Master and PCM to be raised.

[Kai-Heng Feng (kaihengfeng)]

> On 29 Oct 2017, at 4:48 PM, Dylan Borg <email address hidden> wrote:
>
> The provided kernel has swapped the speaker and headphone channels. The
> Headphone channel in alsamixer is controlling the laptop speakers! If
> you need some alsa dumps to aid in correctly mapping the channels do not
> hesitate to ask.

That’s the idea. Because the default speaker does not have amp-out ability, reroute it to use headphone’s amp-out to make its volume changeable.

I think you can change the speaker volume via default GUI widget now without changing any config file, right?

>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1721345
>
> Title:
> ALC295 codec seems to have Master and PCM channels swapped
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
> UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
> the Master ALSA channel. If I vary that channel in alsamixer I get no
> variation in volume. If I vary the PCM channel instead I get the
> desired effect that volume buttons should have. Since pulseaudio
> varies the Master channel by default and does not respect any
> configuration settings telling it to use other settings, I suggest
> swapping these two channels so that pulseaudio works out of the box.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic]
> ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
> Uname: Linux 4.13.0-12-generic x86_64
> NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
> ApportVersion: 2.20.7-0ubuntu2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: dylan 1532 F.... pulseaudio
> CurrentDesktop: GNOME
> Date: Wed Oct 4 19:25:38 2017
> HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
> InstallationDate: Installed on 2017-10-02 (1 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 8087:0a2b Intel Corp.
> Bus 001 Device 002: ID 13d3:5755 IMC Networks
> Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: ASUSTeK COMPUTER INC. UX550VE
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.13.0-12-generic N/A
> linux-backports-modules-4.13.0-12-generic N/A
> linux-firmware 1.168
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/05/2017
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: UX550VE.300
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: UX550VE
> ...

[Dylan Borg (borgdylan)]

No, using stock pulseuadio configuration or the one I had patched will not work. I had to increase the headphone volume with alsamixer manually. Before your patch, I could change the volume by keeping master at 100% and vary the PCM channel. Thr PCM channel seems to alter the amplifier attached to the main speakers. The amplifier attached to the subwoofer has a separate channel named bass speaker in alsamixer. My pulseuadio config patch with a stock kernel allows changing volume from the GUI and hotkeys without any fuss.

[Kai-Heng Feng (kaihengfeng)]

Does "Master" change the output volume of speaker now?

[Dylan Borg (borgdylan)]

It does, but teh other two channels must be raised as well.

[Dylan Borg (borgdylan)]

Output of amixer -c 0 controls:
numid=15,iface=CARD,name='Front Headphone Jack'
numid=42,iface=CARD,name='HDMI/DP,pcm=10 Jack'
numid=18,iface=CARD,name='HDMI/DP,pcm=3 Jack'
numid=24,iface=CARD,name='HDMI/DP,pcm=7 Jack'
numid=30,iface=CARD,name='HDMI/DP,pcm=8 Jack'
numid=36,iface=CARD,name='HDMI/DP,pcm=9 Jack'
numid=12,iface=CARD,name='Mic Phantom Jack'
numid=13,iface=CARD,name='Speaker Front Phantom Jack'
numid=14,iface=CARD,name='Speaker Surround Phantom Jack'
numid=11,iface=MIXER,name='Master Playback Switch'
numid=10,iface=MIXER,name='Master Playback Volume'
numid=5,iface=MIXER,name='Headphone Playback Switch'
numid=4,iface=MIXER,name='Headphone Playback Volume'
numid=53,iface=MIXER,name='PCM Playback Volume'
numid=9,iface=MIXER,name='Mic Boost Volume'
numid=8,iface=MIXER,name='Capture Switch'
numid=7,iface=MIXER,name='Capture Volume'
numid=19,iface=MIXER,name='IEC958 Playback Con Mask'
numid=25,iface=MIXER,name='IEC958 Playback Con Mask',index=1
numid=31,iface=MIXER,name='IEC958 Playback Con Mask',index=2
numid=37,iface=MIXER,name='IEC958 Playback Con Mask',index=3
numid=43,iface=MIXER,name='IEC958 Playback Con Mask',index=4
numid=20,iface=MIXER,name='IEC958 Playback Pro Mask'
numid=26,iface=MIXER,name='IEC958 Playback Pro Mask',index=1
numid=32,iface=MIXER,name='IEC958 Playback Pro Mask',index=2
numid=38,iface=MIXER,name='IEC958 Playback Pro Mask',index=3
numid=44,iface=MIXER,name='IEC958 Playback Pro Mask',index=4
numid=21,iface=MIXER,name='IEC958 Playback Default'
numid=27,iface=MIXER,name='IEC958 Playback Default',index=1
numid=33,iface=MIXER,name='IEC958 Playback Default',index=2
numid=39,iface=MIXER,name='IEC958 Playback Default',index=3
numid=45,iface=MIXER,name='IEC958 Playback Default',index=4
numid=22,iface=MIXER,name='IEC958 Playback Switch'
numid=28,iface=MIXER,name='IEC958 Playback Switch',index=1
numid=34,iface=MIXER,name='IEC958 Playback Switch',index=2
numid=40,iface=MIXER,name='IEC958 Playback Switch',index=3
numid=46,iface=MIXER,name='IEC958 Playback Switch',index=4
numid=6,iface=MIXER,name='Auto-Mute Mode'
numid=3,iface=MIXER,name='Bass Speaker Playback Switch'
numid=2,iface=MIXER,name='Bass Speaker Playback Volume'
numid=1,iface=MIXER,name='Speaker Playback Switch'
numid=17,iface=PCM,name='Capture Channel Map'
numid=16,iface=PCM,name='Playback Channel Map'
numid=23,iface=PCM,name='ELD',device=3
numid=48,iface=PCM,name='Playback Channel Map',device=3
numid=29,iface=PCM,name='ELD',device=7
numid=49,iface=PCM,name='Playback Channel Map',device=7
numid=35,iface=PCM,name='ELD',device=8
numid=50,iface=PCM,name='Playback Channel Map',device=8
numid=41,iface=PCM,name='ELD',device=9
numid=51,iface=PCM,name='Playback Channel Map',device=9
numid=47,iface=PCM,name='ELD',device=10
numid=52,iface=PCM,name='Playback Channel Map',device=10

[Dylan Borg (borgdylan)]

I think Bass Speaker,Master and Headphone all have amp-out capability. They need PCM to be raised. PCM is analogous to a mixing console channel fader, and the former three are analogous to volume knobs on audio amplifiers.

[Kai-Heng Feng (kaihengfeng)]

That's right, what you describe is exactly what we are looking for: to use headphone change speaker volume.

I am not sure why default PA doesn't work though. Do you mean that after removing all PA and ALSA conf, the volume slider in gnome-control-center does not work?

[Dylan Borg (borgdylan)]

When using a stock kernel and stock PA/Alsa configurations, the volume controls end up raising Master only without also raising PCM as PA thinks that PCM and Master are merged. This codec does not require raising Headphone volume for speakers, it only requires it when actually using headphones. The headphone scenario works perfectly out of the box. Please do not change anything with headphones as that would be a regression.

[Kai-Heng Feng (kaihengfeng)]

Master should also change the speaker volume with my patch. But probably we should keep it the way it is...

[Dylan Borg (borgdylan)]

Your patch added an extra requirement to get sound, i.e. that the Headphone volume has to be raised in order to get sound from speakers. It is not only counter-intuitive but also works against how PA operates in general. PA does not raise Headphone volume unless headphones are actually plugged in.

[Dylan Borg (borgdylan)]

SO bettr to keep how it is, and use a PA config patch that is manually applied.

[Mario Vukelic (kreuzsakra)]

Still occurs with Ubuntu 19.04 on Asus ZenBook Flip 15 UX561UD.
The workaround helped.

Codec: Realtek ALC295

[Mario Vukelic (kreuzsakra)]

Still occurs on 19.10 after upgrade, on the same Asus ZenBook Flip 15 UX561UD as in comment #30.
As the upgrade replaced "/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common", had to reapply the workaround from comment #8 (which is kind of bearable on a machine that is has a proper admin, but sucks for normal people)

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/

[Mario Vukelic (kreuzsakra)]

Thanks, will do, but will take a bit as I don't always have access to the machine

[Mario Vukelic (kreuzsakra)]

Still occurs on this Asus in 20.04 with kernel 5.4.0-15 and the -proposed -17.

Super annoying, I have to fix this for the Asus' owner by adding the [Element Master] workaround on every Ubuntu upgrade or in case the responsible package updates.

[Jule Marcoueille (jule.createrocks)]

Same here.

[Dawid (dawidmt)]

I've fixed this issue on my Asus UX550VE, Ubuntu 20.04, kernel 5.4.0-42. I followed Optiman's instructions, which are supposed to "activate bottom speakers" using jack retasking:

https://askubuntu.com/questions/973690/my-volume-is-either-max-volume-or-muted-no-middle-ground