Jump to content

5960X, Rampage V Extreme OsxAptioFix Problem


cool_recep
 Share

62 posts in this topic

Recommended Posts

Hi,

 

I am trying to install Yosemite on a Haswell-E System with following specs:

 

  • 5960X
  • Rampage V Extreme
  • 16 GB RAM
  • GTX 980
  • 6 TB HDD
  • RevoDrive PCIe SSD (Won't use for install)
  • 4K panel via DP

I could not get past the OsxAptioFix memory allocation part.

 

I have tried:

 

  • slide=0
  • Disabling CSM
  • Using latest Clover
  • Using OsxAptioFix2
  • Patched kernel
  • Safe Mode
  • cpus=1
  • Rampagedev Kexts
  • Rampagedev Config
  • BIOS: 0901
  • Legacy mode: Stuck at root device UUID

 

Nothing worked. Errors:

 

post-1192686-0-61598000-1420239041_thumb.jpg

 

post-1192686-0-05643700-1420239066_thumb.jpg

 

Thank you for your help.

Link to comment
Share on other sites

I guess you missed the introduction to my Installation Guide:

 

The following guide is a step by step guide on how to install Mac OS X onto a custom PC Configuration. For installations onto systems that require the use of a modified Kernel you must install using a Real Macintosh Computer or a Hackintosh that supports UEFI booting as Clover Kernel injection does not currently support Mac OS X 10.10. This includes x99 and AMD based systems.
Link to comment
Share on other sites

I guess you missed the introduction to my Installation Guide:

 

Well, my hackintosh supports UEFI Booting. And I have diabled CSM completely. But yet again, I was stuck at OsxAptioFix.

 

To clarify, he is referring to the error you get using legacy mode. It sounds like you need to use legacy mode. The other error is from using uefi.

 

I have already told that I have used legacy mode and got stuck at root device UUID...

Link to comment
Share on other sites

No. I was actullay referring to the system I was trying to install. And I am Using Olarila's RAW image with Dual Bootloader.

 

I don't get the part why a modified kernel does not work ? Why do we have to patch the kernel from Mac ? What is the difference ? And why Clover can not patch the kernel on the fly ?

Link to comment
Share on other sites

The following guide is a step by step guide on how to install Mac OS X onto a custom PC Configuration. For installations onto systems that require the use of a modified Kernel you must install using a Real Macintosh Computer or a Hackintosh that supports UEFI booting as Clover Kernel injection does not currently support Mac OS X 10.10. This includes x99 and AMD based systems.

Link to comment
Share on other sites

Clover has never had an option to patch kernels on the fly, aside from the built-in options such as the kernelpm (early reboot) patch.

 

Root Device UUID errror = can't load the kernel

AptioFixDrv error = need to use legacy boot. Even though your system supports UEFI, Clover is having trouble with UEFI installations on some X99 boards.

 

This is my understanding of it (Rampage Dev, correct me if I'm wrong): Booting a patched kernel with an installation USB vs. an existing installation is different. The problem is that you can't boot the Yosemite installer on a computer that requires a patched kernel to boot (unless it is one of the built-in options). In previous versions of OS X, you could simply replace the kernel in the installer with a patched one. With Yosemite, it is now only possible to replace the kernel once the system is installed. The obvious solution would be to just "inject" the kernel, meaning load the patched kernel from say, the root of the drive or something. This isn't currently working in Yosemite. So the only way to install it is from another computer, and then afterwards replace the kernel with the patched one. 

 

If you don't have a real Mac, my suggestion is to either borrow a friend's for the installation process or stick with Mavericks until this is resolved (EDIT: sorry, I see you have a GTX 980 so I guess Mavericks is not an option).

 

Disappointing to hear the RVE is only working with Legacy Clover, this is the board I was looking into for my next build.

Link to comment
Share on other sites

Here is the issue with 10.10:

 

With Apples changes to compression and where and how the Kernel is used. The issue is the prelinked kernel that can not be changed. 

 

That said you can install 10.9 with a modded kernel without issues. 

 

More technical information can be found here:

 

http://sourceforge.net/p/cloverefiboot/tickets/97/

Link to comment
Share on other sites

You can create a Clover installer easily if you have access to the patched kernel. Build an installer using "createinstallmedia". Use Pacifist to extract the /System/Libray/Kernels folder from the Install OS X Yosemite.app (In the Essentials.pkg). Copy the patched kernel to the extracted Kernels folder and then copy the Kernels folder to the USB /System/Library/ folder. Install CloverUEFI and your done creating a working installer. On the reboot of the first stage of the install, boot to installer again and run Terminal, copy the patched kernel to new system drive. Exit terminal and reboot, the install should complete successfully. This process works fine on a GA-X99M-GAMING 5 and 5930K.

Link to comment
Share on other sites

You can create a Clover installer easily if you have access to the patched kernel. Build an installer using "createinstallmedia". Use Pacifist to extract the /System/Libray/Kernels folder from the Install OS X Yosemite.app (In the Essentials.pkg). Copy the patched kernel to the extracted Kernels folder and then copy the Kernels folder to the USB /System/Library/ folder. Install CloverUEFI and your done creating a working installer. On the reboot of the first stage of the install, boot to installer again and run Terminal, copy the patched kernel to new system drive. Exit terminal and reboot, the install should complete successfully. This process works fine on a GA-X99M-GAMING 5 and 5930K.

 

You can use my USB script to make the USB. This is also not a clean way and can cause issues under 10.10. 

Link to comment
Share on other sites

I had a lot of similar issues. I did once get the installer to load in Legacy mode and install the OS from a USB, unsure how, since I then ran into the OsxAptioFix errors after that.

I re-installed Window 8.1 as UEFI, and disabled CMS in the BIOS. It also seems a bit temperamental - it doesn't seem to like booting via the BIOS menus, only a straight boot to Clover UEFI.

 

I saw Rampage's comment, so now use a USB-SATA to plug the SSD into a Mac - far easier. Upgraded HD to Clover r3113 and added patched kernel.

  Note: Under "Get Info" on the USB disk, uncheck "Ignore ownership on this volume" so it isn't mounted under your user, and can chown to root:wheel

I used Rampage's X99.dmg (many thanks) and got the Yosemite SSD booted, and installed the Nvidia drivers (GTX 980).

It all was working fine on 4K.... I left the machine a while, and for some reason (maybe tried to sleep) it rebooted to Clover on it's own.

Now the kernel size is about 16MB (before Nvidia install it was about 12MB) and have a new OsxAptioFix error:

 

OsxAptioFixDrv

  requested memory exceeded our allocation block

  requested memory: 4068000 - 164D9FFF, Pages 12472, Size 12472000

  Reloc block: 10E7F000 - 272E5FFF, Pages 16467, Size 16467000

  Reloc block can handle memory requests: 0 - 16466FFF

 

Tried the old 12MB kernel in cache and prelinkedkernel, but no joy.

 

Unsure why the system rebooted. Any suggestions much appreciated.

 

As an aside, boot args were

  -v npci=0x2000 kext-dev-mode=1    with nv_disable=1 then nvda_drv=1

 

/EFI/CLOVER/drivers64UEFI

  FSInject-64.efi

  HFSPlus-64.efi

  OsxAptioFixDrv-64.efi

  OsxFatBinaryDrv-64.efi

 

kext in /EFI/CLOVER/kext/10.10  (seemed to work so didn't place in /S/L/E)

 

I turned on both boot debugging and kernel debug which was echoed to the screen which was useful.

  • Like 1
Link to comment
Share on other sites

Back up and running...

Simply mounted HD via USB and updated cache :  kextcache -u /Volumes/MacHD

 

Apps I did download via the AppStore won't launch now - guess it's created a new MAC addr for Wifi, since there are two WiFi devices listed in Networks - odd.

 

Great to have the machine working with X99, CPU and GTX 980.

 

Extensions are:

AppleACPIPlatform.kext

AppleIntelE1000e.kext
FakeSMC.kext
GenericUSBXHCI.kext
IOPCIFamily.kext
NullCPUPowerManagement.kext
VoodooTSCSync.kext
 

Going to have a look at Audio. Some things that are not working

   Bluetooth

   RAIDed Disks via motherboard - appears as two disks, writes not copied

   Thunderbolt Adaptor

   USB - high current warning - maybe tick box in Clover

     USBF: 4.870 The IOUSBFamily did not receive enough extra current for the SuperSpeed device (ASM107x) at 0x15500000, asked for 400mA but got 0 mA

   Wired Ethernet - ext not loading

kernel[0]: Kext com.insanelymac.driver.AppleIntelE1000e - library kext com.apple.iokit.IONetworkingFamily not found.

kernel[0]: Can't load kext com.insanelymac.driver.AppleIntelE1000e - failed to resolve library dependencies.mcache: 16 CPU(s), 64 bytes CPU cache line size
kernel[0]: mbinit: done [128 MB total pool size, (85/42) split]
kernel[0]: Kext com.insanelymac.driver.AppleIntelE1000e failed to load (0xdc00800e).
kernel[0]: Failed to load kext com.insanelymac.driver.AppleIntelE1000e (error 0xdc00800e).
kernel[0]: Couldn't alloc class "AppleIntelE1000e"

 

Will see what I can get working :)

Link to comment
Share on other sites

I had this issue and I solved it by going into my EFI partition and navigating to "/EFI/EFI/CLOVER/drivers64UEFI/" and deleting (or just save it in case this doesn't help you) "OsxAptioFix.efi" and replacing it with "OsxAptioFix2Drv.efi". I've attached it for you to try out.

 

You'll need a way to access the EFI partition and modify the files. I used a Macbook Air and connected my SSD via USB.

AptioFix2Test3.zip

Link to comment
Share on other sites

Cheers Garry, I'll give it a go.

 

For the EFI partition I enable the DiskUtility debug menu and turn on "Show every partition"

   $ defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

 

Can also mount the EFI in Windows with diskpart command.

 

Shame the UEFI shell can't read/write HFS+ (as far as I know)

Link to comment
Share on other sites

I had this issue and I solved it by going into my EFI partition and navigating to "/EFI/EFI/CLOVER/drivers64UEFI/" and deleting (or just save it in case this doesn't help you) "OsxAptioFix.efi" and replacing it with "OsxAptioFix2Drv.efi". I've attached it for you to try out.

 

You'll need a way to access the EFI partition and modify the files. I used a Macbook Air and connected my SSD via USB.

Nope that did not work either. No one was able to pass PCI Configuration begin on Rampage V Extreme... I have insatlled Mavericks though but no use since it does not support Maxwell!

Link to comment
Share on other sites

Umm... you are wrong.

 

You have the 8 core and with that CPU you need to Roll Backs found on Stiga's post and on my x99 DMG for 10.10.X ... This has been well documented for this CPU and other boards and CPUs for years. You learned something today.

Link to comment
Share on other sites

Umm... you are wrong.

 

You have the 8 core and with that CPU you need to Roll Backs found on Stiga's post and on my x99 DMG for 10.10.X ... This has been well documented for this CPU and other boards and CPUs for years. You learned something today.

 

Same {censored} over and over again. There is no one on the internet that got passed PCI Configuration begin with Rampage V Extreme using Yosemite. I have spent an entrie day and more than 50 {censored} combinastions both in UEFI and Legacy mode bro. So I know what CPU I am using, I have used Stinga's Kexts, I have used latest Clover, thousands of AptioFix {censored}...

 

I used Mavericks and I have installed it but Mavericks has no Maxwell support. So it was nothing more than a useles bunch of {censored}.

 

To sum up, If you have a Rampage V Extreme mobo and 5960X CPU and you have installed Yosemite, make a video of it. Show us a proof. If not, please do not talk and wait for someone to come up with a solution cuz I am really bored of this {censored}.

 

Hence, your script does not even patch the kernel...

Link to comment
Share on other sites

all, I do have both ASUS X99 with the i5960x up and running stable as a rock.

using the latest BIOS and clover.

 

Setup: 

X99 Rampage V, BIOS Rev. 901, 5960x, 32GB DDR4, 2 x SSD, 4 x spinning media, all SATA6, 1 DVD/BD Drive, 2 x Geforce 780 ASUS

same works with X99 deluxe

 

I followed the guide on rampage-dev; using the SSDTs and Kexts

by the way - a big thanks to Andrew for his great support.

 

If you use latest clover, tick mark the AptioFix-2 on setup - that does it.

 

Jens

Link to comment
Share on other sites

this is a shame ...

Actually I won't help people who are not believing in that.

 

But, for the rest of the community: rampage-dev has a guide - you need to use OS10.9.5 IOPCIFamily.kext for overcome that. there are also posts here. I was one of the first who had the X99 up and running. 

so, either you look at rampage´s guide or you search for the X99 5960x posts here 

 

jens

Link to comment
Share on other sites

http://www.insanelymac.com/forum/topic/301585-haswell-e-mach-kernel-patch-5960x-5830k-and-5820k-yosemite/page-10?hl=+asus%20+x99

 

and.... you need to do a install from a real Mac or another stable hack.

then once drive / install is ready, patch the kernel (see link) - then add clover and the rampage kexts - make sure you patch the iopci.... 

simply follow the guides. 

 

got it?

 

this was my last post on that

jens

Link to comment
Share on other sites

 Share

×
×
  • Create New...