Thread: Retrieve Mark model number via bash
View Single Post
Old 06-20-2017, 07:40 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by helour View Post
I've found this useful command in the /bin/kobo_config.sh:

Code:
ntx_hwconfig -s -p /dev/mmcblk0 PCB 2>/dev/null
On my Kobo Glo HD this script prints 'E60Q90'.
Yes, that script is used in "/etc/eint.d/rcS" while working out what is available for an upgrade. And the id returned is used work out which u-boot and uImage file to use. And "ntx_hwconfig" is used with other parameters to determine other details of the hardware.
Quote:
The another useful info is inside the folder /upgrade/mx6sl-ntx/ of each kobo-update-x.y.zzzz zip file.
Well that's were the uImage and u-boot files are. But, be careful you use the right one for your device.

All the above is reasonably well known. I don't really consider the id you have found a substitute for the "mark". It's probably better, but there are alternatives that might be better depending on what you are actually trying to do. Care to share what the purpose is?
davidfor is offline   Reply With Quote