Jump to content
8755 posts in this topic

Recommended Posts

2 hours ago, NorthAmTrans said:

Im curious here. I use the generic section under Platform Info and everything is fine. Is there an advantage to using the full SMBIOS section instead?

 

OpenCore DataBase is periodically updated, and it relieves you of routine and mistakes.

 

But on models year of the end of production 2011 and older, PlatformInfo necessary to fill manually. It is made not to litter OpenCore library

 

https://docs.google.com/spreadsheets/d/1kGFz3_kp5xCDRRQpfnIUOvbiHXTmxEgyx97u73ImXXE/edit#gid=0

Edited by Andrey1970
  • Like 3
  • Thanks 1

Hi guys,

i'm trying to migrate from clover to opencore but it always hangs during boot (a second or so after selecting the operating system to boot) and i can't understand why.

 

could somebody point me in the right direction ?

I'm attaching my OC folder without the kext folder (all the kext are the same i use in clover and anyway they are up to date to the latest version)

 

 

Thanks

Mattia

 

20191112_174239.jpg

OC.zip

22 hours ago, Andrey1970 said:

 

OpenCore DataBase is periodically updated, and it relieves you of routine and mistakes.

 

But on models year of the end of production 2011 and older, PlatformInfo necessary to fill manually. It is made not to litter OpenCore library

 

https://docs.google.com/spreadsheets/d/1kGFz3_kp5xCDRRQpfnIUOvbiHXTmxEgyx97u73ImXXE/edit#gid=0

 

Big thanks for the info. It inspired me to go back through Platform and fix my ROM string which got rid of my Parse Field 2 error that flashed before Picker showed up. Leaving that bit of obvious info for anyone searching.

Edited by NorthAmTrans
grammar
1 hour ago, NorthAmTrans said:

 

Big thanks for the info. It inspired me to go back through Platform and fix my ROM string which got rid of my Parse Field 2 error that flashed before Picker showed up. Leaving that bit of obvious info for anyone searching.

 

DataBase updated in 0.5.3

Edited by Andrey1970
3 hours ago, Andrey1970 said:

 

Updated in 0.5.3

 

Thats what Im on, it looks like I made a bad copy and paste when moving from Clover to OC, again.

 

Edit: I owe you an apology, I'm on 0.5.2. 

Edited by NorthAmTrans
Was very wrong
On 11/8/2019 at 12:32 AM, Wppley2 said:

When I've installed OpenCore for the first time, I don't disable these two things and was getting the same error that you have, so I disable these but it don't work. I think if you don't disable this on in the first time you configure OpenCore, you need to do all configuration again, from zero point, disabling vault.

Yes I did it but it doesn't worked.

4 hours ago, meaganmargaret said:

@ellybz, and anyone else who is trying to build a custom menu on OpenCore:

 

i have two problems.  The first is I can't boot Linux.

 

This is my path, and its identical to the path in Clover (except for the slashes reversed) and in Clover it works, but in OC, it goes off into space and does not load.  You can see my attached jpg from the Clover boot screen below.  Is it possible this is a video display issue?

 

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x3,0xFFFF,0x0)/HD(1,GPT,F23633BD-5766-4C50-9EC6-5D24425B8542,0x800,0x100000)/\EFI\ubuntu\grubx64.efi

 

The second problem is more basic.  I am loading a scan policy identical to yours, @Ellybz:  2689795.  But below you can see what I get after adding my Entries, 4-7 work just fine, btw.

 

I tried it with Hide Self on and Hide Self off.  Any thoughts?  Would use picker make a difference?

 

1771709650_ScreenShot2019-11-13at2_09_16PM.thumb.png.c93203dbf92398bf3fdd0361ea0de497.png1771709650_ScreenShot2019-11-13at2_09_16PM.thumb.png.c93203dbf92398bf3fdd0361ea0de497.png

Screen Shot 2019-11-13 at 2.42.05 PM.png

 

Curious, what does "Mojave Menu" lead you to?

5 hours ago, meaganmargaret said:

 

 

1771709650_ScreenShot2019-11-13at2_09_16PM.thumb.png.c93203dbf92398bf3fdd0361ea0de497.png1771709650_ScreenShot2019-11-13at2_09_16PM.thumb.png.c93203dbf92398bf3fdd0361ea0de497.png

Screen Shot 2019-11-13 at 2.42.05 PM.png

 

HideSelf =YES
Recovery partitions were deleted thru Terminal:  "Diskutil List" , look for recovery partition then:
Terminal command:  diskutil eraseVolume apfs Blank diskXsY    ( REPLACE X/Y Accordingly )

Step 2:  Delete "Blank" APFS Volume in your Disk utility app.
( There's a faster way to do this, but I like the two step process for my own verification )

Also, for Linux, I have a NTFS Driver in my EFI folder. ( attached below ).

PS: In  Entries Only Windows & Linux path are reported .

Screen Shot 2019-11-13 at 7.59.04 PM.png

NTFS.efi

Edited by Ellybz

I'm a little confused here. After moving the Windows Entry I used in my initial build on clover to my EFI I was able to add a custom entry in OC to point to it's EFI which caused it to show up in Picker. Yay! However when I select it doesn't boot. I've also tried adding the NTFS.efi driver because that makes sense but no dice.

 

So i've removed the windows folder from the EFI and thought maybe I should hop in shell to get device path but selecting shell does the same thing: resets Picker.

 

I've been over the docs but can't quite figure this one out. Has anybody here worked this out and care to share their experience?

Config.plist

 

45 minutes ago, NorthAmTrans said:

I'm a little confused here. After moving the Windows Entry I used in my initial build on clover to my EFI I was able to add a custom entry in OC to point to it's EFI which caused it to show up in Picker. Yay! However when I select it doesn't boot. I've also tried adding the NTFS.efi driver because that makes sense but no dice.

 

So i've removed the windows folder from the EFI and thought maybe I should hop in shell to get device path but selecting shell does the same thing: resets Picker.

 

I've been over the docs but can't quite figure this one out. Has anybody here worked this out and care to share their experience?

Config.plist

 

 

Finding the correct path in Custom Entries have been already explained several times within the last few pages of this thread. It should start with " PciRoot". 

 

 

Edited by Ellybz
  • Like 1
14 minutes ago, Ellybz said:

 

Finding the correct path in Custom Entries have been already explained several times within the last few pages of this thread. It should start with " PciRoot". 

 

For sure it has and thanks for the link. I think i've the gotten right path. Im confused however on why when I select Shell in Picker it doesn't load. I'll keep digging.

EDIT: Ignore this. I should probably umm place Shell in the tools folder.

Edited by NorthAmTrans

Could you please provide an example for CPU emulation (fake CPUID) for pentium CPUs. We normally use 0x0306A0 (Ivy Bridge i5) as a fake ID. This would be really helpful in the description below. Also, NullCPUPowerManagementkext is often needed do you know if it's compatible?

Edited by mashuk12

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?

well, I have some problem here, 

I'm using z390 aorus master with i9-9900k, and installed with a titan-ridge thunderbolt card, and oc runs perfectly, and yesterday, I found giga-byte released a F10 bios for this board, then I decided to upgrade, and after upgrade, I can no longer use oc, 

 

It always tells me that error allocating pages, so I followed a guide here, and go to discord, the bot help me calculated the slide should be 196, then I set the slide=196 in boot-args, but I still can not boot.

 

After slide=196, I can see the apple logo, then few seconds, oc told me there is a fatal error, system hang for 10 seconds. (tried with or without any ssdt patch, result are same)

 

so what should I do to use oc with new version of bios? 

 

I've attached these files hoping someone can help me.

 

Thanks.

memmap.txt

opencore-2019-11-15-165352.txt

oc.zip

1 hour ago, mashuk12 said:

Could you please provide an example for CPU emulation (fake CPUID) for pentium CPUs. We normally use 0x0306A0 (Ivy Bridge i5) as a fake ID. This would be really helpful in the description below. Also, NullCPUPowerManagementkext is often needed do you know if it's compatible?

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.

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

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

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.

×
×
  • Create New...