Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

mangombia

macrumors member
Jun 12, 2019
84
16
Nashville, Tennessee
I thought updated versions of OpenCore were released on the first Monday of each month (which would have been yesterday). I also thought I read somewhere that the development team was "on vacation" and there wouldn't be an update until Sept. Anyone have any insight?
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I read somewhere that the development team was "on vacation" and there wouldn't be an update until Sept. Anyone have any insight?
It seems that they are still working on it.
Screenshot 2020-07-08 at 12.35.31 AM.png
 
  • Love
Reactions: 205Maxi

mangombia

macrumors member
Jun 12, 2019
84
16
Nashville, Tennessee
In order not to rush things because of Big Sur, the July release is skipped.
Been monitoring the chatter regarding BS super-SIP issues, SMBIOS spoofing, etc. A lot to work around. Understandable not doing a release until those can be understood and handled, particularly since 0.5.9 is rock solid stable with Mojave/Catalina & Win10 (at least it is for me). I've decided not not get caught up in trying to shoe horn BS into either of my cMPs while in either the private or public beta stages. I'm content to wait until release for both it and OC.
 
  • Like
Reactions: cdf

6DecadesLater

macrumors regular
Jun 5, 2020
106
45
Northern California
I actually got this resolved. I ended up just using a base config.plist file instead of @h9826790's (not that it was the .plist file that was the issue! Thanks btw) and making any edits I wanted to use on OpenCore. Everything worked perfectly! But then I wanted to enable NightShift and followed the directions on the first page. I had the same exact problem as before. My Mojave SSD would boot but not the NVME. I mounted the EFI and deleted the NightShiftEnabler.kext. I remembered that I had installed Lilu, WhateverGreen, and AppleALC on my NVME previously. OpenCore was injecting those kexts and Catalina was also loading them as well. I made sure to delete those kexts from my Cataline NVME, grab the latest, and stick them into EFI partition. Boom. Everything worked!

Double check and see if you have the same problem.

Speaking of kexts, what's the best way to get HDMI/DP Audio? Do I inject the kext using OpenCore using AppleALC?

EDIT: OpenCore is on my SSD not on my NVME. I don't believe installing OpenCore on an NVME is recommended.

I installed OC on an NVME, I used Carbon Copy Cloner to copy Mojave from a SATA drive to the NVME. I then installed OC on the NVME. I then updated the NVME Mojave to Catalina. It works well. I did have some issues a couple of days ago I posted but I'm sure I had messed something up. I ended up re-installing OC on the Catalina drive. Redid the HW accel, nightshift, etc. Everything is working fine now and seems very stable. Posting this to say OC on NVME seems to work ok. (SilverStone Technology M.2 M Key PCIe NVMe Adapter to PCIe X4 with Integrated Heatsink SST-ECM24 and Samsung (MZ-V7E1T0BW) 970 EVO SSD 1TB - M.2 NVMe Solid State Drive).
 
  • Like
Reactions: JedNZ

HuRR

macrumors regular
Jul 21, 2003
188
60
You make it too complicated, all you need is just this in the PlatformInfo section. You better simply use a Text Editor to do that.
Code:
    <key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>SMBIOS</key>
        <dict>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
            <key>ProcessorType</key>
            <integer>1281</integer>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>
N.B. my example above assume the config also activate HWAccel. If not, please ignore the
Code:
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
[automerge]1594047918[/automerge]

No need to touch ACPI or DSST for cMP.

I have a single x5680 and added this code to the .plist because I wanted it to show as 3.33. Still shows as 3.3 instead of 3.33. Is that not a thing?
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I have a single x5680 and added this code to the .plist because I wanted it to show as 3.33. Still shows as 3.3 instead of 3.33. Is that not a thing?
That's completely another issue.

That 3.3GHz is because you spoofed the SMBIOS for HWAccel. Therefore, macOS use the iMac Pro format to display the CPU info (only 2 digits). If you want it to show 3.33GHz (3 digits), you can disable SMBIOS spoofing.
 

HuRR

macrumors regular
Jul 21, 2003
188
60
That's completely another issue.

That 3.3GHz is because you spoofed the SMBIOS for HWAccel. Therefore, macOS use the iMac Pro format to display the CPU info (only 2 digits). If you want it to show 3.33GHz (3 digits), you can disable SMBIOS spoofing.

Ahh Gotcha. I have an R9-280x so I don't have the need for HWAccel since there is none. Thanks again for all your work!
 

dataid

macrumors regular
Feb 1, 2020
100
66
USA
They mentioned they would skip July release here due to WWDC

Are you suffering from (OCMRDS) OpenCore Monthly Release Deprivation Syndrome?
ATTENTION! ATTENTION!

Through the Github project known as OpenCore-Factory you can get the latest, automatically built release of the current version of OpenCore under development. Currently pre-release builds of 0.6.0 incorporate the latest commits and are released automatically every 8 hours. You may never feel OpenCore deprived again!

However README.md file states:

THIS PROJECT IS NOT OFFICIALLY SUPPORTED BY ACIDANTHERA.
BUILD RESULTS IN THIS REPO ARE AUTO-GENERATED WITHOUT ANY TESTING.
I'M NOT RESPONSIBLE FOR ANY OF THOSE BUILD RESULTS.

TAKE YOUR OWN RISK WHEN USING THE BINARIES.

The Github project is known as OpenCore-Factory. It is the project of williambj1.
Here is the URL: OpenCore-Factory on Github

Sign up to watch the project and you will automatically receive an email titled, Bat.bat, like the one below informing you of the latest changes.

2020-07-07
Repository: williambj1/OpenCore-Factory · Tag: 2020-07-07 · Commit: 03100b8 · Released by: williambj1

Changes
OpenCorePkg
  • OcAppleKernelLib: Fix arg order for OcKernelLoadKextsAndReserve
  • OcAcpiLib: Check for invalid reset register width

This release has 4 assets:

  • OpenCore-0.6.0-DEBUG.zip
  • OpenCore-0.6.0-RELEASE.zip
  • Source code (zip)
  • Source code (tar.gz)
Visit the release page to download them.


You are receiving this because you are watching this repository.
 
  • Like
Reactions: cdf

205Maxi

macrumors regular
Nov 3, 2019
175
53
Same as before. Can perform update "natively" with complete iMac Pro SMBIOS spoofing.
View attachment 931636

Once finished, you can remove the SMBIOS spoofing.
View attachment 931637
Did you use 0.6? or 5.9?

I got in trouble you know that I have Dual Procs, it installed it and on the third reboot boom blackout no screen and impossible to boot back on the SSD nor the get open core loading.

Thank you nice pics.
 

Charmandrigo

macrumors member
Jul 3, 2018
94
22
You can check the first few pages of this thread. We posted about how to completely spoof the cMP as iMac Pro at there.

Anyway, we just need to spoof the cMP ident for installation. Once Big Sur is installed, we can boot Big Sur with the current OpenCore config and keep the 5,1 ident.
View attachment 926218
I have a quick question regarding this screenshot, you still got hardware acceleration while having the Mac Pro 5,1 ID? Thought you had to spoof always as an iMac to have a successfull HW accel like this guide says on OP
 

nobullone1964

macrumors 6502
Oct 20, 2018
279
111
I have a quick question regarding this screenshot, you still got hardware acceleration while having the Mac Pro 5,1 ID? Thought you had to spoof always as an iMac to have a successfull HW accel like this guide says on OP
Works for me. The standard config.plist made everything all good. 5,1 success!
 
  • Like
Reactions: h9826790

nobullone1964

macrumors 6502
Oct 20, 2018
279
111
Is it possible to change the "esc" key to "option" key to pull up the boot picker when config.plist is set to boot straight? It would feel somewhat authentic....
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
Is it possible to change the "esc" key to "option" key to pull up the boot picker when config.plist is set to boot straight? It would feel somewhat authentic....

The Option key should also work, but the timing has to be right. Too early and the keypress is picked up by the firmware of the Mac Pro to bring up the native boot picker (or a black screen in the case of a standard graphics card). The right timing is shortly after the native chime.

By the way, with the right timing, Command and R should work to enter recovery through OpenCore, and Option, Command, P, and R to reset the NVRAM.
 

nobullone1964

macrumors 6502
Oct 20, 2018
279
111
The Option key should also work, but the timing has to be right. Too early and the keypress is picked up by the firmware of the Mac Pro to bring up the native boot picker (or a black screen in the case of a standard graphics card). The right timing is shortly after the native chime.

By the way, with the right timing, Command and R should work to enter recovery through OpenCore, and Option, Command, P, and R to reset the NVRAM.
I'm just speaking aesthetics. Forget the timing. I'm talking config.plist is set to boot straight to default drive without the boot picker screen. The current config.plist requires holding "esc" to force the boot picker. I'm just saying assign the "option" key as per a normal Mac. Strictly aesthetic........
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
I'm just speaking aesthetics. Forget the timing. I'm talking config.plist is set to boot straight to default drive without the boot picker screen. The current config.plist requires holding "esc" to force the boot picker. I'm just saying assign the "option" key as per a normal Mac. Strictly aesthetic........

I get the aesthetics. I'm just explaining that the issue is timing. The Option key is already assigned in OpenCore to bring up the boot picker. The problem is that the native firmware is still there and it will detect the key before OC. That's why we also have the Escape key.
 

Macbookprodude

Suspended
Jan 1, 2018
3,306
898
What is the difference with this vs Dosdude's app ? Also, I don't have metal card - can I still use this to install Mojave or Catalina ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.