MK908 Kernel upgrade to 3.0.72+

[leolas]

My first try with this kernel modded to fit in my qx1 was a fail, the boot procces hangs after some green lines appears on the screen, maybe it failed to load the proper modules, I am going to try it again after lunch.

leolas

[Omegamoon]

My first try with this kernel modded to fit in my qx1 was a fail, the boot procces hangs after some green lines appears on the screen, maybe it failed to load the proper modules, I am going to try it again after lunch.

leolas

It's really dirty of course, but try to set the SUBLEVEL in the root Makefile to 36 instead of 72 to see if the problem is related to any of the kernel modules. In that case the system will behave as if it is running a 3.0.36+ kernel

[leolas]

Re: MK908 Kernel upgrade to 3.0.72+

It's really dirty of course, but try to set the SUBLEVEL in the root Makefile to 36 instead of 72 to see if the problem is related to any of the kernel modules. In that case the system will behave as if it is running a 3.0.36+ kernel

Ok, I will try that.

leolas

[Omegamoon]

Ok, I will try that.

leolas

One addition. Make sure to run the 'gpio' tool on a working device using the stock kernel. Most common problems with all these different devices is the use of different GPIOs.

Download the tool here: 2013-09-30 GPIODUMP_Omegamoon.zip
Use it as follows:

1. Push the GPIO_DUMP tool somewhere in the /system dir using adb push. You need to do a adb remount to be able to write there
2. Run adb shell
3. Run insmod user-gpio-drv.ko
4. Run gpio dump gpio
5. Run dmesg

Post the complete dmesg result here, showing the complete boot sequence and the GPIO_DUMP

[leolas]

One addition. Make sure to run the 'gpio' tool on a working device using the stock kernel. Most common problems with all these different devices is the use of different GPIOs.

Download the tool here: [ATTACH]3429[/ATTACH]
Use it as follows:

1. Push the GPIO_DUMP tool somewhere in the /system dir using adb push. You need to do a adb remount to be able to write there
2. Run adb shell
3. Run insmod user-gpio-drv.ko
4. Run gpio dump gpio
5. Run dmesg

Post the complete dmesg result here, showing the complete boot sequence and the GPIO_DUMP

Yes, thanks a lot, I know that, I made some scripts and compiled the module for 3.0.36 kernel and gpio bin in :http://www.freaktab.com/showthread.p...n-more-devices

here is my stock giio dump dmesg: For the QX1:

 GPIO gpio0 160 poweronpin
 GPIO gpio0 161 NULL
 GPIO gpio0 162 ?
 GPIO gpio0 163 ?
 GPIO gpio0 164 play
 GPIO gpio0 165 (null)
 GPIO gpio0 166 (null)
 GPIO gpio0 167 usb_detect
 GPIO gpio0 168 ?
 GPIO gpio0 169 (null)
 GPIO gpio0 170 (null)
 GPIO gpio0 171 (null)
 GPIO gpio0 172 (null)
 GPIO gpio0 173 (null)
 GPIO gpio0 174 (null)
 GPIO gpio0 175 (null)
 GPIO gpio0 176 (null)
 GPIO gpio0 177 (null)
 GPIO gpio0 178 (null)
 GPIO gpio0 179 (null)
 GPIO gpio0 180 (null)
 GPIO gpio0 181 (null)
 GPIO gpio0 182 (null)
 GPIO gpio0 183 (null)
 GPIO gpio0 184 (null)
 GPIO gpio0 185 (null)
 GPIO gpio0 186 (null)
 GPIO gpio0 187 (null)
 GPIO gpio0 188 (null)
 GPIO gpio0 189 (null)
 GPIO gpio0 190 (null)
 GPIO gpio0 191 (null)
 GPIO gpio1 192 (null)
 GPIO gpio1 193 (null)
 GPIO gpio1 194 (null)
 GPIO gpio1 195 (null)
 GPIO gpio1 196 rtc gpio
 GPIO gpio1 197 (null)
 GPIO gpio1 198 (null)
 GPIO gpio1 199 (null)
 GPIO gpio1 200 (null)
 GPIO gpio1 201 (null)
 GPIO gpio1 202 (null)
 GPIO gpio1 203 (null)
 GPIO gpio1 204 (null)
 GPIO gpio1 205 (null)
 GPIO gpio1 206 (null)
 GPIO gpio1 207 (null)
 GPIO gpio1 208 (null)
 GPIO gpio1 209 (null)
 GPIO gpio1 210 (null)
 GPIO gpio1 211 (null)
 GPIO gpio1 212 (null)
 GPIO gpio1 213 (null)
 GPIO gpio1 214 (null)
 GPIO gpio1 215 (null)
 GPIO gpio1 216 (null)
 GPIO gpio1 217 (null)
 GPIO gpio1 218 (null)
 GPIO gpio1 219 (null)
 GPIO gpio1 220 (null)
 GPIO gpio1 221 (null)
 GPIO gpio1 222 (null)
 GPIO gpio1 223 (null)
 GPIO gpio2 224 (null)
 GPIO gpio2 225 (null)
 GPIO gpio2 226 (null)
 GPIO gpio2 227 (null)
 GPIO gpio2 228 (null)
 GPIO gpio2 229 (null)
 GPIO gpio2 230 (null)
 GPIO gpio2 231 (null)
 GPIO gpio2 232 (null)
 GPIO gpio2 233 (null)
 GPIO gpio2 234 (null)
 GPIO gpio2 235 (null)
 GPIO gpio2 236 (null)
 GPIO gpio2 237 (null)
 GPIO gpio2 238 (null)
 GPIO gpio2 239 (null)
 GPIO gpio2 240 (null)
 GPIO gpio2 241 (null)
 GPIO gpio2 242 (null)
 GPIO gpio2 243 (null)
 GPIO gpio2 244 (null)
 GPIO gpio2 245 (null)
 GPIO gpio2 246 (null)
 GPIO gpio2 247 (null)
 GPIO gpio2 248 (null)
 GPIO gpio2 249 (null)
 GPIO gpio2 250 (null)
 GPIO gpio2 251 (null)
 GPIO gpio2 252 (null)
 GPIO gpio2 253 (null)
 GPIO gpio2 254 (null)
 GPIO gpio2 255 (null)
 GPIO gpio3 256 (null)
 GPIO gpio3 257 sdmmc-power
 GPIO gpio3 258 mmc0-clk
 GPIO gpio3 259 mmc0-cmd
 GPIO gpio3 260 mmc0-data0
 GPIO gpio3 261 mmc0-data1
 GPIO gpio3 262 mmc0-data2
 GPIO gpio3 263 mmc0-data3
 GPIO gpio3 264 (null)
 GPIO gpio3 265 (null)
 GPIO gpio3 266 ?
 GPIO gpio3 267 (null)
 GPIO gpio3 268 (null)
 GPIO gpio3 269 (null)
 GPIO gpio3 270 (null)
 GPIO gpio3 271 (null)
 GPIO gpio3 272 mmc1-cmd
 GPIO gpio3 273 mmc1-data0
 GPIO gpio3 274 mmc1-data1
 GPIO gpio3 275 mmc1-data2
 GPIO gpio3 276 mmc1-data3
 GPIO gpio3 277 mmc1-clk
 GPIO gpio3 278 tcc_bt_wake
 GPIO gpio3 279 (null)
 GPIO gpio3 280 (null)
 GPIO gpio3 281 ldoonpin
 GPIO gpio3 282 (null)
 GPIO gpio3 283 NULL
 GPIO gpio3 284 (null)
 GPIO gpio3 285 ?
 GPIO gpio3 286 (null)
 GPIO gpio3 287 (null)

My device QX1 is a bit rare, No wifi_power or wifi_reset anounced in the list, it uses 3.3V to feed the wifi chip(rtl8189es SDIO card) instead of 1,8V of the rest of SDIO cards, and in the stock rom and all customs there is a problem: after reboot wifi fail to load again we have to power off totally the device to make wifi work again :P , I am trying to resolve this bug but no luck for the moment.

Kernel boots using 3.0.36+ change in the makefile, so maybe I fail instaling the modules. I am going to test it and I will report back.

Edited: ok kernel is working, wifi and bt working like in the stock rom (with the reboot bug), I am going to change some thinks (rtc gpio and led stay on after power off the device) and clean a bit the code.

[Finless]

Nice job Leolas, I knew you would get it.
I plan to work on a updated QX1 ROM so let me know if you want me to test your kernel for inclusion in the ROM kit.

Bob

[leolas]

Nice job Leolas, I knew you would get it.
I plan to work on a updated QX1 ROM so let me know if you want me to test your kernel for inclusion in the ROM kit.

Bob

Thanks a lot Bob but actually there is the same bug in all sources I try, wifi on reboot, and this one is exasperating me, I tried to contact imito and explain detailed the problem, but they refuse to answer my mails and we must wait for their fixed stock kernel (if it can be done, it can be an hardware problem) to take a reference to fix the customs.
The last custom kernels in http://www.freaktab.com/showthread.p...els-09-09-2013.
I will follow trying to solve it.
And omegamoon (thanks again omegamoon ) gave me some sources for the wifi driver, the next is to try to experiment with them.

[Molle]

1. Could you send me a kernel log of the stock kernel completely booting up Android?
2. I guess you used the MK908 kernel config to build the kernel for the T428. Can you confirm that?

1. Sure, I'll do that tomorrow.

2. I used the Marvin tool with options 'marvin config t428 1080p' to generate the kernel config.

[Omegamoon]

1. Sure, I'll do that tomorrow.

2. I used the Marvin tool with options 'marvin config t428 1080p' to generate the kernel config.

Good news is we got the T428 up and running now, as well as the MK802IV (thanks linuxium!). I'll push the kernel .configs later.

[kbgbef]

MK908v1 with 1080P kernel

Omegamoon, thank you for the excellent work.

I have a MK908v1 on which I am using strauzo's SDK2 Nexus ROM. I have a kernel compiled using Marvin with 1080P FrameBuffer, DDR at 720MHZ and GPU at 600MHZ and I get excellent video playback.

I compiled the new sources with a 1080P FrameBuffer, DDR overclocked to 720MHz and GPU overclocked to 600MHZ (by changing rk3188_mk908_defconfig) and flash it on my MK908v1 along with the boot.img that Omegamoon uploaded to this thread using RKAndroid tool. The device does not boot and is stuck on the GoogleTV logo. Any help is greatly appreciated.

--
Thanks,

[Molle]

I tried to build the kernel this time with the following steps:

• copied an existing kernel config I have used with Marvin to build working kernels as 'arch/arm/configs/rk3188_t428_defconfig'
• copied 'build_omegamoon_mk908' as 'build_omegamoon_t428' and changed the config file parameter to point to the file above
• Edited the TOOLCHAIN parameter in 'build_omegamoon_base' to point to system's own cross compiler (TOOLCHAIN=arm-linux-armeabi-)
• executed './build_omegamoon_t428'
• copied the 3.0.72+ libraries to '/system/lib/modules'
• tested my updated 'boot.img' (rk30xxnand_ko.ko.3.0.72+ included) by rebooting with a working kernel.

The new kernel built fine but still the device won't boot with it.

Here is the dmesg file after a reboot with my working Marvin-built kernel (see the sig):

dmesg.zip

[leolas]

I tried to build the kernel this time with the following steps:

• copied an existing kernel config I have used with Marvin to build working kernels as 'arch/arm/configs/rk3188_t428_defconfig'
• copied 'build_omegamoon_mk908' as 'build_omegamoon_t428' and changed the config file parameter to point to the file above
• Edited the TOOLCHAIN parameter in 'build_omegamoon_base' to point to system's own cross compiler (TOOLCHAIN=arm-linux-armeabi-)
• executed './build_omegamoon_t428'
• copied the 3.0.72+ libraries to '/system/lib/modules'
• tested my updated 'boot.img' (rk30xxnand_ko.ko.3.0.72+ included) by rebooting with a working kernel.

The new kernel built fine but still the device won't boot with it.

Here is the dmesg file after a reboot with my working Marvin-built kernel (see the sig):

[ATTACH]3434[/ATTACH]

I always use my own scripts to build kernel for test, is easy to use the commands:

make ARCH=arm mrproper
make ARCH=arm clean
make ARCH=arm menuconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j2 zkernel.img
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- INSTALL_MOD_PATH=MODULES modules_install

And you discard problems with scripts, I prefer too make a menuconfig the first time to ensure all options and dependencies are ok, using marvin (Great tool to build various kernels with different speeds, thanks phjanderson) there is not the same options in kernel tweaks, or other options are added or missing, so the best for me is check manually in menuconfig the settings. Once we have a stable kernel then we can mod marvin to build multiple configurations in a row.

I have problems with the modules(for sure my fault, maybe i modded the boot and system/lib/modules/ in a bad way) so to test and, discard modules problems and try to contribute I ported back this sources to 3.0.36+ changing in the main Makefile 72 for 36 (like omegamoon suggested to me), and 0 problems at time to boot.

I think that is better to change the version for compatibility and easier rom mod to 3.0.36 so it can be used in the actual stock or modded roms (but this is only my opinion )

[leolas]

I had a question, I can be wrong but only imito QX1 needs in act8846 act_dcdc4 set to 3V and act_ldo6 to 3,3V, so for a more clear code this changes can be resumed in one option in the config. I am ready to submit some changes to omegamoon github and add this option in the pull request, of course omegamoon, if you think you want to keep the current config only ignore them and adapt the code if you want, the changes are for adding suport for RDA5876 BT chip used in the first MK802IV with rtl8188 wifi chip and in my QX1, both used tcc_bt_dev to control BT. And some minor changes to add RTL8189es, support. Some GPIO changes to fit my stock kernel (like an option of course) so this sources can be used to compile a full functional kernel for qx1 (with the wifi on reboot bug like in all stock or custom kernels, I didn’t solved it yet) with wifi and BT

Here is the dmesg:dmesg_QX1_omegamoon.txt

your module for 8189es.ko don’t work in my device, and I cant to make work the sources you gave me (thanks a lot for them anyway, they compiled ok, loads ok, but module don’t work ) so I needed to use the stock module.http://www.freak-tab.de/leolas/8189es.ko here is it if you want to patch it to fit in your 3.0.72 kernel (I dont know how to patch it). But I think for better compatibility port the kernel back to 3.0.36

[Omegamoon]

I had a question, I can be wrong but only imito QX1 needs in act8846 act_dcdc4 set to 3V and act_ldo6 to 3,3V, so for a more clear code this changes can be resumed in one option in the config. I am ready to submit some changes to omegamoon github and add this option in the pull request, of course omegamoon, if you think you want to keep the current config only ignore them and adapt the code if you want, the changes are for adding suport for RDA5876 BT chip used in the first MK802IV with rtl8188 wifi chip and in my QX1, both used tcc_bt_dev to control BT. And some minor changes to add RTL8189es, support. Some GPIO changes to fit my stock kernel (like an option of course) so this sources can be used to compile a full functional kernel for qx1 (with the wifi on reboot bug like in all stock or custom kernels, I didn’t solved it yet) with wifi and BT

Here is the dmesg:[ATTACH]3435[/ATTACH]

your module for 8189es.ko don’t work in my device, and I cant to make work the sources you gave me (thanks a lot for them anyway, they compiled ok, loads ok, but module don’t work ) so I needed to use the stock module.http://www.freak-tab.de/leolas/8189es.ko here is it if you want to patch it to fit in your 3.0.72 kernel (I dont know how to patch it). But I think for better compatibility port the kernel back to 3.0.36

Thanks for the additions leolas, much appreciated! I hope to find some time tomorrow to review and commit your changes.

There's more good news. Tonikasch contacted me that he succeeded in making the kernel work on his mk808 (RK3066) which is excellent news. At the same time I made some adjustments myself to get the kernel running on my mk808b (RK3066) as well. Hopefully I'll have some time tomorrow to do some reviewing, testing and commit all necessary changes to git.

The problems that some of you face with a non-booting device may well be related to the rk30xxnand_ko.ko.3.0.72 kernel module. Linuxium did some investigation there, and it seems there are newer versions of that specific kernel module. We found 3 different versions so far. So if you try to build the kernel and you find it won't boot, please first try to (re)set the kernel revision in the root Makefile to 36 (instead of the current 72) to see if that helps. We'll do some testing with the different modules ourself to find out if there's one version that works across all devices.

Last but not least, I hope more people adopt this kernel. We will try to add as much of the more popular rockchip devices out there, and add more functionality along the way. Is there interest for tablet support as well for instance?

[Legitsu]

ill get that GPIO dump to you as soon as I get a chance to reflash to stock been testing binary patched kernels tho I don't think the problem is a GPIO mismatch as we have sources that work on the v1 and sorta work on the V3 but CPU scaling is broken