MK908 Kernel upgrade to 3.0.72+

[leolas]

I have the 8189es driver here. Please contact me for a location to share the source.

PM sent.

Adding TCC_BT_DEV driver for BT for the old MK802 and Imito QX1 with rda5876 BT chip. I will send you the patch when I finish it.

[Omegamoon]

I have the 8189es driver here. Please contact me for a location to share the source.

or else you could try attached precompiled module

[leolas]

or else you could try attached precompiled module

Thanks a lot but if you have the sources it can help me a lot. I tried to find this sources but no sucess.

[lewy20041]

how do you flash the kernel, do you use linux or windows?

on windows with finless tools.

[Legitsu]

on windows with finless tools.

did you copy the modules in /system/lib/modules before FLASHING you need todo it that way or its not gonna work
OFC its not gonna boot to ADB without the newer modules ABD Requires the system to boot
do this
1. flash back to a working kernel
2. copy the modules to /system/etc/modules (you will need to mount in @root /w R/W for this)

3. check and make sure you aren't loading any of the older modules either remove them or comment them out in the rc script IN /boot.img/intird
4. power off and flash the new kernel and or boot.img
5. profit

@omegamoon doesn't build here(./build_omegamoon_mk908)

your older tree builds fine this one dies for some reason its not outputting a zimg but there is no errors in the build log that would indicated a problem
I haven't had any issues building older sources

[lewy20041]

why /system/etc/modules and not /system/lib/modules/?:P

[Legitsu]

why /system/etc/modules and not /system/lib/modules/?:P

woops
yep if you wanted to get creative you could just use insmod

[lewy20041]

i deleted all 3.0.36 modules and replaced them with 3.0.72
but it still hungs up after bootlogo:"

[Legitsu]

i deleted all 3.0.36 modules and replaced them with 3.0.72
but it still hungs up after bootlogo:"

should't have Deleted them now you can't flash back to the stock kernel and dump the previous dmsg
you didn't rename the new ones or anything did you ?

[lewy20041]

i just created new firmware with this modules, the names are the same.
i trayed with both with blablabla.ko.3.0.72+ and without like blablabla.ko
and still cant get it to work:"

[freakkid]

This is great news...I came here looking for an upgraded kernel for mk908 as per title..However I see different kernal requests for different devices ..at least provide a mk908 kernel for the forgotton ones or change title to "3188 kernel upgrades to 3.0.72+"

Nevertheless congratulations on developing and refining this kernel...Tronsmart owes you a chunk of change or your efforts...

[Gfunk]

I compiled a new 3.0.72+ kernel and modules and copied the new xxxx.ko.3.0.72+ modules to /system/lib BEFORE flashing kernel and no go here also. I noticed the rk30xxnand_ko.ko.3.0.36+ module is located in the / root directory so if I copy the new rk30xxnand_ko.ko.3.0.72+ to the root directory (with rw permissions) and reboot the module disappears. Maybe this is why we get no boot on the 3.0.72+ kernel.

I noticed also in the init.rc script that the modules that are insmod DO NOT have the 3.0.72+.ko extension so does this mean we should rename mail.3.0.72+ and ump.3.0.72+ to ump.ko and mail.ko for a successful boot?

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/rk30_mirroring.ko
insmod /system/lib/modules/rk29-ipp.ko

Just some thoughts. I can't wait to test this new kernel out

Lewy if you build a successful firmware with this new kernel I would love to beta test my friend!

[Omegamoon]

I compiled a new 3.0.72+ kernel and modules and copied the new xxxx.ko.3.0.72+ modules to /system/lib BEFORE flashing kernel and no go here also. I noticed the rk30xxnand_ko.ko module is located in the / root directory so if I copy the new rk30xxnand_ko.ko.3.0.72+ to the root directory (with rw permissions) and reboot the module disappears. Maybe this is why we get no boot on the 3.0.72+ kernel.

You need to add the rk30xxnand_ko.ko.3.0.72+ to the boot.img otherwise it won't boot Android!

[lewy20041]

yap.
rk30xxnand_ko.ko.3.0.72+ must be in boot.img.
but as of now i cant get it to boot yet.
i will tray tomorow as its late.

[Gfunk]

You need to add the rk30xxnand_ko.ko.3.0.72+ to the boot.img otherwise it won't boot Android!

How do I go about adding modules into the boot.img? Do I just make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- boot.img? Or should I use rktools to repack the firmware with new boot.img and kernel.img?