Would it be possible that the following change causes the hang with the Chuwi boot.img?

--- boot_pipo/init.rk30board.rc 2015-04-01 21:38:21.889597942 +0200
+++ boot_chuwi/init.rk30board.rc        2015-04-01 18:38:23.383864739 +0200
@@ -10,9 +10,10 @@
 
 on post-fs
     insmod /system/lib/modules/ump.ko
-    insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50
+    insmod /system/lib/modules/mali.ko mali_dvfs=133,160,200,266,400,600,798 mali_init_clock=50

EDIT: Nope - switching to slower clock speeds did not cure the hang...

Thanks,

awl

Bump...

@Oma/Jochen (sorry for my impatience in case you are on Easter vacation!):

I still need your help with regards to my questions in #121.

Also, do you see anything in the logs as attached to #123 that could explain why the display goes black after the framebuffer (but only with the Chuwi boot.img)?

I'm still experimenting with making kernel drivers/options more similar to the stock TrekStor 3.0.8+ kernel, but so far, have not succeeded in getting the display and touchscreen to work properly, even though the correct drivers are included in my kernel:

CONFIG_LCD_B101EW05=y
CONFIG_TOUCHSCREEN_GT92X_IIC=y

Unfortunately, in the 3.0.36+ dmesg log in #123, I do NOT see the "GTP-INFO" startup messages from the touchscreen driver that are present in 3.0.8+, where they look like the following:

<4>[    5.555485] <<-GTP-INFO->> GTP driver installing...
<4>[    5.560512] <<-GTP-INFO->> GTP Driver Version: V1.8<2013/06/08>
<4>[    5.568525] <<-GTP-INFO->> GTP Driver Built@21:25:39, Mar  4 2015
<4>[    5.574649] <<-GTP-INFO->> GTP I2C Address: 0x5d
<4>[    5.715059] <<-GTP-INFO->> driver send config
<6>[    5.743715] input: Goodix Capacitive TouchScreen as /devices/virtual/input/input3

What can be the reason for this? How is the touchscreen initialized?

Thanks a million & best regards,

awl

Hello Jochen,

sorry it took that long for me to upload the source to github. As a complete newbie to git, I needed to sort out two major issues first in order to be able to successfully push: First, I was running into

https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1111882

(which basically means that using the https protocol from Ubuntu to github does not work due to a bug in GnuTLS and you need to revert to using ssh) and then with ssh I still needed to find out on increasing git client-side ssh timeouts (as my ADSL upload is real slow):

https://confluence.atlassian.com/display/STASHKB/Git+SSH+push+timeout+on+large+changes

Quite a disillusioning first-time git experience...

The repository is finally online now:

https://github.com/awl1/kernel-st10216a-3036

So the most critical questions/issues with regards to the 3.0.36+ kernel (kernel config in arch/arm/configs/st10216-2a_defconfig) currently are:

1) Why does the display go black after the frame buffer with Chuwi boot.img?

2) Why does adb hang after some seconds if I use the Pipo boot.img?

3) Why does the tochpad not work even though there is a display with Pipo boot.img?

4) Why is

<<-GTP-INFO->> GTP driver installing...

the only dmesg line written by the touchpad driver (as opposed to the correct drive startup documented in #124 for 3.0.8+)?

I have now put several days of research into this, but without any progress - so I am thinking about abandoning this project and staying with the CM10.1 build for the Ventos...

Thanks a million in advance for your kind help!

awl

Hello again,

some limited progress:

When (only) replacing the init.rc within the Chuwi boot.img by the one from the Pipo boot.img, I can make the display work with the Chuwi image as well, but at the expense of adb hanging some very few seconds after the Welcome screen is displayed.

When looking at the differences between these two init.rc files, there are only three minor (!?) differences:

• The Chuwi version writes a value for kernel parameter "ping_group_range"
• The Chuwi version has the "vold" service disabled, while it is enabled in the Pipo version
• The Chuwi version has an additional service "daemonsu"

--- boot_pipo/init.rc   1970-01-01 01:00:00.000000000 +0100
+++ boot_chuwi/init.rc  1970-01-01 01:00:00.000000000 +0100
@@ -131,6 +131,10 @@
 # This is needed by any process that uses socket tagging.
     chmod 0644 /dev/xt_qtaguid
 
+# ICMPv6 group id range from 0~0x7fffffff for passing cts loopback ping
+       write /proc/sys/net/ipv4/ping_group_range "0 2147483647"
+
+
 # Create location for fs_mgr to store abbreviated output from filesystem
 # checker programs.
     mkdir /dev/fscklogs 0770 root system
@@ -469,6 +473,7 @@
     class core
     socket vold stream 0660 root mount
     ioprio be 2
+    disabled
 
 service netd /system/bin/netd
     class main
@@ -605,3 +610,8 @@
 service whtest /system/bin/whtest.sh
     disabled
     oneshot
+
+service daemonsu /system/xbin/daemonsu --auto-daemon
+    class core
+    user root
+    group root

While at the first glance, I don't see why any of those should cause the differences in behaviour:

• Screen does properly display (Pipo) vs. stays blank black (Chuwi)
• adbd hangs some few seconds after displaying the Welcome screen (Pipo) vs. adbd works fine (Chuwi)

Will try to track this down further during the next couple of days...

Thanks & best regards,

awl