View Single Post
Old 04-02-2018, 07:56 PM   #199
cvarrick
Junior Member
cvarrick doesn't littercvarrick doesn't litter
 
Posts: 9
Karma: 110
Join Date: Mar 2018
Device: Kobo H202
Quote:
Originally Posted by tshering View Post
Let us see whether KSM does identify the device correctly. Press the button "basic info" and see the values for PRODUCT and PRODUCT_ID.
Code:
PRODUCT=snow, PRODUCT_ID=unknown, CPU=mx6sll, PLATFORM=mx6sll-ntx,
WIFI_MODULE=8189fs, WIFI_MODULE_PATH=/drivers/mx6sll-ntx/wifi/8189fs.ko
uname=Linux (none) 4.1.15-00104-gcd6a6a6 #9 SMP PREEMPT Wed Nov 15 15:40:03 CST 2017 armv7l GNU/Linux, FW=4.6.10197
I can see that PRODUCT_ID is set by getmodelnr.sh which reads /mnt/onboard/.kobo/version, which is this:

Code:
N867832001697,4.1.15,4.6.10197,4.1.15,4.1.15,00000000-0000-0000-0000-000000000378
So PRODUCT_ID = 378

Quote:
Then check which touch driver KSM is trying to use.
Code:
/adds/kbmenu/Qt/plugins/mousedrivers/libKoboTS_h2o2.so
Quote:
Next check whether the driver is available,
Code:
-rwxr-xr-x    1 root     root         26180 Apr  2 19:19 /adds/kbmenu/Qt/plugins/mousedrivers/libKoboTS_h2o2.so

Last edited by cvarrick; 04-02-2018 at 08:07 PM.
cvarrick is offline   Reply With Quote