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.
Hi. On my MacPro I have a strange behavior that I guess is related to OpenCore. I can't be totally sure, because it's something I don't notice immediately but previously for some months I used Catalina through Dosdudes patcher and didn't notice it (and sure it didn't happen before). What going on? Every time I reboot my MacPro, Archicad says license key is damaged and need to be repaired. This means that I must upload the license on software house server and download it again. Nothing to bud, until key remains reparable and Graphisoft won't ask me way I have corrupted license even more times in a day.
Before I installed OpenCore, this happened only after a system update. Now it happens at every reboot. Is there someone that can figure what can cause this? And is there's something I can do to prevent it?
I would start with understanding how Archicad is managing the license keys. In most cases the Mac will connect on startup or on application startup (using a license daemon) to a remote server to check if the locally installed license is still valid.

So I would assume this check does not really work out on boot, possibly because you did not allow a license daemon to work through the security pref pane?

Search the web for Archicad license management....
 
I would start with understanding how Archicad is managing the license keys. In most cases the Mac will connect on startup or on application startup (using a license daemon) to a remote server to check if the locally installed license is still valid.
Older versions of Archicad used a USB dongle (WIBU box for older users like me, Codemeter in a second time). Since some years, Graphisoft replaced hardware dongle with a software dongle. The software that enabled software dongle, in the same time disabled hardware dongle. Software dongle works pretty the same as hardware dongle: I can use it completely off-line (if it won't corrupt as now happens every reboot), and I can transfer the dongle to any my computer (Mac or Windows) uploading the key to Graphisoft Server and downloading it again on another computer. In any case, I can use the software only on one computer at time. Uploading and downloading again can be used to repair the dongle, if it went corrupted for some reasons (that happened mostly after macOS updates). But now it happens to
 
Tried to update from 11.2.3 to 11.5.2 using OTA delta update. Got stuck part way through.

Managed to boot back into a Catalina partition and could see there was an "Update" partition created on the drive I was using for Big Sur. Tried a few different upgrade routes, and ended up deciding to nuke the drive and do a fresh install of 11.5.2 along with everything else.

Success. Open Core 0.7.2 using Martin Lo's package. Made a bootable USB installer using the Dortania guide https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html
 

Attachments

  • Screen Shot 2021-08-14 at 6.40.06 pm.png
    Screen Shot 2021-08-14 at 6.40.06 pm.png
    100.6 KB · Views: 85
Tried to update from 11.2.3 to 11.5.2 using OTA delta update. Got stuck part way through.

Managed to boot back into a Catalina partition and could see there was an "Update" partition created on the drive I was using for Big Sur. Tried a few different upgrade routes, and ended up deciding to nuke the drive and do a fresh install of 11.5.2 along with everything else.

Success. Open Core 0.7.2 using Martin Lo's package. Made a bootable USB installer using the Dortania guide https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html

you noticed the incompatibility and race condition thing?
 
  • Like
Reactions: 0134168
Tried to update from 11.2.3 to 11.5.2 using OTA delta update. Got stuck part way through.

Managed to boot back into a Catalina partition and could see there was an "Update" partition created on the drive I was using for Big Sur. Tried a few different upgrade routes, and ended up deciding to nuke the drive and do a fresh install of 11.5.2 along with everything else.

Success. Open Core 0.7.2 using Martin Lo's package. Made a bootable USB installer using the Dortania guide https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html
You most likely would have had success continuing to force reboot till you got to a desktop, this is normal for every 11.3+ or Monterey install or update.
 
I
You most likely would have had success continuing to force reboot till you got to a desktop, this is normal for every 11.3+ or Monterey install or update.
I had hoped to force my way through it, but there came a point where I cut my losses and restarted.
Happily working away now and I can get on with my work.

Locked down, down under here - so it's not like we can go anywhere, visit family etc. 200 days of lockdown in Melbourne since last year...
 
After playing around with the ram, we can now say that we can run 256GB 8x32GB of ram in this Mac Pro.

The 1.12TB of ram showing here is just to see how far I could go with the config.

No more " Notification Message Error " anymore. I do not even think that Notification disabler.Kext is needed anymore too..

Everything runs smooth..View attachment 999535View attachment 999499
205maxi, may I ask how to accomplish this. I 128ram in my MP. Martin is cool enough to let me know to find a proper post. I found this and something about the Plist. All this is really new to me and finally got OC with 11.2.3 up and running.
 
205maxi, may I ask how to accomplish this. I 128ram in my MP. Martin is cool enough to let me know to find a proper post. I found this and something about the Plist. All this is really new to me and finally got OC with 11.2.3 up and running.
There is a thread just for 32GB DIMMs experimentation, please ask for support there and not here.

 
But it is disabled by default.

Config.plist says:
<string>latebloom.kext</string>
<key>Comment</key>
<string>PCI delay for BS/Monterey</string>
<key>Enabled</key>

OC 0.7.2 Martin Lo package - think this means it is enabled?

Now to get USB working. USB 2 works however I have an old UBS 1.1. headset which is not recognised. Bluetooth working fine. Seems all my meetings are via Zoom these days, being locked down and all. Not being sociopolitical - just stating the facts.
 
OK I saw a tip here on MR and plugged in an old wired Apple extended keyboard. USB 2.0.

Plugged my old USB 1.1. headset into the keyboard and voila - it works. Should now be able to Zoom more easily.

Thanks everyone.
 
Config.plist says:
<string>latebloom.kext</string>
<key>Comment</key>
<string>PCI delay for BS/Monterey</string>
<key>Enabled</key>

OC 0.7.2 Martin Lo package - think this means it is enabled?

Now to get USB working. USB 2 works however I have an old UBS 1.1. headset which is not recognised. Bluetooth working fine. Seems all my meetings are via Zoom these days, being locked down and all. Not being sociopolitical - just stating the facts.

yes, the key: Enabled, is it true or false?
 
  • Like
Reactions: hwojtek
Running Big Sur 11.2.3 in my Mac Pro 4,1->5,1 with the @h9826790 package, works like a charm. I have cloned the SSD and updated to 11.5.2., activating Latebloom. The installation went smooth, no problems at all. Boot at first try and working with it now. Seems to run perfect.

Thank you so much, @h9826790 and everyone involved.
 
Last edited:
Running 11.2.3 on a 5,1 using OC 0.7.2 (Martin's package with a changes, though a stock install of it changes nothing). Currently trying to get Windows installed alongside on a separate drive using the Windows Install Appendix. Tried a handful of different W10 USBs. I created one via the appendix guide's method, one via W10's Media tool and one that was a kitbashed W11 installer. None appeared in my boot select menu; I have triple checked that the config.plist has the driver and that it exists in the EFI partition.
Any suggestions for how to get this to cooperate?
 
Running Big Sur 11.2.3 in my Mac Pro 4,1->5,1 with the @h9826790 package, works like a charm. I have cloned the SSD and updated to 11.5.2., activating Latebloom. The installation went smooth, no problems at all. Boot at first try and working with it now. Seems to run perfect.

Thank you so much, @h9826790 ands everyone involved.
How about the WiFi ?, does that still work ?
 
How about the WiFi ?, does that still work ?
Yes, working so nice. But I replaced the original ones with a new Wifi/Bluetooth card long time ago.
 

Attachments

  • trifero_2021-Aug-15.jpg
    trifero_2021-Aug-15.jpg
    75.8 KB · Views: 88
  • Captura de pantalla 2021-08-16 a las 5.55.47.png
    Captura de pantalla 2021-08-16 a las 5.55.47.png
    74 KB · Views: 95
  • Captura de pantalla 2021-08-16 a las 5.54.44.png
    Captura de pantalla 2021-08-16 a las 5.54.44.png
    84.7 KB · Views: 103
Hello,

I have a MacPro 2012 running BigSur with Opencore 7.2 (Martin Lo package).
It's a new installation I've done, drive was completely wiped.

I have in this Mac installed an iMac Wifi card which is using the chipset BCM943602 and this adapter (attached image of it)

Screenshot 2564-08-16 at 11.05.32.png

I am getting the Wifi to work fine but bluetooth is not detected and I would like to use airdrop.
I've tried with and without attaching the USB lines to the bluetooth connector as some mentioned in another guide but with no difference.

Is this an adapter problem from your experience and I will need to get a PCI-e adapter instead or there something else I can do to fix this?

Thanks.
 

Attachments

  • 1629086895143.png
    1629086895143.png
    102.2 KB · Views: 86
I tried updating 11.5.2, and it hangs halfway through, don't know what I'm doing wrong. Will have to buy another wifi card it seems. currently on 11.2.3
 
I have in this Mac installed an iMac Wifi card which is using the chipset BCM943602 and this adapter (attached image of it)
Sorry about your predicament, but this is the wrong thread to ask about Wi-Fi/Bluetooth hardware updates. Such concerns have nothing to do with OpenCore.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.