Closed z3ntu closed 8 years ago
you have to port kexec hardboot to you custom kernel
@sndnvaps is this really the issue...?
i think, i was the one problem of you multirom mgr.
@sndnvaps What did you mean as I didn't really understood your last message?
See https://github.com/Tasssadar/multirom/issues/99#issuecomment-232130506 for a bit more information.
[ 7.433124] multirom: Framebuffer:
[ 7.436752] multirom: fi.smem_len: 16711680
[ 7.440850] multirom: fi.type: 0
[ 7.444061] multirom: fi.type_aux: 0
[ 7.447681] multirom: fi.visual: 2
[ 7.451003] multirom: fi.xpanstep: 1
[ 7.454565] multirom: fi.ypanstep: 1
[ 7.458181] multirom: fi.ywrapstep: 0
[ 7.461771] multirom: fi.line_length: 4352
[ 7.465867] multirom: fi.mmio_start: 0x0
[ 7.469796] multirom: fi.mmio_len: 0
[ 7.473312] multirom: fi.accel: 0
[ 7.476631] multirom: vi.xres: 1080
[ 7.480127] multirom: vi.yres: 1920
[ 7.483559] multirom: vi.xres_virtual: 1088
[ 7.487757] multirom: vi.yres_virtual: 3840
[ 7.491931] multirom: vi.xoffset: 0
[ 7.495362] multirom: vi.yoffset: 0
[ 7.498853] multirom: vi.bits_per_pixel: 32
[ 7.503042] multirom: vi.grayscale: 0
[ 7.506665] multirom: vi.red: offset: 24 len: 8 msb_right: 0
[ 7.512292] multirom: vi.green: offset: 16 len: 8 msb_right: 0
[ 7.518163] multirom: vi.blue: offset: 8 len: 8 msb_right: 0
[ 7.523748] multirom: vi.transp: offset: 0 len: 8 msb_right: 0
[ 7.529618] multirom: vi.nonstd: 0
[ 7.532950] multirom: vi.activate: 128
[ 7.536747] multirom: vi.height: 4294967295
[ 7.540852] multirom: vi.width: 4294967295
[ 7.544931] multirom: vi.accel_flags: 0
I will try the MR_QCOM_OVERLAY_CUSTOM_PIXEL_FORMAT
patch next (maybe tomorrow)
New kmsg, it skips multirom now (doesn't display it): http://pastebin.com/Pu2yaMxL and boots to Android
@z3ntu i get the same issue.. multirom menu cannt show on boot .. just show the black screen .. after 30 sec,, bootam is show ..
I actually got it working now. /closed
@z3ntu what you have done .. make it work for you device .?
https://github.com/z3ntu/android_device_fairphone_fp2/commit/ebc16e53be249a520e42b921c72ee77a2fefd9ff that was the last thing I had to do.
When I try to compile multirom for the Fairphone 2, it crashes when trying to use the framebuffer (
fb_update()
)I already found out (with many
INFO()
statements) that multirom crashes in theEDIT2:: The last printed line (from my debug lines) is in https://github.com/Tasssadar/multirom/blob/master/lib/framebuffer.c#L289 (thefb_update()
function in https://github.com/Tasssadar/multirom/blob/master/lib/framebuffer.c#L189 EDIT: the functionfb_cpy_fb_with_rotation
. (Line in source: https://github.com/Tasssadar/multirom/blob/master/lib/framebuffer.c#L280). 99% thememcpy
function/statement crashes everything.memcpy(dst, src, fb.vi.xres_virtual * fb.vi.yres * PIXEL_SIZE);
line)Output of
fb_dump_info()
:Some important-looking lines from last_kmsg:
I have set the pixel format to RGBX_8888 (with
MR_PIXEL_FORMAT := "RGBX_8888"
in theBoardConfig.mk
).EDIT:
last_kmsg
tells me something about "Unable to handle kernel paging request at virtual address"(and yes, the broken characters are in last_kmsg)
TWRP reports in
/tmp/recovery.log
about the framebuffer:EDIT2: Complete
last_kmsg
: http://pastebin.com/eiBFgL76