[chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output"

[Jaime Pérez]

chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices.

Audio options shows device and it works if I do this:

 git clone https://github.com/plbossart/UCM.git
 cd UCM
 cp -r chtmax98090/ /usr/share/alsa/ucm/
 alsactl store

It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jaime 1293 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 17 20:32:35 2019
InstallationDate: Installed on 2019-06-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2014
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Gnawty
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

[greensysadmin (greensysdmin)]

I still have this on the latest 20.04 dailies on an Asus C200 Chromebook (that also has the
chtmax98090 chip). Even using the Github approach as listed in the OP doesn't seem to help - it appears in Pulsemixer but I still have no sound output.

[Jaime Pérez (jaime-91)]

https://bugzilla.kernel.org/show_bug.cgi?id=201787

[greensysadmin (greensysdmin)]

Thanks for the link, but I'm a little confused. That seems to be a patch for 4.19? I've still got no audio on the C200 on today's daily ISO of Ubuntu Mate 20.04 out of the box. Kernel version is 5.4.0-14-generic.

Following the instructions to use the settings from the OP to use the Github repo makes the device (chtmax98090) appear in the volume control, but the device is muted and cannot be unmuted.

[greensysadmin (greensysdmin)]

On the latest 18.04.4 ISO, it's a little different. After following the Github instructions, the chtmax98098 device appears, and there appears to be output in Pulsemixer when you play sound, but nothing comes out of the speakers.

[greensysadmin (greensysdmin)]

Attached is the output of the crashlog from 20.04 after applying the git settings as detailed in the OP and rebooting - Pulseaudio seems to be crashing.

[Jaime Pérez (jaime-91)]

https://bugzilla.kernel.org/show_bug.cgi?id=201787#c14

Bug is only "fixed" for Swanky and Gnawty chromebooks. They are marked to use a quirk, as an update breaks sound. To get a fix you should contact with Hans de Goede (you can in bugzilla) and ask for a fix.

[Dylan Taylor (dylanmtaylor)]

Having the same issue on a Lenovo N20 "Clapper" Chromebook. Applying the Git patch crashes PulseAudio for me as well. Can't get any sound to play at all from the built-in speakers.

dylan@dylan-Clapper:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: chtmax98090 [chtmax98090], device 0: 3 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: chtmax98090 [chtmax98090], device 1: Deep-Buffer Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

dylan@dylan-Clapper:~$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)

[Gabriele Tettamanzi (gabriel3)]

For Focal Fossa 20.04 and newer releases, check bug 1871306 out:

https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306

The bug has been assigned, the priority is now high: we're going to have it fixed.

Temporary work around: get the missing config UCM2 files from alsa project github or install alsa-ucm-conf 1.2.3 from Debian testing.

Links

alsa-project github:
https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/chtmax98090
https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/codecs/max98090

debian testing package:
https://packages.debian.org/bullseye/all/alsa-ucm-conf/download