- Joined
- Jul 24, 2010
- Messages
- 50
- Motherboard
- << need manufacturer >> See Forum Rules !!
- CPU
- i7-3930K
- Graphics
- GTX 570
- Mobile Phone
You're using MacPro 7,1 SMBIOS, right? That's a standard problem with that SMBIOS.
In Catalina and earlier it could be fixed with a special kext, MacProMemoryNotificationDisabler.kext.
But unfortunately this kext currently no longer works in Big Sur, because some of Big Sur's changes broke a certain method of injection used by Lilu.
Last week I tried an alternative method to fix this - using OpenCore's CustomMemory setup to specifically define all of my RAM chips. This works in the sense that the configuration you specify does show up in About This Mac -> Memory. But no matter what I tried, I could not get rid of that error and its notification.
So currently the only solution I know of is to use the iMacPro 1,1 SMBIOS instead, which I think a lot of users in this thread are already using? Personally I would prefer to use MacPro 7,1 as I feel it fits my hardware better (Comet Lake X), however given this annoying memory notification, maybe I too will move to iMacPro 1,1.
It's possible that in time the developers of Lilu will find another way to run these patches on Big Sur, which could make MacProMemoryNotificationDisabler.kext work again. But I don't know if that's likely or not.
You're using MacPro 7,1 SMBIOS, right? That's a standard problem with that SMBIOS.
In Catalina it could be fixed with a special kext, MacProMemoryNotificationDisabler.kext.
But unfortunately this kext currently no longer works in Big Sur, because some of Big Sur's changes broke a certain method of injection used by Lilu.
Last week I tried an alternative method to fix this - using OpenCore's CustomMemory setup to specifically define all of my RAM chips. This works in the sense that the configuration you specify does show up in About This Mac -> Memory. But no matter what I tried, I could not get rid of that error and its notification.
So currently the only solution I know of is to use the iMacPro 1,1 SMBIOS instead, which I think a lot of users in this thread are already using? Personally I would prefer to use MacPro 7,1 as I feel it fits my hardware better (Cascade Lake X), however given this annoying memory notification, maybe I too will move to iMacPro 1,1.
It's possible that in time the developers of Lilu will find another way to run these patches on Big Sur, which could make MacProMemoryNotificationDisabler.kext work again. But I don't know if that's likely or not.
thanks for the clarification @TheBloke . I am indeed on MacPro 7,1 - however, when I try any other SMBIOS (eg: iMacPro 1,1), my display doesn't render when booting. In other words, I can then only get the display to render on MacPro 7,1 - weird.. because that memory info is annoying when not displaying correct!
Next issue to fix.. Audio. Thanks for the help