Upgrading Kernel for Working Android X86

[Jeff Singleton]

Hello..

OK so after much research and more research, I finally was able to to compile a custom Kernel v4.0.3 under the latest lollipop-x86 sources.

I know in standard Linux, it is customary to create a initrd.img file, and then also copy the modules into /lib/modules/<kernel version>.

How would I do this for Android X86, so that I can properly test that the kernel works. Because I am certain, since this is a different version kernel, that I would need the initrd.img and modules for the new kernel.

I am not against building the full iso_img so this would be done automatically...but I would like to try this kernel out before going through it all.

NOTE - I currently have the latest kitkat-x86 working for the most part on a dedicated 64GB partition on my ASUS Q302L i5 laptablet. But I have to statically set my IP when connecting to wireless, and I would like to use my GPU instead of UVESA...which is why I am determined to do this new kernel.

Is there a make command that will generate the initrd.img under the out folder and then should I manually copy the modules folder to the proper location under my androidx86 partition?

BTW, for the most part my kernel config is based off the x86_64_defconfig, but updated for kernel 4.0.3, and some minor fine tuning to match this laptop's specs.

Thanks,
Jeff

[Povilas Staniulis]

Done this many times.

I usually build new kernels by replacing the "kernel" directory in Android x86 sources and then doing

make kernel

This will create a new kernel and initrd files in "out" directory.

For modules (they should be somewhere in out directory as well), mount system.img and copy them to /lib/modules/

[Jeff Singleton]

Kool, that is what I figured.

My hopes was to test this with my working Android X86 ... but the make kernel doesn't seem to create the initrd.img.

So I am just going to build the iso_img with my_defconfig, test it with a Live Boot before installing it to my HD partition.

I've got a powerhouse machine I built just for compiling Android on...so it shouldn't take more than a couple of hours.

I will respond again...with results.

[Chih-Wei Huang]

2015-05-31 7:10 GMT+08:00 Jeff Singleton <gvi...@gmail.com>:
> Kool, that is what I figured.
>
> My hopes was to test this with my working Android X86 ... but the make kernel doesn't seem to create the initrd.img.

You don't need to rebuild initrd.img for new kernel.
Just replace the kernel image (bzImage)
and modules in /system/lib/modules.

[Veti]

wouldnt it be a good idea to put  /system/lib/modules in its own image and mount it with along with system.sfs so that changing it becomes it becomes very easy?

[Chih-Wei Huang]

2015-06-06 13:21 GMT+08:00 Veti <aren...@googlemail.com>:
> wouldnt it be a good idea to put /system/lib/modules in its own image and
> mount it with along with system.sfs so that changing it becomes it becomes
> very easy?

Provide a patch, please.