vince026 Posted April 8, 2016 Share Posted April 8, 2016 I have the following setup running el capitan dual booting windows 10 on one drive with a few problems: - MSI Tomahawk Z170A - Intel i5 6600k Skylake - Asus GTX 770 - Samsung 850 evo 1tb I'm running the latest clover but booting seems to be a hit or miss. Currently i'm using OsxAptioFix2Drv-64.efi because when i use OsxAptioFixDrv-64.efi i get a low memory error. But i think OsxAptioFix2Drv-64.efi is giving me problems, sometimes my system won't boot and i get a "Couldn't allocate runtime area" error. And i have to turn off my pc and turn it on again and hope i'm lucky. If it goes beyond that there aren't any problems. I made a photo of the error: https://dl.dropboxusercontent.com/u/11109447/errorBooting.jpg Next thing, sometimes the clover theme i picked will show and sometimes it goes back to the blue (no-theme selected) theme. Does anyone know what is up with that? Last thing, my audio is functioning (realtek alc891) but the volume is really low. It seems like the sound isn't amplified, i have to set the volume on my speakers around 80-90% (and osx on full) to get a normal volume. I've currently solved this by using the SPDIF port. Link to comment Share on other sites More sharing options...
angelol Posted April 8, 2016 Share Posted April 8, 2016 I had similar problems when initially using OsxAptioFixDrv-64.efi and then switched to OsxAptioFix2Drv-64.efi and I have good news and bad news. The bad news is that you probably have to reinstall but the good news is that after you install while using OsxAptioFix2Drv-64.efi you will have no problems in the future. The reason why this is happening, if I understand the situation correctly, is that there is a slight difference in these 2 .efi files that have to do with the way they read and allocate disk sectors. So basically you can boot your system because the way they understand your disk's structure is not completely different nor exactly the same. Link to comment Share on other sites More sharing options...
vince026 Posted April 10, 2016 Author Share Posted April 10, 2016 I had similar problems when initially using OsxAptioFixDrv-64.efi and then switched to OsxAptioFix2Drv-64.efi and I have good news and bad news. The bad news is that you probably have to reinstall but the good news is that after you install while using OsxAptioFix2Drv-64.efi you will have no problems in the future. The reason why this is happening, if I understand the situation correctly, is that there is a slight difference in these 2 .efi files that have to do with the way they read and allocate disk sectors. So basically you can boot your system because the way they understand your disk's structure is not completely different nor exactly the same. Truth is, i've installed using OsxAptioFix2Drv-64.efi i couldn't even boot the installer using OsxAptioFixDrv-64.efi. 10.11.4 and my setup (or i think skylake for that matter) don't really like to use OsxAptioFixDrv-64.efi Link to comment Share on other sites More sharing options...
angelol Posted April 11, 2016 Share Posted April 11, 2016 try to install in a small partition setting CsrActiveConfig=0x67 with OsxAptioFixDrv-64.efi. Link to comment Share on other sites More sharing options...
Recommended Posts