Linux Mint Forums

Posted: **Sun Jul 24, 2016 1:36 pm**

bbaker6212 wrote:Good. At this point it's prob best to get back to a baseline - especially since this may just be a configuration issue. I would focus on searching the Windows forums to try to find out where to get the touchscreen config parameters for the Hi12. Also try the XDA-Developers forum.

This is from a virgin install of LM Xfca 18

Code: Select all

destry@destry-Default-string ~ $ dmesg | grep -i goodix
[    6.768243] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[    6.778790] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[    6.779116] input: Goodix Capacitive TouchScreen as /devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input8
destry@destry-Default-string ~ $

Posted: **Sun Jul 24, 2016 1:40 pm**

Also ran this:

Code: Select all

destry@destry-Default-string ~ $ modinfo goodix
filename:       /lib/modules/4.4.0-21-generic/kernel/drivers/input/touchscreen/goodix.ko
license:        GPL v2
description:    Goodix touchscreen driver
author:         Bastien Nocera <hadess@hadess.net>
author:         Benjamin Tissoires <benjamin.tissoires@gmail.com>
srcversion:     14EC9CF3D1F29A86BF0A7F7
alias:          i2c:GDIX1001:00
alias:          acpi*:GDIX1001:*
depends:        
intree:         Y
vermagic:       4.4.0-21-generic SMP mod_unload modversions 
destry@destry-Default-string ~ $

Posted: **Sun Jul 24, 2016 1:53 pm**

Looks like this page on the Chuwi Support site has the Hi12 touchscreen settings as per the windows install.
http://forum.chuwi.com/thread-1159-1-1.html

5) Install Goodix touchscreen drivers for dual-boot Chuwi Hi12 or copy TouchSetting.gt (zipped in attachment - size 1 752 bytes) to C:\Windows\INF on tablet

And the TouchSetting.zip file on that page ~900 bytes:
http://forum.chuwi.com/forum.php?mod=at ... U3OHwxMTU5

has this content which I think is the touchscreen parameters:

Code: Select all

[Setting]
;UpdateCFG=0
SendCFG=1		;Send CFG to touch IC when loading driver	
SleepDisable=0
PhysicalXsize=3072	;Physical size£¬the unit is 0.1mm
PhysicalYsize=1800

[Support]
ESD=1		;Driver supports ESD recovery processing
;SensorID=0	;According to the different SensorID send different configuration
GtpTool=0	;GuitarTestPlateform tool support
X2X=0
Y2Y=0
X2Y=0
Log=0
Flashless=0
ICType=GT910
PrtScreen=0
CtrlAltDel=0
HomeKeyTouchTime=3
VolumeKeyEnable=0
FingerFirst=0
PenAsFinger=0
resetRevert=0

[Feature]
Pen=1		;stylus/pen support
NumberOfKey=1	;The total number of keys supported,equal to 0 does not support key
Key1=0xe3	;0xe3 is home key,Must be a hexadecimal number
Key2=
Key3=
Key4=

[CFG]
DefaultCFG=0x00,0x70,0x08,0x78,0x05,0x0A,0x7C,0x01,0x01,0x08,0x19,0x0F,0x64,0x3C,0x03,0x05,0x00,0x00,0x00,0x00,0x12,0x23,0x00,0x18,0x1A,0x1E,0x14,0x95,0x35,0xFF,0x38,0x3A,0x12,0x0C,0x00,0x00,0x00,0x21,0x03,0x1D,0x16,0x18,0x1A,0xA0,0x82,0x03,0x41,0x28,0x1E,0x00,0x00,0x31,0x4F,0x94,0xD5,0x02,0x08,0x00,0x00,0x04,0x8F,0x33,0x00,0x88,0x38,0x00,0x7F,0x3E,0x00,0x79,0x44,0x00,0x73,0x4B,0x00,0x73,0x80,0x00,0x00,0x00,0xF0,0x4A,0x3A,0xFF,0xFF,0x27,0xFF,0x00,0x00,0x4A,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0A,0x0B,0x0C,0x0D,0x0E,0x0F,0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,0x19,0x1A,0x1B,0x1C,0x1D,0x2A,0x29,0x28,0x27,0x26,0x25,0x24,0x23,0x22,0x21,0x20,0x1F,0x1E,0x1D,0x1C,0x1B,0x19,0x18,0x17,0x16,0x15,0x14,0x13,0x12,0x11,0x10,0x0F,0x0E,0x0D,0x0C,0x0B,0x0A,0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01,0x00,0xDE,0x01
senserid_0=
senserid_1=
senserid_2=
senserid_3=
senserid_4=
senserid_5=

Posted: **Sun Jul 24, 2016 2:05 pm**

Fyi, you can grab the config info with the below commands (Note: first long line wraps onto two lines, run them as one line).
So now, if that assumption is correct we need to find out where this info gets stored in Linux.

Code: Select all

wget -O TouchSetting.zip  "http://forum.chuwi.com/forum.php?mod=attachment&aid=MjM4fGQ5M2UzNzA3fDE0NjkzODA3NzJ8NDU3OHwxMTU5"
unzip TouchSetting.zip
cat TouchSetting.gt

Posted: **Sun Jul 24, 2016 2:34 pm**

Just to complicate matters, as if we needed it!

This page seems to show there may be two different config files - one for the Dual-Boot Hi12 and one for Win10 only version. Your's is dual boot right? http://forum.chuwi.com/thread-1212-1-1.html

Here's the command for downloading the other (dual boot?) TouchSetting.gt file:

Code: Select all

wget -O TouchSetting.zip "http://forum.chuwi.com/forum.php?mod=attachment&aid=MTQ1fGJkZDAwNjM1fDE0NjkzODM4NTl8NDU3OHwxMjEy"

I think it's more likely this is the correct one as the guy in that link said...

UPDATE 23/04/2016: SOLUTION for you guys out there, with the same problem:
go to c:/recovery/oem (directory is hided) and copy the backuped TouchSetting.gt to your windows - inf folder. And the touch rainbows*ng runs again!!!

The TocuhSetting.gt from other driver releases won't work(!) with the newer dual boot version of the chuwi hi12! Thx to god, that chuwi was smart enough to backup the most important file in the whole system!

I have uploadet my TouchSetting.gt here (http://uploaded.net/file/ixuxjca0) and in the attachement:

Posted: **Sun Jul 24, 2016 2:44 pm**

bbaker6212 wrote:Fyi, you can grab the config info with the below commands (Note: first long line wraps onto two lines, run them as one line).
So now, if that assumption is correct we need to find out where this info gets stored in Linux.
Code: Select all
wget -O TouchSetting.zip  "http://forum.chuwi.com/forum.php?mod=attachment&aid=MjM4fGQ5M2UzNzA3fDE0NjkzODA3NzJ8NDU3OHwxMTU5"
unzip TouchSetting.zip
cat TouchSetting.gt

Code: Select all

destry@destry-Default-string ~ $ wget -O TouchSetting.zip  "http://forum.chuwi.com/forum.php?mod=attachment&aid=MjM4fGQ5M2UzNzA3fDE0NjkzODA3NzJ8NDU3OHwxMTU5"
--2016-07-24 14:42:24--  http://forum.chuwi.com/forum.php?mod=attachment&aid=MjM4fGQ5M2UzNzA3fDE0NjkzODA3NzJ8NDU3OHwxMTU5
Resolving forum.chuwi.com (forum.chuwi.com)... 222.73.144.157
Connecting to forum.chuwi.com (forum.chuwi.com)|222.73.144.157|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 900 [application/octet-stream]
Saving to: ‘TouchSetting.zip’

TouchSetting.zip    100%[===================>]     900  --.-KB/s    in 0s      

2016-07-24 14:42:27 (38.6 MB/s) - ‘TouchSetting.zip’ saved [900/900]

destry@destry-Default-string ~ $ unzip TouchSetting.zip
Archive:  TouchSetting.zip
  inflating: TouchSetting.gt         
destry@destry-Default-string ~ $ cat TouchSetting.gt
[Setting]
;UpdateCFG=0
SendCFG=1		;Send CFG to touch IC when loading driver	
SleepDisable=0
PhysicalXsize=3072	;Physical size��the unit is 0.1mm
PhysicalYsize=1800

[Support]
ESD=1		;Driver supports ESD recovery processing
;SensorID=0	;According to the different SensorID send different configuration
GtpTool=0	;GuitarTestPlateform tool support
X2X=0
Y2Y=0
X2Y=0
Log=0
Flashless=0
ICType=GT910
PrtScreen=0
CtrlAltDel=0
HomeKeyTouchTime=3
VolumeKeyEnable=0
FingerFirst=0
PenAsFinger=0
resetRevert=0

[Feature]
Pen=1		;stylus/pen support
NumberOfKey=1	;The total number of keys supported,equal to 0 does not support key
Key1=0xe3	;0xe3 is home key,Must be a hexadecimal number
Key2=
Key3=
Key4=

[CFG]
DefaultCFG=0x00,0x70,0x08,0x78,0x05,0x0A,0x7C,0x01,0x01,0x08,0x19,0x0F,0x64,0x3C,0x03,0x05,0x00,0x00,0x00,0x00,0x12,0x23,0x00,0x18,0x1A,0x1E,0x14,0x95,0x35,0xFF,0x38,0x3A,0x12,0x0C,0x00,0x00,0x00,0x21,0x03,0x1D,0x16,0x18,0x1A,0xA0,0x82,0x03,0x41,0x28,0x1E,0x00,0x00,0x31,0x4F,0x94,0xD5,0x02,0x08,0x00,0x00,0x04,0x8F,0x33,0x00,0x88,0x38,0x00,0x7F,0x3E,0x00,0x79,0x44,0x00,0x73,0x4B,0x00,0x73,0x80,0x00,0x00,0x00,0xF0,0x4A,0x3A,0xFF,0xFF,0x27,0xFF,0x00,0x00,0x4A,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0A,0x0B,0x0C,0x0D,0x0E,0x0F,0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,0x19,0x1A,0x1B,0x1C,0x1D,0x2A,0x29,0x28,0x27,0x26,0x25,0x24,0x23,0x22,0x21,0x20,0x1F,0x1E,0x1D,0x1C,0x1B,0x19,0x18,0x17,0x16,0x15,0x14,0x13,0x12,0x11,0x10,0x0F,0x0E,0x0D,0x0C,0x0B,0x0A,0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01,0x00,0xDE,0x01
senserid_0=
senserid_1=
senserid_2=
senserid_3=
senserid_4=
senserid_5=destry@destry-Default-string ~ $

Posted: **Sun Jul 24, 2016 2:49 pm**

bbaker6212 wrote:Just to complicate matters, as if we needed it! This page seems to show there may be two different config files - one for the Dual-Boot Hi12 and one for Win10 only version. Your's is dual boot right? http://forum.chuwi.com/thread-1212-1-1.html

Here's the command for downloading the other (dual boot?) TouchSetting.gt file:
Code: Select all
wget -O TouchSetting.zip "http://forum.chuwi.com/forum.php?mod=attachment&aid=MTQ1fGJkZDAwNjM1fDE0NjkzODM4NTl8NDU3OHwxMjEy"
I think it's more likely this is the correct one as the guy in that link said...

UPDATE 23/04/2016: SOLUTION for you guys out there, with the same problem:
go to c:/recovery/oem (directory is hided) and copy the backuped TouchSetting.gt to your windows - inf folder. And the touch rainbows*ng runs again!!!

The TocuhSetting.gt from other driver releases won't work(!) with the newer dual boot version of the chuwi hi12! Thx to god, that chuwi was smart enough to backup the most important file in the whole system!

I have uploadet my TouchSetting.gt here (http://uploaded.net/file/ixuxjca0) and in the attachement:

Code: Select all

destry@destry-Default-string ~ $ wget -O TouchSetting.zip "http://form/forum.php?mod=attachment&aid=MTQ1fGJkZDAwNjM1fDE0NjkzODM4NTl8NDU3OHwxMjEy"
--2016-07-24 14:45:40--  http://forum.chuwi.com/forum.php?mod=attachment&aid=MTQ1fGJkZDAwNjM1fDE0NjkzODM4NTl8NDU3OHwxMjEy
Resolving forum.chuwi.com (forum.chuwi.com)... 222.73.144.157
Connecting to forum.chuwi.com (forum.chuwi.com)|222.73.144.157|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 941 [application/octet-stream]
Saving to: ‘TouchSetting.zip’

TouchSetting.zip    100%[===================>]     941  --.-KB/s    in 0s      

2016-07-24 14:45:42 (21.6 MB/s) - ‘TouchSetting.zip’ saved [941/941]

destry@destry-Default-string ~ $

Posted: **Sun Jul 24, 2016 4:16 pm**

Something else I just noticed. In the driver code it has this block which I'm assuming is a list of supported devices.

Code: Select all

MODULE_DEVICE_TABLE(acpi, goodix_acpi_match);
#endif

#ifdef CONFIG_OF
static const struct of_device_id goodix_of_match[] = {
	{ .compatible = "goodix,gt911" },
	{ .compatible = "goodix,gt9110" },
	{ .compatible = "goodix,gt912" },
	{ .compatible = "goodix,gt927" },
	{ .compatible = "goodix,gt9271" },
	{ .compatible = "goodix,gt928" },
	{ .compatible = "goodix,gt967" },
	{ }
};
MODULE_DEVICE_TABLE(of, goodix_of_match);
#endif

See where it says gt911 and gt9110 which are two in the list of Goodix touchscreen devices, I'm assuming. But in your output from "dmesg" was...

Code: Select all

[    6.859742] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[    6.868759] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults

see where it says ID 9111 looks to me like it's a device id of 9111 which is not in that above list. could it be a factor? dunno.
It would take changing the code to add it and recompile. Prob going too deep for you?

Posted: **Sun Jul 24, 2016 4:21 pm**

I just posted a couple questions to Dax on TT. Hopefully he can be of some help here.
[edit] Dax replied http://techtablets.com/forum/topic/linu ... post-44387

copying the info here...

@Dax89...
Yes it’s the touch configuration.

In these cases, the best thing to do is to look the driver’s source code in FreeElectrons, for goodix touchscreen we need to look at the “probe” procedure here:

At some point the driver creates a string which looks like to be a filename: goodix_[touchscreen_id]_cfg.bin and it’s followed by a firmware request by calling “request_firmware_nowait”, this function is new to me so I have googled around in order to know where it looks for files, and I have found this documentation directly from kernel.org: https://www.kernel.org/doc/Documentatio ... ass/README

Which says:

1), kernel(driver):
- calls request_firmware(&fw_entry, $FIRMWARE, device)
- kernel searches the firmware image with name $FIRMWARE directly
in the below search path of root filesystem:
User customized search path by module parameter 'path'[1]
"/lib/firmware/updates/" UTS_RELEASE,
"/lib/firmware/updates",
"/lib/firmware/" UTS_RELEASE,
"/lib/firmware"
So it looks like that it’s the “standard firmware folder” of linux.

Me...
Dax, I found this which supports what you said…http://permalink.gmane.org/gmane.linux. ... ree/139196

Re: [PATCH v7 3/9] Input: goodix - write configuration data to device

On Thu, Oct 08, 2015 at 01:19:29PM +0300, Irina Tirdea wrote:
> Goodix devices can be configured by writing custom data to the device at
> init. The configuration data is read with request_firmware from
> "goodix_<id>_cfg.bin", where <id> is the product id read from the device
> (e.g.: goodix_911_cfg.bin for Goodix GT911, goodix_9271_cfg.bin for
> GT9271).
>
> The configuration information has a specific format described in the Goodix
> datasheet. It includes X/Y resolution, maximum supported touch points,
> interrupt flags, various sensitivity factors and settings for advanced
> features (like gesture recognition).
>
> Before writing the firmware, it is necessary to reset the device. If
> the device ACPI/DT information does not declare gpio pins (needed for
> reset), writing the firmware will not be available for these devices.
>
> This is based on Goodix datasheets for GT911 and GT9271 and on Goodix
> driver gt9xx.c for Android (publicly available in Android kernel
> trees for various devices).

Posted: **Thu Aug 04, 2016 5:01 pm**

20160804_200516.jpg

20160804_200159.jpg

When running gparted on a 20GB partition created by shrinking the 42GB Windows partition
in Win10 for some reason gparted made a change to Android partition #8 instead of the
selected partition #16.

I'm now getting a "Libparted Error (as superuser)" error "Partition(s) 8 on /dev/mmcblk0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes."

Anyone know why the error in the first case?

Do I need to reflash Android or is there a simple fix to Partition #8?

Thanks!

Posted: **Fri Aug 05, 2016 12:38 pm**

When did you take these screenshots? What were ALL the steps you took prior to this? When are you seeing this error message?

Edit: just noticed, that android_system (partition xxxx7, hard to read the blurry pic) partition is mounted, which is odd. You should be running on Live-USB with nothing on your HD mounted. That's prob what's causing the problem. From this screenshot it looks like you have not yet performed the allocation or formatting of that ~19.5GB unallocated space (where you want to install Mint).
I would try rebooting with the live-usb, enter Gparted, make sure nothing is mounted and unmount any partitions that are. Then select that unallocated space and partition it and format it as Ext4, then exit Gparted and proceed to install Linux Mint there. If this does not work I would restore all your original partitions with Macrium Reflect or whichever backup software you used and start over. You did make backups, right???

PS. This thread is of guy installing Mint alongside Windows 7 and Android. It may be of help. I have not yet installed on a machine with Android on it, so I have no direct experience with how it's laid out, partitions, etc.
viewtopic.php?f=46&t=206846&p=1077050&h ... d#p1077050

Posted: **Fri Aug 05, 2016 1:33 pm**

Another way to go, whether or not you restore from backups is to start again and begin using the non-graphical version of Gparted. To start give a listing of your starting condition - your original partitions with:

Code: Select all

sudo parted -l

In my case I got this. NOTE my Disk device is defined as /dev/sda:

brad@G50 ~ $ sudo parted -l
Model: ATA ST1000LM024 HN-M (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 1050MB 1049MB ntfs Basic data partition hidden, diag
2 1050MB 1322MB 273MB fat32 EFI system partition boot, hidden, esp
3 1322MB 2371MB 1049MB fat32 Basic data partition hidden
4 2371MB 2505MB 134MB Microsoft reserved partition msftres
5 2505MB 234GB 231GB ntfs Windows 10 msftdata
6 234GB 234GB 521MB ntfs hidden, diag
7 234GB 601GB 367GB ext4 LinuxMint 17.2 msftdata
8 601GB 993GB 391GB ext4 LinuxMint 18 Mate
14 993GB 1000GB 7474MB linux-swap(v1)

Model: Mass Storage Device (scsi)
Disk /dev/sdb: 7822MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 4194kB 7822MB 7818MB primary fat32 boot

then run this command replacing /dev/sda with whatever <parted> showed as your Disk:

Code: Select all

fdisk -lu /dev/sda

I got this:

brad@G50 ~ $ sudo fdisk -lu /dev/sda
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3AEA073D-4E4D-4937-B8B9-56D7F530210F

Device Start End Sectors Size Type
/dev/sda1 2048 2050047 2048000 1000M Windows recovery environment
/dev/sda2 2050048 2582527 532480 260M EFI System
/dev/sda3 2582528 4630527 2048000 1000M Lenovo boot partition
/dev/sda4 4630528 4892671 262144 128M Microsoft reserved
/dev/sda5 4892672 456682066 451789395 215,4G Microsoft basic data
/dev/sda6 456683520 457701375 1017856 497M Windows recovery environment
/dev/sda7 457701376 1174501375 716800000 341,8G Microsoft basic data
/dev/sda8 1174501376 1938925567 764424192 364,5G Linux filesystem
/dev/sda14 1938925568 1953523711 14598144 7G Linux swap

post your output text here.

Posted: **Fri Aug 05, 2016 8:28 pm**

OK re. using the non-graphical gparted & recording the starting layout for reference.
(The Beta discussion re. Mint 18 implied some concerns re. gparted that may explain my experience. Can't say for sure.)
I was hoping someone had an undisturbed Chuwi Hi-12 and could provide that reference - I'll get & post it.
I'm too bleary-eyed now to start this - so in the morning I'll attempt the Android re-flash then go from there.
Thanks!

Posted: **Fri Aug 05, 2016 8:52 pm**

As I said in the TechTablets thread, I'd start over and let the install program try to do everything. I only use Gparted if I can't get it to work with the install program. In this case, it may be that Gparted is doing something wrong. Here is install directions for Ubuntu 16.04 that worked for the Chuwi Vi8 and Vi10 without using Gparted. And Linux Mint 18 install should work the same way as Ubuntu 16. https://github.com/Manouchehri/vi8/blob ... uctions.md

Posted: **Fri Aug 05, 2016 9:20 pm**

Something else I didn't realize. Mint Mate once installed does not use gparted it uses gnome-disks for partition management. Not sure if that's also the case when booted on Live-USB. Are you installing with Mate or Cinnamon live-USB?

this page may help if you need Gparted help http://gparted.org/help.php in addition you can go to the Install/boot forum section here on the LM forums. Of note, once you get your Android partition reflashed is what they say about backing up your partition config.

Posted: **Fri Aug 05, 2016 9:34 pm**

bbaker6212 wrote:Something else I didn't realize. Mint Mate once installed does not use gparted it uses gnome-disks for partition management. Not sure if that's also the case when booted on Live-USB. Are you installing with Mate or Cinnamon live-USB?

Gparted is on all of the Mint install (Live) disks but typically is not installed. You can install it later using Synaptic or the Software Manager if you like.

Posted: **Sat Aug 06, 2016 11:39 am**

From the TechTablets forum, a response which may explain the problem partitioning/installing on this and other Chuwi tablets:

@Tikilou on August 6, 2016:

on la test revision of Chuwi Tablets, we need to use linux kernel 4.6 and up about format and repart filesystem. Most of recent linux USB live bootable systems use linux 4.4 by default.

If you want use gparted or other tool, you need to modify any squashfs file of livesystem and replace linux 4.4 by linux 4.6 or 4.7

Posted: **Sun Aug 07, 2016 9:18 pm**

Anyone got paint-by-numbers as to how to accomplish this with a Linux Mint 18 Mate 64 USB Live-Boot, please?

Thanks!

Posted: **Mon Aug 08, 2016 2:29 am**

One way is to use two USB drives. Boot your Live-USB and install onto the other one as your destination drive. Then it should act just like an installed hard drive. Then you can upgrade the kernel in the usual fashion which is easy. Maybe there's another way to do this but I don't know. I tried making a persistent Live-USB drive and updated the kernel and it was gone after I rebooted. It was not really persistent. But I think the two USB method should work if you're looking for a solution that does not involve installing on your HD.

Once you've got your persistent USB drive working, this post has the kernel upgrade instructions: viewtopic.php?f=49&t=226452&hilit=wget#p1195024 <-- EDIT: they changed the URL's to the .deb files, Those no longer work.
Here are the new ones. Do the same "wget" commands with these:

http://kernel.ubuntu.com/~kernel-ppa/ma ... 01_all.deb
http://kernel.ubuntu.com/~kernel-ppa/ma ... _amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/ma ... _amd64.deb

Posted: **Mon Aug 08, 2016 2:55 am**

I tried testing that squashfs route basically creating an installation USB with kernel 4.7 on it, it was a pain and in the end it didn't work. It would not boot up.
If you install onto a USB drive as I described above, then boot into that installed USB drive, you can run Gparted from there to partition your HD. Then after partitioning your HD, unplug that USB and bootup again with your Live-USB Install drive and you should be able to install onto that newly partitioned drive. Kinda rountabout way, but so is doing that squashfs (custom install drive) method which didn't work anyway.

or... maybe you can figure out why installing the 4.7 kernel did not persist when I did it on my Live-USB drive.

Linux Mint Forums

Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core

Re: Linux Mint 18 Working on Chuwi Hi12 Tablet PC 64 Bit Cherry Trail Quad Core