Ok, a fresh question from an old time user. I have a Fusion Disk with Sierra on it booting from Ozmosis (a very old version that allowed for Fusion drives I believe it was 894M) it has served me very well thus far, however with High Sierra I can only get a KP, and it is so fast that It doesn't give me an option to view the error before it scrolls past with a full screen of debug followed by mach restart 3 times.
This is on a separate single SATA drive I use for Beta testing on my hack vs beta testing on my MacBook Pro (where I installed the OS on the disk like I did Sierra). All protections are disabled in firmware so it should see the FakeSMC.ffs like Sierra does, and load it. Any help would be greatly appreciated.
:: Edited ::
After Screencapturing the monitor with my iPhone, the KP is on com.apple.driver.AppleACPIPlatform(6.1)
it does pick up FakeSMC but for some reason, the ACPI for Sierra doesn't work for High Sierra? any thoughts?
Ok I know this is going to sound very weird but here goes. I have a legit Mac Pro 2.1 and I am considering pointing it's boot manager to Ozmosis, but first I have a few questions. can I strip down Ozmosis so that it only has itself (the Fake 64bit EFI environment) that redirects to the 32 bit real EFI/files on the EFI partition? if so I could Greatly reduce the stress load on rebuilding this monster. because PikeAlpha's method doesn't seem to stay stable for me in 10.10.5 which is the OS I plan to run with this Mac.
All input is welcome. including I am a nutcase ;P I already know.