Jump to content

3,197 posts in this topic

Recommended Posts

Ugh, of course I meant RequestBootVarFallback. RequestBootVarRouting is needed on all hacks with OpenCore for default boot volume selection to work. Anyway, I guess, we will try to explore this issue and let you know if we find anything.

Share this post


Link to post
Share on other sites
Advertisement
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
"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

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 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.
        - While in boot picker, F10 can use to take a snapshot of the screen.
                
      [ Ui 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.
         - 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).
          - 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".
       
      4k screen resolutions

       
       

       
      Customized by @btwise

       
       
       
    • By SniperBuddy
      Hello guys,
      I'm relatively new to the world of hackintosh.
      I'm trying to install the latest Mac OS - Catalina with the help of Opencore, however, this is the error that's displayed while booting from the USB:
       
      https://drive.google.com/open?id=1Xd4V2wZ2fEsgRyfVcXlJHXMPGa85g2s3
       
      You can take a look at my config.plist file from here - https://drive.google.com/file/d/17FZpTcVp4RFSaxdm6yW4uELkt7MaLdmt/view?usp=sharing
       
      I'm using the Acer E575 G laptop with Kabylake (i5 7200u)
       
      Any help would be gladly appreciated!
       
       
       
       
    • By Krani93
      Hi guys,
       
      I'm trying to install Catalina on a Lenovo m720q (i5-8600T with B360).
      After some other issues I'm know stuck at attached screen.
      Im using latest opencore version and have my EFI folder attached.
       
      Can someone help me I've got no clue what to try next :/ 
       
       
      Cheers!

      EFI.7z
    • By BlitzPanzer
      Catalina 10.15.3, OC 0.5.5

      Follow the OpenCore AMD Vanilla Guide, everything works fine iMessage, Siri, FaceTime, Continuity, Airdrop, Audio, WiFi
      But here is the problem
      Once I restart or shutdown and reboot, I will have kernel panic, so i have to reboot once again, then no more kernel panic, straight back to the system.
      Down below are the 3 kernel panic reports I got after I am back to the system, also provided specs, kexts, drivers and config.plist I used.
      Please someone help me with the problem
      Thanks in advanced   

      System Specs
      CPU: Ryzen R5 3600
      MOBO: MSI B450 Mortar Max
      RAM: Kingston HyperX Fury 16GB*2 3200MHz DDR4
      SSD: Kingston A2000 500GB NVMe PCIe
      GPU: Gigabyte RX 570 Gaming 4G v2.0
      PCIe: BCM943602CS Kexts:
      AppleALC
      AppleMCEReporterDisabler
      BrcmBluetoothInjector
      BrcmPatchRAM3
      HDMIAudio
      Lilu
      MacProMemoryNotificationDisabler
      NightShiftUnlocker
      NVMeFix
      RealtekRTL8111
      VirtualSMC
      WhateverGreen Drivers:
      ApfsDriverLoader
      AppleUsbKbDxe
      FwRuntimeServices
      VBoxHfs config.plist:
      https://drive.google.com/file/d/1M22Tvn7W-Zf_b_-J52oLcfjECj5qAcp6/view

      Kernel Panic Report 1
      panic(cpu 0 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9f212fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffffa3ce87c000, CR3: 0x00000000263ba000, CR4: 0x00000000003406e0 RAX: 0xffffffa3ce87c000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffffa3ce75bb60, RBP: 0xffffffa3ce75bb80, RSI: 0xffffff806d3141c0, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805cc7c900, R13: 0xffffff835806f000, R14: 0x0000000000000000, R15: 0xffffff8068d2da50 RFL: 0x0000000000010246, RIP: 0xffffff7f9f212fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffffa3ce87c000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffffa3ce75b5c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffffa3ce75b610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffffa3ce75b650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffffa3ce75b6a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75b6c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffffa3ce75b7c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffffa3ce75b810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffffa3ce75b880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffffa3ce75ba00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffffa3ce75ba50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75ba70 : 0xffffff7f9f212fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffffa3ce75bb80 : 0xffffff7f9f24a795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffffa3ce75bba0 : 0xffffff7f9f212ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffffa3ce75bbe0 : 0xffffff7f9f2325c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffffa3ce75bc30 : 0xffffff7f9f1b8adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffffa3ce75bc70 : 0xffffff7f9f1b64be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffffa3ce75bd00 : 0xffffff7f9f128534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffffa3ce75bd80 : 0xffffff7f9f1b488e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffffa3ce75bde0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffffa3ce75be40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffffa3ce75bef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffffa3ce75bf50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffffa3ce75bfa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000->0xffffff7f9f1b2fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c185000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c228000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9f1b3000->0xffffff7f9f6f7fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 47565362999  
      Kernel Panic Report 2
      panic(cpu 10 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9e629fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d25d2000, CR3: 0x0000000029068000, CR4: 0x00000000003406e0 RAX: 0xffffff83d25d2000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d14c3b60, RBP: 0xffffff83d14c3b80, RSI: 0xffffff805f6adb80, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805fba2580, R13: 0xffffff835b02e000, R14: 0x0000000000000000, R15: 0xffffff80631191e0 RFL: 0x0000000000010246, RIP: 0xffffff7f9e629fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff83d25d2000, Error code: 0x0000000000000002, Fault CPU: 0xa, PL: 0, VF: 1 Backtrace (CPU 10), Frame : Return Address 0xffffff83d14c35c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d14c3610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d14c3650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d14c36a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c36c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d14c37c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d14c3810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffff83d14c3880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d14c3a00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d14c3a50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c3a70 : 0xffffff7f9e629fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d14c3b80 : 0xffffff7f9e661795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d14c3ba0 : 0xffffff7f9e629ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d14c3be0 : 0xffffff7f9e6495c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d14c3c30 : 0xffffff7f9e5cfadb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d14c3c70 : 0xffffff7f9e5cd4be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d14c3d00 : 0xffffff7f9e52a534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d14c3d80 : 0xffffff7f9e5cb88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d14c3de0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d14c3e40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d14c3ef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d14c3f50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d14c3fa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000->0xffffff7f9e5b5fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c3f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c09f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9e5ca000->0xffffff7f9eb0efff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 38416992755  
      Kernel Panic Report 3
      panic(cpu 8 caller 0xffffff801da652fa): Kernel trap at 0xffffff7fa084dfe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d44cd000, CR3: 0x000000002b260000, CR4: 0x00000000003406e0 RAX: 0xffffff83d44cd000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d319bb60, RBP: 0xffffff83d319bb80, RSI: 0xffffff8066659c00, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff8061f35280, R13: 0xffffff835d231000, R14: 0x0000000000000000, R15: 0xffffff806189db90 RFL: 0x0000000000010246, RIP: 0xffffff7fa084dfe3, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0xffffff83d44cd000, Error code: 0x0000000000000002, Fault CPU: 0x8, PL: 0, VF: 1 Backtrace (CPU 8), Frame : Return Address 0xffffff83d319b5c0 : 0xffffff801d93bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d319b610 : 0xffffff801da734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d319b650 : 0xffffff801da64f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d319b6a0 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319b6c0 : 0xffffff801d93b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d319b7c0 : 0xffffff801d93b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d319b810 : 0xffffff801e0d2aa9 mach_kernel : _panic + 0x61 0xffffff83d319b880 : 0xffffff801da652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d319ba00 : 0xffffff801da64ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d319ba50 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319ba70 : 0xffffff7fa084dfe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d319bb80 : 0xffffff7fa0885795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d319bba0 : 0xffffff7fa084def0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d319bbe0 : 0xffffff7fa086d5c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d319bc30 : 0xffffff7fa07f3adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d319bc70 : 0xffffff7fa07f14be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d319bd00 : 0xffffff7fa074e534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d319bd80 : 0xffffff7fa07ef88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d319bde0 : 0xffffff801e01b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d319be40 : 0xffffff801e01adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d319bef0 : 0xffffff801e01a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d319bf50 : 0xffffff801e01c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d319bfa0 : 0xffffff801d8e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000->0xffffff7fa07d9fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9e5f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9e29f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7fa07ee000->0xffffff7fa0d32fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001d600000 Kernel text base: 0xffffff801d800000 __HIB text base: 0xffffff801d700000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 27776834167  
      config.plist
    • By Trung_Nguyen
      Hi, I'm using a Dell laptop, modeled Latitude E6230, bios version A11(I don't have any batteries to update :'( ).
      I'm using Catalina with OpenCore boot loader. 
      Everything is good, fast boot time.
      But when comes to sleeping there's 2 issues that randomly happen when the sleeping time is long enough:
      - Kernel Panic when sleep: panic log: panic
         This should have something to do with bluetooth, right? I'm using DW380 with BrcmPatchRam3 & BrcmBluetoothInjector.
      - Darkscreen when wakeup:
         After I open the lid, the screen have no backlight, although the UI barely shown.
         All I could do is to use keyboard to enter my password and use hotkey to shutdown the machine and then restart normally.
       
      The EFI/OC folder is attached below, with serial numbers removed.
      Sorry for using .txz format but with .zip, I couldn't get it fit in 10MB. Sorry for any inconvenience.
       
      P/s:If anybody try boot this in the future, please bear in mind that if you inject IO80211Family and AirportBrcm4331 (the one from 10.14.6) to any Recovery or installation media, it will panic the kernel, please disable those 2 before-hand.
       
      Thank you very much
       
      OC.txz
×