Root ICS/CM9-JB/CM10 Development Thread

[tdm]

Can you upload a zip of the rom?

Ill have my kernel source up when i get home from work btw.

I'll upload at EOD. Hopefully I can fix more stuff.

 

[tdm]

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.

 

[Bloodawn]

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.

are you using my zImage from hyperics? the ramdisk/boot.img need compressed with lzma, I have other compressions disabled.

 

[lMonsterl]

are you using my zImage from hyperics? the ramdisk/boot.img need compressed with lzma, I have other compressions disabled.

did u have the source up blood? i didnt see it

 

[tdm]

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.

 

[Bloodawn]

did u have the source up blood? i didnt see it

not yet

 

[Bloodawn]

source is uploaded

https://github.com/Bloodawn

 

[tdm]

source is uploaded

https://github.com/Bloodawn

Thanks. I was just in the middle of switching to xz but I'll abandon that now.

 

[tdm]

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?

 

[tdm]

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.

 

[Bloodawn]

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?

http://releases.linaro.org/12.03/co...12.03-2-2012-03-15_12-39-18-linux-x86.tar.bz2

that should build it

edit: that line is from patching the kernel from .7 to .14

 

[tdm]

What about the section mismatch? Linaro doesn't trigger that issue?

 

[Bloodawn]

What about the section mismatch? Linaro doesn't trigger that issue?

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.

 

[tdm]

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.

Unfortunately section mismatches are errors. Which makes me wonder if the linaro linker hides them...?

 

[Bloodawn]

Unfortunately section mismatches are errors. Which makes me wonder if the linaro linker hides them...?

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.

 

[tdm]

Hmmm strange. I'm sure I'll get it solved tomorrow though.

 

[tdm]

I'm also going to crib from the tesmhacksung latona kernel. It's a gb base but should have back ported ics goodies.

 

[Bloodawn]

Hmmm strange. I'm sure I'll get it solved tomorrow though.

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.

 

[tdm]

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.

Yeah perhaps you are right. I wonder if the FOP kernel will make a better base.

 

[tdm]

O3 makes them errors.

 

[tdm]

First successful build with hyperics kernel is complete. I can't install it tonight though.

Thanks Bloodawn!

 

[tdm]

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.

 

[tdm]

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...

 

[tdm]

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?

 

[Bloodawn]

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?

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.