Errors during CM10.1 build

[Guest Spacecaker]

here is my build.

https://docs.google.com/file/d/0B0eMvI5zvG5kWDJHalIzUFVXNlk/edit?usp=sharing

maybe its ramdisk problem or the kernel source it self :/

[Guest Spacecaker]

http://pastebin.com/9KAdnvk1 dmesg of cm10 kernel

the thing that fails was at drivers/video/msm and drivers/video/msm/mdp4_overlay.c / mdp4.h/c

<4>[ 5.187395] pm8921-bms: probe of pm8921-bms failed with error -22

<3>[ 7.422585] mdp4_mixer_blend_setup: Error: no bg_pipe at mixer=1 <- this one is main problem of not booting but this is mdp4.h/c aka display function

<3>[ 8.158339] mdp4_mixer_blend_setup: Error: no bg_pipe at mixer=0

those above are the errors

Edited September 7, 2013 by Spacecaker

[Guest Spacecaker]

i got rid of the error above

http://pastebin.com/MCbyi2a7 dmessg

but weirdly enough it doesnt boot :/

shows init logo then black screen but kernel keeps saying messages i will try to logcat aswell ;)

http://pastebin.com/X9JTHPTj logcat

will upload my kernel soon with updated mdp4_overlay.c i restarted from cm10 kernel

[list]
	[*]	[color=#000000][background=rgb(255, 255, 255)]

<3>[ 5.142743] pm8921_bms_probe: Using TI Gauge[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<4>[ 5.146009] pm8921-bms: probe of pm8921-bms failed with error -22[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<3>[ 5.153059] power_supply usb: driver failed to report `present' property: 4294967274[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<3>[ 5.159835] power_supply usb: driver failed to report `present' property: 4294967274[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<3>[ 5.167587] power_supply pm8921-dc: driver failed to report `present' property: 4294967274[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<3>[ 5.175827] power_supply pm8921-dc: driver failed to report `present' property: 4294967274[/background][/color]	

[/list]
[list]
	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.433816] EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: barrier=1[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.445383] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.482832] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<4>[ 5.536334] e2fsck used greatest stack depth: 5728 bytes left[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.546650] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mode. Opts: barrier=1,noauto_da_alloc,discard,errors=panic[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.569754] EXT4-fs (mmcblk0p15): recovery complete[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.571036] EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1,discard,errors=panic[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.578605] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: barrier=1[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.592064] EXT4-fs (mmcblk0p14): re-mounted. Opts: barrier=1[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

<6>[ 5.626522] EXT4-fs (mmcblk0p14): re-mounted. Opts: barrier=1[/background][/color]	

[/list]

also this

[list]
	[*]	[color=#000000][background=rgb(255, 255, 255)]

[ 09-07 10:20:26.202   155:  391 E/overlay  ][/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

cannot open framebuffer(2)[/background][/color]	

	[*]	


	[*]	[color=#000000][background=rgb(255, 255, 255)]

[ 09-07 10:20:26.202   155:  391 E/overlay  ][/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

initOverlay failed[/background][/color]	

	[*]	


	[*]	[color=#000000][background=rgb(255, 255, 255)]

[ 09-07 10:20:26.312   155:  391 E/hwcomposer ][/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument[/background][/color]	

	[*]	


	[*]	[color=#000000][background=rgb(255, 255, 255)]

[ 09-07 10:20:26.312   155:  391 E/hwcomposer ][/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

init: Failed to setup primary base pipe[/background][/color]	

	[*]	[color=#000000][background=rgb(255, 255, 255)]

[*]

Edited September 7, 2013 by Spacecaker

[Guest vache]

In hardware/qcom/display/liboverlay/overlayUtils.h :

#define NUM_FB_DEVICES 3

You could try to change this to :

#define NUM_FB_DEVICES 2

Then recompil liboverlay.

It's more a workaround than a fix cause we're missing an entry in /dev/graphics/ (created by kernel).

Edited September 7, 2013 by vache

[Guest gkai]

Somehow I have lost most of my modifs for compiling CM10.1 :( don't know how it happened, I made a copy before reclonind device/vendor/kernel....but my copies ended up almost identical to branch CM10.1 and now i can not build it anymore...Ha well, I guess I have to redo what I did before and correct one error at a time :(

[Guest Spacecaker]

In hardware/qcom/display/liboverlay/overlayUtils.h :

#define NUM_FB_DEVICES 3

You could try to change this to :

#define NUM_FB_DEVICES 2

Then recompil liboverlay.

It's more a workaround than a fix cause we're missing an entry in /dev/graphics/ (created by kernel).

its in the .cpp btw :P

also gonna try some adjustements to the Power driver

as from some google results the thermaldeamon errors are caused because of this

and causes shutdown

[Guest Spacecaker]

Somehow I have lost most of my modifs for compiling CM10.1 :( don't know how it happened, I made a copy before reclonind device/vendor/kernel....but my copies ended up almost identical to branch CM10.1 and now i can not build it anymore...Ha well, I guess I have to redo what I did before and correct one error at a time :(

github.com/spacecaker <- here i have uploaded my changes for now ;)

device and vendor

kernels and such ;)

[Guest Spacecaker]

if u guys want here are my edited boot.imgs

https://dl.dropboxusercontent.com/u/56034188/1sgsIII-iv/bootmdp4mod.img this one got the MDP4 drivers fixed and such

https://dl.dropboxusercontent.com/u/56034188/1sgsIII-iv/boot79powermod.img this one same as above ^^ but has Power drivers updated * not yet tested as i am not home *

[Guest iAl3x]

if u guys want here are my edited boot.imgs

https://dl.dropboxus...bootmdp4mod.img this one got the MDP4 drivers fixed and such

https://dl.dropboxus...t79powermod.img this one same as above ^^ but has Power drivers updated * not yet tested as i am not home *

Has anyone tried to boot CM10.1 with this kernel? I can't test it as an idiot friend dropped my phone on the side and broke my Vol-UP rocker and i can't boot into bootloader in case it won't boot up :((

[Guest vache]

Has anyone tried to boot CM10.1 with this kernel? I can't test it as an idiot friend dropped my phone on the side and broke my Vol-UP rocker and i can't boot into bootloader in case it won't boot up :((

Still black screen but not the same error.

[Guest iAl3x]

Still black screen but not the same error.

What's the error now? Maybe i can help as i know a little bit of C/C++.

[Guest vache]

What's the error now? Maybe i can help as i know a little bit of C/C++.

Didn't keep log. Rebuilding...

[Guest Spacecaker]

Still black screen but not the same error.

wich version u tried ?

can u share the dmsesg / eror log ?

[Guest Spacecaker]

What's the error now? Maybe i can help as i know a little bit of C/C++.

i posted my dmesg and logcat few posts above yours with mdp4 version of kernel ;)

[Guest Spacecaker]

Has anyone tried to boot CM10.1 with this kernel? I can't test it as an idiot friend dropped my phone on the side and broke my Vol-UP rocker and i can't boot into bootloader in case it won't boot up :((

u can use adb reboot-bootloader;) and us twrp recovery

[Guest iAl3x]

u can use adb reboot-bootloader;) and us twrp recovery

Cool! I didn't knew adb is loaded so early by kernel

[Guest iAl3x]

Hmm...From the logcat it seems something wrong with SurfaceFlinger. It died or it locked in before it registered with the servicemanager.

Edited September 7, 2013 by iAl3x

[Guest Spacecaker]

Cool! I didn't knew adb is loaded so early by kernel

how could i take mesg and logcat otherwis ? xD

[Guest Spacecaker]

Hmm...From the logcat it seems something wrong with SurfaceFlinger. It died or it locked in before it registered with the servicemanager. Maybe we should take a closer look at hwcomposer.msm8960.so

maybe take it from Xperia T cm10.1 / mint as its the device from wich hardware specs are soo close to ours ;)

[Guest Spacecaker]

https://docs.google.com/file/d/0B0eMvI5zvG5kdV9BZ2VCQ2hWdWs/edit?usp=sharing new rom build with updated EGL Gralloc and some edits in ramdisk * compared to Mint device and some others as they are almost identical in specs and such ;) *

i havent tried it yet as i am not home so uploaded in a rush

[Guest razvankim]

I will test and report asap!

[Guest Spacecaker]

I will test and report asap!

if not boot please try a dmesg and logcat ;)

i am sure it wont boot though

[Guest razvankim]

Doesn't work. It gives me failed. some updater-script error.

[Guest razvankim]

E: Error executing updater binary in zip /external_sd/rom.zip

Error flashing zip /external_sd/rom.zip

that;s the error

[Guest Spacecaker]

E: Error executing updater binary in zip /external_sd/rom.zip

Error flashing zip /external_sd/rom.zip

that;s the error

u used twrp or cwm ? try to use the meta inf from my previous build ;)

Edited September 8, 2013 by Spacecaker