Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Regi Yassin
Regi Yassin
Posted
Posted

 

I'm not sure what you're asking? Did you do the other steps? Did you try setting a test variable, restart and check if it was there? Did you try setting to 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00 before this?

 

 

test var wasnt success, 

still have no working nvram.

never set anything before for nvream

apianti
apianti
Posted
Posted

test var wasnt success, 

still have no working nvram.

never set anything before for nvream

 

Those are tests to see if you have working native NVRAM. Are you sure that you couldn't write to the global Timeout variable? You restarted? It seems to me that ASUS Z97 and X99 both have the whitelist issue, where your NVRAM is actually working but you can only write a small subset of non consequential variables because they are whitelisted by the firmware.

 

EDIT: Anyone with these platforms that can't replace or patch the modules will have to use EmuVar still for now.

  • Like 1
el_charlie
el_charlie
Posted
Posted

 

Please try the AptioFix2 driver attached to this post.

 

The same message. Removing the slide=39 boots just fine.

 

TL;DR: slide=0 , slide=39 results in printf message. slide=257 or slide=513 boots fine but apparently it does nothing.

apianti
apianti
Posted
Posted

The same message. Removing the slide=39 boots just fine.

 

TL;DR: slide=0 , slide=39 results in printf message. slide=257 or slide=513 boots fine but apparently it does nothing.

 

What about no slide at all? Please try this driver:

OsxAptioFix2Drv-64.efi

Regi Yassin
Regi Yassin
Posted
Posted

Those are tests to see if you have working native NVRAM. Are you sure that you couldn't write to the global Timeout variable? You restarted? It seems to me that ASUS Z97 and X99 both have the whitelist issue, where your NVRAM is actually working but you can only write a small subset of non consequential variables because they are whitelisted by the firmware.

 

EDIT: Anyone with these platforms that can't replace or patch the modules will have to use EmuVar still for now.

after running this

sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00

and restarted

it still the same, not back to 1

 

i tried all bioses from asus, all of them cant write to nvram, so i presume i have no modules that writeable, am i right?

 

but i dont need emuvar and/or rc script,

all working as expected. volume level is preserved after restart. (i dont know what that means)

apianti
apianti
Posted
Posted

after running this

sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00

and restarted

it still the same, not back to 1

 

i tried all bioses from asus, all of them cant write to nvram, so i presume i have no modules that writeable, am i right?

 

but i dont need emuvar and/or rc script,

all working as expected. volume level is preserved after restart. (i dont know what that means)

 

So you are no able to write sudo nvram test="value", restart, and see sudo nvram test, print out it is "value"? But you can write to the global Timeout if it stayed at 5, and if you can write to other variables and you are not using EmuVar are you sure you couldn't write the test variable??

el_charlie
el_charlie
Posted
Posted

What about no slide at all? Please try this driver:

It boots fine(*) with no slide at all. slide=39 results in printf message (no boot).

 

(*) sometimes I get prohibited sign after a reboot, sometimes after a cold boot. Most of the times it boots.

Regi Yassin
Regi Yassin
Posted
Posted

So you are no able to write sudo nvram test="value", restart, and see sudo nvram test, print out it is "value"? But you can write to the global Timeout if it stayed at 5, and if you can write to other variables and you are not using EmuVar are you sure you couldn't write the test variable??

correct, nvram test="value", restart, nvram test >> nvram: Error getting variable - 'test': (iokit/common) data was not found

can i test timeout to another value ?

 

EDIT : change time out back to 1

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %01%00

restart, and its stayed 1.

Guest
Guest
Posted
Posted

Hi apianti

variable below are achieved in this way

osx 10.13.2

no RC Script and no emuvariable installed

on clover boot menu Nvram cleaned with f11 key

all these variable are set by OSX/Clover R.4369

Last login: Tue Jan  9 07:18:43 on consolefabios-Mac-Pro:~ fabio$ sudo nvram -pPassword:fakesmc-key-MSWr-ui8	%00flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00fakesmc-key-RBr -ch8*	j90%00%00%00%00%00fakesmc-key-EPCI-ui32	%06%f0%f0%00fakesmc-key-MSAc-ui16	%00%00efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>3A55787E-1275-45BE-87EB-0ACF96BC0343</string></dict></dict></dict></array>fakesmc-key-CLKH-{clh	%00%00p%80%00%01%19@bootercfg	(%00fakesmc-key-NATi-ui16	%00%1eLocationServicesEnabled	%01fakesmc-key-NTOK-ui8	%01fakesmc-key-BATP-flag	%00fakesmc-key-$Num-ui8	%01fakesmc-key-REV -ch8*	%02 %0f%00%00%18bluetoothActiveControllerInfo	%0a%18%05%0b%00%00%00%00`%14%f0%03%8c<%b5%a3fakesmc-key-HI0N-ui8	%10fmm-computer-name	fabio%e2%80%99s Mac Profakesmc-key-MSTc-ui8	%00fakesmc-key-MSPS-ui16	%00%03fakesmc-key-RMde-char	Acsr-active-config	g%00%00%00fakesmc-key-RPlt-ch8*	j90%00%00%00%00%00fakesmc-key-BEMB-flag	%00fakesmc-key-#KEY-ui32	%00%00%00%10SystemAudioVolume	Afakesmc-key-MSFW-ui8	%01%00specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00security-mode	nonefakesmc-key-LsBA-ui8	%90fakesmc-key-$Adr-ui32	%00%00%03%00nvda_drv	1%00EFILoginHiDPI	%00%00%00%00fakesmc-key-CLKT-ui32	%00%00f%d8fakesmc-key-BNum-ui8	%00SystemAudioVolumeDB	%f0fakesmc-key-NATJ-ui8	%02efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00fabios-Mac-Pro:~ fabio$
And it seems a common situation with x99 users (maybe only Asus users?)

So you are no able to write sudo nvram test="value", restart, and see sudo nvram test, print out it is "value"? But you can write to the global Timeout if it stayed at 5, and if you can write to other variables and you are not using EmuVar are you sure you couldn't write the test variable??

apianti
apianti
Posted
Posted

correct, nvram test="value", restart, nvram test >> nvram: Error getting variable - 'test': (iokit/common) data was not found

can i test timeout to another value ?

 

EDIT : change time out back to 1

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %01%00

restart, and its stayed 1.

 

Hi apianti

variable below are achieved in this way

osx 10.13.2

no RC Script and no emuvariable installed

on clover boot menu Nvram cleaned with f11 key

all these variable are set by OSX/Clover R.4369

Last login: Tue Jan  9 07:18:43 on consolefabios-Mac-Pro:~ fabio$ sudo nvram -pPassword:fakesmc-key-MSWr-ui8	%00flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00fakesmc-key-RBr -ch8*	j90%00%00%00%00%00fakesmc-key-EPCI-ui32	%06%f0%f0%00fakesmc-key-MSAc-ui16	%00%00efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>3A55787E-1275-45BE-87EB-0ACF96BC0343</string></dict></dict></dict></array>fakesmc-key-CLKH-{clh	%00%00p%80%00%01%19@bootercfg	(%00fakesmc-key-NATi-ui16	%00%1eLocationServicesEnabled	%01fakesmc-key-NTOK-ui8	%01fakesmc-key-BATP-flag	%00fakesmc-key-$Num-ui8	%01fakesmc-key-REV -ch8*	%02 %0f%00%00%18bluetoothActiveControllerInfo	%0a%18%05%0b%00%00%00%00`%14%f0%03%8c<%b5%a3fakesmc-key-HI0N-ui8	%10fmm-computer-name	fabio%e2%80%99s Mac Profakesmc-key-MSTc-ui8	%00fakesmc-key-MSPS-ui16	%00%03fakesmc-key-RMde-char	Acsr-active-config	g%00%00%00fakesmc-key-RPlt-ch8*	j90%00%00%00%00%00fakesmc-key-BEMB-flag	%00fakesmc-key-#KEY-ui32	%00%00%00%10SystemAudioVolume	Afakesmc-key-MSFW-ui8	%01%00specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00security-mode	nonefakesmc-key-LsBA-ui8	%90fakesmc-key-$Adr-ui32	%00%00%03%00nvda_drv	1%00EFILoginHiDPI	%00%00%00%00fakesmc-key-CLKT-ui32	%00%00f%d8fakesmc-key-BNum-ui8	%00SystemAudioVolumeDB	%f0fakesmc-key-NATJ-ui8	%02efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00fabios-Mac-Pro:~ fabio$
And it seems a common situation with x99 users (maybe only Asus users?)

 

 

Yes, ASUS Z97 and X99 users will have to continue to use EmuVar if setting the test variable does not work, as they still don't have fully working NVRAM because the firmware itself has a very stupid bug....

It boots fine(*) with no slide at all. slide=39 results in printf message (no boot).

 

(*) sometimes I get prohibited sign after a reboot, sometimes after a cold boot. Most of the times it boots.

 

So neither of those two other drivers gives different results? Hmmmmm... Please try this one then

OsxAptioFix2Drv-64.efi

Funky frank
Funky frank
Posted
Posted

 

I actually think you need to remove the key for your CPU bus speed from config.plist.

0:100  0:000  BrandString = Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
...
0:100  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:100  0:000  MaxDiv/MinDiv: 34.0/8
0:100  0:000  Turbo: 37/38/39/39
0:100  0:000  Features: 0xBFEBFBFF
0:100  0:000  Threads: 8
0:100  0:000  Cores: 4
0:100  0:000  FSB: 100 MHz
0:100  0:000  CPU: 3400 MHz
0:100  0:000  TSC: 3400 MHz
0:100  0:000  PIS: 100 MHz
0:100  0:000  ExternalClock: 25 MHz
...
164:674  0:000  Finally: ExternalClock=24MHz BusSpeed=99768kHz CPUFreq=3392MHz PIS: hw.busfrequency=96000000Hz

That's a pretty significant clock difference.

 

Hi, I do not set the bus speed in config.plist. Please have a look at it: 

config.plist.zip

 

How can I fix that? Btw. my bios is in "turbo" mode, so maybe overclock everything a bit. Should I then set the busspeed?

 

Do you mean that it is too slow? Because I am fine with it, if it was too fast :)

 

 

EDIT: So the busspeed should be 100MHz / 100000kHz? I now actually set the busspeed to 100000, and it is reporting now:

Finally: ExternalClock=25MHz BusSpeed=100000kHz CPUFreq=3400MHz PIS: hw.busfrequency=100000000Hz

Does that look correct to you?

 

 

 

So neither of those two other drivers gives different results? Hmmmmm... Please try this one then

 

This one still crashes in FCPX while using opencl hd4600+nvidia. Do you really think that it crashes because of memory corruption?  The area in my memory map at 0x10000 looks quite big to me....?

 

 

btw. the Info.plist kext patching in clover is quite retarded: You cannot use strings for search/replace, it seems:

 

 

0:114  0:000   - [06]: AppleGraphicsPowerManagement (disable GFX0 pm)[ERROR] bin2hex 'GFX0' syntax error

0:114  0:000  [ERROR] bin2hex 'GFXX' syntax error

0:114  0:000   - invalid Find/Replace data - skipping!

kgp
kgp
Posted
Posted

News from the Skylake-X/X299 SMBIOS iMacPro1,1 front

 

System boots flawless with OsxAptioFixDrv-64.efi from Clover_v2.4k_r4369. No memory allocation errors and no slide boot flag necessary (see attachment IMG_5991.png)

 

Nevertheless, problems with the macOS 10.13.2 17C2120 USB Flash Drive Installer. 

 

USB MacOS Installer partition does not appear in the Clover Boot Menu.

 

I don't know if the problem is Clover or macOS USB Flash Drive Installer related.  

 

When booting with the EFI on the USB Drive, I get the following message before entering the clover boot menu (see attachment 2 IMG-9550.png)

 

  

 

 

post-1362934-0-80970600-1515499298_thumb.png

post-1362934-0-65950100-1515499634_thumb.png

el_charlie
el_charlie
Posted
Posted

 

So neither of those two other drivers gives different results? Hmmmmm... Please try this one then

 

The same results :(

 

I think I might go with Aptio1. With Aptio 2, sometimes I get the prohibited sign. Mostly when I turn off the computer for more than a minute. 

 

When I get the prohibted sign, I turn it off (just press the power button, no need to press and hold) and turn it on right away and it boots fine. 

 

Thanks anyway you've been very helpful. I have to live with those graphics glitches.

Matthew82
Matthew82
Posted
Posted

News from the Skylake-X/X299 SMBIOS iMacPro1,1 front

 

System boots flawless with OsxAptioFixDrv-64.efi from Clover_v2.4k_r4369. No memory allocation errors and no slide boot flag necessary (see attachment IMG_5991.png)

 

Nevertheless, problems with the macOS 10.13.2 17C2120 USB Flash Drive Installer. 

 

USB MacOS Installer partition does not appear in the Clover Boot Menu.

 

I don't know if the problem is Clover or macOS USB Flash Drive Installer related.  

 

When booting with the EFI on the USB Drive, I get the following message before entering the clover boot menu (see attachment 2 IMG-9550.png)

You have asus x299? Your NVRAM working natively? Your MSR is unlocked? 

kgp
kgp
Posted
Posted

sudo nvram Test="Value" > reboot > nvram Test 

 

 

Ambiguous output redirect

other weird behaviour... 

 

Even with 10.13.2 (17C2120) and SMBIOS iMacPro1,1, the Appstore does not recognise my system as iMac pro and just provides standard MacOS Installers instead of the iMac Pro specific ones. 

 

If I intent to download e.g. the 10.13.2 Full Package installer, I get the following error message (see attachment)

 

If I just update to 10.13.2 SA, again the standard installer is taken... 

 

I don't know if this issue is Clover_v2.4k_r4369 or build related.. I have a i9-7980XE which is not natively implemented yet by OSX (in contrary to the i9-7900X) and I use a Nvidia GPU instead of a Vega 64. 

 

Surprisingly, for user DSM2 with an ASUS Prime X299 Deluxe, a  i9-7900X  and 2x Vega 64 but Clover _v2.4k_4318, everything works as expected.. His system is fully recognised by the Appstore as iMacPro and he receives the correct iMac Pro specific macOS installer packages. 

post-1362934-0-95991600-1515506317_thumb.png

Guest
Guest
Posted
Posted

to check you have to delete emuuefivariable64 if you have installed

also you have to remove clover RCScript from your disk if you have installed

thn

from terminal

 

sudo nvram test="value"

 

it puts in nvram a variable named test with value as "value"

you can check with

sudo nvram -p

 

then you have to reboot

when osx is on again you can run on terminal

sudo nvram -p

and see if there is present test value (persistent to reboot)

if so

your nvram is fully working

 

Yes... i9-7980XE with ASUS Prime X299 Deluxe... MSR is locked.. no way so far to unlock..

 

How to check if NVRAM works natively?  

kgp
kgp
Posted
Posted

to check you have to delete emuuefivariable64 if you have installed

also you have to remove clover RCScript from your disk if you have installed

thn

from terminal

 

sudo nvram test="value"

 

it puts in nvram a variable named test with value as "value"

you can check with

sudo nvram -p

 

then you have to reboot

when osx is on again you can run on terminal

sudo nvram -p

and see if there is present test value (persistent to reboot)

if so

your nvram is fully working

 

But if I remove EmuVariableUefi-64.efi, my SMBIOS iMacPro1,1 serial number, board serial number and UUID will not be correctly transmitted and I will face issues with iCloud, iMessage and Facetime, isn't it? 

Guest
Guest
Posted
Posted

if you have a working nvram you can delete it and have functionality in the same way

you can try and then if it does not work for you you can put in folder again! .-)

 

But if I remove EmuVariableUefi-64.efi, my SMBIOS iMacPro1,1 serial number, board serial number and UUID will not be correctly transmitted and I will face issues with iCloud, iMessage and Facetime, isn't it? 


For MSR, have you tested it with uefipatch?

fabios-Mac-Pro:desktop fabio$ /Users/fabio/Desktop/UEFIPatch PRIME-X299-DELUXE-ASUS-1004.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
parseVolume: unknown file system 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
Image patched
fabios-Mac-Pro:desktop fabio$

Yes... i9-7980XE with ASUS Prime X299 Deluxe... MSR is locked.. no way so far to unlock..

 

How to check if NVRAM works natively?  


I can't test it but if you have windows you should use some tools to see if it is unlocked or not after uefipatch mod

kgp
kgp
Posted
Posted

to check you have to delete emuuefivariable64 if you have installed

also you have to remove clover RCScript from your disk if you have installed

thn

from terminal

 

sudo nvram test="value"

 

it puts in nvram a variable named test with value as "value"

you can check with

sudo nvram -p

fakesmc-key-MSWr-ui8	%00
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
efi-backup-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%14%03%05%06%00%13%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%b0%9f%e5%00%00%00%00%00%9a%b5?]Y%f5pB%b7%89%0b%b0%82(;%d2%02%02%7f%ff%04%00
fakesmc-key-RBr -ch8*	j137%005a%00
fakesmc-key-EPCI-ui32	%09p%f0%00
fakesmc-key-MSAc-ui16	%00%00
efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA9B2E14-1DA7-4436-B44F-8EFBC6AFD622</string></dict></dict></dict></array>
fakesmc-key-CLKH-{clh	%00%00p%80%00%01%19@
bootercfg	(%00
fakesmc-key-NATi-ui16	%00%00
fakesmc-key-NTOK-ui8	%01
fakesmc-key-BATP-flag	%00
efi-backup-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>5D3FB59A-F559-4270-B789-0BB082283BD2</string></dict></dict></dict></array>
fakesmc-key-$Num-ui8	%01
fakesmc-key-REV -ch8*	%02A%0f%00%00%01
bluetoothActiveControllerInfo	%8d%82%ac%05%02%00%000r%14x1%c1%e7%e7n
fmm-computer-name	iMac Pro
fakesmc-key-MSTc-ui8	%00
bluetoothInternalControllerInfo	%8d%82%ac%05%000r%14x1%c1%e7%e7n
fakesmc-key-MSPS-ui16	%00%03
fakesmc-key-RMde-char	A
csr-active-config	g%00%00%00
fakesmc-key-RPlt-ch8*	j137%00%00%00%00
fakesmc-key-BEMB-flag	%00
test	value
fakesmc-key-#KEY-ui32	%00%00%00%16
SystemAudioVolume	A
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSFW-ui8	%01%00
security-mode	none
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1d%01%01%06%00%00%00%03%17%10%00%01%00%00%00%00%258Uq%b1%bfm%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`-jt%00%00%00%00%14.%9b%da%a7%1d6D%b4O%8e%fb%c6%af%d6"%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBp<%25%e1%e3c5:%94%92H%19|%d3%13@%7f%ff%04%00
IDInstallerDataV2	%e03bplist00%a1%01%df%10%16%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%0f%10%11%12%13%14%15%16%17%18%19%09%1a%1b%1c%1d%1d%1e%1f !"#$%25&'()*+S200Q9S103%00%0a%e55S214%00%08%e56Q0Q1%f3@%182%e60S150Q%00%1e%c8%1c15Q%80&3Q%80%0a99%e58Q6Q7%00&%08%16%e0%119Z552.985492VfailedX1.697801X5.70%003%e0%011X0.016603U17C88Z%00%1c%e0%0f.909295VpassedTIASU[solid state%082%e0%0302201[unencryptedY1%00%16%e0%0724543_%10%10case insensitiv%182%08e%e0%10X2.063994WupgradeSYESZ332.164620%08)%00%c4%e0K82%00%08%00%0a%009%00=%00?%00C%00G%00K%00O%00Q%00S%00W%00[%00_%00a%00e%00g%00k%00m%00q%00u%00w%00y%00}%00%81%00%8c%00%93%00%9c%00%a5%00%ae%00%b4%00%bf%00%c6%00%cb%00%d7%00%e0%00%ec%00%f6%01%09%01%12%01%1b%01#%01'%012%00%10%01%ce%02%01%00%f2%9e,%00%f6%e3%00%01;%06%00%00%00%00%00%00%00
fakesmc-key-$Adr-ui32	%00%00%03%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-CLKT-ui32	%00%00%89%05
fakesmc-key-MSDW-ui8	%00
fakesmc-key-BNum-ui8	%00
SystemAudioVolumeDB	%f0
fakesmc-key-NATJ-ui8	%00
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1d%01%01%06%00%00%00%03%17%10%00%01%00%00%00%00%258Uq%b1%bfm%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`-jt%00%00%00%00%14.%9b%da%a7%1d6D%b4O%8e%fb%c6%af%d6"%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBp<%25%e1%e3c5:%94%92H%19|%d3%13@%7f%ff%04%00
prev-lang:kbd	en:0
Guest
Guest
Posted
Posted

if after a reboot and without emudriver64 uefi and rc script you have a native working nvram! :-)


fakesmc-key-MSWr-ui8	%00
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
efi-backup-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%14%03%05%06%00%13%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%b0%9f%e5%00%00%00%00%00%9a%b5?]Y%f5pB%b7%89%0b%b0%82(;%d2%02%02%7f%ff%04%00
fakesmc-key-RBr -ch8*	j137%005a%00
fakesmc-key-EPCI-ui32	%09p%f0%00
fakesmc-key-MSAc-ui16	%00%00
efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA9B2E14-1DA7-4436-B44F-8EFBC6AFD622</string></dict></dict></dict></array>
fakesmc-key-CLKH-{clh	%00%00p%80%00%01%19@
bootercfg	(%00
fakesmc-key-NATi-ui16	%00%00
fakesmc-key-NTOK-ui8	%01
fakesmc-key-BATP-flag	%00
efi-backup-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>5D3FB59A-F559-4270-B789-0BB082283BD2</string></dict></dict></dict></array>
fakesmc-key-$Num-ui8	%01
fakesmc-key-REV -ch8*	%02A%0f%00%00%01
bluetoothActiveControllerInfo	%8d%82%ac%05%02%00%000r%14x1%c1%e7%e7n
fmm-computer-name	iMac Pro
fakesmc-key-MSTc-ui8	%00
bluetoothInternalControllerInfo	%8d%82%ac%05%000r%14x1%c1%e7%e7n
fakesmc-key-MSPS-ui16	%00%03
fakesmc-key-RMde-char	A
csr-active-config	g%00%00%00
fakesmc-key-RPlt-ch8*	j137%00%00%00%00
fakesmc-key-BEMB-flag	%00
test	value
fakesmc-key-#KEY-ui32	%00%00%00%16
SystemAudioVolume	A
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSFW-ui8	%01%00
security-mode	none
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1d%01%01%06%00%00%00%03%17%10%00%01%00%00%00%00%258Uq%b1%bfm%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`-jt%00%00%00%00%14.%9b%da%a7%1d6D%b4O%8e%fb%c6%af%d6"%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBp<%25%e1%e3c5:%94%92H%19|%d3%13@%7f%ff%04%00
IDInstallerDataV2	%e03bplist00%a1%01%df%10%16%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%0f%10%11%12%13%14%15%16%17%18%19%09%1a%1b%1c%1d%1d%1e%1f !"#$%25&'()*+S200Q9S103%00%0a%e55S214%00%08%e56Q0Q1%f3@%182%e60S150Q%00%1e%c8%1c15Q%80&3Q%80%0a99%e58Q6Q7%00&%08%16%e0%119Z552.985492VfailedX1.697801X5.70%003%e0%011X0.016603U17C88Z%00%1c%e0%0f.909295VpassedTIASU[solid state%082%e0%0302201[unencryptedY1%00%16%e0%0724543_%10%10case insensitiv%182%08e%e0%10X2.063994WupgradeSYESZ332.164620%08)%00%c4%e0K82%00%08%00%0a%009%00=%00?%00C%00G%00K%00O%00Q%00S%00W%00[%00_%00a%00e%00g%00k%00m%00q%00u%00w%00y%00}%00%81%00%8c%00%93%00%9c%00%a5%00%ae%00%b4%00%bf%00%c6%00%cb%00%d7%00%e0%00%ec%00%f6%01%09%01%12%01%1b%01#%01'%012%00%10%01%ce%02%01%00%f2%9e,%00%f6%e3%00%01;%06%00%00%00%00%00%00%00
fakesmc-key-$Adr-ui32	%00%00%03%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-CLKT-ui32	%00%00%89%05
fakesmc-key-MSDW-ui8	%00
fakesmc-key-BNum-ui8	%00
SystemAudioVolumeDB	%f0
fakesmc-key-NATJ-ui8	%00
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1d%01%01%06%00%00%00%03%17%10%00%01%00%00%00%00%258Uq%b1%bfm%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`-jt%00%00%00%00%14.%9b%da%a7%1d6D%b4O%8e%fb%c6%af%d6"%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBp<%25%e1%e3c5:%94%92H%19|%d3%13@%7f%ff%04%00
prev-lang:kbd	en:0
kgp
kgp
Posted
Posted

 

if after a reboot and without emudriver64 uefi and rc script you have a native working nvram! :-)

 

 

after reboot  :drool:

fakesmc-key-MSWr-ui8	%00
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
efi-backup-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%14%03%05%06%00%13%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%b0%9f%e5%00%00%00%00%00%9a%b5?]Y%f5pB%b7%89%0b%b0%82(;%d2%02%02%7f%ff%04%00
fakesmc-key-RBr -ch8*	j137%005a%00
fakesmc-key-EPCI-ui32	%09p%f0%00
fakesmc-key-MSAc-ui16	%00%00
efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA9B2E14-1DA7-4436-B44F-8EFBC6AFD622</string></dict></dict></dict></array>
fakesmc-key-CLKH-{clh	%00%00p%80%00%01%19@
bootercfg	(%00
fakesmc-key-NATi-ui16	%00%00
fakesmc-key-NTOK-ui8	%01
fakesmc-key-BATP-flag	%00
efi-backup-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>5D3FB59A-F559-4270-B789-0BB082283BD2</string></dict></dict></dict></array>
fakesmc-key-$Num-ui8	%01
fakesmc-key-REV -ch8*	%02A%0f%00%00%01
bluetoothActiveControllerInfo	%8d%82%ac%05%02%00%000b%14x1%c1%e7%e7n
fmm-computer-name	iMac Pro
fakesmc-key-MSTc-ui8	%00
bluetoothInternalControllerInfo	%8d%82%ac%05%000r%14x1%c1%e7%e7n
fakesmc-key-MSPS-ui16	%00%03
fakesmc-key-RMde-char	A
csr-active-config	g%00%00%00
fakesmc-key-RPlt-ch8*	j137%00%00%00%00
fakesmc-key-BEMB-flag	%00
test	value
fakesmc-key-#KEY-ui32	%00%00%00%16
SystemAudioVolume	@
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSFW-ui8	%01%00
security-mode	none
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1d%01%01%06%00%00%00%03%17%10%00%01%00%00%00%00%258Uq%b1%bfm%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`-jt%00%00%00%00%14.%9b%da%a7%1d6D%b4O%8e%fb%c6%af%d6"%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBp<%25%e1%e3c5:%94%92H%19|%d3%13@%7f%ff%04%00
fakesmc-key-$Adr-ui32	%00%00%03%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-CLKT-ui32	%00%00%89%05
fakesmc-key-MSDW-ui8	%00
fakesmc-key-BNum-ui8	%00
SystemAudioVolumeDB	%fd
fakesmc-key-NATJ-ui8	%00
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1d%01%01%06%00%00%00%03%17%10%00%01%00%00%00%00%258Uq%b1%bfm%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`-jt%00%00%00%00%14.%9b%da%a7%1d6D%b4O%8e%fb%c6%af%d6"%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBp<%25%e1%e3c5:%94%92H%19|%d3%13@%7f%ff%04%00
prev-lang:kbd	en:0

@fabiosun ,

 

what about CsmVideoDxe-64.efi? Can I skip that too?

 Share
Go to topic listing
×
×
  • Create New...