Back in October - N4000 non-working Win11 cbmem logs from coreboot 4.21 were compared with working ChromeOS dmsg logs and @WeirdTreeThing identified
HID input: GTCH7503:00 device as the touchscreen working on ChromeOS.
On Win11 - device manager appears to see device - but touch screen function missing (even with proper drivers installed)
on another unit Blipper/Beetly (N6000) with no Issues – the device was identified as
Not sure if this is a Coreboot issue or a not supported Driver issue on Win11
Mine does this too, phaser360
It’s possible increasing reset_delay_ms in coreboot may fix it. May want to ask @MrChromebox for a ROM with it adjusted on GTCH7503
Does it work under Linux?
Touchscreen does not work on Win or Fedora- only ChromeOS (when reverted back to stock)
please provide cbmem logs and dmesg logs for both working and non-working cases
ok, ChromeOS says you have a G2 touchscreen:
[ 0.969015] input: GTCH7503:00 2A94:A822 as /devices/pci0000:00/0000:00:15.2/i2c_designware.1/i2c-12/i2c-GTCH7503:00/0018:2A94:A822.0001/input/input5
My firmware also detects this:
[INFO ] \_SB.PCI0.I2C2.H040: G2 Touchscreen at I2C: 00:40
so I’m at a bit of a loss as to why it wouldn’t work under Linux/Windows, unless the delays between power states need some tweaking. Other DEDEDE boards use the same touchscreen with slightly different delays, we can try using those instead