Touchscreen issue and i suspect its due to missing drivers, please help

System Details

  • Device: [ChromeOS board name] magolor
  • OS: [ChromeOS, Linux, Windows] windows
  • Firmware Type: [Stock, RW_LEGACY, UEFI Full ROM] uefifullrom
  • Firmware Version: [As reported by the script] the latest build available, i just updated it before writing this hoping it would solve the issue. i dont want to have to boot back into my linux liveusb and check but i can remember it was from sometime in april of 2026
  • Internal storage type: [SATA, NVMe, eMMC, UFS] (if applicable) emmc? im not 100% sure

Summary of the Issue

i for the life of me cannot get the touch screen to work in this thing. ive tried various different drivers from the coolstar github including updating crosec, cr50,and both versions of crostouchscreen to their latest version. i have done some digging around in device manager to try and troubleshoot and i seem to be missing the driver for these hardware ids ACPI\VEN_INTC&DEV_1026 and ACPI\OVTI5675\0

Steps to Reproduce

  1. touch the screen

  2. observe the lack of response

  3. write forum post asking for help

Expected Behavior

the screen should have responded to the input of the touchscreen

in the previous post i had mentioned i had updated to fw ver 2603.2
i’m going to try and update to 2606.1, but i dont think the issue is due to the firmware, although i will post again if the issue persists

Magolor has 7 different touchscreen options - which does yours have? Boot a Linux USB, verify it works there, check dmesg log (sudo dmesg | grep input). 2 of the touchscreens use drivers from coolstar, the other 5 are i2c-hid devices and use the generic drivers from Windows. Device manager will show this as well.

i am currently booted into my liveusb, not sure if the linux distrobution is the issue, i used trixiepup64 with wayland, and can confirm the touchscreen appears to be non-functioning under linux as well
the logs from the command you gave me show it as an elan touchscreen, it appears to be using i2c if im interpreting the logs correctly

[ 62.419721] input: Elan Touchscreen as /devices/pci0000:00/0000:00:15.2/i2c_designware.2/i2c-2/i2c-ELAN0001:00/input/input8

i ran the dmesg command a second time without piping into input and got these debug messages, let me know if this helps

[62.005749] input: Intel Virtual Buttons as /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input3
[ 62.005780] input: Intel Virtual Switches as /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input4
[ 62.011398] cros-usbpd-notify-acpi GOOG0003:00: Couldn’t get Chrome EC device pointer.
[ 62.292703] elan_i2c i2c-ELAN0000:00: supply vcc not found, using dummy regulator
[ 62.319208] elants_i2c i2c-ELAN0001:00: supply vcc33 not found, using dummy regulator
[ 62.319262] elants_i2c i2c-ELAN0001:00: supply vccio not found, using dummy regulator

that’s the standard Elan touchscreen, which would use coolstar’s drivers under Windows.

provide a cbmem log from Linux or Windows as per the debugging info in the docs

i’ve uploaded the logs to catbox. you can access

them at https://files.catbox.moe/dd8otu.log

[INFO ] _SB.PCI0.I2C0.D015: ELAN Touchpad at I2C: 00:15
[INFO ] _SB.PCI0.I2C2.D010: ELAN Touchscreen at I2C: 00:10

standard ELAN0001 touchscreen. should work OOTB in Linux and with coolstar’s drivers under Windows.

ACPI\VEN_INTC&DEV_1026 is your intel Serial IO / I2C controller, which means Windows doesnt even have the bus active to talk to the Touchscreen. Heres what you should do:

  1. go find and install the Intel Serial IO I2C and GPIO drivers for your processor generation, then reboot and check device manager for it to see its not Unknown Device

  2. re run the Touchscreen driver install from Coolstar

  3. look under human Interface Deivices inside device manager to see if the Touch digitizer pops upif it still does nothing, double-check if you grabbed the right driver version for your specific panel variant, because CoolStar sometimes has a couple of different ones for the same board

    If that doesnt work check if the ribbon cable is properly inserted or see if wat the screen panel is matches what the firmware thinks it is