Intel Classmate Laptop - Touchscreen works perfect in installer, but stops working once installed. [Archive]

quantumfireball

2018-05-31, 02:44

Like it says, today i booted up the Kali installation CD and when it finished booting to the installer my touchpad was strangely not working, but then when i bumped the screen the mouse moved, so i just used the touchscreen in place of the mouse thru the whole install process and was pleasantly suprised it seemed to work right out of the box.

Well, after install finished, and booted in for the first time, now the touchscreen doesnt work anymore....

I can see the touchscreen is detected by running evtest, it is /dev/input/event2

There is a duplicate device on event3, but when i test, no input comes from the duplicate, when i test event2, i see the coordinates feeding in when i touch the screen.

The touchscreen is connected via internal USB header, and identifies itself as "eTurboTouch eTurboTouch"

dmesg | grep -i touch reveals:

[ 6.485087] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04731/0xa40000/0xa0000/0x0, board id: 0, fw id: 528321[ 6.532903] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input6
[ 6.655220] usb 3-1: Product: eTurboTouch
[ 6.655224] usb 3-1: Manufacturer: eTurboTouch
[ 6.681660] input: eTurboTouch eTurboTouch as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/0003:22B9:0006.0001/input/input9
[ 6.682291] input: eTurboTouch eTurboTouch as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/0003:22B9:0006.0001/input/input10
[ 6.682877] hid-generic 0003:22B9:0006.0001: input,hiddev0,hidraw0: USB HID v1.01 Mouse [eTurboTouch eTurboTouch] on usb-0000:00:1d.1-1/input0
[ 773.942322] usbcore: registered new interface driver usbtouchscreen

evtest list:
root@X:/media/root/New Volume# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: AT Translated Set 2 keyboard
/dev/input/event1: SynPS/2 Synaptics TouchPad
/dev/input/event2: eTurboTouch eTurboTouch
/dev/input/event3: eTurboTouch eTurboTouch
/dev/input/event4: Power Button
/dev/input/event5: Lid Switch
/dev/input/event6: Sleep Button
/dev/input/event7: Power Button
/dev/input/event8: cmpc_keys
/dev/input/event9: cmpc_tablet
/dev/input/event10: cmpc_accel_v4
/dev/input/event11: Intel Webcam: Intel Webcam
/dev/input/event12: PC Speaker
/dev/input/event13: HDA Digital PCBeep
/dev/input/event14: HDA Intel Mic
/dev/input/event15: HDA Intel Headphone
/dev/input/event16: HDA Intel Headphone
/dev/input/event17: Video Bus
Select the device event number [0-17]:

evtest results for event2 device:

root@X:/media/root/New Volume# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: AT Translated Set 2 keyboard
/dev/input/event1: SynPS/2 Synaptics TouchPad
/dev/input/event2: eTurboTouch eTurboTouch
/dev/input/event3: eTurboTouch eTurboTouch
/dev/input/event4: Power Button
/dev/input/event5: Lid Switch
/dev/input/event6: Sleep Button
/dev/input/event7: Power Button
/dev/input/event8: cmpc_keys
/dev/input/event9: cmpc_tablet
/dev/input/event10: cmpc_accel_v4
/dev/input/event11: Intel Webcam: Intel Webcam
/dev/input/event12: PC Speaker
/dev/input/event13: HDA Digital PCBeep
/dev/input/event14: HDA Intel Mic
/dev/input/event15: HDA Intel Headphone
/dev/input/event16: HDA Intel Headphone
/dev/input/event17: Video Bus
Select the device event number [0-17]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x22b9 product 0x6 version 0x101
Input device name: "eTurboTouch eTurboTouch"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 320 (BTN_TOOL_PEN)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 391
Min 0
Max 4095
Event code 1 (ABS_Y)
Value 1859
Min 0
Max 4095
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1527734249.710876, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1527734249.710876, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1527734249.710876, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1527734249.710876, type 3 (EV_ABS), code 0 (ABS_X), value 3826
Event: time 1527734249.710876, type 3 (EV_ABS), code 1 (ABS_Y), value 1831
Event: time 1527734249.710876, -------------- SYN_REPORT ------------
Event: time 1527734249.720849, type 3 (EV_ABS), code 0 (ABS_X), value 3824
Event: time 1527734249.720849, type 3 (EV_ABS), code 1 (ABS_Y), value 1828
Event: time 1527734249.720849, -------------- SYN_REPORT ------------
Event: time 1527734249.741865, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1527734249.741865, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1527734249.741865, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1527734249.741865, -------------- SYN_REPORT ------------
^Croot@X:/media/root/New Volume#

Even did a cat of the device and touched the screen once to make sure raw data was there:

root@X:/dev# cd input
root@X:/dev/input# ls
by-id event1 event12 event15 event2 event5 event8 js1 mouse1
by-path event10 event13 event16 event3 event6 event9 mice mouse2
event0 event11 event14 event17 event4 event7 js0 mouse0
root@X:/dev/input# cat event2
E`[0ï¿½JE`[0ï¿½@E`[0ï¿½ï¿½E`[0ï¿½ï¿½
E`[0ï¿½E`[( ï¿½E`[( ï¿½
E`[( E`[ï¿½Cï¿½E`[ï¿½C~
E`[ï¿½CE`[ï¿½jï¿½E`[ï¿½jï¿½
E`[Wï¿½JE`[Wï¿½@E`[Wï¿½^C
root@X:/dev/input#

Any clues what i can do to get the touchscreen working in the full install, like i said, i ran through the whole graphical installer using it, so the drivers and config must be there somewhere.