Develop Bugs

Help needed compiling the kernel

So... I download the kernel source from HTC (http://developer.htc.com) and I found this blog that got me started on compiling it...
http://blog.coralic.nl/2009/10/25/how-to-compile-the-htc-hero-kernel/comment-page-1/#comment-42
Well, at first attempt, I got an error that make couldn't find the rule to make projector.o. Well, I went through the .config and changed that option to No...
Then, it gets all the way to where it looks like it's going to make vmlinux1 and it errors out with the message "arm-eabi-ld: no machine record defined .... make: *** [.tmp_vmlinux1] Error 1"
Has anybody successfully compiled the source yet?

jmanley69 said:
So... I download the kernel source from HTC (http://developer.htc.com) and I found this blog that got me started on compiling it...
http://blog.coralic.nl/2009/10/25/how-to-compile-the-htc-hero-kernel/comment-page-1/#comment-42
Well, at first attempt, I got an error that make couldn't find the rule to make projector.o. Well, I went through the .config and changed that option to No...
Then, it gets all the way to where it looks like it's going to make vmlinux1 and it errors out with the message "arm-eabi-ld: no machine record defined .... make: *** [.tmp_vmlinux1] Error 1"
Has anybody successfully compiled the source yet?
Click to expand...
Click to collapse
Try "make msm7200a_defconfig" before compiling, do not pull config.gz.

Lox_Dev said:
Try "make msm7200a_defconfig" before compiling, do not pull config.gz.
Click to expand...
Click to collapse
That was a very good starting point...
It all comes down to these two lines
On the config from my phone it says
Code:
# CONFIG_ARCH_MSM7200A is not set
CONFIG_ARCH_MSM75010A=y
on msm7200a_defconfig, it has
Code:
CONFIG_ARCH_MSM7200A=y
# CONFIG_ARCH_MSM75010A is not set
Also, msm7200a_defconfig has these two extra lines that don't exist at all in my config
Code:
CONFIG_MACH_SAPPHIRE=y
CONFIG_MACH_HERO=y
That wouldn't be too big a problem, but my config has
Code:
# CONFIG MSM_AMSS_SUPPORT_256MB_EBI1 is not set
and msm7200a_defconfig has
Code:
CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
and without that set, SAPPHIRE.o won't compile because an integer is long instead of unsigned....
Any idea how I can figure out the correct file to fix for the CONFIG_ARCH_MSM75010A? I looked in /arch/arm/Makefile, and it says ARCH_MSM7XXXX points to msm, and I look in /arch/arm/msm/Makefile, and don't see anything referencing either MSM7200A or MSM75010A, but 7200A has to be someplace

Standard config pulled from running 1.5 should compile just fine.
Done it countless times myself.
What version of the toolchain are you running?

packetlss said:
Standard config pulled from running 1.5 should compile just fine.
Done it countless times myself.
What version of the toolchain are you running?
Click to expand...
Click to collapse
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin

Just tried it myself with the same toolchain:
Code:
[email protected]:~/android/kernel/kernel_hero$ [B]cp config-gsm-stock .config[/B]
[email protected]:~/android/kernel/kernel_hero$ [B]CROSS_COMPILE=~/android/src/aosp/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make[/B]
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
...
<lots of muck removed>
....
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gz
AS arch/arm/boot/compressed/piggy.o
CC arch/arm/boot/compressed/misc.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Building modules, stage 2.
MODPOST 0 modules
[email protected]:~/android/kernel/kernel_hero$ [B]ls -al arch/arm/boot/zImage[/B]
-rwxr-xr-x 1 mange mange 1648748 2009-12-05 02:13 arch/arm/boot/zImage
[email protected]:~/android/kernel/kernel_hero$
The error your getting is usually due to a incomplete machine specification for the linker.
Try and checkout the prebuilt stuff again from AOSP, it's possibly corrupted.
Mine is master branch, synced yesterday.

kernel compiling

did someone could provide a minimal guide for compile kernel ? got some problem with using gcc prebuilt in samsung source. can you tell what defconfig you used ?
once used defconfig versatile_defconfig and .config saved i have got the following error:
[email protected]:~/Downloads/android-source/GalaxyS/linux-2.6.29# make ARCH=arm CROSS_C
OMPILE=/root/Downloads/android-source/opensrc/prebuilt/linux-x86/toolchain/arm-e
abi-4.2.1/bin/arm-eabi-
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CALL scripts/checksyscalls.sh
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
CC init/main.o
In file included from init/main.c:79:
include/linux/kernel_sec_common.h:9:22: error: mach/map.h: No such file or direc
tory
include/linux/kernel_sec_common.h:10:29: error: plat/regs-clock.h: No such file
or directory
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
I tried also with s3c6400_config with the following error:
[email protected]:~/Downloads/android-source/GalaxyS/linux-2.6.29# make ARCH=arm CROSS_C
OMPILE=/root/Downloads/android-source/opensrc/prebuilt/linux-x86/toolchain/arm-e
abi-4.2.1/bin/arm-eabi-
scripts/kconfig/conf -s arch/arm/Kconfig
net/ipv6/netfilter/Kconfig:165:warning: config symbol defined without type
CHK include/linux/version.h
Generating include/asm-arm/mach-types.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
GEN include/linux/bounds.h
CC arch/arm/kernel/asm-offsets.s
GEN include/asm/asm-offsets.h
CALL scripts/checksyscalls.sh
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/ihex2fw
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
CC init/main.o
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
CC init/do_mounts.o
CC init/do_mounts_rd.o
CC init/do_mounts_initrd.o
LD init/mounts.o
CC init/initramfs.o
CC init/calibrate.o
LD init/built-in.o
HOSTCC usr/gen_init_cpio
GEN usr/initramfs_data.cpio.gz
AS usr/initramfs_data.o
LD usr/built-in.o
CC arch/arm/kernel/compat.o
CC arch/arm/kernel/elf.o
AS arch/arm/kernel/entry-armv.o
AS arch/arm/kernel/entry-common.o
CC arch/arm/kernel/irq.o
CC arch/arm/kernel/process.o
arch/arm/kernel/process.c: In function 'arm_machine_restart':
arch/arm/kernel/process.c:107: error: 'S5P_INFORM5' undeclared (first use in thi
s function)
arch/arm/kernel/process.c:107: error: (Each undeclared identifier is reported on
ly once
arch/arm/kernel/process.c:107: error: for each function it appears in.)
make[1]: *** [arch/arm/kernel/process.o] Error 1
make: *** [arch/arm/kernel] Error 2

How about pulling the config directly from the device, did you try that? (BTW I didn't get to compiling just yet, I only have SGS for two busy days now, so no direct experience yet, just asking).

Case_ said:
How about pulling the config directly from the device, did you try that? (BTW I didn't get to compiling just yet, I only have SGS for two busy days now, so no direct experience yet, just asking).
Click to expand...
Click to collapse
dont know if and where the config is stored on SGS, apparently theres no .config

I have downloaded the AOSP eclair build and am trying to compile it.
It's still compiling.
I believe(stress on believe) you have to download the Samsung firmware from wesgamer and he has a sh file that gets rid of dream and other htc code.
Also he might have a different config
I am not experienced at android rom compiling.
Please take extreme care with whatever you do.
HOLY CRAP!!! I'm so sorry. I must have missed the readme.txt
Follow neldar.

If you have the latest sourcecode from opensource.samsung.com
then you should take a look into the README.txt and build_kernel.sh.
Everything you need to know to successfully build the kernel + modules is described in these files.

husq510 said:
dont know if and where the config is stored on SGS, apparently theres no .config
Click to expand...
Click to collapse
Yeah, sorry, I thought it could be pulled from /proc/config.gz as usual and didn't verify, but as I see now with adb, apparently Samsung has this disabled in their kernel.

I've compiled the kernel as per the readme file, but after I flash it, I get a kernel panic. Are there any other steps needed that are not in the readme? The kernel I created is around 2.5mb

vibez said:
I've compiled the kernel as per the readme file, but after I flash it, I get a kernel panic. Are there any other steps needed that are not in the readme? The kernel I created is around 2.5mb
Click to expand...
Click to collapse
you need the initramfs (contains the initial / with drivers and other stuff). check out this http://forum.samdroid.net/wiki/show...amsung+Spica+i5700?highlight=zImage+initramfs it's not for the i9000 but it works like that. you just have to take the other initramfs.
hope this helps, i just got it finished here myself
edit:
* my zImage is 6051460 bytes ...
* the right initramfs is also on leshak's git. explanation is on samdroid.net

Hi there,
I 've followed the instrucions in the README.txt.
No errors, but my zImage is just 2.5 mb
I assume the .config which is in the linux-2.6.29 directory is default one.The only change I made is to enable USB_ETH for RNDIS support.
make menuconfig
then
build kernel
Am i missing something?
I recompiled serveral time the linux kernel on standard computers, this time it might need a different setup.
thanks
Found that there is this useful discussion already
http://forum.xda-developers.com/showthread.php?t=727357

gettons said:
I 've followed the instrucions in the README.txt.
No errors, but my zImage is just 2.5 mb
I assume the .config which is in the linux-2.6.29 directory is default one.The
...
Am i missing something?
Click to expand...
Click to collapse
please read before posting! you are missing initramfs as i wrote in my post above yours!

I'm getting confused with the linking of capela_defconfig
Can anyone explain in more detail please
EDIT: Ok it seems the build script is overwriting whatever I set in the .config file
EDIT 2 Ok it seems .config gets overwritten by contents of arc/arm/configs/aries_rev03_defconfig
So I added the 3 lines about initramfs to the aries_rev03_defconfig and changed the path to now point towards the source downloaded from github. Compiling now....

ups. sorry. delete plz anyone?

Ok it seems the build script is overwriting whatever I set in the .config file
Click to expand...
Click to collapse
yeah i had this too so i didn't use the build_kernel.sh script. just make ARCH=arm CROSS_COMPILE=tool-chain-path_and_prefix after make menuconfig. worked like a charm. have you tried to boot your kernel yet?

No I still get a file 2.5mb in size
Can you point me in the right direction?
Which config file are you using?

anyone has a mirror of the source code #2 posted sometime back? samsung hv removed from their site.. dont know if the current source code is the old or new code (#2)..

vibez said:
No I still get a file 2.5mb in size
Can you point me in the right direction?
Which config file are you using?
Click to expand...
Click to collapse
i did a "./build_kernel.sh Clean"
then i made "make menuconfig" and set the initramfs from leshak. you have to modify the initrd.arm.initramfs_list file to fit your file tree.
after that i did the make .... in the "linux-2.6.29" directory
edit: i did not change the .config file!
raspdeep said:
anyone has a mirror of the source code #2 posted sometime back? samsung hv removed from their site.. dont know if the current source code is the old or new code (#2)..
Click to expand...
Click to collapse
i think the currently available code is the newest one. it's slightly bigger and contains the build scripts/readme etc. additionally i had problems with uncompressing the code with the linux zip program. i suspect the archive was damaged somehow...

mine is 6MB, using the .config default and leshak initramfs and just make ARCH=arm CROSS_COMPILE=path-gcc
didnt use build_kernel.sh at all.

If you want to change the .config, then you should run once build_kernel.sh and then comment out line 75 in build_kernel.sh , like this:
Code:
#make ARCH=arm $PROJECT_NAME"_rev"$HW_BOARD_REV"_defconfig"
This will keep your .config and you could still use build_kernel.sh.

neldar said:
If you want to change the .config, then you should run once build_kernel.sh and then comment out line 75 in build_kernel.sh , like this:
Code:
#make ARCH=arm $PROJECT_NAME"_rev"$HW_BOARD_REV"_defconfig"
This will keep your .config and you could still use build_kernel.sh.
Click to expand...
Click to collapse
Thanks, I've commented out that line and it seems to be actually trying to load initramfs now
you have to modify the initrd.arm.initramfs_list file to fit your file tree.
Click to expand...
Click to collapse
Ah, I didn't realise the contents of this file needed to be edited too (I see now it's pointed to leshak's folder tree). So i've made the changes to point to my initramfs dir and recompiling now. Fingers crossed this time.....
EDIT
Success! I now have an image 6003928 bytes in size Thanks for all the help!
Right, any tips on how to patch in ext4 support?

i flashed my kernel before and it does work quite well. i am not able to root with the update.zip however. adb gives me root access to the device but i can not get root directly on the phone (#su gives me "su: uid 10085 not allowed to su"). this is quite strange because the root methods works well with the stock kernel...hm

Can Anyone Get a Kernel Working?

I've tried a hundred different settings, tweaking Samsung's original c1_rev05_na_spr_defconfig file.
c1_rev05_na_spr_defconfig is the .config file given by Samsung in the open source code for those of you who don't know.
When you can correctly compile the kernel with the settings in this .config file, you should be able to end up with a stock zImage that works but right now, these kernels end up in a boot-loop or boot-freeze.
I suspect it's settings in the .config file (off the c1_rev05_na_spr_defconfig) that could be at fault. I am not an expert at this (by any means) but perhaps those of you who are can recommend me any changes to the settings.
There's also an older c1_rev02_na_spr_defconfig but it doesn't compile so...

as ive stated in other threads, you wanna double check your kernels use tools to unpack the zimage.. if you dont have the initramfs in there then its not gunna boot

shabbypenguin said:
as ive stated in other threads, you wanna double check your kernels use tools to unpack the zimage.. if you dont have the initramfs in there then its not gunna boot
Click to expand...
Click to collapse
It's definitely in there, here's a copy and paste from my make menuconfig:
[ ] Namespaces support x x
x x [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support x x
x x () Initramfs source file(s) x x
x x [*] Support initial ramdisks compressed using gzip x x
x x [ ] Support initial ramdisks compressed using bzip2 x x
x x [ ] Support initial ramdisks compressed using LZMA x x
x x [ ] Support initial ramdisks compressed using LZO

Bro, it's not that simple, you have to set the initramfs path in the config to a folder on your local machine and what Shabby is saying is that nobody has unpacked the stock zImage on the phone (or found out how to) to have an initramfs to load into the zImage you are compiling.
Just find a way to pull the stock zImage and unpack the initramfs and load the correct path, or it will keep having the same problems.

bubby323 said:
Bro, it's not that simple, you have to set the initramfs path in the config to a folder on your local machine and what Shabby is saying is that nobody has unpacked the stock zImage on the phone (or found out how to) to have an initramfs to load into the zImage you are compiling.
Just find a way to pull the stock zImage and unpack the initramfs and load the correct path, or it will keep having the same problems.
Click to expand...
Click to collapse
Ok, I actaully tried unpacking initramfs from zImage but it seems like it doesn't exist....

zedomax said:
Ok, I actaully tried unpacking initramfs from zImage but it seems like it doesn't exist....
Click to expand...
Click to collapse
..and that is the problem. Without the initramfs android WILL NOT boot, since it doesn't know how, the zImage itself only houses the drivers and such. It's useless without the initramfs.

bubby323 said:
..and that is the problem. Without the initramfs android WILL NOT boot, since it doesn't know how, the zImage itself only houses the drivers and such. It's useless without the initramfs.
Click to expand...
Click to collapse
can something like this work?
http://forum.xda-developers.com/showthread.php?t=777380
---------- Post added at 05:05 PM ---------- Previous post was at 05:02 PM ----------
Here's my build output during compile, it seems like initramfs has been compiled correctly, no?
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/initramfs.o
CC arch/arm/kernel/setup.o
CC arch/arm/kernel/traps.o
CC arch/arm/kernel/machine_kexec.o
AS arch/arm/kernel/relocate_kernel.o
CC arch/arm/kernel/atags.o
CC kernel/panic.o
CC kernel/printk.o
LD init/built-in.o
CC drivers/base/cpu.o
LD arch/arm/kernel/built-in.o
CC kernel/sys.o
LD drivers/base/built-in.o
CC kernel/ksysfs.o
CC kernel/kexec.o
LD drivers/built-in.o
LD kernel/built-in.o
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 13 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Building modules, stage 2.
MODPOST 6 modules
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gzip
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready

It may compile correctly but your not injecting the initramfs into it...so it won't boot your phone.

bubby323 said:
It may compile correctly but your not injecting the zImage into it...so it won't boot your phone.
Click to expand...
Click to collapse
injecting the zImage to where?

zedomax said:
injecting the initramfs to where?
Click to expand...
Click to collapse
The initramfs into the zImage.

bubby323 said:
The initramfs into the zImage.
Click to expand...
Click to collapse
This is pretty frustrating, didn't have to do that on HTC open source, it shouldn't be so hard to compile a kernel, ARGHHH, I am about to give up.

Never give up, just find somebody to pull the stock zImage.

bubby323 said:
Never give up.
Click to expand...
Click to collapse
Yeah, don't give up. Good things take time
Sent from my SPH-D700 using xda premium

I can do this but I have no idea how to flash to and use odin
Sent from my sprint galaxy s2

bbedward said:
I can do this but I have no idea how to flash to and use odin
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
Compile the kernel, then compress zImage it using tar:
tar cvf blahblah.tar zImage
Use Odin and select blahblah.tar under PDA then hit Start.
But don't do this as the kernel will put you in bootloop or boot freeze for now.

I get that much, but is the tar supposed to be setup with the same directory structure as the phone?

That's the .pit files job bro.

Yea this is my first samsung experience lol
Sent from my sprint galaxy s2

thanks bubby, i kept saying it again and again.. yet no one was listening
anyways only way we are gunna get it is by having root

shabbypenguin said:
thanks bubby, i kept saying it again and again.. yet no one was listening
anyways only way we are gunna get it is by having root
Click to expand...
Click to collapse
Well... Whosdaman or Korey usually releases the tars for odin on officail releases... S lets hope for that..
Sent from my SPH-D710 using XDA App

help rebuilding/install CM10 kernel (I get a bootloop)

has anyone here rebuilt the CM10 nightly kernel before? I am trying to rebuild it and install it myself (which I've done on many other devices), but for some reason after installing my kernel I'm getting stuck in a bootloop.
I have a SGS3 AT&T, but from what I've read all US versions use a unified kernel. By digging through the Cyanogenmod github repositories, I found that this is the CM10 kernel:
https://github.com/CyanogenMod/android_kernel_samsung_d2
The kernel configuration that it ends up using is: cyanogen_d2_defconfig ... so to build the kernel I do:
Code:
make ARCH=arm clean
make ARCH=arm cyanogen_d2_defconfig
make -j2 ARCH=arm CROSS_COMPILE=arm-eabi-
Now, I need to create boot.img and pack the ramdisk. I extracted the ramdisk from one of the CM10 nightlies, and I do:
Code:
./mkbootfs ramdisk | gzip > ramdisk.gz
cp arch/arm/boot/zImage .
./mkbootimg --kernel zImage --ramdisk ramdisk.gz --cmdline "androidboot.hardware=qcom user_debug=31" -o boot.img --base 0x80200000 --pagesize 2048
I got the command line using unpackbootimg:
Code:
$ ../unpackbootimg -i boot.img
BOARD_KERNEL_CMDLINE androidboot.hardware=qcom user_debug=31
BOARD_KERNEL_BASE 80200000
BOARD_PAGE_SIZE 2048
Finally, I took the updater script from this kernel, replacing its boot.img with my boot.img, as well as placing my kernel modules in system/lib/modules. In the end, I have no created the following update zip file to flash in CWM. Feel free to download it and verify the updater script, however here is the updater code:
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
unmount("/system");
assert(package_extract_file("boot.img", "/cache/boot.img"),
write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7"),
delete("/cache/boot.img"));
show_progress(0.100000, 0);
But like I said, whenever I go to install this kernel it just gives me a bootloop, so something doesn't seem right. I get no errors/warnings when building the kernel, I extracted the ramdisk correctly... can anyone pick out something I'm missing? maybe mkbootimg?
Thanks!

Why do you need to do this?
Sent from my SGH-I747 using xda app-developers app

because I'm creating a custom kernel, and I figured before I modified it I would just try a simple rebuild...

Look at my repo and match up everything or just use it whole and create the folders for Package and Ramdisk that it wants, then replace the toolchain/cross_compile that I use with the path of yours.
Build script:
https://github.com/ktoonsez/KT747-JB/blob/jellybean/build_d2att_aosp.sh
Alos replace your existing "mkbootfs" and "mkbootimg" files with mine.

thanks a bunch for the pointer to your scripts! I am now using your mkbootfs and mkbootimg, and I also noticed that you included the following in your mkbootimg, which I didn't:
Code:
--ramdiskaddr 0x81500000
So, I added this and now I actually boot but my screen is not working I get the Samsung logo, then the Samsung Galaxy SIII boot screen, then my screen never turns on. I am able to grab dmesg and logcat now though, so I am digging through to narrow down the problem as I continue to go through your scripts!

if I don't want to overclock with my kernel, can I skip including 00post-init.sh which runs these commands:
Code:
#Set governor items
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo 1512000 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq;
echo 1512000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo $(date) END of post-init.sh

I was trying to jump on the bandwagon and build KT747 but I encounter the following errors:
Code:
/home/trevor/programming/android/linaro4.7/bin/arm-eabi-ld: error: arch/arm/boot/compressed/piggy.gzip.o: unknown CPU architecture
/home/trevor/programming/android/linaro4.7/bin/arm-eabi-ld: error: arch/arm/boot/compressed/lib1funcs.o: unknown CPU architecture
/home/trevor/programming/android/linaro4.7/bin/arm-eabi-ld: error: arch/arm/boot/compressed/ashldi3.o: unknown CPU architecture
Anyone know why this is happening? I am using GCC 4.7 and the appropriate toolchain. More detailed log: http://pastebin.com/Kb3PWYtq

so I am still having issues where my phone goes through the entire boot process, but my screen does not re-activate after the Samsung Galaxy SIII logo. So I never end up seeing the Cyanogen animation.
Here are relevant logs:
No screen logcat: http://pastebin.com/W4v6Xk9g
No screen dmesg: http://pastebin.com/ydGtj216
With screen logcat: http://pastebin.com/DjENx2gE
With screen dmesg: http://pastebin.com/f3sAzjZa
The "with screen" cases are using the prebuilt CM10 nightlies

Rocket Nine said:
I was trying to jump on the bandwagon and build KT747 but I encounter the following errors:
Code:
/home/trevor/programming/android/linaro4.7/bin/arm-eabi-ld: error: arch/arm/boot/compressed/piggy.gzip.o: unknown CPU architecture
/home/trevor/programming/android/linaro4.7/bin/arm-eabi-ld: error: arch/arm/boot/compressed/lib1funcs.o: unknown CPU architecture
/home/trevor/programming/android/linaro4.7/bin/arm-eabi-ld: error: arch/arm/boot/compressed/ashldi3.o: unknown CPU architecture
Anyone know why this is happening? I am using GCC 4.7 and the appropriate toolchain. More detailed log: http://pastebin.com/Kb3PWYtq
Click to expand...
Click to collapse
where did you download your linaro 4.7 binaries from?

Components > Android > android-toolchain 4.7 (ICS, JB)
http://www.linaro.org/downloads/
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Rocket Nine said:
Components > Android > android-toolchain 4.7 (ICS, JB)
http://www.linaro.org/downloads/
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
thanks! So, in another thread ktoonsez said to use the :June 2012 build. That one seems to be from September. Here is the June link:
http://releases.linaro.org/12.06/co...12.06-3-2012-06-19_14-52-07-linux-x86.tar.bz2

using the June toolchain, the kernel almost builds entirely successfully until the last few links when I get these errors:
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Building modules, stage 2.
MODPOST 13 modules
Kernel: arch/arm/boot/Image is ready
CC arch/arm/mach-msm/dma_test.mod.o
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/mach-msm/msm-buspm-dev.mod.o
CC arch/arm/mach-msm/reset_modem.mod.o
CC crypto/ansi_cprng.mod.o
CC drivers/crypto/msm/qce40.mod.o
CC drivers/crypto/msm/qcedev.mod.o
CC drivers/crypto/msm/qcrypto.mod.o
CC drivers/input/evbug.mod.o
CC drivers/media/video/gspca/gspca_main.mod.o
CC drivers/net/wireless/bcmdhd/dhd.mod.o
CC drivers/net/wireless/btlock/btlock.mod.o
CC drivers/scsi/scsi_wait_scan.mod.o
CC drivers/spi/spidev.mod.o
LD [M] arch/arm/mach-msm/dma_test.ko
CC arch/arm/boot/compressed/misc.o
LD [M] arch/arm/mach-msm/msm-buspm-dev.ko
LD [M] arch/arm/mach-msm/reset_modem.ko
LD [M] crypto/ansi_cprng.ko
LD [M] drivers/crypto/msm/qce40.ko
LD [M] drivers/crypto/msm/qcedev.ko
LD [M] drivers/crypto/msm/qcrypto.ko
LD [M] drivers/input/evbug.ko
LD [M] drivers/media/video/gspca/gspca_main.ko
LD [M] drivers/net/wireless/bcmdhd/dhd.ko
CC arch/arm/boot/compressed/decompress.o
LD [M] drivers/net/wireless/btlock/btlock.ko
LD [M] drivers/scsi/scsi_wait_scan.ko
LD [M] drivers/spi/spidev.ko
CC arch/arm/boot/compressed/string.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
SHIPPED arch/arm/boot/compressed/ashldi3.S
AS arch/arm/boot/compressed/piggy.gzip.o
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/ashldi3.o
LD arch/arm/boot/compressed/vmlinux
/home/owner/Documents/android-wmon/core/linaro-android-toolchain/bin/arm-eabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and output
/home/owner/Documents/android-wmon/core/linaro-android-toolchain/bin/arm-eabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o and output
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2

hedpe said:
using the June toolchain, the kernel almost builds entirely successfully until the last few links when I get these errors:
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Building modules, stage 2.
MODPOST 13 modules
Kernel: arch/arm/boot/Image is ready
CC arch/arm/mach-msm/dma_test.mod.o
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/mach-msm/msm-buspm-dev.mod.o
CC arch/arm/mach-msm/reset_modem.mod.o
CC crypto/ansi_cprng.mod.o
CC drivers/crypto/msm/qce40.mod.o
CC drivers/crypto/msm/qcedev.mod.o
CC drivers/crypto/msm/qcrypto.mod.o
CC drivers/input/evbug.mod.o
CC drivers/media/video/gspca/gspca_main.mod.o
CC drivers/net/wireless/bcmdhd/dhd.mod.o
CC drivers/net/wireless/btlock/btlock.mod.o
CC drivers/scsi/scsi_wait_scan.mod.o
CC drivers/spi/spidev.mod.o
LD [M] arch/arm/mach-msm/dma_test.ko
CC arch/arm/boot/compressed/misc.o
LD [M] arch/arm/mach-msm/msm-buspm-dev.ko
LD [M] arch/arm/mach-msm/reset_modem.ko
LD [M] crypto/ansi_cprng.ko
LD [M] drivers/crypto/msm/qce40.ko
LD [M] drivers/crypto/msm/qcedev.ko
LD [M] drivers/crypto/msm/qcrypto.ko
LD [M] drivers/input/evbug.ko
LD [M] drivers/media/video/gspca/gspca_main.ko
LD [M] drivers/net/wireless/bcmdhd/dhd.ko
CC arch/arm/boot/compressed/decompress.o
LD [M] drivers/net/wireless/btlock/btlock.ko
LD [M] drivers/scsi/scsi_wait_scan.ko
LD [M] drivers/spi/spidev.ko
CC arch/arm/boot/compressed/string.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
SHIPPED arch/arm/boot/compressed/ashldi3.S
AS arch/arm/boot/compressed/piggy.gzip.o
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/ashldi3.o
LD arch/arm/boot/compressed/vmlinux
/home/owner/Documents/android-wmon/core/linaro-android-toolchain/bin/arm-eabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and output
/home/owner/Documents/android-wmon/core/linaro-android-toolchain/bin/arm-eabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o and output
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
Click to expand...
Click to collapse
I am having the same errors now but this post apparently has a fix. Trying now.

Rocket Nine said:
I am having the same errors now but this post apparently has a fix. Trying now.
Click to expand...
Click to collapse
thanks! tried that fix but getting some memcpy issue despite string.h being included... still digging!

hedpe said:
thanks! tried that fix but getting some memcpy issue despite string.h being included... still digging!
Click to expand...
Click to collapse
Try replacing your arch/arm/boot/compressed/Makefile with this http://pastebin.com/J0m6ka26
It compiles successfully now :good:

Rocket Nine said:
Try replacing your arch/arm/boot/compressed/Makefile with this http://pastebin.com/J0m6ka26
It compiles successfully now :good:
Click to expand...
Click to collapse
Thanks bud! I'm having one last error, not sure if it was an issue with your paste:
Code:
/home/owner/Documents/android-wmon/core/KT747-JB/arch/arm/boot/compressed/Makefile:112: *** missing separator. Stop.
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
Here is the relevant part of the Makefile:
Code:
$(addprefix $(obj)/,$(libfdt) $(libfdt_hdrs)): $(obj)/%: $(srctree)/scripts/dtc/libfdt/%
$(call cmd,shipped) <----- this is line 112
The odd thing is that this exists in the original Makefile unmodified
----
EDIT: Sorry! I got this working now, it was an issue with tabs/spaces from copying and pasting

I believe that is caused by wrong indentation. Did you copy the code from the webpage? My browser (Chrome) copies the tabs as spaces. Try downloading the paste and flat out replace the file with it.
I copied the META-INF folder out of a KT747 zip to my build and according to TWRP it flashes successfully. Now we are on the same page with the boot loop.

Rocket Nine said:
I believe that is caused by wrong indentation. Did you copy the code from the webpage? My browser (Chrome) copies the tabs as spaces. Try downloading the paste and flat out replace the file with it.
I copied the META-INF folder out of a KT747 zip to my build and according to TWRP it flashes successfully. Now we are on the same page with the boot loop.
Click to expand...
Click to collapse
Thanks a bunch! I got it to build successfully.
I'm officially dumbfounded. I no longer get the bootloop in either one of my kernels (stock CM10 or the KT747 rebuild), but in both cases my phone boots without the display working. I have NO clue why my display doesn't work when I rebuild these kernels.
Let me help you get your bootloop fixed though first... then I'm curious if your screen will work.
I think what was causing my bootloop was a lack of this parameter when using mkbootfs:
Code:
--ramdiskaddr 0x81500000
However, if you're using ktoosez script, that should already be included. Also, make sure to clear your cache, dalvik, and fix permissions.

also, come to #cyanogenmod on irc.freenode.net, we might be able to work through this more quickly there

finalllyyyyy i have a display working! Apparently I was using too old of a version of userspace that did not match with my kernel. So my nightly was too old with the kernel rebuilds I was using. Let me know if you still have issues.

Kernel Compilation ERROR

[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/input/touchscreen/ft5x06_ts.o
drivers/input/touchscreen/ft5x06_ts.c: In function 'ft5x06_get_factory_id':
drivers/input/touchscreen/ft5x06_ts.c:432:45: warning: 'ft5336_bootloader_ver' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: ft5x06_ts.c:432
make[3]: *** [drivers/input/touchscreen/ft5x06_ts.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2

DevendraMilmile121 said:
[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
Click to expand...
Click to collapse
its toolchain error..use Linaro 4.6 toolchain

Luffy.d said:
its toolchain error..use Linaro 4.6 toolchain
Click to expand...
Click to collapse
Thanks Bro Problem Now solved now another problem presist
Code:
CC drivers/video/msm/mdss/mdss_mdp_overlay.o
drivers/video/msm/mdss/mdss_mdp_overlay.c: In function ‘mdss_mdp_overlay_ioctl_handler’:
drivers/video/msm/mdss/mdss_mdp_overlay.c:2273:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdss_mdp_overlay.c:2273
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1
make[3]: *** [drivers/video/msm/mdss] Error 2
make[2]: *** [drivers/video/msm] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2

DevendraMilmile121 said:
Thanks Bro Problem Now solved now another problem presist
Code:
CC drivers/video/msm/mdss/mdss_mdp_overlay.o
drivers/video/msm/mdss/mdss_mdp_overlay.c: In function ‘mdss_mdp_overlay_ioctl_handler’:
drivers/video/msm/mdss/mdss_mdp_overlay.c:2273:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdss_mdp_overlay.c:2273
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1
make[3]: *** [drivers/video/msm/mdss] Error 2
make[2]: *** [drivers/video/msm] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
this also seem toolchain error bro....do one thing bro use sabermod toolchain
i successfully compile the kernel with saber toolchain

Luffy.d said:
this also seem toolchain error bro....do one thing bro use sabermod toolchain
i successfully compile the kernel with saber toolchain
Click to expand...
Click to collapse
Im using 64bit os any problem with this and can u give me saber toolchain link

DevendraMilmile121 said:
Im using 64bit os any problem with this and can u give me saber toolchain link
Click to expand...
Click to collapse
os is ok....try this toolchain
https://github.com/SaberMod/arm-eabi-4.9

Luffy.d said:
os is ok....try this toolchain
https://github.com/SaberMod/arm-eabi-4.9
Click to expand...
Click to collapse
4.9 won't work, you'll need 4.7(i use linaro)

CoreWolf said:
4.9 won't work, you'll need 4.7(i use linaro)
Click to expand...
Click to collapse
i use linaro 4.6 no luck i will try 4.7 and tell u tomorrow

CoreWolf said:
4.9 won't work, you'll need 4.7(i use linaro)
Click to expand...
Click to collapse
i tried it work...getting one or two error but compile successfully

I downloaded both tool chain Im trying today

@DevendraMilmile121 have you solved compilation errors? which toolchain you are using ??

Used linero 4.7 2014 build. compile kernel but some problem in display driver it show only mi logo

DevendraMilmile121 said:
Used linero 4.7 2014 build. compile kernel but some problem in display driver it show only mi logo
Click to expand...
Click to collapse
how did you repack kernel? did you generate a dt.img?

thewisenerd said:
how did you repack kernel? did you generate a dt.img?
Click to expand...
Click to collapse
same question wat i have did you get the DT.img ???? m stuck there :crying:

Tarun93 said:
same question wat i have did you get the DT.img ???? m stuck there :crying:
Click to expand...
Click to collapse
p.s. compiled kernel, added s2w, dt2w (by showp1984) (thx showp1984)

thewisenerd said:
p.s. compiled kernel, added s2w, dt2w (by showp1984) (thx showp1984)
Click to expand...
Click to collapse
i wanna get my carbon rom kicked up with the kernel source i have the kernel ready with a couple of governors n schedulers n working on other things too but i wanna have a stock kernel kicked in n booted first for the rom tried everything i could but cant get it started @thewisenerd do you have any idea how do i get around this ??

I pack kernel on windows I have two system .kernel booted but only show mi logo how to solve this

How to solve milogo bug

DevendraMilmile121 said:
How to solve milogo bug
Click to expand...
Click to collapse
What you had done with source code?

DevendraMilmile121 said:
How to solve milogo bug
Click to expand...
Click to collapse
the kernel wont work on old cm and old rom....try it on latest cm11 r15 and see the magic