Clover General discussion

KGP-iMacPro · January 9, 2018

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.

January 9, 2018

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-iMacPro · January 9, 2018

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?

January 9, 2018

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-iMacPro · January 9, 2018

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

January 9, 2018

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-iMacPro · January 9, 2018

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?

January 9, 2018

one condition is verified! :-P

after reboot

KGP-iMacPro · January 9, 2018

one condition is verified! :-P

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

January 9, 2018

not related

this one is related to Nvram discussion

EmuVariableUefi-64.efi

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

KGP-iMacPro · January 9, 2018

not related

this one is related to Nvram discussion

EmuVariableUefi-64.efi

I know.. but anyway I guess also CsmVideoDxe-64.efi might be obsolete..

Slice · January 9, 2018

ops

fabios-Mac-Pro:~ fabio$ sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout

Password:

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

fabios-Mac-Pro:~ fabio$

This is legacy Clover BDS menu timeout. I am not sure if it used anywhere.

January 9, 2018

#16160

apianti advice to understand better Nvram problem in x99 Asus board

This is legacy Clover BDS menu timeout. I am not sure if it used anywhere.

el_charlie · January 9, 2018

This is legacy Clover BDS menu timeout. I am not sure if it used anywhere.

Hello Slice,

I know that an HD3000 system is an old equipment, but that's the one I have. Do you have any insight on how to get rid of the graphics glitches?

I already have 8GB of RAM and don't know the DVMT size or how to increase it.

I was booting in legacy mode but I discovered I can do UEFI and now I'm using Aptio2Fix without a slide parameter. My calculated slide=39 doesn't work.

cecekpawon · January 9, 2018

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)

I wondering how can you show boot.efi messages like that?

* it must be after entering OS entry, but you said before?

KGP-iMacPro · January 9, 2018

@fabiosun ,

CsmVideoDxe-64.efi seems apfs.efi related...

If I don't use it I get these messages before entering the clover boot menu (see attachment).

Back to the topic...

The remaining question is why my system is not recognised by the Appstore as iMac Pro and if this issue is Clover_v2.4k_r4369 related..

Update:

I wondering how can you show boot.efi messages like that?

* it must be after entering OS entry, but you said before?

Yes.... Same behaviour with my system disk if I omit CsmVideoDxe-64.efi (in fact I formerly also did not implement CsmVideoDxe-64.efi in the EFI-Folder of my MacOS USB Flash Drive Installer).

With CsmVideoDxe-64.efi, also some messages appear before entering the clover boot menu.. but for a millisecond.. thus, I am not able to see or trace the content..

January 9, 2018

Many people stated this thing about output of apfs.efi

but using that driver is useful for display resolution and in some case it delay video output and people does not see apfs.efi lines

if you search in this forum you can find a simple patch from PMHeart and a more simple script from ErmaC to patch apfs.efi to disappear that log output.

#81

link verbose apfs boot added

@fabiosun ,

CsmVideoDxe-64.efi seems apfs.efi related...

If I don't use it I get these messages before entering the clover boot menu (see attachment).

Back to the topic...

The remaining question is why my system is not recognised by the Appstore as iMac Pro and if this issue is Clover_v2.4k_r4369 related..

Update:

Yes.... Same behaviour with my system disk if I omit CsmVideoDxe-64.efi (in fact I formerly also did not implement CsmVideoDxe-64.efi in the EFI-Folder of my MacOS USB Flash Drive Installer).

With CsmVideoDxe-64.efi, also some messages appear before entering the clover boot menu.. but for a millisecond.. thus, I am not able to see or trace the content..

Edited January 9, 2018 by Guest

Slice · January 9, 2018

Hello Slice,

I know that an HD3000 system is an old equipment, but that's the one I have. Do you have any insight on how to get rid of the graphics glitches?

I already have 8GB of RAM and don't know the DVMT size or how to increase it.

I was booting in legacy mode but I discovered I can do UEFI and now I'm using Aptio2Fix without a slide parameter. My calculated slide=39 doesn't work.

Once upon a time I heard about slide=0 may help to artefact problem on Intel HD3000. I can't confirm or comment this because I have no such video.

My HD4000 depends on BIOS version (comp #2 in sig). Version A12 good while version A23 is full of artefacts. Did you checked different BIOSes?

el_charlie · January 9, 2018

Once upon a time I heard about slide=0 may help to artefact problem on Intel HD3000. I can't confirm or comment this because I have no such video.

My HD4000 depends on BIOS version (comp #2 in sig). Version A12 good while version A23 is full of artefacts. Did you checked different BIOSes?

For that model, ASUS didn't release many BIOSes, the one I'm using is the latest and that's the one that boots Win8 and Win10.

In fact, on the download site there's no previous version. I'm even afraid to downgrade because I bricked the same laptop by flashing a bad BIOS. Had to replace the motherboard.

The slide=0 I think was a placebo. Currently, I can't boot with slide=0 on AptioFix2. With AptioFix1 slide=0 allows me to boot but the artifacts are there. They appear later when the computer has a more time on.

KGP-iMacPro · January 9, 2018

Many people stated this thing about output of apfs.efi

but using that driver is useful for display resolution and in some case it delay video output and people does not see apfs.efi lines

if you search in this forum you can find a simple patch from PMHeart and a more simple script from ErmaC to patch apfs.efi to disappear that log output.

#81

link verbose apfs boot added

perfect... apsf.efi issue resolved... thanks!

BTW.. apparently I do not need the CsmVideoDxe-64.efi on my system.. also thanks for all related info

Now back to my original question:

Can it be that the incorrect recognition of my system in the Appstore can be due to the current Clover_v2.4k_r4369 iMacPro implementation?

The same question states for the apparent issue with the MacOS 10.13.2 (17C2120) USB Flash Drive Installer partition, which currently is not visible in the Clover Boot Menu.

BTW.. the native NVRAM implementation also concludes that the MSR in the ASUS Prime X299 Deluxe v1014 BIOS is in fact unlocked?

January 9, 2018

no. sorry not related to Nvram...

maybe you can check with pikeralpha tool to see but i think it is locked.

Maybe you can try with uefipatch

I see in the latest Patches.txt some lines related to skylake CPU

.....

BTW.. the native NVRAM implementation also concludes that the MSR in the ASUS Prime X299 Deluxe v1014 BIOS is in fact unlocked?

KGP-iMacPro · January 9, 2018

no. sorry not related to Nvram...

maybe you can check with pikeralpha tool to see but i think it is locked.

Maybe you can try with uefipatch

I see in the latest Patches.txt some lines related to skylake CPU

I did previously check the MSR with AppleIntelInfo.kext (still using a i7-7800X) and within earlier ASUS Prime X299 Deluxe BIOS versions the MSR was always locked.

Now with the i9-7980XE, my system immediately reboots on kextload of AppleIntelInfo.kext. The kext is not compatible with the latter CPU, see https://github.com/Piker-Alpha/AppleIntelInfo/issues/22.

The UEFI patch apparently works fine with the ASUS X299 Prime-A and ASUS X299 Strix BIOS, however with the ASUS Prime X299 Deluxe BIOS it fails apparently due to a different BIOS file system.. See https://github.com/LongSoft/UEFITool/issues/91.

January 9, 2018

offtopic

If you are sure uefipatch is working with ASUS X299 Prime-A

output message is the same also for your motherboard after patching..

Last login: Tue Jan  9 17:40:28 on console
fabios-Mac-Pro:~ fabio$ cd desktop
fabios-Mac-Pro:desktop fabio$ /Users/fabio/Desktop/UEFIPatch PRIME-X299-A-ASUS-1004.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
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$

I did previously check the MSR with AppleIntelInfo.kext (still using a i7-7800X) and within earlier ASUS Prime X299 Deluxe BIOS versions the MSR was always locked.

Now with the i9-7980XE, my system immediately reboots on kextload of AppleIntelInfo.kext. The kext is not compatible with the latter CPU, see https://github.com/Piker-Alpha/AppleIntelInfo/issues/22.

The UEFI patch apparently works fine with the ASUS X299 Prime-A and ASUS X299 Strix BIOS, however with the ASUS Prime X299 Deluxe BIOS it fails apparently due to a different BIOS file system.. See https://github.com/LongSoft/UEFITool/issues/91.

KGP-iMacPro · January 9, 2018

offtopic

If you are sure uefipatch is working with ASUS X299 Prime-A

output message is the same also for your motherboard after patching..

Last login: Tue Jan  9 17:40:28 on console
fabios-Mac-Pro:~ fabio$ cd desktop
fabios-Mac-Pro:desktop fabio$ /Users/fabio/Desktop/UEFIPatch PRIME-X299-A-ASUS-1004.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
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$

Off topic request: can you please attach your patches.txt? I will give it a try...

Sherlocks · January 9, 2018

i tested my hp 4230s sandy laptop

now, i can use native NVRAM with OsxAptioFix2Drv.efi.

i always used slide=0 before. but if i use new OsxAptioFix2Drv.efi, i can't use slide=0. i have to remove slide=0 bootarg.

as result, only use OsxAptioFix2Drv.efi

thank you so much again.

EDIT1.

i will check Snow leopard booting.

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites