• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ICS/CM9-JB/CM10 Development Thread

My biggest two problems right now are:

1. I can't seem to build a bootable boot.img. But the hyperics image boots fine. Don't know if the issue is the boot.img format or my rc-scripts. Working on that now.

2. I can get rild running and get service, but when rild comes up, system_server crashes.
 
tdm said:
My biggest two problems right now are:

1. I can't seem to build a bootable boot.img. But the hyperics image boots fine. Don't know if the issue is the boot.img format or my rc-scripts. Working on that now.

2. I can get rild running and get service, but when rild comes up, system_server crashes.
Click to expand...

are you using my zImage from hyperics? the ramdisk/boot.img need compressed with lzma, I have other compressions disabled.
 
The problem with boot.img is that CONFIG_RD_GZIP is not set in the hyperics kernel. The android build wants to make a gzip initramfs but the kernel won't boot it.

I'm going to hack up the build scripts to use xz for now and see if it works. But I really need the hyperics sources so that I can tinker with them, and when I get them, I'll enable CONFIG_RD_GZIP.
 
The line ".arch_extension sec" in security/smc/omap3/bridge_pub2sec.S breaks my build. I assume it's a newer extension from the Linaro toolchain.

Do you know what it is, where it came from, and why it's there?
 
Also have one or more section mismatches that need to be tracked down, possibly from removing that line.

I'll look at that in the morning. As soon as I can get a good build, I'll post a ROM.
 
tdm said:
What about the section mismatch? Linaro doesn't trigger that issue?
Click to expand...

don't worry about it or the warnings, they're harmless. as long as your not getting any errors (which you shouldn't unless you start changing things) your good.
 
Bloodawn said:
don't worry about it or the warnings, they're harmless. as long as your not getting any errors (which you shouldn't unless you start changing things) your good.
Click to expand...

Unfortunately section mismatches are errors. Which makes me wonder if the linaro linker hides them...?
 
tdm said:
Unfortunately section mismatches are errors. Which makes me wonder if the linaro linker hides them...?
Click to expand...

I don't know bro, I've had the mismatches since I patched the kernel but its never effected anything. everything works. the only errors I care about are ones that fail a build.
 
I'm also going to crib from the tesmhacksung latona kernel. It's a gb base but should have back ported ics goodies.
 
Bloodawn said:
your probably just gonna be wasting time if you actually try to fix them bro, theres 20 section mismatches, and its probably useless shit causing them.
Click to expand...

Yeah perhaps you are right. I wonder if the FOP kernel will make a better base.
 
First successful build with hyperics kernel is complete. I can't install it tonight though.

Thanks Bloodawn!
 
Oh, almost forgot to mention ... it looks like you added CONFIG_MACH_LGE_SNIPER manually with no corresponding Kconfig entry. That doesn't play nice with "make oldconfig" so I tossed in an entry in arch/arm/mach-omap2/Kconfig. It looked like the best place at the time.

I noticed the entry CONFIG_LGE_LAB3_BOARD, which may be a suitable alternative. This is set in sniper_lab3_emmc_defconfig, which is our vendor config, but not in sniper_rev_a_emmc_defconfig. I can only guess that the latter is a non-production prototype of the sniper board... based on nothing more than the config name, really.
 
I haven't been able to get my compiled kernel to boot, but I have been able to repack Blooddawn's kernel. Need to work on this some more. I can't really release a ROM until I can build a boot.img. :/

Got rild working and successfully made a phone call to myself. There was no audio but everything else looked good.

Got wifi working and authenticating to WPA networks.

More news as it happens...
 
Bloodawn, I'm getting this:


kernel/lge/hyperics/security/smc/omap3/bridge_pub2sec.S:43: Error: selected processor does not support ARM mode `smc 1'

Are you sure that's the correct toolchain?
 
tdm said:
Bloodawn, I'm getting this:


kernel/lge/hyperics/security/smc/omap3/bridge_pub2sec.S:43: Error: selected processor does not support ARM mode `smc 1'

Are you sure that's the correct toolchain?
Click to expand...

yes, thats the toolchain I'm using.

did you change anything in the source? try just downloading the source, set the location for the toolchain in the Makefile, it should be something like this:

/home/whatever/whatever/android-toolchain-eabi/bin/arm-eabi-

cd to the kernel folder and do ./SNIPER.sh and it should build and boot fine, if all that works then you can do your changes.
 
You must log in or register to reply here.
Back
Top Bottom