-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multirom crashes (framebuffer issue?) #98
Comments
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 #99 (comment) for a bit more information.
I will try the |
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 .. |
I actually got it working now. /closed |
@z3ntu what you have done .. make it work for you device .? |
z3ntu/android_device_fairphone_FP2@ebc16e5 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/eiBFgL76The text was updated successfully, but these errors were encountered: