Search the Community: Showing results for tags 'F8'.
Found 1 result
fullerfun posted a topic in OSx86 10.10 (Yosemite)After further review, I'm convinced the test2.efi method is the best way to go no matter what system you are using. If it doesn't work for some reason, put your boot drive in sata port 1, boot another system, mount the efi on sata1 drive. Delete the efi folder. do a clean install of latest clover..drop in your appropriate files. (see below for full history....) 5/23/16 ---- Edit: So, I've discovered, after much forum hunting and seeing other user's experiences, my original issue turns out to be an issue with having additional PCI cards installed. I'm sure my MOTU audio pci & thunderbolt PCI are the causes.... By adding the the test2.efi file from the below link to clover, I can boot from any menu! Credit to Nick Woodhams. https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/ This is an X99 firmware problem known by the developers, and they have yet to make a good solution. Talked about extensively here: https://sourceforge.net/p/cloverefiboot/tickets/125/ I recently updated to the latest clover v2.3k_r3526, dropped in test2.efi and boom, I can boot any way I like without errors or problems! This works perfectly for me on 10.10.5 Edit.. Turns out on my system, it totally depends on which sata port your boot drive containing clover is. test2.efi seems to work more consistently, even on 10.11.5 when I'm booting with a drive on one of the 1st sata ports. When I have a drive on port 5, the h4x's method worked(below)...so weird... If running 10.11.4 or 10.11.5 on an X99 board with additional PCI cards, and your boot drive is not in one of the 1st sata ports, and you get the errors, try need a different efi file h4x has created one that works for me scroll down to the comments section on this page https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/ This is his comment and instructions. "h4x Good news! I merged OsxAptioFix2Drv with OsxLowMemFixDrv and it works with 10.11.4. Compiled binary (compiled with Clover r3354, tested with r3354 and r3469): https://drive.google.com/file/d/0B2-g_coTRnPnaU53Z1F6Qm5OeXM/view?usp=sharing Put it into your driverUEFI64 folder and delete "OsxAptioFixDrv.efi", "OsxAptioFIx2Drv.efi", "OsxLowMemFixDrv.efi" and "test2.efi" if presented. I can also share the patch file after some cleanup if you need it. Basically I moved DoFixes() from LowMemFix to AptioFix2 and call it before RunImageWithOverrides(). This binary will free low memory up to 0x20000000 (512M) before run actual AptioFix2." Awesome fix, credit to h4x & Nick Woodhams! You guys rock! Bill edited 5/18/16 ------------- Hello all. As always, thank you to everyone in this community. I’ve learned a ton from too many to mention by name! I've finally gotten to the bottom of some funky Clover UEFI booting behavior on my system. When booting(cold or from restart), If I press-hold F8 to get the BIOS boot device selection menu, and select any UEFI Drive, clover boots normally to clover menu. But no matter which system I select with clover and try to boot, I get the dreaded “AllocateReloceBlock(): can not allocate relocation block (0X16405 pages below 0x10000000)” error that many people have been seeing on X99 systems. However, if I boot into the BIOS (press & hold F2 on boot), go to the boot section, make the very first boot device option the UEFI drive that has the drive I want to run clover from, save & exit (F10),( it saves even though it says no changes). Wait for the computer to re-boot. press nothing, clover boots, viola, I can boot any system from within clover I want without any errors. Also, in the BIOS boot section, if I try the boot override options on UEFI Drives, it does not work either. Same error as above. I have Asus X99 Deluxe (BIOS 1203 (also had the issue with BIOS 1103)), 5960X, running latest Clover build Clover_v2k_r3128 (although I experienced the same issues with older versions of clover also). I suspect the issue is specific to my ASUS X99 Deluxe board..but I suppose it could be that in combination with the 5960X specifically.(maybe some of you with the same or similar boards and/or other processors can confirm this bug) This issue happens on my system no matter which OS I'm trying to boot 10.9.5 or 10.10.1...both on different SSD's hooked up to SATA ports 1 & 2. Clover boot loader installed on both SSD’s. No matter which drive I boot to clover menu, same error. This error also appears if I try booting via a USB jump drive using UEFI with the same methods above. So for any of you attempting to use a USB device with clover to install or boot a system..it won’t work unless it’s the 1 item in your boot list in the BIOS. (pressing F8 or boot override will give you the same errors) Also on another note, for my system, getting 10.10 to boot properly after installing OS 10.10 for the 1st time, there was some more Clover funkiness. The first time I tried to boot clover it just refused to boot and would stop at “uuid ++++++++++” Which normally you get that error when kernel is not properly patched, but mine was properly patched. I weirdly discovered if I simply go into the bios(F2), go to the boot menu, select my 10.9.5 system with clover as the 1st boot device(instead of the clover I had just installed on my 10.10 drive), reboot the computer, select my 10.10 system in clover menu and it booted right up. very strange. ever since doing that once, now both my clover boot loaders work normally without any errors, as long as I do as above(let the system boot to the 1st UEFI item in the boot list item in BIOS) FYI, One final note, for my specific system using OsxAptioFixDrv-64.efi was the only one that works. OsxAptioFix2Drv-64.efi does not work on my system. Hope this helps save someone hours of time…took me forever to narrow this down… Bill