windows 1909 drivers update breaks ALC294 sound

Bug #1876459 reported by Alexey Kuznetsov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Committed
Undecided
Unassigned

Bug Description

Hello!

SHORT VERSION:

Recent windows drivers initialize ALC294 with 24bit 48000HZ, after rebooting to linux it produce garbaged sound (it decay every second, very strange effect). If you reboot from windows 10 1909 directly to linux it broken. You have to turn power off complete to reset the device.

LONG VERSION:

I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly!

also-info.sh shows two devices:

http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d

This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device".
Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs...
Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio".

AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100& REV_1007\5&14BACE15&0&0001
Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01&VEN_10EC&DEV_0294&SUBSYS_10431B11& REV_1000\5&7195807&0&0001
AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022&DEV_15E2&SUBSYS_15E21022&REV_00\4&280 56CF2&0&0541
High Definition Audio Controller/10.0.18362.1
/PCI\VEN_1022&DEV_15E3&SUBSYS_1B111043&REV_00\4&28056CF2&0&0641
High Definition Audio Controller/10.0.18362.1/PCI\VEN_1002&DEV_15DE&SUBSYS_15DE1002&REV_00\4&28056CF2&0&0141

As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3

On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do.

I found several links about this issue here:

https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439

https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound-from-speakers-headphones/1186977

Windows 1909 without updates shows those id's:

AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100& REV_1007\5&14BACE15&0&0001
High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01&VEN_10EC&DEV_0294&SUBSYS_10431B11& REV_1000\5&7195807&0&0001

Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux):

AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100& REV_1007\5&14BACE15&0&0001
High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01&VEN_10EC&DEV_0294&SUBSYS_10431B11& REV_1000\5&7195807&0&0001
AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022&DEV_15E2&SUBSYS_15E21022&REV_00\4&280 56CF2&0&0541

Also, this sound card requires few addtitional actions to perform from here:

https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: axet 1433 F.... pulseaudio
 /dev/snd/controlC0: axet 1433 F.... pulseaudio
CasperMD5CheckResult: skip
Date: Sat May 2 16:25:01 2020
MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-26-generic N/A
 linux-backports-modules-5.4.0-26-generic N/A
 linux-firmware 1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX431DA.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX431DA
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.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX431DA_UM431DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Alexey Kuznetsov (axet) wrote :
description: updated
description: updated
Alexey Kuznetsov (axet)
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Alexey Kuznetsov (axet)
description: updated
Alexey Kuznetsov (axet)
description: updated
Alexey Kuznetsov (axet)
description: updated
Alexey Kuznetsov (axet)
description: updated
Revision history for this message
Alexey Kuznetsov (axet) wrote :
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Will be fixed by 5.4.0-38.42.

Changed in linux (Ubuntu):
status: Confirmed → Fix Committed
tags: added: alc294
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.