Contribute
Register

Is NVRAM emulation necessary if Clover is injecting SMBIOS?

Status
Not open for further replies.
Joined
Aug 11, 2011
Messages
58
Motherboard
Gigabyte Z390 Designare
CPU
i7-9700K
Graphics
EVGA GTX 1080; MSI RX 580 8GB
Trying to trouble shoot iMessage not working on my legacy install of High Sierra. Everything is working perfect except iMessage. I've done a a clean install about four times trying to get it working with no success.

The build:
GA-X58A-UD5 (rev2.0)
EVGA GTX 1080 FTW
High Sierra 10.13.1
RTL8111 en0 - ethernet cable plugged into en0
RTL8111 en1
iMac 14,2 definitions
Clover 2.4 r4509 (Legacy Install)

SmUUID and Hardware UUID are different, and stay the same after every boot.
ROM is the last 12 characters of SmUUID and is injected from Rt Variables ROM field.
MLB and Serial were both generated by Clover Configurator (5.1.2.0) and are injected from SMBIOS.
SmUUID was generated from uuidgen in terminal ran about ten times, and is injected from SMBIOS.
System Parameters has Inject System ID checked and Custom UUID field is left blank.

Questions I'm looking for answers:
Do I need to emulate NVRAM if Clover is injecting SMBIOS?
Is EmuVariableUefi-64.efi necessary on legacy clover build?
Is it better to inject MLB from SMBIOS or Rt Variables?
Clover config generated a serial that starts with D2 instead of C0 like before. Is that an issue?
I've read through the fix iMessage thread, but I wasn't able to find all the information I'd like to know.
 
Does your motherboard support native NVRAM ?
Test

If not then you cannot emulate it if you installed Clover in Legacy mode as I understand it, which means that the web drivers for your GTX 1080 will not work either.
 
Ugh... Reset my iTunes password, deleted the old machines from my devices, got a new WAN ip address and iMessage still didn't work. :(

Put my login in and it worked to open the iMessage interface, but when I went to preferences and accounts it said error signing in try again. Any ideas?
 
Attached below
I can't see anything there that would prevent it from working.
The only thing that I can think of that we haven't covered yet is that some old information may be in NVRAM
Look at the root of your partitions for files named nvram.plist and if found delete them.
Then in Terminal :
Code:
sudo nvram -c
Press return then type your password (it will not be visible on screen) and press return.
Restart
 
Status
Not open for further replies.
Back
Top