Jump to content

2,199 posts in this topic

Recommended Posts

Advertisement
1 hour ago, hardcorehenry said:

Have you noticed you have in your config ACPI SSDT add-ons with .dsl extensions. Should be ACPI Maschine Language Binary with .aml extensions. Don't you need UEFI quirks like RequestBootVarRouting and probably others. You really have to read about quirks in Configuration.pdf

 

Yes, I am aware that they have a .dsl extension. Nonetheless, they are disabled ATM as I am using patching as per my previous post, hence will not need any .aml files.

 

I have taken a look already at the Configuration.pdf file as well as the Vanilla guide, and I do not need them enabled for my machine, as far as I can tell.

 

I am not an expert, but from what the message tells me, it cannot load the "boot options". So perhaps, it does not recognise my HFS+ and APFS partitions?

 

Thanks!

Share this post


Link to post
Share on other sites
27 minutes ago, lottenow said:

 

I am not an expert, but from what the message tells me, it cannot load the "boot options". So perhaps, it does not recognise my HFS+ and APFS partitions?

 

Thanks!

When changing the value for ScanPolicy, make sure you don’t add commas, let Xcode add them (otherwise the value will be corrupted). If you’re not sure what value you should be using initially, try 0 and see if that works. (Failsafe value does not support HFS+)

Share this post


Link to post
Share on other sites
15 minutes ago, canyondust said:

When changing the value for ScanPolicy, make sure you don’t add commas, let Xcode add them (otherwise the value will be corrupted). If you’re not sure what value you should be using initially, try 0 and see if that works. (Failsafe value does not support HFS+)

 

My USB where OpenCore is formatted as HFS+, whilst Catalina is using APFS.

 

Your suggestion actually took me to a new error, which I have attached below.

 

I had my ScanPolicy set to 0 and changed it to 983,299 as per Vanilla Guide under Security. It does boot now, even though I still get an error. I am not sure why it would not boot when I select 0, i.e. scan all.

 

Quote

 

I do not use Xcode, but PlistEdit Pro, which works flawlessly.

screenshot.jpg

Share this post


Link to post
Share on other sites

I know this has been asked as a feature request by Sniki but I wanted to second his request for InfoPlistPatch.

 

I'm having most everything working well in OC v050 (using the X299 build) in both Mojave and Catalina, except for an InfoPlist Patch item. The code is for adjusting the monitor brightness with the F1/F2 keys, using the NativeDisplayBrightness.app

 

SOLVED:

 

I used a different app, MonitorControl. It doesn't require any config.plist entries to work. https://github.com/the0neyouseek/MonitorControl/releases

 

Edited by iGPU
Solved problem.

Share this post


Link to post
Share on other sites
13 hours ago, lottenow said:

 

My USB where OpenCore is formatted as HFS+, whilst Catalina is using APFS.

 

Your suggestion actually took me to a new error, which I have attached below.

 

 

Seems to be a potential issue with virtualsmc. Did you include it’s plugins in your config kext list?

Share this post


Link to post
Share on other sites
13 hours ago, lottenow said:

 

My USB where OpenCore is formatted as HFS+, whilst Catalina is using APFS.

 

Your suggestion actually took me to a new error, which I have attached below.

 

 

Seems to be a potential issue with virtualsmc. Did you include it’s plugins in your config kext list?

Share this post


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

 

My USB where OpenCore is formatted as HFS+, whilst Catalina is using APFS.

 

Your suggestion actually took me to a new error, which I have attached below.

 

I had my ScanPolicy set to 0 and changed it to 983,299 as per Vanilla Guide under Security. It does boot now, even though I still get an error. I am not sure why it would not boot when I select 0, i.e. scan all.

 

 

I do not use Xcode, but PlistEdit Pro, which works flawlessly.

screenshot.jpg

 

Do you try to remove virtualsmc.efi (keep virtualsmc.kext of course)

Share this post


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

Seems to be a potential issue with virtualsmc. Did you include it’s plugins in your config kext list?

 

5 hours ago, canyondust said:

Seems to be a potential issue with virtualsmc. Did you include it’s plugins in your config kext list?

 

Yes, I have it in the OC/Drivers folder as well as under UEFI>Drivers>0>VirtualSMC.efi on my config.plist.

 

I still cannot understand why my VirtualSMC is broken, given that I updated it to the latest release.

 

2 hours ago, Matgen84 said:

 

Do you try to remove virtualsmc.efi (keep virtualsmc.kext of course)

 

I have tried that and my screen has now change. I have also swapped the AppleGenericInput.efi for UsbKbDxe.efi to try and resolve the issue of ApplePS2Controller, but it still stands.

 

- ACPI: Same as before

- Drivers: ApfsDriverLoader, FwRuntimeServices, UsbKbDxe, VBoxHfs

- config.plist updated attached as well as screenshot

 

Thank you!

 

unnamed.jpg

config.plist

Edited by lottenow

Share this post


Link to post
Share on other sites
53 minutes ago, lottenow said:

 

 

Yes, I have it in the OC/Drivers folder as well as under UEFI>Drivers>0>VirtualSMC.efi on my config.plist.

 

I still cannot understand why my VirtualSMC is broken, given that I updated it to the latest release.

 

 

I have tried that and my screen has now change. I have also swapped the AppleGenericInput.efi for UsbKbDxe.efi to try and resolve the issue of ApplePS2Controller, but it still stands.

 

- ACPI: Same as before

- Drivers: ApfsDriverLoader, FwRuntimeServices, UsbKbDxe, VBoxHfs

- config.plist updated attached as well as screenshot

 

Thank you!

 

 

config.plist

 

 

Get Acidanthera VoodooPS2. Edit your config like this:PS2.png.aa2a24e206d9a0ff5d4a91f6401f4cd2.png

Share this post


Link to post
Share on other sites
51 minutes ago, lottenow said:

 

 

Yes, I have it in the OC/Drivers folder as well as under UEFI>Drivers>0>VirtualSMC.efi on my config.plist.

 

I still cannot understand why my VirtualSMC is broken, given that I updated it to the latest release.

 

 

I have tried that and my screen has now change. I have also swapped the AppleGenericInput.efi for UsbKbDxe.efi to try and resolve the issue of ApplePS2Controller, but it still stands.

 

- ACPI: Same as before

- Drivers: ApfsDriverLoader, FwRuntimeServices, UsbKbDxe, VBoxHfs

- config.plist updated attached as well as screenshot

 

Thank you!

 

unnamed.jpg

config.plist

 

VirtualSMC.efi module is recommended for boot.efi compatibility when FileVault 2 is enabled. :) If you don't use FileVault2, remove it.

 

Do you try to select 'ThirdPartyTrim' Quirk to YES.

Share this post


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

 

 

Get Acidanthera VoodooPS2. Edit your config like this:PS2.png.aa2a24e206d9a0ff5d4a91f6401f4cd2.png

 

Thanks for this! To be honest, I was using VoodooPS2Controller from RehabMan. I was not aware of Acidanthera's kext in relation to VoodooPS2.

I have updated my new configuration which took me to a new screen, yet my VirtualSMC is still broker and will not boot. Strange how everything works under Clover but not under OpenCore, as the system is the same.

 

Please find everything attached to the post.

 

1 hour ago, Matgen84 said:

 

VirtualSMC.efi module is recommended for boot.efi compatibility when FileVault 2 is enabled. :) If you don't use FileVault2, remove it.

 

Do you try to select 'ThirdPartyTrim' Quirk to YES.

 

Fair enough. I believed it was a compatibility issue as FakeSMC requires FakeSMC.efi. Also, my VirtualSMC is still broken as you can see below.

 

I have enabled TRIM even though I am using an HDD for my Catalina partition.

 

Thanks again!

 

config.plist

EFI folder.png

unnamed.jpg

Share this post


Link to post
Share on other sites
34 minutes ago, lottenow said:

 

Thanks for this! To be honest, I was using VoodooPS2Controller from RehabMan. I was not aware of Acidanthera's kext in relation to VoodooPS2.

I have updated my new configuration which took me to a new screen, yet my VirtualSMC is still broker and will not boot. Strange how everything works under Clover but not under OpenCore, as the system is the same.

 

Please find everything attached to the post.

 

 

Fair enough. I believed it was a compatibility issue as FakeSMC requires FakeSMC.efi. Also, my VirtualSMC is still broken as you can see below.

 

I have enabled TRIM even though I am using an HDD for my Catalina partition.

 

Thanks again!

 

config.plist

 

Download virtual smc package. Rigt click VirtualSMC  Show Package Contents, enter Contents directory. Create folder named PlugIns and put all virtual smc plugins in it. Edit config:smc.png.15ac132fec507197a6c718972a25c920.png

34 minutes ago, lottenow said:

 

 

Share this post


Link to post
Share on other sites
57 minutes ago, hardcorehenry said:

 

Download virtual smc package. Rigt click VirtualSMC  Show Package Contents, enter Contents directory. Create folder named PlugIns and put all virtual smc plugins in it. Edit config:smc.png.15ac132fec507197a6c718972a25c920.png

 

 

I have done what you suggested, but there is no real change. I can see as well that one of the ACPI table is failing on start up. I have also tried adding "-vsmcbeta" in my boot-args, because I am running Catalina Beta 8, but without success to boot.

 

I have updated my config.plist and I have attached it to this post.

 

I was wondering whether it is worth looking at my DSDT.aml with MaciASL?

 

Thank you!

 

config.plist

unnamed.jpg

Share this post


Link to post
Share on other sites
40 minutes ago, lottenow said:

 

I have done what you suggested, but there is no real change. I can see as well that one of the ACPI table is failing on start up. I have also tried adding "-vsmcbeta" in my boot-args, because I am running Catalina Beta 8, but without success to boot.

 

I have updated my config.plist and I have attached it to this post.

 

I was wondering whether it is worth looking at my DSDT.aml with MaciASL?

 

Thank you!

 

config.plist

 

Try only with SMCProcessor.kext and SMCSuperIO.kext, also edit Config.

 

 

Edited by hardcorehenry

Share this post


Link to post
Share on other sites

Hey everyone!

 

So I was able to set up OpenCore config and almost everything works on my MSI GS65- 8SE. The only issue I have is that I am unable to shut down or restart my computer. Booting in verbose, I get this after I click restart/shutdown and it stays there forever and does not move forward.

com.apple.xpc.launchd.domain.systen <notice>: userspace teardown took 5039 ms
com.apple.xpc.launchd.domain.systen <notice>: Will be calling reboot(2) with flags 0x8

Notice: I removed my smbios from config.plist and I also compiled OpenCore 0.5.1 from source.

EFI.zip

Edited by e12350

Share this post


Link to post
Share on other sites

@gndzer0 Thanks for your results. Unfortunately, we're currently quite busy and would like to assist with debugging the issue only in a short while. The first important thing we'd like to find out is whether the stall is required inbetween operations or only preceeding the first after wake. If you can debug this part yourself, that'd be great actually. That'd require some sort of flag before S3 (e.g. setting a "magic" NVar) which will then be retrieved and cleared on wake's first SetVariable call.

Share this post


Link to post
Share on other sites

And regarding the Booter quirk set, it may be interesting to know what is on off. Also please remind whether it worked or not with AptioMemoryFix in the past.

Share this post


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

And regarding the Booter quirk set, it may be interesting to know what is on off. Also please remind whether it worked or not with AptioMemoryFix in the past.

@vit9696 Assuming this is @ me, AptioMemoryFix would have the same issue with restarting/shutdown.

Share this post


Link to post
Share on other sites

I have no backlight or brightness slider on macOS Mojave 10.14.6 with OpenCore 0.5.1

anyone can tell me what is problem

Share this post


Link to post
Share on other sites
11 hours ago, e12350 said:

Hey everyone!

 

So I was able to set up OpenCore config and almost everything works on my MSI GS65- 8SE. The only issue I have is that I am unable to shut down or restart my computer. Booting in verbose, I get this after I click restart/shutdown and it stays there forever and does not move forward.


com.apple.xpc.launchd.domain.systen <notice>: userspace teardown took 5039 ms
com.apple.xpc.launchd.domain.systen <notice>: Will be calling reboot(2) with flags 0x8

Notice: I removed my smbios from config.plist and I also compiled OpenCore 0.5.1 from source.

EFI.zip

 

set DisableVariableWrite = YES and try again. 

remove UsbKbDxe.efi and AppleGenericInput.efi if you Do NOT use FV2, plus if you DO use FV2, you must choose one of them, not both.  

Edited by justin

Share this post


Link to post
Share on other sites
21 hours ago, hardcorehenry said:

Try only with SMCProcessor.kext and SMCSuperIO.kext, also edit Config.

 

 

 

Thanks for your reply. I actually managed to get everything working back again, following my Clover configuration and adapting it to OpenCore. I also used another online resource.

 

My specs: i7 8750H, UHD 630, RAM 16GB.

Working: Ethernet, Audio, iGPU.

 

So far, I do not want to configure the whole system as I am using this for testing purpose only on this laptop.

 

Nonetheless, I would like to dig deeper into my ACPI and the correct functioning with OpenCore.

 

Effectively, the system is working without any ACPI patches, as I have completely removed the ACPI folder as it kept on giving me problems with the ACPI samples I found on the vanilla guide, and I have only left the EC0 to EC from my previous post. Most of the ACPI is also changed automatically by WhateverGreen anyway. I also had to add all the "beta" args for Lilu, WhateverGreen and AppleALC for it to work properly on Catalina.

 

I can also see the Recovery option on the OpenCore Boot Menu, but it does not work as it does not load. It is not an issue as I would probably never use it anyway, and it is for testing only, so I am going to pass on this.

 

I am assuming Reset NVRAM option worked as I get a reboot with a black screen and I am back again in OpenCore.

 

I have not tried the BOOTCAMP Windows options, but as far I can understand, ACPI should not be automatically patched in Windows from OpenCore. Even so, I would never use OpenCore to boot to Windows.

 

I would like to know what could be causing the following errors:

Quote

VirtualSMC: efend @ failed to find valid status (000000000000000E, 8), VirtualSMC EFI module is broken

 

Quote

ACPI Error: [_ON_] Namespace lookup failure, AE_ALREADY_EXISTS (20160930/dswload-462)

ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160930/psobject-318)

ACPI Exception: AE_ALREADY_EXISTS, (SSDT: INSVDE) while loading table (20160938/tbxfload-319)

ACPI Error: 1 table load failures. 16 successful (201609930/tbxfload-342)

 

I also get an error regarding power management but I have the configuration set with MacBookPro15,2 which has the CPU I utilise.

 

I would further like to know how to dump a log of OpenCore, as I tried with the F keys, but I am unsuccessful. Perhaps, I have to enable a setting in my config.plist I am unaware of?

 

Last but not least, I would like to know whether OpenCore settings, such as Quirks are off by default rather than me specifying them all the time. So I can have a cleaner config.plist.

 

Particularly with SignedPolicy, is it YES (true) but default or NO (false)?

 

Thank you in advance!

 

config.plist

Schermata 2019-09-14 alle 12.55.34.png

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

  • Similar Content

    • By notiflux
      Unfortunately, this project has come to a halt, at least for now. I don't have enough time to work on the project and it's lacking behind, so please don't use it for configuring OpenCore, it will produce broken configuration files.
      I will leave the source code on GitHub, so in case someone wants to take over the project, they can.
       
      original post:
      OpenCore Configurator Source
    • By clockT
      sono un pò arrugginito ..e volevo chiedere un aiuto su come installare opencore anzichè clover. ho provato ma dopo il post installazione riesco solo a far partire catalina tramite pendrive. quale congifurazione sbaglio?
      EFI.zip

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --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://olarila.com/forum/download/file.php?id=24376
      *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 rusty-bits
      Command line tool that will build a working EFI folder based on the settings in the config.plist file.
      https://github.com/rusty-bits/OC-tool
       
       
      you can also copy your config.plist to the RELEASE folder and double-click OC-tool  
      this is the same as running
      ./OC-tool -uo build release from the command line  
       
      see the wiki for more info  
       
      https://github.com/rusty-bits/OC-tool/wiki
       
      added functionality to the -T option  (update ver 1.6pt)  

      TUI (Text based User Interface) now has limited functionality  
      kexts, drivers, tools and quirks can be toggled on or off, then by pressing g an EFI folder will be created based on what you set  
       
       
      working:  
      - BOOT/BOOTx64.efi built automatically  
      - OC/OpenCore.efi build automatically
      - OC/ACPI folder built automatically from settings in ACPI/Add section of config.plist  
      - - the tool can compile .dsl to .aml on the fly if iasl is present, but I recommend compiling them to .aml yourself for the tool to move over  
      - OC/Drivers folder built automatically from settings in UEFI/Drivers section of config.plist  
      - OC/kexts folder built automatically from settings in Kernel/Add section of config.plist  
      - OC/Tools/Shell.efi built automatically from setings in Misc/Tools section of config.plist  
      - OC/vault.plist and OC/vault.sig are built automatically from the Misc/Security/RequireVault setting in config.plist  
      - can specify debug or release version of resources to be built  
      - parses plist files internally, no longer needs to call /usr/libexec/PlistBuddy which may not exist on Catalina  
      - kexts, drivers, tools and quirks can be enabled or disabled before building the EFI by using the -T option  
       
×