Matgen84 Posted October 9, 2018 Share Posted October 9, 2018 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. " Link to comment Share on other sites More sharing options...
dgsga Posted October 9, 2018 Share Posted October 9, 2018 @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? 1 Link to comment Share on other sites More sharing options...
camillionario Posted October 10, 2018 Share Posted October 10, 2018 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. Link to comment Share on other sites More sharing options...
Matgen84 Posted October 10, 2018 Share Posted October 10, 2018 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 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted October 10, 2018 Share Posted October 10, 2018 Unless I’m wrong the virtualsmc.efi driver is only for FV2? I’m using the kext alone and it works fine. Sent from my iPhone using Tapatalk 1 Link to comment Share on other sites More sharing options...
Pavo Posted October 16, 2018 Share Posted October 16, 2018 Would like to report F11 in Clover menu isn't clearing all the NVRAM anymore. Link to comment Share on other sites More sharing options...
Sherlocks Posted October 16, 2018 Share Posted October 16, 2018 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에서 보냄 1 Link to comment Share on other sites More sharing options...
gujiangjiang Posted October 17, 2018 Share Posted October 17, 2018 @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. Link to comment Share on other sites More sharing options...
Sherlocks Posted October 17, 2018 Share Posted October 17, 2018 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 Link to comment Share on other sites More sharing options...
gujiangjiang Posted October 17, 2018 Share Posted October 17, 2018 (edited) 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. Edited October 17, 2018 by gujiangjiang Link to comment Share on other sites More sharing options...
Slice Posted October 18, 2018 Share Posted October 18, 2018 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. I have to remind you a condition for the inject You must inject override-no-edid manually even if empty. 1 Link to comment Share on other sites More sharing options...
gujiangjiang Posted October 18, 2018 Share Posted October 18, 2018 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 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 19, 2018 Share Posted October 19, 2018 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? Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2018 Share Posted October 20, 2018 @Pavo. i worked NVRAM cleaner and tested all.its same that CleanNvram.efi of vit9696. try latest clover.나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
LockDown Posted October 20, 2018 Share Posted October 20, 2018 Any progress for the nvram issue on 300 series? Link to comment Share on other sites More sharing options...
SavageAUS Posted October 20, 2018 Share Posted October 20, 2018 @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 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2018 Share Posted October 20, 2018 Pressing F11 at clover GUI froze up the GUI and deleted the boot option for clover. Sent from my iPhone using Tapatalkfroze 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에서 보냄 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 20, 2018 Share Posted October 20, 2018 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? Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2018 Share Posted October 20, 2018 (edited) 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 October 20, 2018 by Sherlocks 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 20, 2018 Share Posted October 20, 2018 Yeah, pressed "F11" to clear NVRAM with r4716 it changed "Bootloader Entries" Order on my case. (Left: before F11, Right: after). Link to comment Share on other sites More sharing options...
moldus Posted October 20, 2018 Share Posted October 20, 2018 1 hour 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. 나의 LG-F800S 의 Tapatalk에서 보냄 Thanks, deleting the boot menu will break other OS installations. May prevent booting at all on some systems. Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2018 Share Posted October 20, 2018 Thanks, deleting the boot menu will break other OS installations. May prevent booting at all on some systems.try latest version r4717. cleannvram.efi has deleting the boot menu option. i added that disabled this option. i tested again. there is no problem.나의 LG-F800S 의 Tapatalk에서 보냄 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 20, 2018 Share Posted October 20, 2018 1 minute ago, Sherlocks said: ".. cleannvram.efi has deleting the boot menu option." Sorry, I've removed this *.efi before (on last r4716 test) and it still changed bootloader orders. OK, I'll try again with r4717. Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2018 Share Posted October 20, 2018 (edited) 7 minutes ago, Badruzeus said: Sorry, I've removed this *.efi before (on last r4716 test) and it still changed bootloader orders. OK, I'll try again with r4717. you can't see BootOrder nnvram in macos. cleannvram.efi remove BootOrder nvram value and other from filter that has Boot####. it affects our clover boot option entry in BIOS. after press f11, my nvram result(aptiomemoryfix, vitrualsmc). it's very clean status. Last login: Sat Oct 20 21:15:07 on ttys000 SherloccBookPro:~ sherlocks$ nvram -p fmm-computer-name Sherlocks%ec%9d%98 MacBook%c2%a0Pro security-mode none bluetoothActiveControllerInfo z%e0%89%04%00%00%00%000%14%ac%d1%b8%e2%a4%d0 EFILoginHiDPI %00%00%00%00 specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00%00H%06%00%00%00%00%00%00(*%08%00%00%00%00%8f%0a5%8c%c6P%e6C%ad%a6^%16p%d2e%d9%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ba%afc~%ff%1e%a9M%b0%d2$%86%1e%e2HD%7f%ff%04%00 SystemAudioVolume # SystemAudioVolumeDB %d9 csr-active-config w%00%00%00 backlight-level i%05 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 SherloccBookPro:~ sherlocks$ Edited October 20, 2018 by Sherlocks 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 20, 2018 Share Posted October 20, 2018 3 minutes ago, Sherlocks said: you can't see BootOrder nnvram in macos. cleannvram.efi remove BootOrder nvram value and other from filter that has Boot####. it affects our clover boot option entry in BIOS. OK, not a big issue for me since I have "Boot entry" options on my Aptio BIOS (firmware) and could be re-ordered easily. 1 Link to comment Share on other sites More sharing options...
Recommended Posts