No sound output on Zen AIO 27 Z272SD_Z272SD

[Derek Gordon]

I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well.

No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

# cat /proc/asound/card0/codec* | grep Codec
Codec: Realtek ALC274
Codec: Intel Kabylake HDMI

# cat /proc/asound/card0/pcm0c/info
card: 0
device: 0
subdevice: 0
stream: CAPTURE
id: ALC274 Analog
name: ALC274 Analog
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

d# hwinfo --sound
21: PCI 1f.3: 0403 Audio device
  [Created at pci.378]
  Unique ID: nS1_.WnojYJLVCm0
  SysFS ID: /devices/pci0000:00/0000:00:1f.3
  SysFS BusID: 0000:00:1f.3
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0xa348
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x31d0
  Revision: 0x10
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
  Memory Range: 0xdd100000-0xdd1fffff (rw,non-prefetchable)
  IRQ: 145 (663 events)
  Module Alias: "pci:v00008086d0000A348sv00001043sd000031D0bc04sc03i80"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gdm 1903 F.... pulseaudio
                      derek 2464 F.... pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-16-generic N/A
 linux-backports-modules-4.18.0-16-generic N/A
 linux-firmware 1.173.3
Tags: bionic
Uname: Linux 4.18.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/26/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Z272SD.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Z272SD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 13
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
dmi.product.family: Zen AIO
dmi.product.name: Zen AIO 27 Z272SD_Z272SD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (6 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: bionic
Uname: Linux 5.1.0-050100rc2-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (6 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: bionic
Uname: Linux 5.1.0-050100rc2-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1821936

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.

[Derek Gordon (derek-9ft1)]

Apologies my first run of apport was mainline 5.0. I immediately rebooted and use a standard default kernel for 18.04. I deleted both mainlines since they didn't solve my issue anyway.

[Daniel van Vugt (vanvugt)]

Derek, are you saying kernel 4.18 (or earlier) does not have the bug?

[Daniel van Vugt (vanvugt)]

If the problem is the kernel version then please try to find the closest two versions where one works and the other does not, from this list:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

[Derek Gordon (derek-9ft1)]

No, my point is that I tried other kernel versions to see if it was patched. No kernel world with ACL274 on this machine. Windows works great.

4.18, installed with Ubuntu 18.04.2, to 5.0 were tested with the same results. The issue persists.

Sorry for the confusion.

How do I get this to stop being incomplete?

[Derek Gordon (derek-9ft1)]

See post #5 at https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

It references another Linux variant (eww). But, reading their thread you will find that they made a patch in December 2018 to solve the 294 issue. Then, the bug report for Ubuntu let to y'all doing the same.

I've done all the same steps mentioned in both threads. It appears that the same patch is needed for ACL274.

Post 28 from December 2018, https://forum.manjaro.org/t/alc294-analog-audio-card-detected-but-no-sound-internaly-or-headphones/54089/28, states: "each one of ASUS new laptop models with Realtek ALC294 have individual hwinfo SubVendor and SubDevice values. They are needed for QUIRK hack directly in /sound/pci/hda/patch_realtek.c file." Additionally, it includes 3 patches for the kernel regarding realtek.c.

This makes sense since all other methods to resolve fail.

So, what commands should I run to get you all that data to solve this matter? :-)

[Kai-Heng Feng (kaihengfeng)]

Please run `apport-collect 1821936` to collect log.

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

I did this yesterday per request and marked it as confirmed. I just completed this for a second time agreeing to send some data which mentioned pulse-audio, etc., to you all. It completed at 16:39 local time, Miami.

[Daniel van Vugt (vanvugt)]

I think you might be right about bug 1784485 being similar. In that case this would be a kernel bug. And the title should refer to the model of the computer instead of the model of sound chip.

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

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Does kernel parameter "snd_hda_intel.model=alc256-asus-aio" help?

[Derek Gordon (derek-9ft1)]

Added this and rebooted, did not help at all. No sound.

[Kai-Heng Feng (kaihengfeng)]

Ah, that's because the model name wasn't included in kernel v4.18. Please use mainline kernel [1]
with the kernel parameter.

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc2/

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

That did not help.

I ran apport-collect again for this ticket after booting mainline 5.1-rc2 and testing with the alsa flag added.

I will now remove the flag and reboot to try without the flag using this mainline and will do the same.

[Derek Gordon (derek-9ft1)]

apport information

[Derek Gordon (derek-9ft1)]

Same result - no sound. apport-collect just ran again at 09:18 local for logs.

[Kai-Heng Feng (kaihengfeng)]

Please attach dmesg, thanks!

[Derek Gordon (derek-9ft1)]

dmesg

[Kai-Heng Feng (kaihengfeng)]

The module parameter isn't applied.

Pleas runt this as root:
echo 'options snd_hda_intel model=alc256-asus-aio' > /etc/modprobe.d/lp1821936.conf

And reboot.

[Derek Gordon (derek-9ft1)]

Command ran to add it again and run dmesg so it shows. That does not help. See attached dmesg.