Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope

[John Cummings]

Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope.

I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here

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

Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop.

Best
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: skip
CasperVersion: 1.455
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lsusb:
 Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. USB Storage
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 014: ID 04ca:7097 Lite-On Technology Corp. Integrated Camera
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Google Nami
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
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 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-25-generic N/A
 linux-backports-modules-5.8.0-25-generic N/A
 linux-firmware 1.190
Tags: groovy
Uname: Linux 5.8.0-25-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: 09/19/2019
dmi.bios.release: 4.0
dmi.bios.vendor: coreboot
dmi.board.name: Nami
dmi.board.vendor: Google
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Google
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvncoreboot:bvr:bd09/19/2019:br4.0:efr0.0:svnGoogle:pnNami:pvr1.0:rvnGoogle:rnNami:rvr1.0:cvnGoogle:ct3:cvr:
dmi.product.family: Google_Nami
dmi.product.name: Nami
dmi.product.sku: sku16227
dmi.product.version: 1.0
dmi.sys.vendor: Google

[John Cummings (mrjohncummings)]

For more information:

Sound: Does not recognise sound output at all, just says 'Dummy Output', I can play sound through bluetooth or USB connected speaker
Microphone: Same as sound
Touchscreen: Does not recognise the screen as a touchscreen
Gyroscope: It recognises the gyroscope but the gyroscope is upside down, meaning when you boot the laptop everything is displayed upside down.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1903217/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[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 1903217

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.

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

apport information

[John Cummings (mrjohncummings)]

I am running Ubuntu as part of dual boot so if there is anything I can copy over or run from ChromeOS to provide more information please let me know, this is the output from dmesg in ChromeOS in developer mode, hopefully its useful in understanding what's missing

chronos@localhost / $ dmesg
[ 0.000000] microcode: microcode updated early to revision 0xd6, date = 2020-04-27
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.232-19103-g45c370e0810f (chrome-bot@chromeos-ci-legacy-us-central2-d-x32-38-6tbk) (Chromium OS 11.0_pre394483_p20200618-r9 clang version 11.0.0 (/var/cache/chromeos-cache/distfiles/egit-src/llvm-project b726d071b4aa46004228fc38ee5bfd167f999bfe)) #1 SMP PREEMPT Sun Nov 1 19:51:22 PST 2020
[ 0.000000] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 4710400 verity payload=PARTUUID=888936ea-0bef-2f4d-af0b-a6c2da398a8b/PARTNROFF=1 hashtree=PARTUUID=888936ea-0bef-2f4d-af0b-a6c2da398a8b/PARTNROFF=1 hashstart=4710400 alg=sha256 root_hexdigest=ffabf6b54172c1cfe99119a3d8b21adbcd000aa09335e87c463b367629a59da8 salt=e555f7f66570d372f51db8d2846e893df6243ac8fc1cfec41e953bfa234b0244" noinitrd vt.global_cursor_default=0 kern_guid=888936ea-0bef-2f4d-af0b-a6c2da398a8b add_efi_memmap boot=local noresume noswap i915.modeset=1 nmi_watchdog=panic,lapic intel_idle.slp_s0_check=1 gsmi.s0ix_logging_enable=1 disablevmx=off
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 960, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 1024, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR'
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 1088 bytes, using 'standard' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] type 16
[ 0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007a986fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007a987000-0x000000007affffff] type 16
[ 0.000000] BIOS-e820: [mem 0x000000007b000000-0x000000007fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe00ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed84fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000...

[John Cummings (mrjohncummings)]

It seems that a solution has been found by a Lenovo employee, please could this be implemented?

https://forums.lenovo.com/t5/Fedora/How-can-I-get-support-for-missing-drivers-for-my-laptop/m-p/5048544?page=1#5185031

[Kai-Heng Feng (kaihengfeng)]

This need to be fix in upstream first:
https://github.com/alsa-project/alsa-ucm-conf

[Launchpad Janitor (janitor)]

[Expired for alsa-ucm-conf (Ubuntu) because there has been no activity for 60 days.]