Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

@vector sigma Thanks for your commit anyway.. as you've said it works only with Xcode 5 #ATM so.. it seems I get some localizations issue after building r4692 using Xcode 8 (missing FileVault for Legacy && UEFI driver menus). :)

Screenshot.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
Advertisement
1 hour ago, Badruzeus said:

as you've said it works only with Xcode 5

I've asked vit9696 to implement a fix.. waiting for an answere

1 hour ago, Badruzeus said:

(missing FileVault for Legacy && UEFI driver menus).

Is not missing, just it takes the wrong translation. Need to take a better look on how Poedit works... since I've installed it only yestarday and I used it once.... but I'll do that tomorrow, now here is really late.

Share this post


Link to post
Share on other sites
16 hours ago, camillionario said:

I start with the laptop and the tower without SMC helper.efi without problems, so I do not think it is mandatory.

1633772446_Capturadepantalla2018-10-01alas14_26_53.png.66dfd01818f7364c0e6738360acefd2d.png

 

Here some explanation from Slice about SMCHelper.efi. Take a look if you want: Click Here

Share this post


Link to post
Share on other sites

@Slice

I have found a problem between EDID injection and DevicesProperties injection.

 

If Devices-Properties was empty and the EDID can inject without problem.

 

If there's contents in Devices-Properties, the EDID injection will fail, but according to boot.log generated by Clover, the injection succeeded.

 

I've tested this 3 times and it seems that these two functions conflict with each other.

 

Thanks.

 

CD9D10D19F9EDB80070468DF246C75E7.png

B45EEF82BDFCBB6C4D8832B59F8938B5.png

C59E89B11B7D3FC64209213244DA0DAA.png

Edited by gujiangjiang

Share this post


Link to post
Share on other sites

Due to various 3rd party package changes (EfiPkg's development branch got renamed to develop, EfiMiscPkg got removed and OcSupportPkg is now required instead) Clover's build script (ebuild.sh) --ext-co build flag no longer works.

 

Here's a quick diff/patch for fixing it (tested and confirmed on latest revision):

--- Clover/ebuild.sh
+++ Clover/ebuild.sh
@@ -799,8 +799,8 @@
     # add github links below to checkout packages
     local extDriversDependecies=( 'https://github.com/acidanthera/AptioFixPkg'
                                   'https://github.com/acidanthera/AppleSupportPkg'
+                                  'https://github.com/acidanthera/OcSupportPkg'
                                   'https://github.com/CupertinoNet/CupertinoModulePkg'
-                                  'https://github.com/CupertinoNet/EfiMiscPkg'
                                   'https://github.com/CupertinoNet/EfiPkg')
     # add below drivers you want to build
     local externalDrivers=( AptioFixPkg AppleSupportPkg )
@@ -824,7 +824,7 @@
         local branch=master
 
         case $pkg in
-        CupertinoModulePkg | EfiMiscPkg | EfiPkg)
+        CupertinoModulePkg)
           branch=development
         ;;
         esac

 

Edited by Dids
Updated diff and comment about EfiMiscPkg being removed.

Share this post


Link to post
Share on other sites
3 hours ago, Dids said:

Due to various 3rd party package changes (EfiPkg's development branch got renamed to develop, and OcSupportPkg is now also required) Clover's build script (ebuild.sh) --ext-co build flag no longer works.

 

Here's a quick diff/patch for fixing it (tested and confirmed on latest revision):


--- Clover/ebuild.sh
+++ Clover/ebuild.sh
@@ -801,7 +801,8 @@
                                   'https://github.com/acidanthera/AppleSupportPkg'
                                   'https://github.com/CupertinoNet/CupertinoModulePkg'
                                   'https://github.com/CupertinoNet/EfiMiscPkg'
-                                  'https://github.com/CupertinoNet/EfiPkg')
+                                  'https://github.com/CupertinoNet/EfiPkg'
+                                  'https://github.com/acidanthera/OcSupportPkg')
     # add below drivers you want to build
     local externalDrivers=( AptioFixPkg AppleSupportPkg )
 
@@ -824,7 +825,7 @@
         local branch=master
 
         case $pkg in
-        CupertinoModulePkg | EfiMiscPkg | EfiPkg)
+        CupertinoModulePkg | EfiMiscPkg)
           branch=development
         ;;
         esac

 

 

You're right :) in other topic, @fusion71au says: "Just a heads up that @vit9696 has removed EfiMiscPkg (and added OcSupportPkg) in his latest commits to AppleSupportPkg. "

 

 

Share this post


Link to post
Share on other sites

@vit9696

I have tried to compile the latest commit of AppleSupportPkg on GitHub using gcc 8.2 rather than Xcode 10 and get the following error:

[CC] DevicePathUtilities
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c: In function 'OcOverflowAddUN':
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:44:34: error: passing argument 3 of 'OcOverflowAddU32' from incompatible pointer type [-Werror=incompatible-pointer-types]
   return OcOverflowAddU32 (A, B, Result);
                                  ^~~~~~
In file included from ~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:19:
~/edk2/OcSupportPkg/Include/Library/OcOverflowLib.h:51:12: note: expected 'UINT32 *' {aka 'unsigned int *'} but argument is of type 'UINTN *' {aka 'long long unsigned int *'}
   UINT32  *Result
   ~~~~~~~~~^~~~~~
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c: In function 'OcOverflowSubUN':
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:58:34: error: passing argument 3 of 'OcOverflowSubU32' from incompatible pointer type [-Werror=incompatible-pointer-types]
   return OcOverflowSubU32 (A, B, Result);
                                  ^~~~~~
In file included from ~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:19:
~/edk2/OcSupportPkg/Include/Library/OcOverflowLib.h:58:12: note: expected 'UINT32 *' {aka 'unsigned int *'} but argument is of type 'UINTN *' {aka 'long long unsigned int *'}
   UINT32  *Result
   ~~~~~~~~~^~~~~~
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c: In function 'OcOverflowMulUN':
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:72:34: error: passing argument 3 of 'OcOverflowMulU32' from incompatible pointer type [-Werror=incompatible-pointer-types]
   return OcOverflowMulU32 (A, B, Result);
                                  ^~~~~~
[CC] Allocate
In file included from ~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:19:
~/edk2/OcSupportPkg/Include/Library/OcOverflowLib.h:65:12: note: expected 'UINT32 *' {aka 'unsigned int *'} but argument is of type 'UINTN *' {aka 'long long unsigned int *'}
   UINT32  *Result
   ~~~~~~~~~^~~~~~
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c: In function 'OcOverflowAddSN':
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:86:34: error: passing argument 3 of 'OcOverflowAddS32' from incompatible pointer type [-Werror=incompatible-pointer-types]
   return OcOverflowAddS32 (A, B, Result);
                                  ^~~~~~
In file included from ~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:19:
~/edk2/OcSupportPkg/Include/Library/OcOverflowLib.h:104:11: note: expected 'INT32 *' {aka 'int *'} but argument is of type 'INTN *' {aka 'long long int *'}
   INT32  *Result
   ~~~~~~~~^~~~~~
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c: In function 'OcOverflowSubSN':
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:100:34: error: passing argument 3 of 'OcOverflowSubS32' from incompatible pointer type [-Werror=incompatible-pointer-types]
   return OcOverflowSubS32 (A, B, Result);
                                  ^~~~~~
[SLINK] UefiRuntimeServicesTableLib
In file included from ~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:19:
~/edk2/OcSupportPkg/Include/Library/OcOverflowLib.h:111:11: note: expected 'INT32 *' {aka 'int *'} but argument is of type 'INTN *' {aka 'long long int *'}
   INT32  *Result
   ~~~~~~~~^~~~~~
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c: In function 'OcOverflowMulSN':
Building ... ~/edk2/MdePkg/Library/UefiBootServicesTableLib/UefiBootServicesTableLib.inf [X64]
~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:114:34: error: passing argument 3 of 'OcOverflowMulS32' from incompatible pointer type [-Werror=incompatible-pointer-types]
   return OcOverflowMulS32 (A, B, Result);
                                  ^~~~~~
In file included from ~/edk2/OcSupportPkg/Library/OcOverflowLib/NativeOverflow.c:19:
~/edk2/OcSupportPkg/Include/Library/OcOverflowLib.h:118:11: note: expected 'INT32 *' {aka 'int *'} but argument is of type 'INTN *' {aka 'long long int *'}
   INT32  *Result
   ~~~~~~~~^~~~~~
cc1: all warnings being treated as errors
make: *** [~/edk2/Build/AppleSupportPkg/RELEASE_GCC82/X64/OcSupportPkg/Library/OcOverflowLib/OcOverflowLib/OUTPUT/NativeOverflow.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [~/edk2/Build/AppleSupportPkg/RELEASE_GCC82/X64/OcSupportPkg/Library/OcOverflowLib/OcOverflowLib]


build.py...
 : error F002: Failed to build module
	~/edk2/OcSupportPkg/Library/OcOverflowLib/OcOverflowLib.inf [X64, GCC82, RELEASE]

- Failed -
Build end time: 19:26:54, Oct.09 2018
Build total time: 00:00:05

I've tried to fix these errors but with my limited coding skills I have so far failed. Is it possible to tweak the code to compile using gcc or would you prefer just to stick to Xcode?

Share this post


Link to post
Share on other sites
14 hours ago, Matgen84 said:

 

Tienes razón  :) en otro tema, @ fusion71au dice: "Sólo una cabeza que @ vit9696 ha quitado EfiMiscPkg (y agregados OcSupportPkg) en su último se compromete a AppleSupportPkg."

 

 

Hi Matgen84, I could share your modified Dids Build Clover. I have not got Clover to build virtualSMC.efi in my configuration. Thank you for your attention.

Share this post


Link to post
Share on other sites
33 minutes ago, camillionario said:

Hi Matgen84, I could share your modified Dids Build Clover. I have not got Clover to build virtualSMC.efi in my configuration. Thank you for your attention.

 

I have also not got Clover to build virtualSMC.efi in my configuration. For now, this driver compiles with an xcode5 toolchain, instead of xcode8 toolchain for clover

Share this post


Link to post
Share on other sites
Would like to report F11 in Clover menu isn't clearing all the NVRAM anymore.

your are right. specific nvram value can be removed. i will find way that can remove all NVRAM

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

Share this post


Link to post
Share on other sites

@Rehabman

 

Hi Rehabman

 

I havv saw you have commit twice related with EDID injection and Devices-Properties and i have test the latest Clover r4707 and still cant inject EDID correctly when i set values in Devices-Properties.

 

Here are the logs show EDID injection but actually it dont be injected successfully,

 

25:354  0:000  === [ RestSetup macOS ] ===================================
25:354  0:000  EdidDiscovered size=128
25:354  0:000  --- Discovered EDID Table size:128
25:354  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  16  83
25:354  0:000  010  |  00  00  00  00  00  00  1A  16  01  04
25:354  0:000  020  |  A5  0F  14  78  06  EF  05  A3  54  4C
25:354  0:000  030  |  99  26  0F  50  54  00  00  00  01  01
25:354  0:000  040  |  01  01  01  01  01  01  01  01  01  01
25:354  0:000  050  |  01  01  01  01  20  4E  00  53  60  00
25:354  0:000  060  |  0B  80  10  0F  71  00  94  C5  00  00
25:354  0:000  070  |  00  18  00  00  00  10  00  00  00  00
25:355  0:000  080  |  00  00  00  00  00  00  00  00  00  00
25:355  0:000  090  |  00  00  00  FE  00  4C  50  30  39  37
25:355  0:000  100  |  51  58  32  2D  53  50  41  56  00  00
25:355  0:000  110  |  00  FC  00  43  6F  6C  6F  72  20  4C
25:355  0:000  120  |  43  44  0A  20  20  20  00  A8
25:355  0:000      HorizontalSyncPulseWidth = 0x0F changed to 0x20
25:355  0:000  --- Patched EDID Table size:128
25:355  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  16  83
25:355  0:000  010  |  00  00  00  00  00  00  1A  16  01  04
25:355  0:000  020  |  A5  0F  14  78  06  EF  05  A3  54  4C
25:355  0:000  030  |  99  26  0F  50  54  00  00  00  01  01
25:355  0:000  040  |  01  01  01  01  01  01  01  01  01  01
25:355  0:000  050  |  01  01  01  01  20  4E  00  53  60  00
25:355  0:000  060  |  0B  80  10  20  71  00  94  C5  00  00
25:355  0:000  070  |  00  18  00  00  00  10  00  00  00  00
25:355  0:000  080  |  00  00  00  00  00  00  00  00  00  00
25:355  0:000  090  |  00  00  00  FE  00  4C  50  30  39  37
25:355  0:000  100  |  51  58  32  2D  53  50  41  56  00  00
25:355  0:000  110  |  00  FC  00  43  6F  6C  6F  72  20  4C
25:355  0:000  120  |  43  44  0A  20  20  20  00  97
25:355  0:000  add device: PciRoot(0x0)/Pci(0x2,0x0)
25:355  0:000     Add key=framebuffer-stolenmem valuelen=4
25:355  0:000     Add key=framebuffer-patch-enable valuelen=4
25:355  0:000     Add key=framebuffer-fbmem valuelen=4
25:355  0:000     Add key=AAPL,ig-platform-id valuelen=4
25:355  0:000  Intel HD Graphics 5300 [8086:161E] :: PciRoot(0x0)\Pci(0x2,0x0)
25:355  0:000    Found Unknown Resolution Display - ?:? :: Width=1536 Height=2048
25:355  0:000    AAPL00,override-no-connect: added
25:355  0:000    Beginning DualLink auto-detection
25:355  0:000    Unknown Resolution Display
25:355  0:000    AAPL00,DualLink = 1
25:355  0:000    FakeID Intel GFX: not set
25:355  0:000    ig-platform-id = 0x16260006
25:355  0:000    Beginning Intel GFX auto-detection with ACPI injection
25:355  0:000    Found FakeID Intel GFX = 0x161E8086
25:355  0:000  Intel GFX revision  = 0x9
25:355  0:000  stringlength = 2600
25:355  0:000  CurrentMode: Width=1536 Height=2048

 

Throughout the boot.log it shows it inject EDID first and then inject Properties later and the EDID injection failed when Properties injected.

Share this post


Link to post
Share on other sites
5 hours ago, gujiangjiang said:

@Rehabman

 

Hi Rehabman

 

I havv saw you have commit twice related with EDID injection and Devices-Properties and i have test the latest Clover r4707 and still cant inject EDID correctly when i set values in Devices-Properties.

 

Here are the logs show EDID injection but actually it dont be injected successfully,

 


25:354  0:000  === [ RestSetup macOS ] ===================================
25:354  0:000  EdidDiscovered size=128
25:354  0:000  --- Discovered EDID Table size:128
25:354  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  16  83
25:354  0:000  010  |  00  00  00  00  00  00  1A  16  01  04
25:354  0:000  020  |  A5  0F  14  78  06  EF  05  A3  54  4C
25:354  0:000  030  |  99  26  0F  50  54  00  00  00  01  01
25:354  0:000  040  |  01  01  01  01  01  01  01  01  01  01
25:354  0:000  050  |  01  01  01  01  20  4E  00  53  60  00
25:354  0:000  060  |  0B  80  10  0F  71  00  94  C5  00  00
25:354  0:000  070  |  00  18  00  00  00  10  00  00  00  00
25:355  0:000  080  |  00  00  00  00  00  00  00  00  00  00
25:355  0:000  090  |  00  00  00  FE  00  4C  50  30  39  37
25:355  0:000  100  |  51  58  32  2D  53  50  41  56  00  00
25:355  0:000  110  |  00  FC  00  43  6F  6C  6F  72  20  4C
25:355  0:000  120  |  43  44  0A  20  20  20  00  A8
25:355  0:000      HorizontalSyncPulseWidth = 0x0F changed to 0x20
25:355  0:000  --- Patched EDID Table size:128
25:355  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  16  83
25:355  0:000  010  |  00  00  00  00  00  00  1A  16  01  04
25:355  0:000  020  |  A5  0F  14  78  06  EF  05  A3  54  4C
25:355  0:000  030  |  99  26  0F  50  54  00  00  00  01  01
25:355  0:000  040  |  01  01  01  01  01  01  01  01  01  01
25:355  0:000  050  |  01  01  01  01  20  4E  00  53  60  00
25:355  0:000  060  |  0B  80  10  20  71  00  94  C5  00  00
25:355  0:000  070  |  00  18  00  00  00  10  00  00  00  00
25:355  0:000  080  |  00  00  00  00  00  00  00  00  00  00
25:355  0:000  090  |  00  00  00  FE  00  4C  50  30  39  37
25:355  0:000  100  |  51  58  32  2D  53  50  41  56  00  00
25:355  0:000  110  |  00  FC  00  43  6F  6C  6F  72  20  4C
25:355  0:000  120  |  43  44  0A  20  20  20  00  97
25:355  0:000  add device: PciRoot(0x0)/Pci(0x2,0x0)
25:355  0:000     Add key=framebuffer-stolenmem valuelen=4
25:355  0:000     Add key=framebuffer-patch-enable valuelen=4
25:355  0:000     Add key=framebuffer-fbmem valuelen=4
25:355  0:000     Add key=AAPL,ig-platform-id valuelen=4
25:355  0:000  Intel HD Graphics 5300 [8086:161E] :: PciRoot(0x0)\Pci(0x2,0x0)
25:355  0:000    Found Unknown Resolution Display - ?:? :: Width=1536 Height=2048
25:355  0:000    AAPL00,override-no-connect: added
25:355  0:000    Beginning DualLink auto-detection
25:355  0:000    Unknown Resolution Display
25:355  0:000    AAPL00,DualLink = 1
25:355  0:000    FakeID Intel GFX: not set
25:355  0:000    ig-platform-id = 0x16260006
25:355  0:000    Beginning Intel GFX auto-detection with ACPI injection
25:355  0:000    Found FakeID Intel GFX = 0x161E8086
25:355  0:000  Intel GFX revision  = 0x9
25:355  0:000  stringlength = 2600
25:355  0:000  CurrentMode: Width=1536 Height=2048

 

Throughout the boot.log it shows it inject EDID first and then inject Properties later and the EDID injection failed when Properties injected.

 

case1

no intel injection, Device/Properties, inject EDID

 

case2

no intel injection, no inject EDID, Device/Properties(AAPL00,override-no-connect)

 

case3

intel injection, Device/AddProperties(IntelGFX), inject EDID

 

i'm using case3

Share this post


Link to post
Share on other sites
3 hours ago, Sherlocks said:

 

case1

no intel injection, Device/Properties, inject EDID

 

case2

no intel injection, no inject EDID, Device/Properties(AAPL00,override-no-connect)

 

case3

intel injection, Device/AddProperties(IntelGFX), inject EDID

 

i'm using case3

 

i'm using case1(no intel injection, Device/Properties, inject EDID) because i need Intel Framebuffer patching using WhateverGreen with DVMT patch but i must use patched EDID to solve the display problem.

 

but case1 have conflict between EDID injection and Device/Properties.

QQ20181018-020937@2x.png

QQ20181018-021002@2x.png

Edited by gujiangjiang

Share this post


Link to post
Share on other sites
17 hours ago, gujiangjiang said:

 

i'm using case1(no intel injection, Device/Properties, inject EDID) because i need Intel Framebuffer patching using WhateverGreen with DVMT patch but i must use patched EDID to solve the display problem.

 

but case1 have conflict between EDID injection and Device/Properties.

QQ20181018-020937@2x.png

QQ20181018-021002@2x.png

I have to remind you a condition for the inject

You must inject override-no-edid manually even if empty.

Share this post


Link to post
Share on other sites
I have to remind you a condition for the inject
You must inject override-no-edid manually even if empty.


Sorry for my ignorance.

I will look into this post carefully and thanks for your help and reply.

Good wishes!


从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites
On 10/16/2018 at 9:49 AM, Pavo said:

Would like to report F11 in Clover menu isn't clearing all the NVRAM anymore.

@Pavo. i traced NVRAM values and i checked vit9696 cleanvram efi file.

i saw many nvram values for system.

if ease all option, maybe we can lost our system. therefore specific nvram values were removed.

 

2:259  0:000  DIAGSPLSHSCRN
2:259  0:000  SetupMode
2:259  0:000  SignatureSupport
2:259  0:000  SecureBoot
2:260  0:000  VendorKeys
2:260  0:000  XVar
2:260  0:000  TxeUnlockBootCount
2:260  0:000  BootOptionSupport
2:260  0:000  PlatformLangCodes
2:261  0:000  SctCapResvMemAddr
2:261  0:000  SctCapResvMemSize
2:261  0:000  SetupVolatileData
2:261  0:000  CpuSetupVolatileData
2:262  0:000  ColdReset
2:262  0:000  SaColdReset
2:262  0:000  MeColdReset
2:262  0:000  CpuColdReset
2:262  0:000  PchColdReset
2:262  0:000  IccMbpData
2:263  0:000  ConOutDev
2:263  0:000  ErrOutDev
2:263  0:000  ConInDev
2:263  0:000  MeInfoSetup
2:264  0:000  OsIndicationsSupported
2:264  0:000  BootCurrent
2:264  0:000  AuthVarKeyDatabase
2:264  0:000  VendorKeysNv
2:264  0:000  SaDataBase
2:264  0:000  PbaStatusVar
2:265  0:000  XnoteFpVar
2:265  0:000  SecureBootEnable
2:265  0:000  PciBusSetup
2:265  0:000  MeBiosExtensionSetup
2:265  0:000  SelectView
2:265  0:000  UCR
2:266  0:000  CustomMode
2:266  0:000  MemoryOverwriteRequestControlLock
2:266  0:000  TcgSetup
2:266  0:000  RTC
2:267  0:000  MemoryConfig
2:267  0:000  AcpiGlobalVariable
2:267  0:000  PlatformLang
2:267  0:000  SctLoadDefaultCreateFlag
2:267  0:000  ExFPDT
2:267  0:000  SetupCpuFeatures
2:268  0:000  HDDPWD
2:268  0:000  SinitSvnSetup
2:268  0:000  InitSetupVariable
2:268  0:000  OsProfile
2:268  0:000  TREE_CONFIGURATION
2:268  0:000  Boot0010
2:269  0:000  Boot0011
2:269  0:000  Boot0012
2:269  0:000  Boot0013
2:269  0:000  BootMenu
2:269  0:000  Boot0014
2:270  0:000  Boot0015
2:270  0:000  Boot0016
2:270  0:000  Boot0017
2:270  0:000  Boot0018
2:270  0:000  BootAllPciLan
2:270  0:000  Boot0019
2:271  0:000  BootOrderDefault
2:271  0:000  ProtectedBootOptions
2:271  0:000  Key0000
2:271  0:000  Key0001
2:271  0:000  Key0002
2:272  0:000  Key0003
2:272  0:000  Key0004
2:272  0:000  Key0005
2:272  0:000  Key0006
2:272  0:000  ConOut
2:272  0:000  TrEEPhysicalPresenceFlags
2:273  0:000  TrEEPhysicalPresence
2:273  0:000  BootState
2:273  0:000  S3MemoryVariable
2:273  0:000  CapsuleLongModeBuffer
2:273  0:000  FirmwarePerformance
2:273  0:000  HSTI_RESULTS
2:274  0:000  PlatformConfigurationChange
2:274  0:000  MemoryTypeInformation
2:274  0:000  MeSetupStorage
2:274  0:000  SystemAccess
2:274  0:000  CpuSmm
2:275  0:000  PNP0604_1_VV
2:275  0:000  PNP0604_1_NV
2:275  0:000  PNP0501_0_VV
2:275  0:000  PNP0501_0_NV
2:275  0:000  PNP0510_1_VV
2:275  0:000  PNP0510_1_NV
2:276  0:000  PNP0400_0_VV
2:276  0:000  PNP0400_0_NV
2:276  0:000  PNP0604_0_VV
2:276  0:000  PNP0604_0_NV
2:276  0:000  PNP0501_2_VV
2:277  0:000  PNP0501_2_NV
2:277  0:000  PNP0400_1_VV
2:277  0:000  PNP0400_1_NV
2:277  0:000  PNP0604_2_VV
2:277  0:000  PNP0604_2_NV
2:277  0:000  PNP0501_3_VV
2:278  0:000  PNP0501_3_NV
2:278  0:000  PNP0501_4_VV
2:278  0:000  PNP0501_4_NV
2:278  0:000  PNP0400_2_VV
2:278  0:000  PNP0400_2_NV
2:278  0:000  UserManagerVar
2:279  0:000  Timeout
2:279  0:000  CurrentActivePolicy
2:279  0:000  certdb
2:279  0:000  CurrentPolicy
2:279  0:000  BootDebugPolicyApplied
2:280  0:000  Kernel_SiStatus
2:280  0:000  Kernel_RvkSiStatus
2:280  0:000  Kernel_SkuSiStatus
2:280  0:000  Kernel_WinSiStatus
2:280  0:000  Kernel_ATPSiStatus
2:280  0:000  Kernel_EntRevokeSiStatus
2:281  0:000  WindowsBootChainSvn
2:281  0:000  BootingDeviceTypeInfo
2:281  0:000  UnlockID
2:281  0:000  UnlockIDCopy
2:281  0:000  OfflineUniqueIDEKPub
2:282  0:000  OfflineUniqueIDEKPubCRC
2:282  0:000  dbx
2:282  0:000  MemoryOverwriteRequestControl
2:282  0:000  Boot0001
2:282  0:000  Boot0000
2:282  0:000  UIScale
2:283  0:000  current-network
2:283  0:000  XnoteStat
2:283  0:000  System
2:283  0:000  HDD_Password_Status
2:283  0:000  boot-feature-usage
2:284  0:000  Boot0081
2:284  0:000  Boot0080
2:284  0:000  LastBootOrder
2:284  0:000  LastBootCurrent
2:284  0:000  BiosSetup
2:284  0:000  XnoteBootFailCounts
2:285  0:000  Setup
2:285  0:000  SaSetup
2:285  0:000  PchSetup
2:285  0:000  CpuSetup
2:285  0:000  MeSetup
2:286  0:000  PlatformInfo
2:286  0:000  BootOrder
2:286  0:000  fakesmc-key-$Num-ui8
2:286  0:000  csr-active-config
2:286  0:000  specialbootdevice
2:286  0:000  backlight-level
2:287  0:000  preferred-networks
2:287  0:000  preferred-count
2:287  0:000  bluetoothActiveControllerInfo
2:287  0:000  fakesmc-key-$Adr-ui32
2:287  0:000  fakesmc-key-RMde-char
2:288  0:000  security-mode
2:288  0:000  EFILoginHiDPI
2:288  0:000  flagstate
2:288  0:000  fakesmc-key-RPlt-ch8*
2:288  0:000  fakesmc-key-RBr -ch8*
2:288  0:000  fakesmc-key-EPCI-ui32
2:289  0:000  fakesmc-key-REV -ch8*
2:289  0:000  fakesmc-key-BEMB-flag
2:289  0:000  fakesmc-key-BATP-flag
2:289  0:000  fakesmc-key-BNum-ui8
2:289  0:000  fakesmc-key-BBIN-ui8
2:290  0:000  fakesmc-key-MSTc-ui8
2:290  0:000  fakesmc-key-MSAc-ui16
2:290  0:000  fakesmc-key-MSWr-ui8
2:290  0:000  fakesmc-key-MSFW-ui8
2:290  0:000  fakesmc-key-MSPS-ui16
2:290  0:000  SystemAudioVolumeDB
2:291  0:000  fmm-computer-name
2:291  0:000  fakesmc-key-#KEY-ui32
2:291  0:000  AAPL,PanicInfoLog
2:291  0:000  SystemAudioVolume
2:291  0:000  security-mode
2:292  0:000  backlight-level
2:292  0:000  EFILoginHiDPI
2:292  0:000  flagstate
2:292  0:000  csr-active-config
2:292  0:000  specialbootdevice
2:292  0:000  AAPL,PathProperties0000
2:293  0:000  PVar
2:293  0:000  OpromDevicePath
2:293  0:000  ConIn
2:293  0:000  MTC

Now the macOS nvram value is mixed with the nvram values of my laptop.

 

what is your left nvram values?

Share this post


Link to post
Share on other sites
@Pavo. i worked NVRAM cleaner and tested all.its same that CleanNvram.efi of vit9696. try latest clover.

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

Pressing F11 at clover GUI froze up the GUI and deleted the boot option for clover. But it did in fact clean the nvram.

 

Edit: second reboot cleared nvram, reset boot order and removed custom boot entry but didn’t freeze. I think I had windows highlighted the first time, would that have caused the freeze?

 

Sent from my iPhone using Tapatalk

 

Share this post


Link to post
Share on other sites

Pressing F11 at clover GUI froze up the GUI and deleted the boot option for clover.


Sent from my iPhone using Tapatalk
froze up -> processing -> reboot okay?
i know vit9696 nvram clear has bootorder remove. i think he want all nvram value initialized. i will add that avoid to remove boot option.

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
3 minutes ago, Sherlocks said:

froze up -> processing -> reboot okay?
i know vit9696 nvram clear has bootorder remove. i think he want all nvram value initialized. i will add that avoid to remove boot option.

 

Then "/EFI/CLOVER/tools/CleanNvram.efi" no longer needed with this rev?

Share this post


Link to post
Share on other sites
54 minutes ago, Badruzeus said:
 
Then "/EFI/CLOVER/tools/CleanNvram.efi" no longer needed with this rev?

right. if you want, press f11 in gui

 

in r4717. it's fixed.

some users use virtualsmc. but there is previous fakesmc values in NVRAM. in mojave, it's hard to remove it.

because nvram -c command is not working. so you usually use CleanNvram.efi. now in GUI, press f11, you easily remove NVRAM values.

 
나의 LG-F800S 의 Tapatalk에서 보냄
 

Edited by Sherlocks

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By gengstapo
      @Hervé
       
      Im having similar issue with my HS setup, dell latitute 3480, i5-7200U
      Once the hdmi plugged in, the laptop display went blank, only could see the external tv
      But, when i put my laptop to sleep & wake up again, both screen got display (hdmi still connected)
      Even the hdmi could be plugged off & in (after sleep), the laptop display is fine
       
      What could be the culprit?
      Dell’s MacBook Pro IORegistry.zip
      config.plist.zip
    • By TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By MaLd0n
      ---TUTORIAL---
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Original Post--
      https://www.olarila.com/topic/6531-olarila-hackbeast-z390-designare-thunderbolt-full-dsdt-patches-clover-opencore/
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://www.olarila.com/topic/6364-mojave-catalina-on-mobos-series-100200300-with-opencore-bootloader/
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
×