Thanks you soo much sir for help us kernel things......i halped alot from you,will write a kernel for my devices, i will take ur help if i'm mistaken some steps?
Helped alot sir
Helped alot sir
[REFERENCE] How to compile an Android kernel
- Thread starter nathanchance
- Start date
Sorry, does anyone know how to extract kernel tarball contain linux permission and symlink file or folder on internal/local android storage? I've extracted kernel from lenovo oss but I've problem with loosing actual permission and symlink from compressed kernel oem provide, thanks
Sent from my Redmi 3S using XDA Labs
Sent from my Redmi 3S using XDA Labs
What is the difference of this two
arm-eabi-4.8
And
arm-linux-androideabi-4.9
Because icant fjnd arm-eabi-4.9
arm-eabi-4.8
And
arm-linux-androideabi-4.9
Because icant fjnd arm-eabi-4.9
That really depends. Also if you have to ask, you probably shouldn't attempt it.
E.G. my device's dtsi for voltages and clocks are at " arch/arm/boot/dts/qcom/msm8998-v2.dtsi" If you don't have a pixel 2, 2 XL, OP5 or Z2 force, do not edit that file, it'd be useless. Each chipset uses a different dtsi file.
Last edited:
NepoRood
Recognized Contributor / Retired Forum Moderator
Awesome, built my first "stand alone" kernel! And it Boots! Woot, Woot! :good:
Great write up!
I've followed the steps and attempted to compile for galaxy j7 exynos 7580 kernel.
Ran into some errors, ended up getting past them to only another! Now I understand why you must have patience!
The latest error is,
Which seems like an issues with my toolchain?
I'm sure Ill get past by going through defconfig and checking vdso?
Thanks for this reference, it was very helpful .
I've followed the steps and attempted to compile for galaxy j7 exynos 7580 kernel.
Ran into some errors, ended up getting past them to only another! Now I understand why you must have patience!
The latest error is,
Which seems like an issues with my toolchain?
I'm sure Ill get past by going through defconfig and checking vdso?
Thanks for this reference, it was very helpful .
Last edited:
i was expecting using my device config it will compile flawlessly out of the box but it always stop at the "drivers" part lol
need a little help
trying to compile nexus 6 for android 8.0 using https://github.com/AICP/kernel_moto_shamu/tree/o8.0
i used the google toolchain as stated because up streaming needs patchs, and id like to upstream but im not that good. i get this after i run make:
/home/logan/android_kernel_moto_shamu/scripts/gcc-version.sh: line 25: /home/logan/arm-eabi-4.8gcc: No such file or directory
/home/logan/android_kernel_moto_shamu/scripts/gcc-version.sh: line 26: /home/logan/arm-eabi-4.8gcc: No such file or directory
i did exactly like ZawZaw did
--------------------------------------------------------------------------------------
export CROSS_COMPILE=${HOME}/arm-eabi-4.8
export ARCH=arm && export SUBARCH=arm
make clean && make mrproper
---------------------------------------------------------------------------------------
everything seems to be in the right location and named the correct stuff
https://ibb.co/nvLKsR
my goal is to enable over clocking by modifying the frequency configs, if this cannot be done please let me know.... i haven't found any 8.0 kernels for shamu yet.... please enlighten me
trying to compile nexus 6 for android 8.0 using https://github.com/AICP/kernel_moto_shamu/tree/o8.0
i used the google toolchain as stated because up streaming needs patchs, and id like to upstream but im not that good. i get this after i run make:
/home/logan/android_kernel_moto_shamu/scripts/gcc-version.sh: line 25: /home/logan/arm-eabi-4.8gcc: No such file or directory
/home/logan/android_kernel_moto_shamu/scripts/gcc-version.sh: line 26: /home/logan/arm-eabi-4.8gcc: No such file or directory
i did exactly like ZawZaw did
--------------------------------------------------------------------------------------
export CROSS_COMPILE=${HOME}/arm-eabi-4.8
export ARCH=arm && export SUBARCH=arm
make clean && make mrproper
---------------------------------------------------------------------------------------
everything seems to be in the right location and named the correct stuff
https://ibb.co/nvLKsR
my goal is to enable over clocking by modifying the frequency configs, if this cannot be done please let me know.... i haven't found any 8.0 kernels for shamu yet.... please enlighten me
Last edited:
thank you that allowed make to work, the only documentation on adding frequency at a kernel level iv found is from 2014 for an acer and this kernel doesn't have the cpu frequency configs that i was looking for, could you tell me what im looking for? iv been poking around in the arch/arm but no luck
i was looking at this https://www.youtube.com/watch?v=lBYRLc5GKAI
but what you sent is way better, do you think i would be able to pull that whole file out of a kernel like elementalx? i used that kernel for some time and voltages where perfect.
https://github.com/flar2/shamu/blob/ElementalX-5.00/arch/arm/boot/dts/qcom/apq8084.dtsi
comparing this one to the one from your link i know elementalx allows for a 3.0 ghz overclock but it may be applying it in ramdisk.... do you think if i add a frequency in the current and frequency list for each cpu that it would use it?
Last edited:
Code:
git fetch https://github.com/flar2/shamu ElementalX-5.00
git cherry-pick eb8d56044571a4e597e7665aef1edcc4e2c1bd95That's the proper way to add the change from one kernel to another.
Code:
git fetch <repo_url> <branch_name>
git cherry-pick <commit_hash>I have been trying to build a kernel for my mediatek device for a while now. I was given an incomplete kernel source and now it does not build when I use "make zImage".
It always gets stuck at xt_TCPMSS.c with this error:
There are no other errors.
Here is my kernel source (due to issues with travis-ci, the true stock branch is stock2 and dev is "stock"): https://github.com/Qiangong2/android_kernel_blu_d790q
I'm worried that just copying the xt_TCPMSS.c file from another MT6580 device may brick my device. That is why I have not tried that yet.
It always gets stuck at xt_TCPMSS.c with this error:
Code:
net/netfilter/xt_TCPMSS.c: In function 'tcpmss_mt':
net/netfilter/xt_TCPMSS.c:64:26: error: dereferencing pointer to incomplete type
return (mssval >= info->mss_min &&
^
net/netfilter/xt_TCPMSS.c:65:19: error: dereferencing pointer to incomplete type
mssval <= info->mss_max) ^ info->invert;
^
net/netfilter/xt_TCPMSS.c:65:36: error: dereferencing pointer to incomplete type
mssval <= info->mss_max) ^ info->invert;
^
net/netfilter/xt_TCPMSS.c:73:13: error: dereferencing pointer to incomplete type
return info->invert;
^
net/netfilter/xt_TCPMSS.c: At top level:
net/netfilter/xt_TCPMSS.c:85:23: error: invalid application of 'sizeof' to incomplete type 'struct xt_tcpmss_match_info'
.matchsize = sizeof(struct xt_tcpmss_match_info),
^
net/netfilter/xt_TCPMSS.c:93:23: error: invalid application of 'sizeof' to incomplete type 'struct xt_tcpmss_match_info'
.matchsize = sizeof(struct xt_tcpmss_match_info),
^
scripts/Makefile.build:257: recipe for target 'net/netfilter/xt_TCPMSS.o' failedThere are no other errors.
Here is my kernel source (due to issues with travis-ci, the true stock branch is stock2 and dev is "stock"): https://github.com/Qiangong2/android_kernel_blu_d790q
I'm worried that just copying the xt_TCPMSS.c file from another MT6580 device may brick my device. That is why I have not tried that yet.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
1
sorry I haven't tried, I'm also newbie. I will try first and may tell you if success -
240Introduction
Hello everyone, I will be going over how to compile a kernel from beginning to end!
Prerequisites:
- A Linux environment (preferably 64-bit)
- Knowledge of how to navigate the command line
- Common sense
- A learning spirit, there will be no spoonfeeding here
What this guide will cover:
- Downloading the source
- Downloading a cross compiler
- Building the kernel
- Flashing the kernel
What this guide will NOT cover:
- Setting up a build environment (plenty of existing Linux installation guides)
- Adding features to the kernel (plenty of git cherry-picking guides)
I know this has been done before but on a cursory search, I have not seen a guide that was recently updated at all.
1. Downloading the source
2. Downloading a cross compiler
3. Compile the kernel
4. Flash the kernel
Tips and tricks
Receiving help
I am happy to answer anything that I touched on in this guide. I may point you to another thread if it's better suited but I don't mind off topic (within reason) within the thread. I also want this to be a collaborative effort; other developers, if you have something to add, correct, or improve upon, please let me know!
I am particular in how people ask for help. I do NOT respond to posts asking for a hand out ("How do I fix this?", "Please fix this!", etc.). I only respond to posts with clear logs and steps that you have tried. Basically, show me that you have read this guide and have a specific issue. I am not here to hold your hand through this, this is a developers' forum.20Compile Android Pie kernels for the Pixel (XL) and Pixel 2 (XL)
Google added a new compat vDSO on Android Pie for 32-bit userspace, which requires a 32-bit toolchain (commit). As a result, if CROSS_COMPILE_ARM32 is not set, your build will error.
After setting your main CROSS_COMPILE in step 1, clone this toolchain (or another compatible arm toolchain) next to the aarch64 one (if in the toolchain folder after running 'export CROSS_COMPILE', type 'cd ..'). Move into the 32-bit toolchain folder using cd then run
Example:Code:export CROSS_COMPILE_ARM32=$(pwd)/bin/<toolchain_prefix>
Code:export CROSS_COMPILE_ARM32=$(pwd)/bin/arm-linux-androideabi-
Then continue on with the rest of the steps.98
Unfortunately, my time nowadays is limited between my job, school, and more important open source projects.
However, compiling with GCC 9.2.0 is the same as compiling with GCC 4.9.4, you point the CROSS_COMPILE variable at the GCC 9.2.0 toolchain (or use PATH and update the CROSS_COMPILE prefix to match) and go from there. There are probably going to be new warnings that you will need to solve and there are potentially some other commits that you will need to pick to get a boot off.
If anyone else wants to pitch in and write something up, I'd be happy to add it to the OP.
