Hey Andrew, I'm able to boot the 3.14 kernel now with usb and proper hdmi support. I then started to include the bluetooth modules. The modules seem to load fine. However, now when I'm seeing the boot animation and finally enter to homescreen a crash happens and the boot animation appears again.
This is the output after the crash: binder: 8841: binder_alloc_buf, no vma binder: 8841: binder_alloc_buf, no vma [ 658.943483] binder: 9034:9191 transaction failed 29201, size 248-4 [ 658.951002] alarm_release: clear alarm, pending 0 [ 658.958173] binder: 8841: binder_alloc_buf, no vma [ 658.963237] binder: 9034:9191 transaction failed 29201, size 188-4 [ 658.971025] binder: release 8841:9028 transaction 60843 in, still active [ 658.978173] binder: send failed reply for transaction 60843 to 8968:8968 [ 658.985315] binder: undelivered transaction 61599 [ 658.990261] binder: undelivered transaction 61605 [ 658.995234] binder: undelivered transaction 61606 [ 659.000672] binder: undelivered transaction 61592 [ 659.005677] binder: send failed reply for transaction 61593 to 9265:9265 [ 659.012739] binder: send failed reply for transaction 61607 to 9281:9308 [ 659.019834] binder: send failed reply for transaction 61618 to 9296:9296 [ 659.029835] binder: 8968:8968 transaction failed 29189, size 208-0 [ 659.065614] binder: 9265:9265 transaction failed 29189, size 240-0 [ 659.251928] init: untracked pid 9296 exited [ 659.394084] init: untracked pid 8998 exited [ 659.398895] init: untracked pid 9116 exited [ 659.454135] init: untracked pid 9281 exited [ 659.464443] init: untracked pid 8927 exited [ 659.495386] init: untracked pid 9265 exited [ 662.203936] init: untracked pid 8985 exited [ 662.220119] init: untracked pid 8968 exited I was thinking that the vmalloc size was not big enough. However, It's already at 486MB I do always see the alarm release in the output. Maybe that has something to do with it? Cheers, Michael 2015-03-18 17:20 GMT+01:00 Michael Gobbers <[email protected]>: > Hey Andrew, > > I wasn't able to solve either one of my problems. > Disabling FunctionFS led to a kernel panic. > > Changing the resolutions definitely works but the flickering is still > there. > > I'm pretty much out of options here I guess so I think the next step is > backporting the required kernel modules required for the BLE to 3.8 as I'm > getting nowhere with the 3.14 kernel. > > Cheers, > Michael > > 2015-03-18 14:23 GMT+01:00 Andrew Henderson <[email protected]>: > >> OK, this is starting to make more sense. 1920x1080 at 60 Hz is not a >> supported mode for the BBB. I've seen screen shearing on 1920x1080 at 24 Hz >> before with OpenGL ES on 3.14 with single buffering before. My suggestion >> is to use the "video=" parameter to set a supported resolution lower than >> 1920x1080 and see how well that works for you. Here is a list of the >> supported modes: http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI >> >> Maybe try 1280x720-16@60, instead. >> >> On Wednesday, March 18, 2015 at 7:02:29 AM UTC-4, Michael Gobbers wrote: >>> >>> For the video issue I tried changing the video parameter to >>> 1920x1080-16@60 the native resoltion of my display. However, when I >>> did, I did not see anything on the display. >>> >>> Here is a small video of the display so you get what I mean with >>> flicker. It seems that some video buffer isn't emptied or something as I'm >>> seeing old screens between the one that I should see >>> https://youtu.be/me1_O4iaHB8 >>> >> > > > -- > Michael Gobbers <http://be.linkedin.com/in/michaelgobbers> > > > Desguinlei 6 - 2018 Antwerpen > -- Michael Gobbers <http://be.linkedin.com/in/michaelgobbers> Desguinlei 6 - 2018 Antwerpen -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
