Contribute
Register

[Guide] Booting the OS X installer on LAPTOPS with Clover

black.dragon74 said:
Clover Rev4368+ has working native NVRAM on AMI systems. For that, OsxAptioFixDrv2-64 is preferred. Maybe add a note for it?
Click to expand...

Recommended Clover build is the RehabMan fork. I have not updated to the latest changes in OsxAptioFix2Drv-64.efi.

There is a lot of churn there and more to come. Looks like it will be renamed OsxAptioFix3Drv-64.efi or AptioMemoryFix.efi. And looks like OsxAptioFixDrv-64.efi and OsxAptioFix2Drv-64.efi changes will be reverted, as this change doesn't work for everyone (sounds like some changes to OsxAptioFixDrv-64.efi have completely broken it).

I'm waiting for the dust to settle. And, of course, I have to merge those changes and test for all my published guides (as much as possible anyway).
 
RehabMan said:
There is a lot of churn there and more to come. Looks like it will be renamed OsxAptioFix3Drv-64.efi or AptioMemoryFix.efi. And looks like OsxAptioFixDrv-64.efi and OsxAptioFix2Drv-64.efi changes will be reverted, as this change doesn't work for everyone (sounds like some changes to OsxAptioFixDrv-64.efi have completely broken it).
Click to expand...
You predicted it quite right.
 
RehabMan said:
Now testing with merged Clover and AptioMemoryFix.efi on a variety of computers.
Click to expand...
Means a new release from you sometime soon?
Lemme try using AptioMemoryFix instead of AptioFix3. How can I check if I have defragmentation issue?
 
black.dragon74 said:
Means a new release from you sometime soon?
Click to expand...

I'm pretty busy lately, so it may be some time before I can test on all my computers and put out a build.
I may push updated source sooner than that for those that want to build their own.
Note that building AptioMemoryFix.efi is a separate task as it is not part of Clover.

Lemme try using AptioMemoryFix instead of AptioFix3.
Click to expand...

I think AptioMemoryFix is just updated OsxAptioFix3Drv-64.efi.

How can I check if I have defragmentation issue?
Click to expand...

I don't know which issue you're referring to.
 
RehabMan said:
I may push updated source sooner than that for those that want to build their own.
Click to expand...
Looking forward to it.

RehabMan said:
I don't know which issue you're referring to.
Click to expand...
Sorry. My bad. That was not meant to be “defragmentation”.

I was asking about memory fragmentation issue. How do I check if I am affected by this?

RehabMan said:
I think AptioMemoryFix is just updated OsxAptioFix3Drv-64.efi.
Click to expand...
Oh! Okay. I thought it was a third party driver (read somewhere on IM)

Regards
 
black.dragon74 said:
I was asking about memory fragmentation issue. How do I check if I am affected by this?
Click to expand...

Still don't know which "memory fragmentation issue" you're referring to.

Oh! Okay. I thought it was a third party driver (read somewhere on IM)
Click to expand...

Both come from vit9696 work. It has gone through several renames...
 
How to disable the 32MB patch for DVMT-prealloc, my one is set to 128MB as default. Thanks.
 
pcctsch said:
How to disable the 32MB patch for DVMT-prealloc, my one is set to 128MB as default. Thanks.
Click to expand...

You will find the patch in config.plist/KernelAndKextPatches/KextsToPatch.

But, how are you discovering your DVMT-prealloc is 128mb?
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top