sorry @olboy86, Im no quite sure what you’ve done… or where you are at…
No patches found on the main menu, just means you don’t have patches in the /usbdrive/Patches folder…
this is not needed for OTC… however you do need the Modes folder.
important information for OTC:
if you want to use HDMI output (as when using OTC), always plug it in, and turn on tv/project before powering up the Organelle
the reasons are presented below:
so my projector arrived… cheap one from China, but so far looks good , more info on that later elsewhere.
but it means I could see if I could try to kill OTC mother , like @oiboy86 and @finallaptwin
So I have been able to replicate , under certain conditions, sometimes
if I powerup Organelle without the HDMI attached, then attach the HDMI cable when the Organelle menu screen is showing, then run OTC_Mother. then sometimes it will crash (actually reasonable frequently)
This crash is a low level kernel crash i.e. nothing really to do with OTC, but rather the drivers in the kernel (which I cant replace)
here is am example of the issue, just before the whole organelle seizes up!
[ 46.518796] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_read_edid HDMI in HDMI mode
[ 50.856070] Division by zero in kernel.
[ 50.856080] CPU: 1 PID: 155 Comm: kworker/1:2 Not tainted 3.14.14+ #7
[ 50.856095] Workqueue: events console_callback
[ 50.856118] [<80015284>] (unwind_backtrace) from [<80011558>] (show_stack+0x10/0x14)
[ 50.856134] [<80011558>] (show_stack) from [<806e45ec>] (dump_stack+0x80/0xc0)
[ 50.856145] [<806e45ec>] (dump_stack) from [<802ad2d0>] (Ldiv0+0x8/0x10)
[ 50.856155] [<802ad2d0>] (Ldiv0) from [<802ad2a0>] (__aeabi_uidivmod+0x8/0x18)
[ 50.856168] [<802ad2a0>] (__aeabi_uidivmod) from [<80312074>] (mxcfb_pan_display+0xcc/0x544)
[ 50.856184] [<80312074>] (mxcfb_pan_display) from [<802f78b4>] (fb_pan_display+0xbc/0x138)
[ 50.856210] [<802f78b4>] (fb_pan_display) from [<802f7cfc>] (fb_set_var+0x268/0x338)
[ 50.856220] [<802f7cfc>] (fb_set_var) from [<80301c0c>] (fbcon_switch+0x180/0x4b4)
[ 50.856233] [<80301c0c>] (fbcon_switch) from [<80339740>] (redraw_screen+0x178/0x248)
[ 50.856243] [<80339740>] (redraw_screen) from [<803310ec>] (complete_change_console+0x3c/0xd4)
[ 50.856251] [<803310ec>] (complete_change_console) from [<8033b490>] (console_callback+0x104/0x160)
[ 50.856263] [<8033b490>] (console_callback) from [<80040894>] (process_one_work+0xf8/0x368)
[ 50.856273] [<80040894>] (process_one_work) from [<80041524>] (worker_thread+0x13c/0x3dc)
[ 50.856283] [<80041524>] (worker_thread) from [<80046c00>] (kthread+0xd8/0xf0)
[ 50.856292] [<80046c00>] (kthread) from [<8000e278>] (ret_from_fork+0x14/0x3c)
interestingly, it can materialise in slightly different forms, but in essence, this seems to be the root cause.
so the lesson is (and something to try @oiboy86 and @finallaptwin, if you have not) :
if you want to use HDMI output, always plug it in, and turn on tv/project before power up the Organelle
if you don’t Ive found, not only will sometimes it cause an immediate crash, but also I even had issues with it crash later (when I exited OTC) … i.e. its unstable.
Unfortunately, this instability, does tend to point to a possibility there may be other things that cause similar instabilities e.g. particular TVs/Projectors (and you can see from the first line above, this happens immediately after the edid is read from the display device) … so unfortunately, if your having issues with OTC not getting past the initial screen this is probably the issue.
(you can help verify this, by a) ensuring HDMI is connected when powering up b) try running OTC without any HDMI connected… make sure modes are found, either because the OLED shows the params of the first, or by looking in the otc_mother.log)
So no guarantees following the above will work, but it looks like its ‘good practice’, and certainly explains why I was sometimes getting crashes (since I had the TV in a different room, so kept having to plug HDMI in the Organelle after booting)