Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

pinoli
pinoli
Posted
Posted
2 hours ago, Andres ZeroCross said:


Too many acpi error about RP05.PXSX, RP09.PXSX and RP08.PXSX, It's look you have used SSDT hot Patch with acpi renaming in Clover's config.plist.

Avoid ACPI renaming. Just do it in single DSDT without hotpatch if you don't understand how to renaming acpi with OC's config.plist

sorry @Andres ZeroCross I just read your message.

It's not really clear, I don't understand where I am renaming ACPI in my OC config.plist.

I use a custom SSDT-UCIA-ALL.asl for USB mapping and no USBInjectAll.kext.

I also tried to disable my custom SSDT, install USBInjectAll.kext and use the XHCILimitPort quirk in OC, but still getting the same error: I won't get past this point.

 

Worth mentioning: I have CSM and VT-d disabled in BIOS.

thanks

1 minute ago, yobro said:

 

This could be the same error as I was seeing earlier today after updating my BIOS, you can try setting System Time and Alarm Source to Legacy RTC in BIOS instead of whatever the default is.  

I will try thanks

karacho
karacho
Posted
Posted (edited)

Running OC_EFI_Maker right now and get that's on the pic. Catalina GM is out. Can anyone just give a short info about the Release of OC as @vit9696 statet in Bugtracker there -> https://github.com/acidanthera/bugtracker/issues/486 Is it still Beta?

 

Greetz

 

 

Bildschirmfoto 2019-10-05 um 21.21.52.png

Edited by karacho_ak
  • Like 1
STLVNUB
STLVNUB
Posted
Posted
4 hours ago, Andres ZeroCross said:


I thought VariableRuntimeDxe.efi is depecreated in newest version of OpenCore (AppleSupportPk's driver)

That may be the case but system works 100% with it.

  • Like 1
duffs
duffs
Posted
Posted

When installing catalina i got error "an error occurred while verifying firmware" it turns out that my FirmwareFeatures ported from clover was wrong. Fixing that, install went thru just fine. Used one from sample.plis.

 

 

Missing some functionality from clover like "lastbootedvolume". When installing Macos on reboot  clover automatically selected "macOS installer" and continue installing. does this work?

optysite
optysite
Posted
Posted
1 hour ago, droples said:

k.thumb.png.3004a4f9daf4c0f6f50681b0836d0661.png

Sample.plist.zip

Thats what I originally started with, Im not sure what you are trying to point out. I had even more "max/min kernel at # index" errors than when I went in and changed them all to Matchkernel instead. Still didn't fix the issue. And I know this is a dumb question but does it matter whether is it True/False vs No/Yes? My editor is in true/false.

Matgen84
Matgen84
Posted
Posted
1 hour ago, optysite said:

Thats what I originally started with, Im not sure what you are trying to point out. I had even more "max/min kernel at # index" errors than when I went in and changed them all to Matchkernel instead. Still didn't fix the issue. And I know this is a dumb question but does it matter whether is it True/False vs No/Yes? My editor is in true/false.

 

You have to use <string> instead of <boolean>. Boolean requires true or false (Yes/No). In Sample.plist, MaxKernel/MinKernel are empty.

optysite
optysite
Posted
Posted (edited)
24 minutes ago, Matgen84 said:

 

You have to use <string> instead of <boolean>. Boolean requires true or false (Yes/No). In Sample.plist, MaxKernel/MinKernel are empty.

I must have something else in my EFI causes problems then, because even with Max/Min strings empty (followed both the vanilla guide for CoffeeLake and open core beginners guides. I have everything setup according to their guides and I have a decent idea of what kexts and drivers I need as my hackintosh boots now with clover. I added the DSDT for my motherboard. And to clarify, Im trying to boot OpenCore from a USB, clover is on my SSD. That should cause a problem cuz Im not booting from it right?

 

I don't know enough to know what I don't know... if that makes sense. 

IMG_7535.JPG

Edited by optysite
Matgen84
Matgen84
Posted
Posted (edited)
5 hours ago, optysite said:

I must have something else in my EFI causes problems then, because even with Max/Min strings empty (followed both the vanilla guide for CoffeeLake and open core beginners guides. I have everything setup according to their guides and I have a decent idea of what kexts and drivers I need as my hackintosh boots now with clover. I added the DSDT for my motherboard. And to clarify, Im trying to boot OpenCore from a USB, clover is on my SSD. That should cause a problem cuz Im not booting from it right?

 

I don't know enough to know what I don't know... if that makes sense. 

IMG_7535.JPG

 

I'm not a OC expert and my knowledge is limited.

 

OCS: No Schema... seems to be "warning" based on the comments posted on this topic. Create/Edit your config.plist with PlistEdit Pro.

 

Your AptiomemoryFix isn't in Drivers folder.... OC cannot found

 

EDIT: AptioMemoryFix.efi is no longer maintained. See Differences.pdf page 48: how to migrate

 

Edited by Matgen84
Pavo
Pavo
Posted
Posted
5 hours ago, optysite said:

I must have something else in my EFI causes problems then, because even with Max/Min strings empty (followed both the vanilla guide for CoffeeLake and open core beginners guides. I have everything setup according to their guides and I have a decent idea of what kexts and drivers I need as my hackintosh boots now with clover. I added the DSDT for my motherboard. And to clarify, Im trying to boot OpenCore from a USB, clover is on my SSD. That should cause a problem cuz Im not booting from it right?

 

I don't know enough to know what I don't know... if that makes sense. 

IMG_7535.JPG

No schema means you have something left blank when something should be filled in. You also are missing AptioMemoryFix.efi in your Drivers folder it looks like.

  • Like 1
Guest
Guest
Posted
Posted (edited)

@optysite

MaxKernel and MinKernel are new voices in new OC bootloader (see latest differences.pdf)

AptioMemoryFix should be deprecated I think..so you have to clean your config and to decide which OC versions you want to use 

 

Edited by Guest
Sniki
Sniki
Posted
Posted (edited)

Hi Open Core team or anyone else that can help

 

Im trying to do a clean install on my Lenovo ThinkPad X240.

I did create the Catalina USB Installer but it is not showing on the OC Picker.

 

I don't understand this part very well:

  1. Quote

    What is the simplest way to install macOS?

    Copy online recovery image (*.dmg and *.chunklist files) to com.apple.recovery.boot directory on a FAT32 partition with OpenCore. Load OpenCore Boot Picker and choose the entry, it will have a (dmg) suffix. Custom name may be created by providing .contentDetails file.

     

I attached the EFI folder so maybe someone can point me where the problem is.

Where is tha com.apple.recovery.boot directory supposed to be ?

 

I only see:

1. Mac (currently installed macOS Catalina beta 11 - main boot drive)

2. Recovery (10.15) dmg

3. OpenCore Shell

 

The installer is created with create install media method as requested and the EFI folder is on the EFI partition.

 

CC @vit9696 @Andrey1970 @Download-Fritz @PMheart @vandroiy2012

 

Here is the EFI: EFI.zip

Edited by Sniki
Pavo
Pavo
Posted
Posted
6 minutes ago, Sniki said:

Hi Open Core team or anyone else that can help

 

Im trying to do a clean install on my Lenovo ThinkPad X240.

I did create the Catalina USB Installer but it is not showing on the OC Picker.

 

I don't understand this part very well:

  1.  

I attached the EFI folder so maybe someone can point me where the problem is.

Where is tha com.apple.recovery.boot directory supposed to be ?

 

I only see:

1. Mac (currently installed macOS Catalina beta 11 - main boot drive)

2. Recovery (10.15) dmg

3. OpenCore Shell

 

The installer is created with create install media method as requested and the EFI folder is on the EFI partition.

 

CC @vit9696 @Andrey1970 @Download-Fritz @PMheart @vandroiy2012

 

Here is the EFI: EFI.zip

Try this config, you really should not use ACPI > Patches section to rename DSDT devices. You should use SSDTs

config.plist.zip

Sniki
Sniki
Posted
Posted (edited)
19 minutes ago, Pavo said:

Try this config, you really should not use ACPI > Patches section to rename DSDT devices. You should use SSDTs

config.plist.zip

Ok so it was scanpolicy, Thanks @Pavo

 

I have SSDTs for everything, Renames are necessary for Battery Status and Dual Battery Support.

This is the only way "that i currently know" to implement that without patched DSDT, so you can have full hotpatch system.

 

How would you implement it without Renames and (without Patched DSDT because i want full hotpatch) in this case ?

What would be your recommendations ?

Edited by Sniki
Pavo
Pavo
Posted
Posted
10 minutes ago, Sniki said:

Ok so it was scanpolicy, Thanks @Pavo

 

I have SSDTs for everything, Renames are necessary for Battery Status and Dual Battery Support.

This is the only way "that i currently know" to implement that without patched DSDT, so you can have full hotpatch system.

 

How would you implement it without Renames and (without Patched DSDT because i want full hotpatch) in this case ?

What would be your recommendations ?

Here is an example of how I do my rename for my ethernet port on-board. BR1B > ETH0

  

Scope (\_SB.PCI0.PEX0)
    {
        If (_OSI ("Darwin"))
        {
            Scope (BR1B)
            {
                Method (_STA, 0, NotSerialized)  // _STA: Status
                {
                    Return (Zero)
                }
            }

            Device (ETH0)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Method (_STA, 0, NotSerialized)  // _STA: Status
                {
                    Return (0x0F)
                }
            }

            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Return (Package (0x02)
                {
                    "location", 
                    Buffer (0x02)
                    {
                        "1"
                    }
                })
            }
        }
    }

 

canyondust
canyondust
Posted
Posted (edited)
On 9/28/2019 at 1:52 PM, ham4ever said:

I managed to solve a lot fails by looking at the comments and reading the manual.

 

i have one single fail left that i couldn't find anything about it:

 

OCB: Failed to match a default boot option.

 

EDIT: to be clear, the system does boot and all, is just that line appears before booting and is bothering me. 

I have the same issue since updating to OC 0.5.1. Did you find a fix for this? (I tried selecting the startup disk in system preferences)

 

EDIT: the fix is setting RequestBootVarRouting = TRUE

Edited by canyondust
  • Like 1
littlegtplr
littlegtplr
Posted
Posted

Hi all OpenCore testers,

 

I encountered an issue with assigning default boot option and hope if anyone could shed me some light. Assigning default boot option via Startup Disk preference panel doesn't seem to have any effect to the default boot-up option of OpenCore. I changed it to two different disks but the OpenCore default stays still the first one (an EFI). 

 

I can see that efi-boot-device in nvram.plist is able to change according to the selection on Startup Disk preference panel. However that doesn't change what OpenCore brings up as the default. 

 

These are tested with RequestBootVarRouting enabled. When disabled, the default booting option stayed on the second entry of the booting list (another EFI...), regardless of what was chosen on the Startup Disk preference panel. 

 

Other than this issue, OpenCore has been working flawlessly with my hack. Well done guys! 

 

My plist can be found below, and the specs. Thanks. 

 

CPU: i5-8500

GPU: Sapphire RX580 Pulse

RAM: Corsair - Vengeance LPX 2 x 8GB DDR4-3000

Motherboard/Laptop model: Gigabyte B360 AORUS Gaming 3 WIFI

config copy.plist

taga
taga
Posted
Posted
On 10/7/2019 at 8:12 PM, duffs said:

When installing catalina i got error "an error occurred while verifying firmware" it turns out that my FirmwareFeatures ported from clover was wrong. Fixing that, install went thru just fine. Used one from sample.plis.

 

 

Missing some functionality from clover like "lastbootedvolume". When installing Macos on reboot  clover automatically selected "macOS installer" and continue installing. does this work?

 

i have the same problem opencore catalina 5.0.1 install ,  

How did you solve this problem? please

Andrw0380
Andrw0380
Posted
Posted

Hello everyone, was wondering if someone could answer this question. I am on the latest Open core 0.5.2 and have have noticed this issue for the last few builds. When I select OC to boot quickly before the picker menu is shown, I get the following message: "OCS: No schema for DevicePathsSupported at 0 index!"

 

Any ideas as couldn't find this anywhere?

 Share
Go to topic listing
×
×
  • Create New...