It's a work in progress.
I see... i thought so.
I fixed the Symbols.dylib.dylib issue (makefile bug) as well as a few other things in my last commit. At the same time i just broke a lot of things as well.
yep.. with the Symbols.dylib.dylib check corrected, debug output is pretty much the same on the last commit (712) or 671; so, checking 671 boot-log, is easy to figure that the ModulesLoaded callback i mentioned is added by the GUI module; removing the module, i was able to go to boot prompt and start boot; as you mention there are still problems.. boot hangs while executing ScanMemory hook, after printing the memory modules info; these
Hook 'ScanMemory' callback executed, next is 0x0.
Hook 'ScanMemory' executed.
are never printed; it just sits there, cursor blinking, no keyboard available.
Attached is a 671 bdmesg with modules debug enabled.
I must have missed that post / line about the boot log. I fixed the code as you mentioned.
No problem... even i was already missing this
@Azimutz
I am not understanding this assertion
"Kernel Start" hook needs to be moved before setupBooterLog()
It is very old claim. How for now?
Slice, i'm not sure if i understand;
if you're asking "why Kernel Start hook needs to be moved before setupBooterLog()"? the answer is on the post:
...or anything that uses it, will not print to the log.
If that is not the question, you'll have to explain me
Anyway, Mek fixed it on rev 712.