MadJawa Posted October 19, 2014 Share Posted October 19, 2014 Hello, I am trying to install OS X Yosemite on my hackintosh (Asus Z97-DELUXE, i7 4790k, GTX 780). I had a perfectly working Clover install with Mavericks before I tried to install Yosemite This is not my first hackintosh so I usually know how to fix problems by myself but this time I am stuck. I can install Yosemite without any problem, and boot into the system. I installed Clover on the SSD so I don't need the USB stick to boot.However, after some reboots when I install my kexts, I can't boot into Yosemite anymore (even using the USB install stick).I get an OsxAptioFixDrv error : requested memory exceeds our allocated relocation block.Some people said to add slide=0 to the boot args. That did not help. I also tried to use OsxLowMemFixDrv, without success either (stuck after "root device uuid is xxxxxx")I managed to get it working again once by booting to the recovery HD and deleting the kext cache and rebuilding it using kextcatch -update-volume. This lets me boot again to my Yosemite install, but after a reboot, I get the same error again.I once fixed it also by removing some kexts from the Clover kexts folder. But got the same error after a reboot too... I wondered if it was because of a bad kext so I tried to put only the bare minimum kexts to boot but that still doesn't work. This is weird...Am I the only one with this problem? Link to comment Share on other sites More sharing options...
joriss Posted October 19, 2014 Share Posted October 19, 2014 I've had the same problem, I use chameleon now but take a look at this topic http://www.insanelymac.com/forum/topic/301229-clover-2941-updated-and-signed-xcode-51-clang-and-gcc-491-built/page-2 Link to comment Share on other sites More sharing options...
subjectdenied Posted October 19, 2014 Share Posted October 19, 2014 i had this bug when using yosemite during the beta-phase and nvidias webdrivers, removing them and using apples own gpu-drivers fixed it for me however i was also able to use the webdrivers, after booting into single user mode (from a usb-stick) and rebuilding the kernel-cache in the installation. afterwards i could boot osx normally until the next reboot or shutdown 1 Link to comment Share on other sites More sharing options...
artur_pt Posted October 19, 2014 Share Posted October 19, 2014 hello try using aptiofix2 #282 good hack 3 Link to comment Share on other sites More sharing options...
MadJawa Posted October 19, 2014 Author Share Posted October 19, 2014 i had this bug when using yosemite during the beta-phase and nvidias webdrivers, removing them and using apples own gpu-drivers fixed it for me however i was also able to use the webdrivers, after booting into single user mode (from a usb-stick) and rebuilding the kernel-cache in the installation. afterwards i could boot osx normally until the next reboot or shutdown Wow I think that was it ! Thank you ! I think I will stay with OS X's driver. The web driver was required on Mavericks or OpenCL apps would crash, but it seems that Yosemite has native support for the GTX 780. @arthur-pt: thank you for that link, I will definitively keep that one in case I need to install nvidia's webdriver Link to comment Share on other sites More sharing options...
subjectdenied Posted October 20, 2014 Share Posted October 20, 2014 Wow I think that was it ! Thank you ! I think I will stay with OS X's driver. The web driver was required on Mavericks or OpenCL apps would crash, but it seems that Yosemite has native support for the GTX 780. @arthur-pt: thank you for that link, I will definitively keep that one in case I need to install nvidia's webdriver funny thing is, i expected to see this bug all over the net with hackintosh and yosemite dp or betas and nvidia's webdriver, but this is the first time is have seen it mentioned by someone else. to be honest, this bug did cost me two weekends ("magically" appeared again after having installed a later developer preview while having solved the problem by "accident" the first time) and a lot of hair, until i found what's going on here Link to comment Share on other sites More sharing options...
zookini13 Posted October 30, 2014 Share Posted October 30, 2014 hello try using aptiofix2 #282 good hack Thanks for the tip! I had the same issue on Yosemite with the regular OsxAptioFixDrv-64.efi (bundled with Clover 2976) and had no success adding slide=0 to boot args. However, the aptiofix2test3 driver seems to have fixed this issue for me when running with the latest Nvidia web driver (343.01.01f03). Link to comment Share on other sites More sharing options...
CaspianIV Posted December 24, 2014 Share Posted December 24, 2014 Thanks for the AptioFix2 tip and thanks to the programmer that wrote it! I was on my second install of Yosemite and ready to restore Mavericks again. Glad I read this and tried it. For anyone wondering how to use this, place the OsxAptioFix2Drv.efi into your CLOVER/drivers64UEFI folder on your EFI partition and remove the OsxAptioFixDrv-64.efi file then reboot. At least that's how it worked for me. Stopped my 'OsxAptioFixDrv: Error - requested memory exceeds our allocated relocation block' messages and I'm able to boot into an apparently stable system. Cheers Link to comment Share on other sites More sharing options...
xeye Posted February 11, 2015 Share Posted February 11, 2015 also for people who have to stay on web driver and also tried slide=0 and fix2test3, please try this: http://www.insanelymac.com/forum/topic/304479-possible-solutionx99-osxaptiofixdrv-requested-memory-exceeds-our-allocated-relocation-block/ Link to comment Share on other sites More sharing options...
Recommended Posts