Jump to content
dgsga

OpenCore Discussion

3,027 posts in this topic

Recommended Posts

7 hours ago, vit9696 said:

@floodlitworld, try with 0. 60000 only applies to ASUS Z87 boards.

 

The documentation makes it sound as though the 60000 value applies to all ASUS boards:

 

Quote

The recommended value is 50000 (5 milliseconds) or slightly higher. ASUS boards use 60000 for the interface. Apple boards use 100000. 

 

Should that be updated? Want a PR?

Share this post


Link to post
Share on other sites
Advertisement
"MacBookPro15,1", "MBP151.88Z.F000.B00.1912090131", "1037.80.21.0.0", "Mac-937A206F2EE63C01",


"MacBookPro15,2", "MBP152.88Z.F000.B00.1912090107", "1037.80.21.0.0", "Mac-827FB448E656EC26",

"MacBookPro15,3", "MBP153.88Z.F000.B00.1912082358", "1037.80.21.0.0", "Mac-1E7E29AD0135F9BC", 

"MacBookPro15,4", "MBP154.88Z.F000.B00.1912090124", "1037.80.21.0.0", "Mac-53FDB3D8DB8CA971",

 "MacBookPro16,1", "MBP161.88Z.F000.B00.1912090148", "1037.80.21.0.0", "Mac-E1008331FDC96864", 

 "MacBookAir8,1", "MBA81.88Z.F000.B00.1912090041", "1037.80.21.0.0", "Mac-827FAC58A8FDFA22", 

"MacBookAir8,2", "MBA82.88Z.F000.B00.1912090131", "1037.80.21.0.0", "Mac-226CB3C6A851A671", 

"Macmini8,1", "MM81.88Z.F000.B00.1912082323", "1037.80.21.0.0", "Mac-7BA5B2DFE22DDD8C",

 "iMacPro1,1", "IMP11.88Z.F000.B00.1912082323", "1037.80.21.0.0", "Mac-7BA5B2D9E42DDD94", 

 "MacPro7,1", "MP71.88Z.F000.B00.1912090148", "1037.80.21.0.0", "Mac-27AD2F918AE68F61",

 

Share this post


Link to post
Share on other sites

Quick question.... what to do about in the compile errors for the serialized tool?

Anybody can help with the compile?

This error is driving me nuts.

Thanks, Mike

Quote

 Ranger, this means that some of the <data> fields in your configuration do not seem to be right. One can use OcSupportPkg/TestsUser/Serialized tool to debug configuration issues. Serialized.c contains the compilation command in the beginning of the file (clang -g -fsanitize=undefined,address …). Just compile it in Serialized directory and then pass your config.plist as an argument to see a verbose validation log.

 

Share this post


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

 

The documentation makes it sound as though the 60000 value applies to all ASUS boards:

 

 

Should that be updated? Want a PR?

We have already updated the docs.

 

2 hours ago, Mike Ranger said:

Quick question.... what to do about in the compile errors for the serialized tool?

Anybody can help with the compile?

This error is driving me nuts.

Thanks, Mike

 

Find the error manually for the time being. We will add some build scripts for user tools later.

Share this post


Link to post
Share on other sites
2 hours ago, Mike Ranger said:

Quick question.... what to do about in the compile errors for the serialized tool?

Anybody can help with the compile?

This error is driving me nuts.

Thanks, Mike

 

Serialized.png.fcb05decd1ff475d679ccd30b620f9b6.png

Share this post


Link to post
Share on other sites

tried the same thing with the provided clang command..... full off errors... mostly missing headfiles.

Probably need to download more stuff and put it in the right structure.

I just downloaded the OCSupportPkg Folder and tried to compile from there.

Edited by Mike Ranger

Share this post


Link to post
Share on other sites
On 1/11/2020 at 9:43 PM, nmano said:

Skylake X->Skylake U 0x0406E3
Cpuid1Data   <->  E3060400 00000000 00000000 00000000 
Cpuid1Mask  <->   FFFFFFFF 00000000 00000000 00000000 

 

 

What does this do? Is this worth applying on an X299 board with an i9 7900X?

Share this post


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

generally we use WhateverGreen to disable discrete GPU. As for battery, I am afraid somebody else knows better

Thanks @vit9696 if im correct i think it is documented as it disables external/Dedicated GPU, thanks for the clarification

 

So by that now i know that includes discrete graphics on laptops as well. Nice.

 

I wanted to discuss about Dual Battery support on VirtualSMC/smcbatterymanager.kext

Laptops with Dual Batteries are very common.

MacOS itself has buggy/no dual battery support.

 

As a current solution we use SSDT-BATC.dsl from RehabMan which does work but is not a Acidanthera guidelines friendly solution.

 

What we do with it is that we combine both batteries into a single one and for that to work we also have modify battery notifiers of BAT0 and BAT1 into BATC in order to have correct battery percentage reporting.

For now im modifying battery notifiers with ACPI renames like:

_SB.PCI0.LPCB.EC.BAT0, 0x80 to .....BATC, 0x81.

Usually the notifiers are located into Methods like Method (_Q69,...) etc.

 

I believe with a slight modification for the SSDT to work only with Darwin and if it is possible on virtualsmc side to include a boot-arg or something similar to rename these notifiers in i/o registry level we can have a decent solution.

Or maybe even better solution that those.

 

Its is not a high priority thing but it would be nice to add this if and when it is possible.

 

So what do you think of raising this matter on bugtracker, the number of affected people is decent but the number of them with technical knowledge regarding this is very small, they basically use the guides that we/us with a bit more knowledge make and use them as they are.

I have guides for most of the Haswell Generation Lenovo ThinkPads and pretty much 80% of them have dual batteries, 1 internal and 1 external (removable).

 

Thanks !

Edited by Sniki

Share this post


Link to post
Share on other sites

Updated to OC 0.5.4 with all updated resources, kexts, etc without issue. Seem to have gained about 7% performance as well!

(Though on this update I went from manual platform info to automatic so that might be a factor)

Fantastic work devs!

Share this post


Link to post
Share on other sites
10 hours ago, jinbingmao said:

"MacBookPro15,1", "MBP151.88Z.F000.B00.1912090131", "1037.80.21.0.0", "Mac-937A206F2EE63C01",


"MacBookPro15,2", "MBP152.88Z.F000.B00.1912090107", "1037.80.21.0.0", "Mac-827FB448E656EC26",

"MacBookPro15,3", "MBP153.88Z.F000.B00.1912082358", "1037.80.21.0.0", "Mac-1E7E29AD0135F9BC", 

"MacBookPro15,4", "MBP154.88Z.F000.B00.1912090124", "1037.80.21.0.0", "Mac-53FDB3D8DB8CA971",

 "MacBookPro16,1", "MBP161.88Z.F000.B00.1912090148", "1037.80.21.0.0", "Mac-E1008331FDC96864", 

 "MacBookAir8,1", "MBA81.88Z.F000.B00.1912090041", "1037.80.21.0.0", "Mac-827FAC58A8FDFA22", 

"MacBookAir8,2", "MBA82.88Z.F000.B00.1912090131", "1037.80.21.0.0", "Mac-226CB3C6A851A671", 

"Macmini8,1", "MM81.88Z.F000.B00.1912082323", "1037.80.21.0.0", "Mac-7BA5B2DFE22DDD8C",

 "iMacPro1,1", "IMP11.88Z.F000.B00.1912082323", "1037.80.21.0.0", "Mac-7BA5B2D9E42DDD94", 

 "MacPro7,1", "MP71.88Z.F000.B00.1912090148", "1037.80.21.0.0", "Mac-27AD2F918AE68F61",

 

 

It 10.15.3 beta

Share this post


Link to post
Share on other sites

Sorted out my config.plis, got Serialize compiled..... was a wrong Data written in ROM Generic Section of Platform Data.

So not critical, and now clean.

Thanks again Vit9696 and Download-Fritz

Share this post


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

Updated to OC 0.5.4 with all updated resources, kexts, etc without issue. Seem to have gained about 7% performance as well!

(Though on this update I went from manual platform info to automatic so that might be a factor)

Fantastic work devs!

 

what do you mean 7% performance boost? what kind of performance?

Share this post


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

 

what do you mean 7% performance boost? what kind of performance?

 

GB5 scores went from an average of 1080sc/4650mc to 1250sc/4950mc. The only difference has been upgrading from OC 0.5.3 to OC 0.5.4 and all related support files and kexts. Possible that I had something incorrectly configured in the old version that got corrected in the new version? potentially, but all I did was add the new config parameters to my old config.plist, as well as the aforementioned switch from manual platform info to automatic platform info.

Share this post


Link to post
Share on other sites

@Andrey1970 Correct me if im wrong but is FwRuntimeServices.efi supposed to be removed from sample.plist like VirtualSmc.efi ?

It doesn't seem to be included in any of the supposed packages and description said it was moved to OpenCore which is fine but the sample.plist confused me so I just wanted to know if it should be removed from sample.plist or is the efi needed and forgot to include it ?

Share this post


Link to post
Share on other sites
9 minutes ago, Sniki said:

@Andrey1970 Correct me if im wrong but is FwRuntimeServices.efi supposed to be removed from sample.plist like VirtualSmc.efi ?

It doesn't seem to be included in any of the supposed packages and description said it was moved to OpenCore which is fine but the sample.plist confused me so I just wanted to know if it should be removed from sample.plist or is the efi needed and forgot to include it ?

 

it is included in OpenCore-0.5.4-RELEASE.zip/EFI/OC/Drivers/FwRuntimeServices.efi, check check again.

40 minutes ago, enlaid said:

Is it possible to run native NVRAM on Z390 with OC 0.5.4?

 

No.

Share this post


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

 

GB5 scores went from an average of 1080sc/4650mc to 1250sc/4950mc. The only difference has been upgrading from OC 0.5.3 to OC 0.5.4 and all related support files and kexts. Possible that I had something incorrectly configured in the old version that got corrected in the new version? potentially, but all I did was add the new config parameters to my old config.plist, as well as the aforementioned switch from manual platform info to automatic platform info.

 

illusion, geek bench can't fully utilize CPU during benchmark. Cinebench is more accurate 

Share this post


Link to post
Share on other sites
25 minutes ago, justin said:

 

1 hour ago, enlaid said:

Is it possible to run native NVRAM on Z390 with OC 0.5.4?

 

No.

 

aha .. really ?

 

Share this post


Link to post
Share on other sites

Is is possible to get good performance from OC when booting from a on-board Marvell 88SE9172 SATA Controller on Z77X-UD5H board? When boot drive is connected to this controller, loading to the OC picker menu takes 20+ minutes. Using Intel 7 series port takes seconds. Clover doesn't have this problem so it seems it must be related to some differences in .efi drivers. I currently have only ApfsDriverLoader, FWRuntimeServices, & HFSPlus drivers on OC 0.5.4. Do I need other drivers?

Share this post


Link to post
Share on other sites

Planning to update to OpenCore 0.5.4 from 0.5.3. I've checked the docs and there are a couple of new entries in the config.plist. Is it mandatory to add these entries to my existing config.plist? They are set to False so I think it doesn't matter but still better to be safe.

Also, do I have to compile and use the SSDT***.dsl included in the release package or they're just the same. I cannot seem to find any info that those were changed/updated as well.

 

Thanks.

Share this post


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

Also, do I have to compile and use the SSDT***.dsl included in the release package or they're just the same. I cannot seem to find any info that those were changed/updated as well.

 

you have to compile dsl to aml in order to use them, MaciASL can do the job. You'd better add those items to your config.plist in order to keep update with it. 

Share this post


Link to post
Share on other sites

Hello All!

Getting into OC and feeling a little intimidated. I've always struggled with modifying DSDT or SSDT protocol. Everywhere I look I still am having a hard time figuring out "what is what" in my ACPI tables. I'm using a different motherboard than a lot of the motherboards here (ASrock X299 OC Formula).

I saw that KGP had a basic guide on How to create or modify a simple System SSDT.aml by means of DSDT and IOREG ACPI information. However, his website is down (permanently it looks like). I was able to find a version of it using web archives and thought I'd post it here. It was helpful for me to understand it a little better.

So here is my setup

I am a motion graphics artist and use the GPUs for 3D rendering. MacOS>Windows haha

Clover Bootloader
High Sierra 17G10021 Newest as of 1/10/20
ASrock X299 OC Formula
Intel 9900X
64GB Corsair RGB Vengence Pro
GTX 1080ti in PCIe SLOT-1
GTX 1080ti in PCIe SLOT-3
GTX 1080ti in PCIe SLOT-5
Fenvi T919 in PCIe SLOT-7
Samsung EVO 970 500GB NVME in SLOT M2_1


MACIASL is only showing 5 PCIe slots I think (screenshot attached)
CPUs are mapped weird it think (screenshot attached)
2 of the GRFX cards are thinking they are connected to the same PCIe slot maybe (screenshot attached)

I'm looking for help in the right direction. I know I can do the work, it just hasn't clicked in my head yet. 

If anyone is wanting to take a crack at it, I can provide a RAW DSDT.aml or anything else you might need. Thank you and I love this community.

Also, I have a CUDA issue that causes random reboots on my machine. Only CUDA, the web drivers are fine. The only way to stop it temporarily is to unload CUDA (per a script) when working day to day and then loading CUDA when I need to use it. Once it's loaded, my computer is unstable and will crash sometimes. Hoping OpenCore might help with everything in order.

X299 OC Formula.jpg

PCIe Slots.png

CPUS.png

GRX Same Slot.png

How to create or modify a simple System SSDT.aml by means of DSDT and IOREG ACPI information – KGP's Hackintosh Corner.zip

Edited by cbutters

Share this post


Link to post
Share on other sites
12 hours ago, cbutters said:

Hello All!

Getting into OC and feeling a little intimidated. I've always struggled with modifying DSDT or SSDT protocol. Everywhere I look I still am having a hard time figuring out "what is what" in my ACPI tables. I'm using a different motherboard than a lot of the motherboards here (ASrock X299 OC Formula).

I saw that KGP had a basic guide on How to create or modify a simple System SSDT.aml by means of DSDT and IOREG ACPI information. However, his website is down (permanently it looks like). I was able to find a version of it using web archives and thought I'd post it here. It was helpful for me to understand it a little better.

So here is my setup

I am a motion graphics artist and use the GPUs for 3D rendering. MacOS>Windows haha

Clover Bootloader
High Sierra 17G10021 Newest as of 1/10/20
ASrock X299 OC Formula
Intel 9900X
64GB Corsair RGB Vengence Pro
GTX 1080ti in PCIe SLOT-1
GTX 1080ti in PCIe SLOT-3
GTX 1080ti in PCIe SLOT-5
Fenvi T919 in PCIe SLOT-7
Samsung EVO 970 500GB NVME in SLOT M2_1


MACIASL is only showing 5 PCIe slots I think (screenshot attached)
CPUs are mapped weird it think (screenshot attached)
2 of the GRFX cards are thinking they are connected to the same PCIe slot maybe (screenshot attached)

I'm looking for help in the right direction. I know I can do the work, it just hasn't clicked in my head yet. 

If anyone is wanting to take a crack at it, I can provide a RAW DSDT.aml or anything else you might need. Thank you and I love this community.

Also, I have a CUDA issue that causes random reboots on my machine. Only CUDA, the web drivers are fine. The only way to stop it temporarily is to unload CUDA (per a script) when working day to day and then loading CUDA when I need to use it. Once it's loaded, my computer is unstable and will crash sometimes. Hoping OpenCore might help with everything in order.

X299 OC Formula.jpg

PCIe Slots.png

CPUS.png

GRX Same Slot.png

How to create or modify a simple System SSDT.aml by means of DSDT and IOREG ACPI information – KGP's Hackintosh Corner.zip

 

Shot in the dark but possibly PCIE2 and PCIE6 are on the X299 chipset instead of PCIE bus?

And do any of the PCIE slots share bandwith with other MB features? (M2 slots etc)?

 

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 bufferoverflow
      I've a working Hackintosh but I'm trying to migrate to Opencore. I'm following Vanilla Guide to configure Opencore. I'm able to boot but it fails after entering password for FileVault. Here is the error message and list of file in my Opencore EFI folder. Link to my EFI folder. Help to fix it is appreciated.

       
    • By ChrisWayg
      In Clover there is ForceKextsToLoad. What is the equivalent method in OpenCore?
      I want to force /System/Library/Extensions/IO80211Family.kext to load from S/L/E as it is required by AirPortAtheros40.kext which I am loading via OpenCore, without copying IO80211Family.kext to EFI/OC/Kexts/

      Relevant Specs: Opencore 0.5.4, macOS Mojave 10.14.6, Wifi: TP-Link WDN4800 (AR9380)
    • By n.d.k
      After several weeks of testing OC bootloader,  disecting its source code and also Clover's source code as well, I finally switch from Clover to OC as my main bootloader. Wait! don't get the wrong idea that OpenCore is better than Clover. They both work equally well, producing a bootable macOS as an end result with simliar boot time. OC design direction is different with Clover, I believe it's not intended as a Clover replacement, but more narrowing down to macOS specifically. However, macOS is not the only OS that i am using, so, i decided to add some minimal necessary source code modification to the OC to get some of the features I need. I like to share my customized OC forked https://github.com/n-d-k/OpenCorePkg , you have to compile it yourself if you want, i will not provide pre build binary.    
       
      Additional features/changes:
      ============
       
      [ Multi-Boot ]
        - ACPI patches are optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
        - Booter Quirtks, SMBIOS and Device Properties patches will only applied to macOS.
          
      [ Hotkeys ]
        - Full functional Hotkeys [1-9] corresponding to Boot Entry's Index number and dedicated W (Windows) / X (macOS) keys can be used without seeing Boot Picker.
                
      [ Boot Picker ]
        - Bios Date/time, auto boot to the same OS or manual set to always boot one OS mode, and OC version are displayed in boot picker.
        - Auto boot to previous booted OS (if Misc->Security->AllowSetDefault is NO/false).
        - macOS Recovery/Tools Entries are hidden by default, use Spacebar in Boot Menu as a toggle on/off to show/hide hidden entries.
                
      [ Custom Entries ]
         - Custom entries are now listed first in picker menu and by the orders they are appeared in Misc->Boot->Entries, before all other entries.
         - Individual custom entry can be set hidden using Misc->Entries->Item 0->Hidden (Boolean).
         - Ability to change entry name found by auto scanner by adding custom entry with the exact same device path,
           this will give users the option to complete change how all boot entries listed in Boot Picker.
          
      [ Others ]
         - No verbose apfs.efi driver loading (if using apfs.efi instead of ApfsDriverLoader.efi).
         - Fixed the unmatched 1st and 2nd stages boot Apple logo (* To ensure a match, set Misc->Boot->Resolution to match with one in macOS preferences,
           and to better boot menu text visibility for 4k+ display, set Misc->Boot->ConsoleMode to Max).
          - ndk-macbuild.tool script are set to compile with latest edk2 (One can easily set to stable edk2 if prefer).
          - NvmExpressDxe driver build script are also available for system without native nvme support. (Compatible with OC and Clover).
       
      Usage:
       - To build OpenCore, run "./ndk-macbuild.tool" at Terminal (require Xcode and Xcode Command Line Tool installed, and open xcode to accept license agreement before compiling).
       - To build NvmExpressDxe driver, run "./buildnvme.sh".
       
      * The fix is by setting the screen resolution before starting the apple boot.efi image back to the setting of the Misc->Boot->Resolution, where the setting of Misc->Boot->ConsoleMode doesn't have the same resolution as screen resolution setting.
       
       
       
       
       
       

    • By valueimagery
      Hello,
      I have almost succesfully converted from Clover to OpenCore 0.5.4 following this Vanilla Guide by khronokernel
      https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/
       
      Just an issue with the ethernet intelmausiethernet.kext injecting...
      SOLVED - the sample plist default kernel entry for Ethernet BOOLEAN is NO.  I changed to the kext name correctly, but oversaw to make the simple change to YES!
       
      OC 0.5.4
      OSX 10.15.2
      ASUS Rog Maximus X Code Bios v2203 (uses Intel® I219V)
      i7 8700k w/ AMD RX 580 Sapphire Nitro+ SE
       
      The latest kext is in my EFI/OC/Kexts folder with the other latest kexts that have loaded properly.  It seems to be entered correctly in the config.plist like the other latest kexts.  But the service is inactive and there is no Ethernet connection.  Airport works fine.
       
      I ran kextstat in terminal and could confirm that the kext was not loaded. Nor did en0 report anything with IoRegistryExplorer
      The only way I was able to get ethernet to work was by manually installing the kext into the L/E/ folder via ##### and after reboot.
      I can confirm ethernet is now working and reports as loaded with kextstat, and the device populates in IoRegistryExplorer.
      I know ##### sn't the proper way to install kexts so reaching out for some advice if I've done anything wrong with my config.plist
      Possibly an issue with OC version 0.5.4? I know everything is still BETA.
      Attached is my EFI folder with serial removed
      EFI.zip
×