[Motorola Droid Bionic] androidifyme:
This is the edit to make modules work in the new kernel you must make the edit in the config.gz, tgen recompile the kernel with the new config

ACTIVATING MODULE LOADING SUPPORT IN THE KERNEL

Module loading support is previously disabled in the kernel, if we want to load modules in the kernel we have to enable it:

edit .config file and set: CONFIG_MODULES=y

We have the new ics, but no overclock or webtop without dock, and some other issues that tge older roms have. And its not because the new leaksare locked. Someone is just lazy or ignorant. So here it goes

You will need alot of free space 100GB or more of free space NO JOKE.

First go here: http://source.android.com/source/initializing.html

You may want androids kernel or cyanogens

androids kernel: http://android.git.kernel.org/

$git clone git://android.git.kernel.org/kernel/common

We check which branch we have downloaded: $git branch it shows * android-2.6.27, not the one we are searching for:

To list all remote available branches: $git branch -r

This is only refernce the kernel number for the bionic is up to 3.0 so when you git branch-r choose one for the bionic

$git checkout --track -b android-goldfish-2.6.29 origin/android-goldfish-2.6.29 $git branch

Cyanogens Follow all steps and restart computer then go here: http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source

After you have installed everything you are ready to create a complete distro from scratch.

Now go to adb and pull your working config.

adb pull /proc/config.gz

$gunzip config.gz # uncompressit. $cp config .config # renameitinto.config

Now you can edit .config file the way it suits you the most.

But really all we want is the modules for overclock and symsearch to be compiled for our new kernel

CROSS_COMPILE environment variable stores the path to the arm cross compiling toolchain. I use the one which comes with android source code.

$ARCH=arm CROSS_COMPILE=/path/to/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make

Executing make will build the kernel.

Last lines will show:

Kernel: arch/arm/boot/Image is ready Kernel: arch/arm/boot/zImage is ready

So we have obtained Image and zImage kernel binary files.

ACTIVATING MODULE LOADING SUPPORT IN THE KERNEL

Module loading support is previously disabled in the kernel, if we want to load modules in the kernel we have to enable it:

edit .config file and set: CONFIG_MODULES=y

$ ARCH=arm CROSS_COMPILE=/path/to/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make

I am asked about some options when executing make. I ask yes for module related options.

After compiling I see several modules have been built.

MODPOST 6 modules CC drivers/video/fb_sys_fops.mod.o LD [M] drivers/video/fb_sys_fops.ko CC drivers/video/syscopyarea.mod.o LD [M] drivers/video/syscopyarea.ko CC drivers/video/sysfillrect.mod.o LD [M] drivers/video/sysfillrect.ko CC drivers/video/sysimgblt.mod.o L drivers/video/sysimgblt.ko CC drivers/video/vfb.mod.o LD [M] drivers/video/vfb.ko

Ok so now we have a kernel that supports modules, but we still need the overclock.so or opptimizer.so compiled for this kernel. This is wete I stop because I dont have any of those modules and this was merely for information really. To get someone to compile our kernel for modular support.