OpenCore General Discussion

[Andres ZeroCross]

1 hour ago, vit9696 said:

Two things:

- Do you realise that audio assistance is not yet implemented in OpenCanopy? 

- Does audio assistance work with the previous release of AudioDxe?

It's my mistake, i have copied resource folder from OpenCorePkg, LOL.

I copy resource folder from OcBinaryData, and sound work again

Thank you

[Andres ZeroCross]

10 minutes ago, topolino1 said:

@Andres ZeroCross I have audio assistance on OC 0.5.8 in Intel Core i7 6700 | Gigabyte Z170X - Gaming 7.

Send me config, will I compare.

 

I have no the ringtone and I can't hear PickerAudioAssist on Gigabyte Z390M Gaming / OC 0.5.8.

Does anyone on this set have the ringtone and I can't hear PickerAudioAssist?

 

Thank you for the information and help.

Check your EFI/OC/Resource/Audio,, screenshot

[familygw]

3 hours ago, familygw said:

Hi! thanks for your response. I already did all these options but still booting in windows as first option.

From Windows I‘m able to modify the boot order or the default boot device (in this case the BOOTx64.efi from the EFI partition in the macOS disk), which is basically the same thing that I can do from BIOS Setup. That’s ok, but from the moment that OC boots the computer, the default OS that starts is Windows, no matter if I press Ctrl+Enter or select the macOS disk in Startup Disk.

 

Thanks!

 

 

Any clue?

On my system I have 2 EFI partitions, shall I move the OC folder to the Windows EFI partition?

 

Thanks in advance.

[Tiem]

5 hours ago, familygw said:

Hi! thanks for your response. I already did all these options but still booting in windows as first option.

From Windows I‘m able to modify the boot order or the default boot device (in this case the BOOTx64.efi from the EFI partition in the macOS disk), which is basically the same thing that I can do from BIOS Setup. That’s ok, but from the moment that OC boots the computer, the default OS that starts is Windows, no matter if I press Ctrl+Enter or select the macOS disk in Startup Disk.

 

Thanks!

 

AdviseWindows. Without it, you'll always be fighting the WBM as it will always aggressively throw itself first.

[markl18]

hi I got this error what exactly does it mean it is from rebooter in in diagnostic mode

[MacNB]

1 hour ago, markl18 said:

hi I got this error what exactly does it mean it is from rebooter in in diagnostic mode

 

Check the OC log file in the root of your EFI partition. It will detail the problem - most likely with your config.plist

[familygw]

2 hours ago, Tiem said:

AdviseWindows. Without it, you'll always be fighting the WBM as it will always aggressively throw itself first.

That simple check fixed my issue. Thanks @Tiem

 

There is a way to get HVEC working using SMBIOS iMac15,1? Or, better question: which is the best configuration for a Haswell i7 4790K, only dGPU or iGPU + dGPU?

 

Thanks!

[Tiem]

3 hours ago, familygw said:

That simple check fixed my issue. Thanks @Tiem

 

There is a way to get HVEC working using SMBIOS iMac15,1? Or, better question: which is the best configuration for a Haswell i7 4790K, only dGPU or iGPU + dGPU?

 

Thanks!

Add your system to your signature. Way more likely to get help. Don’t have to write it in every post.

 

No idea about your rig. It’s a bit OT. Go ask in a thread that’s for your specific board.

[francisjfl]

Does the mouse already have support to work in the larger selector of OC? If so, how?

[bbritton]

After updating to 0.5.8 my Catalina Dynamic desktop has lines and spots on it.  Seems the graphics are screwed up a bit.  It is only on the Catalina Dynamic desktop though as all other desktops apps and web pages are good.  I used to have this issue with clover and was very happy when it disappeared with open core 0.5.7. 

 

Any thoughts of what could be the issue?  I have attached my config.plist and screen shot.

 

Thanks 

Config.plist

Edited May 6, 2020 by bbritton
Noticed its only on Catalina Dynamic Desktop

[saleh99]

Hi, thanks for everyone

 

i'm using OpenCore 0.5.8

 

is there anyway to fix sleep/wake in 10.15.4

 

ASUS z270

Kaby Lake 7700K

Edited May 6, 2020 by saleh99

[markl18]

hi does any body knows where are the resources for 0.5.9 yes it is out for couple of weeks now it is very different they apparently took a very different approach to devices there is a shell script that quires your devices and generates devices.plist that being used by the process a much smarter approach than everyone doing who knows what with their devices

6 DeviceProperties 6.1 Introduction

Device configuration is provided to macOS with a dedicated buffer, called EfiDevicePathPropertyDatabase. This buffer is a serialised map of DevicePaths to a map of property names and their values.

Property data can be debugged with gfxutil. To obtain current property data use the following command in macOS:

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//' > /tmp/device-properties.hex &&
gfxutil /tmp/device-properties.hex /tmp/device-properties.plist && cat /tmp/device-properties.plist

6.2 Properties

1.

2.

6.3

Add
Type: plist dict
Description: Sets device properties from a map (plist dict) of deivce paths to a map (plist dict) of variable names and their values in plist metadata format. Device paths must be provided in canonic string format (e.g. PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)). Properties will only be set if not present and not blocked.

Note: Currently properties may only be (formerly) added by the original driver, so unless a separate driver was installed, there is no reason to block the variables.

Block
Type: plist dict
Description: Removes device properties from a map (plist dict) of deivce paths to an array (plist array) of variable names in plist string format.

Edited May 6, 2020 by markl18

[topolino1]

7 hours ago, bbritton said:

After updating to 0.5.8 my Catalina Dynamic desktop has lines and spots on it.  Seems the graphics are screwed up a bit.  It is only on the Catalina Dynamic desktop though as all other desktops apps and web pages are good.  I used to have this issue with clover and was very happy when it disappeared with open core 0.5.7. 

 

If you use Intel 630 graphics. I think you have PciRoot (0x0) / Pci (0x2,0x0) set incorrectly.
This is probably a problem.

[bbritton]

1 hour ago, topolino1 said:

 

If you use Intel 630 graphics. I think you have PciRoot (0x0) / Pci (0x2,0x0) set incorrectly.
This is probably a problem.

Thanks but I do not use the Intel 630 to drive my screen, I use a Vega 64.  I only. intend to use the Intel 630 graphics for H265 etc.

[MacNB]

1 hour ago, markl18 said:

hi does any body knows where are the resources for 0.5.9 yes it is out for couple of weeks now it is very different they apparently took a very different approach to devices there is a shell script that quires your devices and generates devices.plist that being used by the process a much smarter approach than everyone doing who knows what with their devices

6 DeviceProperties 6.1 Introduction

Device configuration is provided to macOS with a dedicated buffer, called EfiDevicePathPropertyDatabase. This buffer is a serialised map of DevicePaths to a map of property names and their values.

Property data can be debugged with gfxutil. To obtain current property data use the following command in macOS:

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//' > /tmp/device-properties.hex &&
gfxutil /tmp/device-properties.hex /tmp/device-properties.plist && cat /tmp/device-properties.plist

6.2 Properties

1.

2.

6.3

Add
Type: plist dict
Description: Sets device properties from a map (plist dict) of deivce paths to a map (plist dict) of variable names and their values in plist metadata format. Device paths must be provided in canonic string format (e.g. PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)). Properties will only be set if not present and not blocked.

Note: Currently properties may only be (formerly) added by the original driver, so unless a separate driver was installed, there is no reason to block the variables.

Block
Type: plist dict
Description: Removes device properties from a map (plist dict) of deivce paths to an array (plist array) of variable names in plist string format.

 

 Your first question/statement does not make sense.

 

If you are asking where the Resources folder is, then it is in the same place as it always was here.

 

But that is totally unrelated to DeviceProperties.

Where did you read about "very different approach" and device.plist ????

It is not mentioned in the Configuration PDF you have quoted.

Nothing has changed as far as I can tell with 0.5.9

 

Are you asking a question about Device Properties or making a suggestion ?

[bbritton]

9 hours ago, bbritton said:

After updating to 0.5.8 my Catalina Dynamic desktop has lines and spots on it.  Seems the graphics are screwed up a bit.  It is only on the Catalina Dynamic desktop though as all other desktops apps and web pages are good.  I used to have this issue with clover and was very happy when it disappeared with open core 0.5.7. 

 

Any thoughts of what could be the issue?  I have attached my config.plist and screen shot.

 

Thanks 

Config.plist

Just figured out the problem.  Not sure which Item fixed the graphics issue but I tried the "sanity Checker" from the OpenCore guide and it advised me to make three changes:

Booter
MmioWhitelist
Quirks

ProtectUefiServices = No.  I had set to Yes

SyncRuntimePermissions = Yes     I had set to No

NVRAM

WriteFlash = Yes     I had set to No

 

The Dynamic desktop works now.

 

[topolino1]

57 minutes ago, bbritton said:

Thanks but I do not use the Intel 630 to drive my screen, I use a Vega 64.  I only. intend to use the Intel 630 graphics for H265 etc.

 

If you use Vega, the more you have a bad section PciRoot (0x0) / Pci (0x2,0x0).

 

Here you have described exactly how it should be.

https://dortania.github.io/OpenCore-Desktop-Guide/config.plist/coffee-lake.html#deviceproperties

 

You generally have some errors in the config.

 

[markl18]

1 hour ago, MacNB said:

 

 Your first question/statement does not make sense.

 

If you are asking where the Resources folder is, then it is in the same place as it always was here.

 

But that is totally unrelated to DeviceProperties.

Where did you read about "very different approach" and device.plist ????

It is not mentioned in the Configuration PDF you have quoted.

Nothing has changed as far as I can tell with 0.5.9

 

Are you asking a question about Device Properties or making a suggestion ?

I thought that that what happens they look into that plist file and add it to the internal map 

just juding by these words

Note: Currently properties may only be (formerly) added by the original driver, so unless a separate driver was installed, there is no reason to block the variables.

Block
Type: plist dict
Description: Removes device properties from a map (plist dict) of deivce paths to an array (plist array) of variable names in plist string format.

 

that makes it sounds like they pick that plist file and add it to the internal map of stuff they even provide shell script to create the file atomaticly if not then they should and yes the resources file came empty thanks for the location

 

Edited May 6, 2020 by markl18

[bbritton]

35 minutes ago, topolino1 said:

 

If you use Vega, the more you have a bad section PciRoot (0x0) / Pci (0x2,0x0).

 

Here you have described exactly how it should be.

https://dortania.github.io/OpenCore-Desktop-Guide/config.plist/coffee-lake.html#deviceproperties

 

You generally have some errors in the config.

 

Thanks, I edited the Config and attached.  i believe it is correct now.  I believe I copied and pasted too many times before and got some extra lines in code.

But now on my login page I get some vertical green lines as per the pic attached.  But the desktop is ok now.

 

I have attached the new config file as well.

 

Config.plist

[MacNB]

53 minutes ago, markl18 said:

 

 

You have completely misunderstood that whole section 6.1.

That EXAMPLE mentioned in the Section 6.1 regarding the use of the ioreg command from terminal is for you to be able to retrieve the device properties from the device tree of your system. That example command saves the list to a plist file as CONVENIENT way to see what you have (for debugging purposes).

OC does nothing with that plist file.

 

As Obi-Wan Kenobi once said "These aren't the droids you're looking for...move along"

[topolino1]

The guide has information on how the section should look correctly.

Start with this!

 

You have nothing correctly.

The section you entered is responsible for Intel 630 graphics:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>BwCbPg==</data>
                <key>framebuffer-con0-alldata</key>
                <data>AQAJAAAEAADHAwAA</data>
                <key>framebuffer-con0-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-alldata</key>
                <data>AgAKAAAEAADHAwAA</data>
                <key>framebuffer-con1-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con2-alldata</key>
                <data>AwQIAAAIAADHAwAA</data>
                <key>framebuffer-con2-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-stolenmem</key>
                <data>AAAwAQ==</data>
            </dict>
        </dict>

 

 

5 hours ago, bbritton said:

Thanks, I edited the Config and attached.  i believe it is correct now.  I believe I copied and pasted too many times before and got some extra lines in code.

But now on my login page I get some vertical green lines as per the pic attached.  But the desktop is ok now.

 

I have attached the new config file as well.

 

Config.plist

 

[markl18]

4 hours ago, MacNB said:

 

You have completely misunderstood that whole section 6.1.

That EXAMPLE mentioned in the Section 6.1 regarding the use of the ioreg command from terminal is for you to be able to retrieve the device properties from the device tree of your system. That example command saves the list to a plist file as CONVENIENT way to see what you have (for debugging purposes).

OC does nothing with that plist file.

 

As Obi-Wan Kenobi once said "These aren't the droids you're looking for...move along"

then at least this should be their option of 'proper tree' options to populate the plist file like it does

[bbritton]

5 hours ago, topolino1 said:

The guide has information on how the section should look correctly.

Start with this!

 

You have nothing correctly.

The section you entered is responsible for Intel 630 graphics:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>BwCbPg==</data>
                <key>framebuffer-con0-alldata</key>
                <data>AQAJAAAEAADHAwAA</data>
                <key>framebuffer-con0-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-alldata</key>
                <data>AgAKAAAEAADHAwAA</data>
                <key>framebuffer-con1-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con2-alldata</key>
                <data>AwQIAAAIAADHAwAA</data>
                <key>framebuffer-con2-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-stolenmem</key>
                <data>AAAwAQ==</data>
            </dict>
        </dict>

 

 

 

I have put your code into my config.  It seems to be the same as I have had at one time before.  The dynamic desktop again now has the lines like originally my problem.  I have attached the latest config.

Config.plist

[topolino1]

@bbritton You still have mistakes.

 

Here you have described exactly how it should be.

https://dortania.github.io/OpenCore-Desktop-Guide/config.plist/coffee-lake.html#deviceproperties

[vit9696]

On 5/4/2020 at 7:38 PM, Sander Spilleman said:

Hi,

 

I've just upgraded to OC 0.5.8. I'm on macOS 10.15.4 on a Asus Prime Z390-A. Over time I've collected some stuff in my config related to RTC patching, which is needed as otherwise I have that F1 POST / Safe mode {censored}. I might have some stuff in my config that may not be needed anymore. I'd like to get some support to get confirmed what is still needed and want I can remove by now.

 

My config contains the following

Kernel --> Quirks --> DisableRtcChecksum set to TRUE (added in update to OC 0.5.8)

UEFI --> ProtocolOverrides --> AppleRtcRam set to TRUE  (added in update to OC 0.5.8)

NVRAM --> Add --> 7C436110-AB2A-4BBB-A880-FE41995C9F82 --> wake-failure set to 5 bytes 0 (added after 10.15.4: https://github.com/acidanthera/bugtracker/issues/765)

ACPI --> Add --> SSDT-AWAC.aml (per vanilla desktop guide)

 

ACPI --> Patch as follows: (I believe this was generated by SSDTTime)

 

And Kernel --> Add --> Patch the following 2: (found these in here... somewhere)

 

Is there something I can get rid of??

 

Thank you so much!

 

Sander

1. ProtocolOverrides — you do not need to override AppleRtcRam as you do not have Apple hardware. Leave it as false.

2. wake-failure can and should be removed.

3. AppleRTC kernel patches can be removed (they are replaced by a quirk).

4. You forgot to mention rtc-blacklist, but I should remind you that it needs to be set to 58 59 for Z390-like.

5. I don't know whether you need an ACPI patch.

On 5/4/2020 at 7:38 PM, Sander Spilleman said:

Hi,

 

I've just upgraded to OC 0.5.8. I'm on macOS 10.15.4 on a Asus Prime Z390-A. Over time I've collected some stuff in my config related to RTC patching, which is needed as otherwise I have that F1 POST / Safe mode {censored}. I might have some stuff in my config that may not be needed anymore. I'd like to get some support to get confirmed what is still needed and want I can remove by now.

 

My config contains the following

Kernel --> Quirks --> DisableRtcChecksum set to TRUE (added in update to OC 0.5.8)

UEFI --> ProtocolOverrides --> AppleRtcRam set to TRUE  (added in update to OC 0.5.8)

NVRAM --> Add --> 7C436110-AB2A-4BBB-A880-FE41995C9F82 --> wake-failure set to 5 bytes 0 (added after 10.15.4: https://github.com/acidanthera/bugtracker/issues/765)

ACPI --> Add --> SSDT-AWAC.aml (per vanilla desktop guide)

 

ACPI --> Patch as follows: (I believe this was generated by SSDTTime)

 

And Kernel --> Add --> Patch the following 2: (found these in here... somewhere)

 

Is there something I can get rid of??

 

Thank you so much!

 

Sander

1. ProtocolOverrides — you do not need to override AppleRtcRam as you do not have Apple hardware. Leave it as false.

2. wake-failure can and should be removed.

3. AppleRTC kernel patches can be removed (they are replaced by a quirk).

4. You forgot to mention rtc-blacklist, but I should remind you that it needs to be set to 58 59 for Z390-like.

5. I don't know whether you need an ACPI patch.

 

As for ACPI patches and

Edited May 7, 2020 by vit9696