Memory Installation Fix for MacPro7,1 SMBIOS

iGPU

Donator
Donator
Joined
May 5, 2020
Messages
14
I've finally figured out how to correctly use the Memory section in OC. I decided to work on this since I've now changed to using MacPro7,1 instead of iMacPro1,1 due to the former apparently being a better match for going forward with AMD 6x00XT GPUs.

If you follow this guide carefully, you will not need the kext "RestrictEvents.kext" file, and you will no longer see a memory error. I've only tested in Big Sur, but it should work under Catalina as well.

Here's the memory guide:

OC's "BANK" numbers were re-arranged to better match the memory upgrade instructions per Apples's docs. The Bank numbers in their order of appearance are slots: 7, 8, 9, 10, 11, 12, 6, 5, 4, 3, 2, and 1. These correspond to the slot numbers on the memory board. In Apple's docs, the slots are arranged into DIMM Channels, A-F. DIMM Channel A are Banks/slots 7, 8; B are 9,10; C are 11, 12; D are 5, 6; E are 3, 4; and F are 1, 2 (as shown in spoiler below).

Screen Shot 2021-05-01 at 12.41.47 PM.png
Screen Shot 2021-05-01 at 12.41.55 PM.png
Screen Shot 2021-05-01 at 12.42.08 PM.png

If properly arranged, below is what is seen with 8 DIMMs installed on my TRX40 mobo. While most mobos only allow 8 memory slots (and some only allow 4), an actual MacPro7,1 has 12 slots, so our mobos will always have at least 4 slots empty. Now, should you only be using 4 memory sticks, then set to empty the following slots: 1, 2, 3, 5, 8, 10, 11, 12. In other words, if you are using 4 DIMMs, only slots 4, 6, 7 and 9 will be populated (thanks djlild7hina!).

Note: this does not mean you physically move your DIMMs about on your mobo; this whole process is to map your DIMMs into software locations where the macOS is expecting them to be positioned. Keep your DIMMs physically where the mobo manual recommends.



The code within OC is shown in excerpt below (I use PlistEditPro; the full code is downloadable as an attachment). Add it enbloc as the "Memory" section within the PlatformInfo section (also make sure to enable "CustomMemory"). The SNs are arbitrary (add your actual ones if you're more OCD than me). The part numbers are mine as used, made by Cosair; change these values as you wish. The AssetTag is also arbitrary but only entered if that memory slot is populated. Finally, change the Size and Speed values to better match your DIMM.


If SystemInformation is run, the following is seen:
Screen Shot 2021-05-01 at 12.18.02 PM.png

In the attachment, I included the 8 DIMMs as well as one for 4 DIMMs (4 DIMM verified and fixed by djlild7hina on another forum). Inactivate either one with "#" symbol or activate by removing "#" and editing the label heading to "Memory":
Screen Shot 2021-05-01 at 12.23.18 PM.png

Attached file updated to also correct 2 and 4 DIMM settings.
 

Attachments

  • OC-Memory-MacPro7,1-2-4-8.plist.zip
    1.6 KB · Views: 9
Last edited:

AudioGod

Guru
Guru
Joined
Nov 7, 2020
Messages
1,243
It’s a bit annoying that if you are only using two sticks of ram you still have to map it for four. I’m tempted to try the new version of restrictevents to see if it does the job with the memory properly now.
 

DarkSilentSC

New member
Joined
Jun 4, 2021
Messages
13
Thank you for this fix-- However, this configuration and removal of RestrictEvents.kext shows proper memory mapping, but resets CPU name to Intel Xeon Processor Name. Enabling back RestrictEvents recovers AMD CPU Name, but the memory map shows iMac Pro configuration view.
 

AudioGod

Guru
Guru
Joined
Nov 7, 2020
Messages
1,243
Thank you for this fix-- However, this configuration and removal of RestrictEvents.kext shows proper memory mapping, but resets CPU name to Intel Xeon Processor Name. Enabling back RestrictEvents recovers AMD CPU Name, but the memory map shows iMac Pro configuration view.
The Restrict events does a much better job of mapping your memory as you don’t have to have dummy slots and dummy ram mapped out. It keeps it all as it should be with the kext in place Plus it removes the PCIe slot population tab which is useless on a Hack.
This method was only ever good for as long as the restrict events kext wasn’t working which in fairness was only with the release of V1.0.1. Now the manual mapping method is dead in the water and just pointless unless of course it makes you feel all warm and fuzzy inside then in that case go for it.. 🤣
 

DarkSilentSC

New member
Joined
Jun 4, 2021
Messages
13
That's good to know! However RestrictEvents alone still has "1 Alert" on the About Mac Menu, so I decided to map it anyways. All is good now, even tho I like the Mac Pro layout better haha.
 

AudioGod

Guru
Guru
Joined
Nov 7, 2020
Messages
1,243
That's good to know! However RestrictEvents alone still has "1 Alert" on the About Mac Menu, so I decided to map it anyways. All is good now, even tho I like the Mac Pro layout better haha.
That’s strange, no errors on any systems I’ve used it on. It’s totally clean every time (did you forget to clear your nvram?) anyway you do whatever rocks your boat bud…lol
 
Last edited:

rthpjm

New member
Joined
May 25, 2021
Messages
1
Hello everyone

I hope no one will mind that I have created a pull request at the dortania guides GitHub repository which incorporates the information I benefited from here. Thanks @iGPU

Until kronokernel approves the changes into the published docs (assuming he accepts the pull request of course!). You can see my write up on my fork…
Fixing MacPro7,1 Memory Errors
 
Top Bottom