Jump to content



Member Since 08 Feb 2011
Offline Last Active Nov 28 2017 06:16 PM

Posts I've Made

In Topic: Clover General discussion

28 November 2017 - 06:16 PM

Guys, I have 2 Systems to Compare...:


1. System:

i7-6700 on H170 (Aptio 4 + ModBios (SMI/CSM etc disabled))

Intel 600p NVME (With APFS+Trim)

Boot Time: Really Fast


2. System:

i9-7900x on X299 (R6E, Aptio 5 + BiosMod not possible, no tools available)

960 Pro NVME (With APFS+Trim)

Boot Time: Fu..ing Slow



I made a preboot.log of both, on the x299 there is an entry (that takes up all the time...)

4:511  0:365  GUI ready

44:568  40:056  Found BIOS RSDP at F0010

But I don't get any information, what exactly takes that long... I don't believe that have something todo with ACPI Tables...


On the fast loading System (1), I have:

1:911  0:112  GUI ready

17:172  15:261  BootVariable of the entry is empty
So that makes Clear, that something doesn't get logged after "GUI ready"
Ive Attached the whole preboot logs of Both Systems...
Ive answered my question myself, after I readed my post to correct typos... I need to activate Debug Log in config, to see what exactly happens....
Im really tired and stupid :-(
Cheers :-)

In Topic: Clover General discussion

05 November 2017 - 08:31 PM

Your NVRAM breaks because it is being locked by your firmware, this is normal for almost all firmware but you should not have that problem with AptioFix2. Also, you are way off on what the AptioFixes do, with out it you wouldn't even be able to boot. AptioFixes add things Apple firmware expects that UEFI doesn't do, changes ACPI memory page types so they are not moved, and then patches the kernel to properly start and fix the device tree. AptioFix creates a relocation region, loads the kernel there, then moves it to the spot it requested. AptioFix2 tries to give it the region the kernel wants to begin.


EDIT: Also maybe try to solve the problem yourself instead of acting like other people should do it for you. I do this because I like to, not because you feel entitled for others working for you without putting in any effort of your own. There are developers who have been doing this for a decade, I myself have for like six or seven years. Do some research, learn, figure the problem out, find the solution. Believe me, no one will do it for you unless they happen to have the same problem. Sometimes, it's the configuration and your firmware settings though, too. But most of the time you need to accept it doesn't work or continue and try to find a way to change it. And just for the record, the NVRAM issue has been known since UEFI booting macOS has been possible, it is an SMI locking problem.


I asked already in my first post, that I don't want anyone spend to much time with this, I know how the things work here apianti.

And I spend my self a lot time, long time ago with the acpi tables and support for some other users...


However, you are right at all points.


I write next time if I found more things out, I will post again.

The first step I need to do anyways is to deactivate SMI lock, that should be np.


And as long we have working nvram with the emulated driver, everything is ok.



There's a topic on this if you're so inclined.


There are exactly all infos, that I've searched, thank you very much!


This issue is probably not SMI related, the region is not moved, iirc the SMIs trigger and yet it does not work... A5 has more checks for var names, but I didnt find out what they were supposed to do before I got bored

Gesendet von meinem ONEPLUS A5000 mit Tapatalk


Seems like you have investigated already time into this.

I think that would be my problem too. Just deactivating SMI Locking will not fix Nvram :-)))



However, thanks very much to everyone here.


Just to be clear, I don't want to waste time here of anyone.

I need to fix my problems myself and I have a lot of them with x299 platform...

Everything works Perfect with x299 on the first look, but unsupported cpu with VoodooTSC and Emulated Nvram sucks.


Thanks to all & Cheers :-)

In Topic: Clover General discussion

05 November 2017 - 02:48 PM

Nonworking NVRAM is a known issue on newer AptioV boards. Are you using EmuVariableUefi.efi?


Yep, ive seen, but there are ways...

1. We can disable SMI Lock in bios (to make things easier)

2. We had same Problems on Aptio4 long time ago but i dont know how it's fixed... (On my Laptop nvram works even with SMI Lock enabled...(Aptio4 Haswell))


So there must be a way, there are just not enough benefits, as far as Emulated Nvram exists...


In my Opnion, 50% of the Aptiofix driver is useless, if nvram doesnt work.

Thats why i want to get that fixed, but no one want to spend time on this...



In Topic: Clover General discussion

04 November 2017 - 10:17 PM

CloverUpdater was not changed since 4000 when it changes 2.3 -> 2.4.

Did you check any other 4xxx revision?

Change AptioFix <-> AptioFix2 or vice versa.

Remove "-v" from boot-args. 

Remove nvram.plist from EFI partition and from Mac root partition.

Slice, Aptiofix or Aptopfix2 doesnt matter, nvram doesnt work...


i can write something into nvram (with terminal and sudo nvram....) but on next boot its gone...

Thats the Problem, why im asking...


Seems for me, like Aptio maps the wrong Memory region...



In Topic: Clover General discussion

02 November 2017 - 10:36 PM



Thank you for the prevous Answer (with the cpuid inject thing), that solved my problem :-)


I have another one...

I want to get aptiofix working...


I just forgot, how to debug it...

Last time ive dumped the memory mappings was ~4 years ago...


Maybe you can Point my Nose to the right direction :-)


I dont want to waste your time.


Cheers :-)



Just the Specs (In case if its already fixed in a future clover version)

Asus X299 R6E + 7900x + 64GB Ram


Cheers :-)

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy