Comment 67 for bug 1871306

Last time I tested it, the bug wasn't fixed yet.

Gabriele

Il Gio 14 Ott 2021, 21:45 Brian Murray <email address hidden> ha
scritto:

> Based off the bug comments its not clear to me if the debdiff for Focal
> actually ended up resolving the issue for people. Additionally, the
> debdiff is rather out of date as there have been a couple of SRUs of
> alsa-ucm-conf since it was created subsequently I'm unsubscribing the
> sponsors team. However, if an updated debdiff is created feel free to
> subscribe the sponsors team.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871306
>
> Title:
> [SRU] No sound from internal card chtmax98090 (missing UCM2 files in
> alsa-ucm-conf)
>
> Status in OEM Priority Project:
> New
> Status in alsa-ucm-conf package in Ubuntu:
> Fix Released
> Status in alsa-ucm-conf source package in Focal:
> In Progress
> Status in alsa-ucm-conf source package in Groovy:
> Won't Fix
>
> Bug description:
> [Impact]
> There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result,
> the audio doesn't work on this machine after installing the 20.04 or
> 20.10.
>
> [Fix]
> The ucm files for this machine are in the alsa-ucm-conf 1.2.3,
> cherry-pick them to ubuntu 20.04 and 20.10
>
> [Test Case]
> After booting up, use speaker to play some sound, it works well,
> plug a headset, play sound to headphone, it basically works but has
> some crankling noise, it is a kernel issue for this noise.
>
> [Regression Risk]
> This SRU adds new ucm files, If the machine uses the audio driver
> of chtmax98090, it will apply this new added ucm files, there will
> be speaker/headphone in the UI. So the possible regression is with
> this SRU, users could see the audio devices in the UI but the audio
> doesn't work (without this SRU, users couldn't see the audio devices
> in the UI at all and the audio doesn't work). This possibility is
> low since we tested it on the ASUS C300.
>
>
> Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox
> script) - Kubuntu Focal minimal fresh installation.
> The sound card is detected: I see it in the Plasma Widget, in
> pavucontrol, in alsamixer and it's not muted.
> I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use
> case config files: no success.
> I tried and unmute speakers left and right in alsamixer: no success.
>
> I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the
> same issue.
>
> I'm running on the same rig Debian Bullseye, kernel 5.4: sound card
> output and input are both working perfectly - I noticed that in
> Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH
> (the HDMI card), while in Debian I find Pulseaudio.
>
> I attach the alsa-info.sh output.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: ubuntu-release-upgrader-core 1:20.04.17
> ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
> Uname: Linux 5.4.0-21-generic x86_64
> ApportVersion: 2.20.11-0ubuntu24
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: KDE
> Date: Tue Apr 7 08:55:46 2020
> InstallationDate: Installed on 2020-04-04 (2 days ago)
> InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200401)
> PackageArchitecture: all
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ProblemType: Bug
> ApportVersion: 2.20.11-0ubuntu24
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: gabriel3 937 F.... pulseaudio
> /dev/snd/controlC0: gabriel3 937 F.... pulseaudio
> CurrentDesktop: KDE
> DistroRelease: Ubuntu 20.04
> InstallationDate: Installed on 2020-04-04 (3 days ago)
> InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200401)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 8087:07dc Intel Corp.
> Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam
> Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless
> Keyboard/Mouse
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: GOOGLE Quawks
> Package: linux (not installed)
> ProcFB: 0 i915drmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic
> root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash
> ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
> RelatedPackageVersions:
> linux-restricted-modules-5.4.0-21-generic N/A
> linux-backports-modules-5.4.0-21-generic N/A
> linux-firmware 1.187
> Tags: focal
> Uname: Linux 5.4.0-21-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 03/17/2020
> dmi.bios.vendor: coreboot
> dmi.bios.version: MrChromebox-4.11.2
> dmi.board.name: Quawks
> dmi.board.vendor: GOOGLE
> dmi.board.version: 1.0
> dmi.chassis.type: 9
> dmi.chassis.vendor: GOOGLE
> dmi.modalias:
> dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr:
> dmi.product.name: Quawks
> dmi.product.version: 1.0
> dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oem-priority/+bug/1871306/+subscriptions
>
>