Ah, interesting. Have you tried
agdpmod=pikera boot argument? I think this is needed for the RX580 GPU you have, but I heard it is
not needed on MacPro7,1 - which could explain why that SMBIOS works for you?
Since I wrote to you earlier I have been doing some investigation on the MacPro 7,1 memory notification issue, and I have made some theoretical progress:
In Catalina, I have successfully removed the "invalid memory" notification,
without using MacProMemoryNotificationDisabler.kext.
The method used was not pretty
In order to do this, I had to manually patch a file on the write-protected /System partition:
/System/Library/CoreServices/MemorySlotNotification
What I did was look at the
source code for MacProMemoryNotificationDisabler.kext to see what kind of binary patch the author was making, and to which file. Then I manually made the same patch to the same file, direct on disk. In other words, I made a static, permanent version of the same patch that MacProMemoryNotificationDisabler.kext makes dynamically via Lilu's patching facilities.
In order to do this on Catalina, I only had to mount the / partition read-write (
mount -uw /). Possibly I needed to disable SIP as well, but I always have that disabled anyway via OpenCore.
Of course on Catalina there is no need for all this, because Lilu's userspace patching works fine, so the MacProMemoryNotificationDisabler.kext works and is much preferable to making a permanent patch on /System.
It's on Big Sur that this method might actually be useful, at least as a last resort.
I haven't yet tested it on Big Sur, but I believe it should work there too. Unfortunately making this change on Big Sur is a lot more hassle. From what I have read, I believe the following steps will be required to make the same patch on Big Sur:
- Disable SIP - csrutil disable (or via OpenCore config.)
- Disable SSV - csrutil authenticated-root disable
- Reboot
- Make a temporary mount location: sudo mkdir /mnt
- Mount the / drive read-write (example command): sudo mount -o nobrowse -t apfs /dev/disk1s5 /mnt
- Copy the patched file to /System/Library/CoreServices/MemorySlotNotification
- Re-snapshot and bless the modified root partition: sudo bless --folder mnt/System/Library/CoreServices --bootefi --create-snapshot
- Reboot: sudo reboot
I copied these commands from a blog post linked earlier in this thread, that explains how to edit a plist file to avoid the bug/issue with Little Snitch firewall not being able to block Apple services in Big Sur:
https://tinyapps.org/blog/202010210700_whose_computer_is_it.html
I don't yet have a Big Sur install, so I can't test this immediately. But I will be doing a test upgrade to Big Sur in the next few days, and will test it then.
TLDR: I believe I may have a workaround/hack for the MacPro 7,1 memory notification problem that will work on Big Sur. However, it will require patching a file direct on /System, and therefore requires disabling SIP and SSV, rebooting, and then re-snapshotting the filesystem. I believe it also requires running without SSV and SIP from then on.
It's far from ideal! Personally, if I couldn't use iMacPro SMBIOS, then I'd be happy doing these steps. I've had SIP disabled forever anyway, and I wouldn't care about also disabling SSV (which no previous macOS even had). But not everyone may be so keen on such methods.
Anyway, I'll report back once I've actually confirmed it does work on Big Sur
Then I can explain how to do the patch, and you and others can decide if it's something you're interested to do on your system.