Ubuntu
linux package

  1. Bug #1850439
  2. Comment #186

Comment 186 for bug 1850439

Revision history for this message
Stéphane Gourichon (stephane-gourichon-lpad) wrote :

Following https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/185 here are instructions that provide a permanent fix.

> ## Next step: have a permanent fix
>
> Some copy-paste instructions as to how to make this fix permanent
> would be appreciated. Else I can figure out some and share,
> e.g. from
> https://askubuntu.com/questions/919054/how-do-i-run-a-single-command-at-startup-using-systemd

Hi all,

This fix works on our machine, where lshw says "ZenBook UX534FAC_UX533FAC" or simply "UX534FAC".

What we did is start from https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX534 and adjust for our machine:

Create `/etc/systemd/system/audio-fix.service` with this content:

------------------------------------------------------------------------

[Unit]
Description=Fix internal audio on ASUS Zenbook UX533/534
# The following options are needed to prevent the service from executing before the sound card is activated and thus failing
Requires=sys-devices-pci0000:00-0000:00:1f.3-sound-card0.device # replace with the result of the previous command
After=sys-devices-pci0000:00-0000:00:1f.3-sound-card0.device # same

[Service]
Type=oneshot
ExecStart=hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf ; hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774 ; hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45 ; hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289

[Install]
# Make it part of the sound initialization routine
WantedBy=sound.target

------------------------------------------------------------------------

Then issue this commands:

------------------------------------------------------------------------

systemctl start audio-fix
systemctl enable audio-fix

------------------------------------------------------------------------

You can now reboot to check if the fix works. On our machine, sound works on speakers and audio jack output, sound is good and we could not find any trace of the bug.

Thanks in advance to all kernel hackers that can propagate towards upstream a proper fix (without regression for other users). :-)