Jump to content

OpenCore General Discussion


dgsga
8,887 posts in this topic

Recommended Posts

hello everyone: I can boot my system with clover perfectly. When I move from clover to opencore 0.53. I  can boot OSX Mojave 10.14.6 without inject Graphics card. When I inject Graphics card, it can't  boot. where is wrong.

my inject  Properties is same as clover.

picture.thumb.png.6f21ed712519e4dae1b2e377375fba93.png config.plist

 

    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>BQClPg==</data>
                <key>AAPL,slot-name</key>
                <string>Internal</string>
                <key>device-id</key>
                <data>pT4AAA==</data>
                <key>device_type</key>
                <string>VGA compatible controller</string>
                <key>disable-external-gpu</key>
                <data>AQAAAA==</data>
                <key>enable-hdmi20</key>
                <data>AQAAAA==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>model</key>
                <string>UHD620 as Iris+ 655 - (for DVMT=64M, 4K)</string>
            </dict>            
        </dict>
        <key>Block</key>
        <dict/>
    </dict>

 

panic info is

 

*** Panic Report ***

panic(cpu 3 caller 0xffffff8009c689ca): Kernel trap at 0xffffff800a23f4e8, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000001f5e0000, CR4: 0x00000000003626e0

RAX: 0x0000000000000000, RBX: 0xffffff8031a70e60, RCX: 0x0000000000000000, RDX: 0x0000000000000000

RSP: 0xffffff812d3cbc60, RBP: 0xffffff812d3cbc80, RSI: 0x0000000000000000, RDI: 0xffffff8031a70eb0

R8:  0x0000000000000000, R9:  0x0000000000000000, R10: 0x000000807fffefff, R11: 0x0000000000000010

R12: 0x00000000e00002c7, R13: 0x0000000000000000, R14: 0xffffff8031a70eb0, R15: 0x0000000000000000

RFL: 0x0000000000010246, RIP: 0xffffff800a23f4e8, CS:  0x0000000000000008, SS:  0x0000000000000000

Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1

 

Backtrace (CPU 3), Frame : Return Address

0xffffff812d3cb6c0 : 0xffffff8009b3f98b

0xffffff812d3cb710 : 0xffffff8009c76c15

0xffffff812d3cb750 : 0xffffff8009c6861e

0xffffff812d3cb7a0 : 0xffffff8009ae6a40

0xffffff812d3cb7c0 : 0xffffff8009b3f077

0xffffff812d3cb8c0 : 0xffffff8009b3f45b

0xffffff812d3cb910 : 0xffffff800a2d2d89

0xffffff812d3cb980 : 0xffffff8009c689ca

0xffffff812d3cbb00 : 0xffffff8009c686c8

0xffffff812d3cbb50 : 0xffffff8009ae6a40

0xffffff812d3cbb70 : 0xffffff800a23f4e8

0xffffff812d3cbc80 : 0xffffff800a242d78

0xffffff812d3cbce0 : 0xffffff7f8d2b74fa

0xffffff812d3cbd20 : 0xffffff7f8d28254d

0xffffff812d3cbd50 : 0xffffff7f8d27de51

0xffffff812d3cbde0 : 0xffffff800a21ba16

0xffffff812d3cbe40 : 0xffffff800a21b5c1

0xffffff812d3cbef0 : 0xffffff800a21a90e

0xffffff812d3cbf50 : 0xffffff800a21d0ad

0xffffff812d3cbfa0 : 0xffffff8009ae613e

      Kernel Extensions in backtrace:

         com.apple.driver.AppleIntelCFLGraphicsFramebuffer(14.0)[CE2A5F06-6FEA-3C66-BB20-088ADC9A0EC7]@0xffffff7f8d24f000->0xffffff7f8d479fff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[E6E855AD-A5B2-3518-A997-1384B4360708]@0xffffff7f8a8a1000

            dependency: com.apple.iokit.IOACPIFamily(1.4)[9BA2613C-A129-3EDD-8DC1-2CFF6B62B832]@0xffffff7f8a88f000

            dependency: com.apple.iokit.IOAcceleratorFamily2(438.1.23)[95FE222A-D225-3208-87A9-C2691A025BE7]@0xffffff7f8c911000

            dependency: com.apple.iokit.IOReportFamily(47)[0CAFCFA4-9263-3847-8ED0-1867D214CDD7]@0xffffff7f8a49f000

            dependency: com.apple.AppleGraphicsDeviceControl(4.1.46)[0266F94C-3545-376D-AF0F-802F6D340F1C]@0xffffff7f8bc87000

            dependency: com.apple.iokit.IOGraphicsFamily(558.3)[23A17FD4-B8DA-3D9D-8AC5-D05039DF41ED]@0xffffff7f8b943000

 

BSD process name corresponding to current thread: kernel_task

 

Mac OS version:

19A602

 

Kernel version:

Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64

Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160

Kernel slide:     0x0000000009800000

Kernel text base: 0xffffff8009a00000

__HIB  text base: 0xffffff8009900000

System model name: MacBookPro15,2 (Mac-827FB448E656EC26)

System shutdown begun: NO

Panic diags file available: YES (0x0)

 

System uptime in nanoseconds: 4177242490

last loaded kext at 4160204600: com.apple.driver.AppleGraphicsDevicePolicy 4.1.46 (addr 0xffffff7f8bc9a000, size 86016)

loaded kexts:

org.rehabman.voodoo.driver.PS2Keyboard

Link to comment
Share on other sites

1 hour ago, zzz3z said:

@ctich

I add Framebuffer patches stolenmem,fbmem,cursormemm unifiedmem to config.plist.   It's same problem. Panic at com.apple.driver.AppleIntelCFLGraphicsFramebuffer with error "page fault" 

Show you EFI.

Link to comment
Share on other sites

3 hours ago, nmano said:

Thanks for Team.

How to fix this?

Build Failed

 

/Users/x99/Desktop/opencore/OpenCorePkg-master/build.sh: line 2: edksetup.sh: No such file or directory

/Users/x99/Desktop/opencore/OpenCorePkg-master/build.sh: line 3: build: command not found

Command ExternalBuildToolExecution failed with a nonzero exit code

 

@nmano the easiest way: download OpenCorePkg and double click macbuild.tool

  • Like 1
Link to comment
Share on other sites

4 hours ago, nmano said:

Thanks for Team.

How to fix this?

Build Failed

164863578_ScreenShot2019-11-16at4_39_18AM.thumb.png.04c16aa9a62f30150b18a4c4c8668720.png

/Users/x99/Desktop/opencore/OpenCorePkg-master/build.sh: line 2: edksetup.sh: No such file or directory

/Users/x99/Desktop/opencore/OpenCorePkg-master/build.sh: line 3: build: command not found

Command ExternalBuildToolExecution failed with a nonzero exit code

 

Do you try to use macbuild.tool in Opencore directory instead of Xcode directly. Just my opinion. Or the best, Pavo's tool: OC Builder in Github.

  • Like 2
Link to comment
Share on other sites

51 minutes ago, ctich said:

replace and check

OC-2.zip

Thank you @ctich 

it‘s still same problem。

Add some info,my laptop's screen resolution is  3000X2000; DVMT prealloc had changed to 64M.

My step is:1. exact your oc-2.zip to my EFI directory. 2. Reboot to clover, and press F11 to clean NVRM, 3.boot use OC. Kernel_2019-11-16-232127_zzz3zdeMacBook-Pro.panic

 

panic.thumb.jpg.5959d394a9b2dc6bc1a78bce97b216b8.jpg

Edited by zzz3z
Link to comment
Share on other sites

30 minutes ago, zzz3z said:

Thank you @ctich 

it‘s still same problem。

Add some info,my laptop's screen resolution is  3000X2000; DVMT prealloc had changed to 64M.

My step is:1. exact your oc-2.zip to my EFI directory. 2. Reboot to clover, and press F11 to clean NVRM, 3.boot use OC. Kernel_2019-11-16-232127_zzz3zdeMacBook-Pro.panic

 

 

try replacing 0500A53E with 0900A53E 

Link to comment
Share on other sites

21 minutes ago, ctich said:

try replacing 0500A53E with 0900A53E 

it's  same.

I remember stolenmem problem error is divided zero,not "page fault"

I think my config 's Properties is no problem,because it's ok in clover. 

whatever green is laster version.

I think I can rollback to open core 0.5.1, whatervegreen to 1.3.3, and test again

Edited by zzz3z
Link to comment
Share on other sites

On 10/16/2019 at 4:31 PM, Download-Fritz said:

Infact, it is a "problem" with the HP firmware. If it's not a literal bug, it's an unexpected state, because the only other person to ever report similar behaviour experienced it on a HP laptop as well. It's not impossible it's a problem with OC, if you want to test further, load the drivers from Shell and run "reconnect -r" before launching OC... it might work if you exit Shell again from within OC too, but not sure

Thank you devs. The key UnblockFsConnect set to true/YES solved my problems with "OcScanForBootEntries not found" on my HP 840 G1.

Now I can boot Catalina on my HP with OC-:hysterical:

Link to comment
Share on other sites

23 hours ago, hardcorehenry said:

Try:a9.png.b5f0065c1e7800651a261a8dbcbf12d6.png


Cpuid1Data: <A9 06 03 00 00 00 00 00 00 00 00 00 00 00 00 00>
Cpuid1Mask: <FF FF FF FF 00 00 00 00 00 00 00 00 00 00 00 00>

or

a0.png.3e789c835863b4f7b3d704186a7a0988.png


Cpuid1Data: <A0 06 03 00 00 00 00 00 00 00 00 00 00 00 00 00>
Cpuid1Mask: <FF FF FF FF 00 00 00 00 00 00 00 00 00 00 00 00>

You can find out more here.

try this method but stuck at black screen

Link to comment
Share on other sites

2 hours ago, zzz3z said:

it's  same.

I remember stolenmem problem error is divided zero,not "page fault"

I think my config 's Properties is no problem,because it's ok in clover. 

whatever green is laster version.

I think I can rollback to open core 0.5.1, whatervegreen to 1.3.3, and test again

 

Replace your OC's config.plist with this,, post the result

config.plist

  • Like 1
Link to comment
Share on other sites

18 hours ago, mashuk12 said:

try this method but stuck at black screen

 

Error caused by wrong FAKECPUID or even lack of it, doesn't manifest itself with black screen. You may need to enable: UEFI>Protocols>ConsoleControl=YES and UEFI>Quirks>ProvideConsoleGop=YES

Edited by hardcorehenry
Link to comment
Share on other sites

Maybe OC developers should work in more closely with OC-Configurator developer so that they are both on the same page.

All very well reading Config PDF and adjusting your config.plist every 5 seconds, but its not very practical IMHO.

 I use Clover till the mess gets sorted out, and then probably still use it.

  • Like 2
Link to comment
Share on other sites

I'm sorry, but the OC approach is the literal opposite of a mess. Every purpose has exactly one property and every defined property has exactly one type (certain user-dictated data like NVRAM variables and device properties are more permissive for obvious reasons). A mess is what you get when you *do* provide backwards-compatibility, because then you have multiple fields serving a similar purpose and there is no obvious guideline on which to use and potentially what type they should have. A mess is when you provide an installer utility that tries to be forwards-migrating to a new directory structure but it just wipes the previously present files - if you automate, it must be pitch-perfect.

Hence, for the current situation, we do not see a benefit but a risk in automation. There is one release every month, I think checking Differences.pdf every bit more than 4 weeks during pre-release stage is not terrible.

 

We reached out to all configurator devs several times in the past, I don't know what you expect: https://github.com/acidanthera/bugtracker/issues/330

  • Like 5
Link to comment
Share on other sites

17 hours ago, Andres ZeroCross said:

 

Replace your OC's config.plist with this,, post the result

config.plist

 

16 hours ago, Andrey1970 said:

 

Set AllowNvramReset=Yes

And look OC menu.)

I use this config.plistv and  remove all other kexts, only user virtualsmc,lilu,whatevergreen. It's still error same.

I give up use opencore 0.5.2, and wait for next version.

 Maybe  I should test with OSX 10.15.

 

 

 

Sun Nov 17 11:21:40 2019

 

*** Panic Report ***

panic(cpu 0 caller 0xffffff80010dbadd): Kernel trap at 0xffffff8001656128, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000016749000, CR4: 0x00000000003626e0

RAX: 0x0000000000000000, RBX: 0xffffff8026aacbe0, RCX: 0x0000000000000000, RDX: 0x0000000000000000

RSP: 0xffffff8123223cb0, RBP: 0xffffff8123223cd0, RSI: 0x0000000000000000, RDI: 0xffffff8026aac4b0

R8:  0x0000000000000000, R9:  0x0000000000000000, R10: 0xffffff80018a3d98, R11: 0x0000000000000013

R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffff8026aac4b0, R15: 0x00000000e00002c7

RFL: 0x0000000000010246, RIP: 0xffffff8001656128, CS:  0x0000000000000008, SS:  0x0000000000000000

Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

 

Backtrace (CPU 0), Frame : Return Address

0xffffff8123223780 : 0xffffff8000fae6ed

0xffffff81232237d0 : 0xffffff80010ea185

0xffffff8123223810 : 0xffffff80010db8ba

0xffffff8123223880 : 0xffffff8000f5bb40

0xffffff81232238a0 : 0xffffff8000fae107

0xffffff81232239c0 : 0xffffff8000fadf53

0xffffff8123223a30 : 0xffffff80010dbadd

0xffffff8123223ba0 : 0xffffff8000f5bb40

0xffffff8123223bc0 : 0xffffff8001656128

0xffffff8123223cd0 : 0xffffff800165a908

0xffffff8123223d40 : 0xffffff7f8490377d

0xffffff8123223d80 : 0xffffff7f848cee8b

0xffffff8123223db0 : 0xffffff7f848ca8b0

0xffffff8123223e40 : 0xffffff80016300bb

0xffffff8123223e80 : 0xffffff800162fd75

0xffffff8123223f00 : 0xffffff800162f337

0xffffff8123223f50 : 0xffffff8001630e26

0xffffff8123223fa0 : 0xffffff8000f5b0ce

      Kernel Extensions in backtrace:

         com.apple.driver.AppleIntelCFLGraphicsFramebuffer(12.1)[8F1CB930-AD11-33C9-83AB-440851B20088]@0xffffff7f8489d000->0xffffff7f84ac4fff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[BFDEB8D4-50FE-3DDB-87B7-F6A504393830]@0xffffff7f81895000

            dependency: com.apple.iokit.IOACPIFamily(1.4)[3E8E9870-2E41-33F6-ACBF-35DDC08F22B5]@0xffffff7f81ecd000

            dependency: com.apple.iokit.IOAcceleratorFamily2(404.14)[618B24B5-1387-31FD-A7F7-53283E2C3FEA]@0xffffff7f83f90000

            dependency: com.apple.iokit.IOReportFamily(47)[0BC9F93B-456A-3D97-BE4C-69DCBB5E8A3C]@0xffffff7f83205000

            dependency: com.apple.AppleGraphicsDeviceControl(3.50.12)[5334847D-B612-3E8C-88A3-C2A5853675CD]@0xffffff7f83178000

            dependency: com.apple.iokit.IOGraphicsFamily(530.66)[373EAB85-2C5F-3B84-B86D-421F79C47DF2]@0xffffff7f82e31000

Link to comment
Share on other sites

On 11/15/2019 at 11:53 AM, startergo said:

I am testing OC on cMP5.1 so I don't need full blown SMBIOS, NVRAM and HUB values. I only updated the board ID to iMacPro and updated only SMBIOS.

In Mojave that worked fine, but when I changed the startup disk to Catalina the boot process stalled with:

waiting for an external debugger...

All debug options have 0 values, so I had to remove the USB with OC and boot without it and remove the board ID injection. 

What instigates the wait for an external debugger?

To be more precise there is actually kernel panic which calls for a debugger on Cat 10.15.1 only:

image.thumb.png.0820f4f9f706b93f0c88c99ad6741124.png

 

Link to comment
Share on other sites

On 11/16/2019 at 10:33 PM, Matgen84 said:

 

Do you try to use macbuild.tool in Opencore directory instead of Xcode directly. Just my opinion. Or the best, Pavo's tool: OC Builder in Github.

 

@vit9696 wrote a perfect macbuild.tool for building OpenCorePkg/AppleSupportPkg, why the heck do you need another one? 

 

 

9 hours ago, mashuk12 said:

see this problem

Screen Shot 2019-11-17 at 1.40.01 PM.png

Screen Shot 2019-11-17 at 1.45.51 PM.png

 

Do not use this TOOL, READ THE F**** OFFICIAL MANUAL. 

 

 

 

51 minutes ago, startergo said:

To be more precise there is actually kernel panic which calls for a debugger on Cat 10.15.1 only:

image.thumb.png.0820f4f9f706b93f0c88c99ad6741124.png

 

 

 

You need to set PanicNoKextDump=YES/True to see the actual panic reason (aka backtrace), try it and post a new photo. 

 

Edited by justin
Link to comment
Share on other sites

×
×
  • Create New...