Touchpad not working after full UEFI flash

Model Name: ASUS Chromebook Plus CX 14

Model Number: CX1405CTA-IS386PT

Board Name: TELTIC

Processor: Intel Core 3 (Alder Lake-N architecture)

MrChromebox-2512.1 01/15/2026

Debian 13 / KDE

Touchpad worked when I used RW_Legacy for initial testing. After full UEFI flash it stopped working. External mouse works fine.

When I watch /proc/interrupts for designware\|093A’ I see numbers increasing when I touch the touchpad. However no movement occurs.

Touchpad settings in OS show enabled.

Any help would be appreciated. Thanks!

Update: the audio also doesn’t work (with WTT’s script) after the full UEFI flash. It, like the touchpad, worked when tested in RW_Legacy mode.

This model should probably be removed from the supported devices on the Mr. Chromebox site or at least documented as no touchpad & no audio.

please provide the necessary debugging logs:

need output of cbmem -1 as well as files generated from the debugging script.

Hi, I’m having the same issue was stated above. Here is a link to a full set of debug logs as requested.

And here is the output of the cbmem -1 command:

Attached are the debugging logs, as well as the cbmem -1.
In the debugging logs, the script had trouble running dmidecode (kept saying it was not installed but it is) so I ran it manually with sudo using the same arguments as the script. It’s included in the zip as dmidecode.log

https://limewire.com/d/LgpIG#O2PSPcwIAx

the UEFI Full ROM firmware is setting up the touchpad exactly the same way as the stock firmware, and the OS is recognizing it. My guess is that you’re using a different distro and there’s a touchpad quirk that isn’t getting applied, or something changed slightly with the device DMI data that is preventing the quirk from being applied

I’m using stock Debian 13 / KDE. That’s one of the distros listed as working right?

After experimenting for a while. I am able to get the touchpad to work (in x11 only) by using an xf86-input-evdev override of libinput, but that also disables the touchscreen and Wayland compatibility.

Do the logs highlight anything to you about why the audio won’t work (after WTT script) on the UEFI Full ROM?

edit: I also just tried it with a liveusb of fedora 43 (Wayland) and the touchpad also does not work. So it doesn’t seem to be particularly distro-related.

Update. I found a solution to the touchpad issue in the Linux Mint Forums ( https://forums.linuxmint.com/viewtopic.php?t=459707 )

In short you need to add a libinput quirk: /etc/libinput/local-overrides.quirks

[PixArt 093A:200F Touchpad]
MatchName=093A:200F Touchpad
AttrResolutionHint=31x31
AttrPressureRange=10:8

I have verified that this works on X11 (Linux Mint) and Wayland (Debian 13 / Gnome)

While testing on Debian 13 / Gnome I got the audio working by running the WeirdTreeThing script. However, I want to run Linux Mint and audio is not working on that platform.

you’ll need to replace the name and ID with the ones from your touchpad device (PRIMAX vs PixArt)

are you using the same laptop that I listed at the top of this thread?

curious because the libinput from your debug logs showed the touchpad as: PNP0C50:00 093A:200F Touchpad just like mine.

My laptop is:
Model Name: Asus Chromebook Plus CX1405CTA

Model Number: CX1405CTA-I38128

Asus-chromebook-cx14-cx1405cta

My model number ends in “-I38128” whereas the model shown in the link above ends in “-S38128”. If that makes a difference… Otherwise the specs are the same.

Update: I got audio working and I was able to map the function keys. In both cases this was done using the WeirdTreeThing scripts but in both cases I had to modify the process to get it to work. Here are the specifics:

Audio
I ran the WeirdTreeThing/chromebook-linux-audio script. The 1st time it through an error - see the output below:

apkeaton@chromebook:\~/Downloads/chromebook-linux-audio$ ./setup-audio
\[sudo\] password for apkeaton:
Detecting platform
Detected Intel Alderlake-N
zstd: /lib/firmware/intel/sof-tplg/sof-adl-rt1019-rt5682.tplg.zst already exists; overwrite (y/n) ? n
Not overwritten

failed to run command: zstd blobs/adl/sof-adl-rt1019-rt5682.tplg -o /lib/firmware/intel/sof-tplg/sof-adl-rt1019-rt5682.tplg.zst
Installing UCM configuration
Cloning into ‘/tmp/alsa-ucm-conf-cros’…
remote: Enumerating objects: 117, done.
remote: Counting objects: 100% (117/117), done.
remote: Compressing objects: 100% (80/80), done.
remote: Total 117 (delta 35), reused 96 (delta 30), pack-reused 0 (from 0)
Receiving objects: 100% (117/117), 20.81 KiB | 5.20 MiB/s, done.
Resolving deltas: 100% (35/35), done.
Checking kernel config for 6.14.0-37-generic
Detecting codecs
Found rt5650
Kernel config check passed
Increasing alsa headroom (fixes instability)
Initializing sound card
alsa-lib parser.c:270:(parse_syntax_field) Incompatible syntax 7 in sof-rt5650.conf
alsa-lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -22
Found hardware: “sof-rt5650” “Intel Alderlake-P HDMI” “HDA:8086281c,80860101,00100000” “” “”
Hardware is initialized using a generic method
Audio setup finished! Reboot to complete setup.
Warning: Your distro is not officially supported. Expect Issues.
Please try a supported distro first before opening an issue. See the README for a list of supported distros.

Note the error: “alsa-lib parser.c:270:(parse_syntax_field) Incompatible syntax 7 in sof-rt5650.conf”. I Googled this error and found that a possible solution was to change the “Syntax” value in the file from 7 to 6 to be allow it to run in older Linux versions. Note, I am running Linux Mint 22.3.

After the script was run the 1st time, I ran the following commands:

find /usr/share/alsa -type f -iname “sof-rt5650.conf”
sudo nano /usr/share/alsa/ucm2/conf.d/sof-rt5650/sof-rt5650.conf
sudo alsactl init; true
  1. The find command finds the path to the “sof-rt5650.conf” file.
  2. The “sof-rt5650.conf” file is edited to change “Syntax 7” to “Syntax 6” on the 1st line.
  3. The alsactl registers the new conf file.

After a reboot audio was working.

Mapping Function Keys

I used the WeirdTreeThing/cros-keyboard-map script to map the function keys. This script also through an error because it was unable to may the key code for the F8 key (key code “A7”). I modified the Python script to map this key code to the mute key. (I didn’t know the appropriate mapping so I used one already defined.)

  1. Edit cros-keyboard-map.py
  2. At line 37 add the line: ’ “A7”: “mute”,’

After the edit run the script and things should work. I suspect the F8 key is not mapped correctly but so far so good.

That’s great work on the audio for Mint. What kernel is it running? The usual answer around here for audio not working on Mint is “sorry, LTS kernels are too old”. Since Mint 22.3 ships with 6.14 maybe all the people who want to run it can now.

Curious, have you tested audio input (mic)?

Can I ask for those that did the touchpad fix, is multitouch working? I can click and move but can’t do two finger taps/scrolling. Could not get audio working. Also on Mint.

  • That’s great work on the audio for Mint. What kernel is it running?
    I was running Linux Mint 22.3 using kernel 6.14.

  • Curious, have you tested audio input (mic)?
    I had not tested the microphone until you asked. The microphone does not work. It shows in the settings windows but you cannot change the gain. I tried using Audacity to record from the mic and wasn’t able to get a usable input level from the mic.

I haven’t found any touchpad actions that don’t work - admittedly there are probably movements/actions I don’t use. In general I am able to click and move using one finger, I can scroll vertically and horizontally using two fingers. If I tap with two fingers on the desktop I see the right-click context menu.

1 Like

What does your quirk file look like, and does it show as being applied? [libinput quirks list /dev/input/eventX where X is event # for touchpad]

1 Like

Ah, sorry already wiped it. I had adjusted a bunch of things like xorg config files that probably interferred with the quirk fix. But thank you for helping. I went back to Chrome OS for now but will probably try a different distro sometime soon.