MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[z0Nker]

tsialex - I would appreciate your analysis of my ROM as well. Please let me know if that would be possible. Regards.

Sorry I looked everywhere and I don’t see how to “public post” a question. I installed opencore on my cmp4,1 flashed to 5,1 & now the cpu reads as a i3 instead of a Xeon ? Also all the videos & instructions on the web are confusing. I don’t know how I did it but I have Big Sur running quite good. But I need help

 

[w1z]

If you want to spoof the ident as well, it make much more sense to use the ident that match the board ID.

e.g. in this case, iMac Pro 1,1

But if the config is only for Big Sur, use the Mac Pro 7,1’s board ID and indent should be the best.

7,1 board ID can activate HWAccel, and activate all ports on the graphic card by default.

I haven’t use the 7,1 board ID in my public package mainly because want to keep the HWAccel support in Mojave.

I can confirm HWAccel is activated with WG kext/DeviceProperties-Add-PciRoot removed from OC config and without using Ident/SystemProductName which causes a memory error to appear on login and a PCI tab under "About this mac" which crashes the about app.

thanks for the tip!

 

[Perana]

Changed the system ident to MacPro7,1 and got the memory error, but nightshift and everything works (also had sidecar appear in my system preferences, but my iPad Pro wasn't showing up at all, changed to MacPro6,1 and lost USB Keyboard and Mouse once booted into Big Sur.

iMacPro1,1 acted the same as MacPro7,1 but no memory error.

 

[TECK]

But if the config is only for Big Sur, use the Mac Pro 7,1’s board ID and indent should be the best.

Can you post the info? Thanks

 

[h9826790]

Can you post the info? Thanks

Open config.plist in any text editor (e.g. TextEdit)

Search Mac-7BA5B2D9E42DDD94

Replace it by Mac-27AD2F918AE68F61

This will inject the 7,1 board ID rather than iMac Pro board ID.

 

[h9826790]

Changed the system ident to MacPro7,1 and got the memory error, but nightshift and everything works (also had sidecar appear in my system preferences, but my iPad Pro wasn't showing up at all, changed to MacPro6,1 and lost USB Keyboard and Mouse once booted into Big Sur.

iMacPro1,1 acted the same as MacPro7,1 but no memory error.

But in Big Sur, if using iMac Pro board ID, most of the ports on the graphic card will be disabled.

And there is a fix for that annoying memory error notification

GitHub - im-not-a-dev/MacProMemoryNotificationDisabler: A simple kext to fix the annoying popup.

A simple kext to fix the annoying popup. Contribute to im-not-a-dev/MacProMemoryNotificationDisabler development by creating an account on GitHub.

github.com

 

[GSXB]

I’m out for work at the moment, tonight I’ll upload it in this post.
Cheers

@GSXB @csxlab

here attached my config.plist and the patched kext to put in the OC/Kexts folder
Clearly pay attention if you think to use my config.plist... I think the best is to only use it about how to insert the strings into your one.

Many thanks, I’m going to compare the two config. Then make a mmm ends to mine and see how I go from there once again thank you 👍👍👍

 

[Paolo-Sp]

Open config.plist in any text editor (e.g. TextEdit)

Search Mac-7BA5B2D9E42DDD94

Replace it by Mac-27AD2F918AE68F61

This will inject the 7,1 board ID rather than iMac Pro board ID.

Please.... With BoardProduct of Mac Pro 7.1 "Mac-27AD2F918AE68F61", FirmwareFeatures and FirmwareFeaturesMask change o remain "03540CE0" and "3FFF1FFF" ?

 

[h9826790]

Please.... With BoardProduct of Mac Pro 7.1 "Mac-27AD2F918AE68F61", FirmwareFeatures and FirmwareFeaturesMask change o remain "03540CE0" and "3FFF1FFF" ?

No need to touch the firmware feature mask, the one that discovered by cdf is fine.

Of course, if you spoof the ident as well, then you can use the native 7,1 firmware feature. Because the 7,1 is supported by Big Sur by default, no need to spoof the firmware feature for anything.

 

[Paolo-Sp]

Thank you so much

 

[PeterHolbrook]

Are there any trade-offs in using a Mac Pro 7,1 spoofing identity instead of an iMac Pro 1,1 one?

 

[h9826790]

Are there any trade-offs in using a Mac Pro 7,1 spoofing identity instead of an iMac Pro 1,1 one?

No more Mojave support, may have that memory error notification (depends on which OS, and what you spoofed. Anyway, already have fix)

 

[lxmeta]

This is what I run in my MacPro have a look here too #4,648

For the memory config I followed the Apple MacPro 2019 scheme -> https://support.apple.com/en-us/HT210103

8 DIMMs is the one we need, note still shows 12 slots. I have configured it on 12 slots scheme because I did not want to see the notification, which as no incidence whatsoever. You would put 1.5TB memory config that it would not change anything.

However when I tried the set the 8 slots according to the supported configuration I would get the error notification. So I reverted back to 12 slots configuration even though we only have 8 slots and the error's gone.

I guess that in the near future if IOIIIO works on the kext notification disabler, that we can properly set the memory config to reflect the true memory configuration of our MacPro5,1.

I preferred to set it that way so 1 less .kext in the driver folder.


I would love to have it configured this way which reflect the true config but then you get error and orange check, which I don't like

This looks awesome! I have a 2 CPU 4.1 and a 1 CPU tray 4.1 and would like to try this as well. Can you share your config, or at least the relevant parts? Many thanks in advance...

 

[w1z]

I just tried the memory notification disabler but it didn't work, with or without -lilubeta added and with OC compiled an hour back.

I also noticed the 7,1 ident made the cMP's performance sluggish as well as losing fan/temp sensors. The network interfaces were reset and the mac pro was being reported as a 2019 Mac Pro under Apple ID devices when it was previously showing as Mac Pro 5,1.

It's best to stick with @cdf firmware feature + 7,1 board ID on the cMP under Big Sur.

 

[PeterHolbrook]

^ I'm not sure I can follow what appear to be conflicting claims about SMBIOS spoofing. Is it possible to reach a consensus? What is the best known configuration? iMac Pro 1,1 spoofing? Mac Pro 7,1 spoofing? A mixture of both? In the view of those who have experimented with this, which is the best config.plist syntax? Can it be improved upon? In what sense would an alternative syntax be better and in which one would it be worse?

 

[h9826790]

I just tried the memory notification disabler but it didn't work, with or without -lilubeta added and with OC compiled an hour back.

I also noticed the 7,1 ident made the cMP's performance sluggish as well as losing fan/temp sensors. The network interfaces were reset and the mac pro was being reported as a 2019 Mac Pro under Apple ID devices when it was previously showing as Mac Pro 5,1.

It's best to stick with @cdf firmware feature + 7,1 board ID on the cMP under Big Sur.

Shouldn't be, I am using the 7,1 board ID right now. That won't change the ident. And won't trigger the memory error notification in Big Sur. And all fans & temperature still works.

Did you spoof the ident by yourself as well?

 

[w1z]

Shouldn't be, I am using the 7,1 board ID right now. That won't change the ident. And won't trigger the memory error notification in Big Sur. And all fans & temperature still works.
View attachment 1673599

View attachment 1673600
View attachment 1673601

Did you spoof the ident by yourself as well?

The issues I reported in my earlier post are with the board ID + ident with or without firmware mask.

Board ID + firmware mask is working perfectly less NightShift which I don’t need. I don’t get any memory errors with this combo and without having that disabler kext referenced in the config file.

 

[startergo]

The issues I reported in my earlier post are with the board ID + ident with or without firmware mask.

Board ID + firmware mask is working perfectly less NightShift which I don’t need. I don’t get any memory errors with this combo and without having that disabler kext referenced in the config file.

But of course you can't boot Mojave or lower MacOS, right?

 

[w1z]

Yes, I’m only using Big Sur now.

 

[h9826790]

The issues I reported in my earlier post are with the board ID + ident with or without firmware mask.

Board ID + firmware mask is working perfectly less NightShift which I don’t need. I don’t get any memory errors with this combo and without having that disabler kext referenced in the config file.

When you spoof the ident as well, sensors and fans (and SMC) still working. Just some software (e.g. iStat) can't function correctly (because they base on the ident to look for some specific sensors value, not base on whatever available).

Anyway, the whole idea of spoofing the ident is to make the cMP ident as the 7,1. Therefore, About this Mac shows 7,1. And all functions availability also base on 7,1.

But if that cause other issues (e.g. network issue), then I also believe better to avoid this config. We can use F.lux to replace Night Shift, and Duet to replace Sidecar, etc.

 

[h9826790]

But of course you can't boot Mojave or lower MacOS, right?

Still can boot, tested on my cMP, but something like HWAccel won't work. Which makes the whole spoofing thing meaningless.

 

[w1z]

When you spoof the ident as well, sensors and fans (and SMC) still working. Just some software (e.g. iStat) can't function correctly (because they base on the ident to look for some specific sensors value, not base on whatever available).

Anyway, the whole idea of spoofing the ident is to make the cMP ident as the 7,1. Therefore, About this Mac shows 7,1. And all functions availability also base on 7,1.

But if that cause other issues (e.g. network issue), then I also believe better to avoid this config. We can use F.lux to replace Night Shift, and Duet to replace Sidecar, etc.

Agree, my only concern was with the sluggish performance and the mac presenting itself/registering as a Mac Pro 7,1 under Apple ID registered devices. Not sure if this is one of the conditions that would cause issues later on with Apple ID.

What really surprises me is that WhateverGreen is no longer needed/used for HWA or multi-screens - that's quite a development. Now if only we could get these cMPs to sleep automatically.

 

[startergo]

Agree, my only concern was with the sluggish performance and the mac presenting itself/registering as a Mac Pro 7,1 under Apple ID registered devices. Not sure if this is one of the conditions that would cause issues later on with Apple ID.

What really surprises me is that WhateverGreen is no longer needed/used for HWA or multi-screens - that's quite a development. Now if only we could get these cMPs to sleep automatically.

There is a kext for sleep HibernationFixup.kext did you try that?

 

[w1z]

@startergo Yup, didn't work.

 

[startergo]

@startergo Yup, didn't work.

Did yo make sure it is loaded? LiLU had some library SDK changes and the dependencies had to be recompiled again.