-
Notifications
You must be signed in to change notification settings - Fork 22
Guide bugs #6
Comments
I believed that UseMacAddress0 was the correct value but it seems that this is incorrect from your comment on AppleLife. So any 6 character MAC address, no specific values have to be chosen?I do understand that you can use the correct Mac address of the hardware but choosing a different value will have no affect? And if it does matter, would you use the BlockID or the deviceID of the NIC? I assume DeviceID but want to make sure
Will fix, thanks for the clarification
That's my fault for making a guide on extremely alpha projects, I will try to clean it up. And thank you for taking the time to point out the issues, I really do appreciate it. And one last question: |
ROM must either be Apple ROM (dumped from a real Mac), or your NIC MAC address, or any random MAC address (could be just 6 random bytes). What is better is discussible and depends on how you configure iMessage. In any case it must not be empty unless you run OpenCore on a real Mac. Also, it is As for a timeline, there is no particular date I could give you now. 0.0.3 will remain being recommended to developers only, but I would say we are quite stable and feature rich now despite the alpha. You could probably try it with general people as long as they are careful enough to read everything. |
Hello,
Some notes:
ROM: <> (Automatically filled in)
Nope, it is not, must contain a 6 character MAC address, could be entirely random. More details: https://applelife.ru/posts/727913
Blocks NVRAM variables, not needed for us. Delete the entires there.
Please leave a note that if a variable exists in NVRAM,
Add
will not overwrite it. You could think ofAdd
as setting default values. To forcibly overwrite the variable value at every boot you will want to add it toBlock
. Normally undesired, as you could usesudo nvram
, but worth understanding clearly.Enables GOP, AptioMemeoryFix already has this
Do not rely on it. It will be gone from AptioMemoryFix in the future. On almost all firmwares it must be YES.
IgnoreInvalidFlexRatio: NO
Mention that it is needed on pretty much all hardware prior to Skylake.
Also, we will have a kext list very soon in Docs/Kexts.md in OpenCorePkg. Stuff like NullCPUPowerManagement is compatible, but is only needed on AMD.
The text was updated successfully, but these errors were encountered: