OpenCore General Discussion

[hardcorehenry]

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

[zzz3z]

12 minutes ago, ctich said:

Show you EFI.

Opencore-config.plist

CLOVER-config.plist

OC.zip

Edited November 16, 2019 by zzz3z

[Matgen84]

4 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

 

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.

[ctich]

2 hours ago, zzz3z said:

Opencore-config.plist

CLOVER-config.plist

OC.zip

replace and check

OC-2.zip

[zzz3z]

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

 

Edited November 16, 2019 by zzz3z

[ctich]

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 

[zzz3z]

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 November 16, 2019 by zzz3z

[obus]

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-

[mashuk12]

23 hours ago, hardcorehenry said:

Try:

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

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

[Andres ZeroCross]

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

[Andrey1970]

3 hours ago, zzz3z said:

Reboot to clover, and press F11 to clean NVRM,

 

Set AllowNvramReset=Yes

And look OC menu.)

[hardcorehenry]

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 November 17, 2019 by hardcorehenry

[mashuk12]

7 hours ago, hardcorehenry said:

 

Error caused by wrong CPUID 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

see this problem

[UefiBooter]

don't use these tools that are outdated, read the Configuration pdf and tailor each option to your needs....

 

There are no quick routes.

[STLVNUB]

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.

[mhaeuser]

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

[zzz3z]

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

[startergo]

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:

 

[justin]

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

 

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:

 

 

 

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

 

Edited November 17, 2019 by justin

[Matgen84]

10 minutes ago, justin said:

 

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

 

It's exactly what I says to @nmano Despite of that OC Builder is useful for those how need complete EFI structure. Right. 

Edited November 17, 2019 by Matgen84

[justin]

4 minutes ago, Matgen84 said:

 

It's exactly what I says to @nmano Despite of that OC Builder is useful for those how need complete EFI structure. Right. 

 

No, third party tools are not needed to complete the EFI structure, the EFI structure is already in the Docs/Configuration.pdf , just click the mouse in Finder or hit the keyboard in Terminal.app

 

i'm just so amazed people do not want to read such a piece of detailed document, READING THE OFFICIAL DOC is the simplest method to get OpenCore running.  

Edited November 17, 2019 by justin

[Andres ZeroCross]

Best OC Configurator is "PlistEdit Pro.app" 

[Matgen84]

10 minutes ago, justin said:

 

No, third party tools are not needed to complete the EFI structure, the EFI structure is already in the Docs/Configuration.pdf , just click the mouse in Finder or hit the keyboard in Terminal.app

 

Keep cool  The EFI structure is already in the Docs, I know. OC Builder is also compiling all necessary efi and kexts, all in one. I don't use it.

 

Let users choosing by themself, is also a good idea 

 

@Andres ZeroCross Right.

Edited November 17, 2019 by Matgen84

[startergo]

35 minutes ago, justin said:

 

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

 

 

 

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

 

 

 

 

 

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

 

[Slice]

Choose iMac13,2 instead of MacPro5,1