OpenCore General Discussion

[Andres ZeroCross]

5 minutes ago, justin said:

https://github.com/acidanthera/OcSupportPkg/blob/40b43134e35dd1423a6d0d73addda00864fe2938/Include/Library/OcAppleBootCompatLib.h#L21

How about ?? Did you tried it before?
SetupAppleMap=YES SetupAppleSlide=NO
 

32 minutes ago, Matgen84 said:

 

@vandroiy2012 said in post above:

 

ConsoleControl=true
 
ProvideConsoleGop=true

It works for my Z390 Aorus Master. I've verbose mode because I use it.

 

Thanks a lot. @Andres ZeroCross  

 

What about others patches: I don't find the way to use it in OC Config.plist

What patch?? Can you be more specific???

[maddie]

16 minutes ago, Andres ZeroCross said:

How about ?? Did you tried it before?
SetupAppleMap=YES SetupAppleSlide=NO
 

What patch?? Can you be more specific???

 

SetupAppleMap=YES SetupAppleSlide=NO actually fixes the Apple logo problem, thanks!

 

But still, the updater wouldn't run. Even Recovery isn't working, it's the same as the updater, reboots itself after 50% of the progress bar.

 

Is there any way I can get a copy of the verbose boot log as a file for the updater? I guess it's not really a problem of OpenCore itself, rather some configuration that makes the updater reboot/panic at some step.

[Andres ZeroCross]

1 minute ago, maddie said:

 

SetupAppleMap=YES SetupAppleSlide=NO actually fixes the Apple logo problem, thanks!

 

But still, the updater wouldn't run. Even Recovery isn't working, it's the same as the updater, reboots itself after 50% of the progress bar.

 

Is there any way I can get a copy of the verbose boot log as a file for the updater? I guess it's not really a problem of OpenCore itself, rather some configuration that makes the updater reboot/panic at some step.

Honestly i don't know what's is your detail problem?? Can you write it again with more details???

[justin]

21 minutes ago, Andres ZeroCross said:

How about ?? Did you tried it before?
SetupAppleMap=YES SetupAppleSlide=NO

 

Setting like that will break Shutdown and Sleep. I have to set both off to get proper sleep/shutdown. 

[Andres ZeroCross]

3 minutes ago, justin said:

 

Setting like that will break Shutdown and Sleep. I have to set both off to get proper sleep/shutdown. 

With CSM == Disabled from BIOS?

[justin]

31 minutes ago, Andres ZeroCross said:

Btw, did you disable CSM Options from BIOS? I have disabled it always

 

YES. It was disabled since the beginning of my hack on this motherboard. I'm just testing the new OC. The one i built on 7/23 worked perfectly with AptioMemoryFix + VariableRuntimeDxe. I think the FwRuntimeServices.efi is to blame for the new OC i built yesterday, as it replaces the two efi.

[maddie]

17 minutes ago, Andres ZeroCross said:

Honestly i don't know what's is your detail problem?? Can you write it again with more details???

 

Sure.

 

Problem: The last supplemental update for 10.14.6 from Apple, cannot be installed on this Z97-A system (in signature). (And another system of mine with Asrock Deskmini 310, but that's another issue)

---

When using older OpenCore at commit 1338b0c:

 

After rebooting by clicking "Restart" on the update pane, only the "macOS Installer" is selectable from the OpenCore picker. When I select "macOS Installer", the Apple logo and progress bar shows. After just a bit more than 50% of the progress bar is done, the system reboots itself, returning to the OpenCore menu with only the "macOS Installer", so I can't get back into the OS.

 

---

Then I compiled the latest OpenCore at commit 60b42e5, hoping that it might be a known issue that's being fixed. The new version can show both "macOS Installer" and the "macOS" boot entry, which is great, or I had to use a Clover USB disk to boot back to macOS.

 

But using the latest OpenCore gives the same result, selecting "macOS Installer" boots into the installer DMG as shown in verbose mode (with "-v keepsyms=1 debug=0x100" boot-args). After around 50% of the progress bar (non-verbose mode) or after NTP service has been ran (verbose mode), the system came to a stop for a while, then went into a black screen without rebooting (guessing it could be because of the debug=0x100 boot-arg, without this boot-arg it would just reboot like it did in non-verbose mode). Since it turns into a black screen, no further logs can be seen on the screen, and I can't really spot anything wrong with the earlier logs, that's why I'm wondering if there's a way to save verbose mode boot log into a file.

[justin]

26 minutes ago, maddie said:

 

SetupAppleMap=YES SetupAppleSlide=NO actually fixes the Apple logo problem, thanks!

 

But still, the updater wouldn't run. Even Recovery isn't working, it's the same as the updater, reboots itself after 50% of the progress bar.

 

Is there any way I can get a copy of the verbose boot log as a file for the updater? I guess it's not really a problem of OpenCore itself, rather some configuration that makes the updater reboot/panic at some step.

 

I installed Mojave 10.14.6 (18G87) few days ago from Settings/Software Update with the OC i built on 7/23 (4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-004-2019-07-23), no problem, everything works as before. 

 

[Andres ZeroCross]

9 minutes ago, justin said:

 

I installed Mojave 10.14.6 (18G87) few days ago from Settings/Software Update with the OC i built on 7/23 (4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-004-2019-07-23), no problem, everything works as before. 

 

 

I still can see nvram boot-path with previous or current OC version

 

 

13 minutes ago, maddie said:

 

Sure.

 

Problem: The last supplemental update for 10.14.6 from Apple, cannot be installed on this Z97-A system (in signature). (And another system of mine with Asrock Deskmini 310, but that's another issue)

---

When using older OpenCore at commit 1338b0c:

 

After rebooting by clicking "Restart" on the update pane, only the "macOS Installer" is selectable from the OpenCore picker. When I select "macOS Installer", the Apple logo and progress bar shows. After just a bit more than 50% of the progress bar is done, the system reboots itself, returning to the OpenCore menu with only the "macOS Installer", so I can't get back into the OS.

 

---

Then I compiled the latest OpenCore at commit 60b42e5, hoping that it might be a known issue that's being fixed. The new version can show both "macOS Installer" and the "macOS" boot entry, which is great, or I had to use a Clover USB disk to boot back to macOS.

 

But using the latest OpenCore gives the same result, selecting "macOS Installer" boots into the installer DMG as shown in verbose mode (with "-v keepsyms=1 debug=0x100" boot-args). After around 50% of the progress bar (non-verbose mode) or after NTP service has been ran (verbose mode), the system came to a stop for a while, then went into a black screen without rebooting (guessing it could be because of the debug=0x100 boot-arg, without this boot-arg it would just reboot like it did in non-verbose mode). Since it turns into a black screen, no further logs can be seen on the screen, and I can't really spot anything wrong with the earlier logs, that's why I'm wondering if there's a way to save verbose mode boot log into a file.

Let's make it simple,,
1. Don't put any USB Installer to your PC
2. Boot with current OC Version bootloader and set Verbose mode
3. Take a screenshoot in your Boot Picker (boot entry)

[maddie]

28 minutes ago, justin said:

 

I installed Mojave 10.14.6 (18G87) few days ago from Settings/Software Update with the OC i built on 7/23 (4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-004-2019-07-23), no problem, everything works as before. 

 

My Z370 system installs fine too, the other two do not however. I'm looking for a way to figure out why..

 

EDIT: On the Asrock Deskmini 310 system, I was able to complete the installation by booting with my old Clover backup. On the Z97 system, however, booting with the old Clover backup for this system doesn't seem to work either. So I'm still guessing some configuration error on my end, but I can't figure out which or what that causes it because the lack of logging from system boot..

Edited August 7, 2019 by maddie

[justin]

2 minutes ago, Andres ZeroCross said:

 

I still can see nvram boot-path with previous or current OC version

 

 

 

 

Yes, me too. with 7/23 version, it shows. with 8/6 version, it shows unless SetupAppleMap=YES SetupAppleSlide=YES. but SetupAppleMap=YES SetupAppleSlide=YES brings more issue to me: 

 

 

[Andres ZeroCross]

30 minutes ago, maddie said:

 

Sure.

 

Problem: The last supplemental update for 10.14.6 from Apple, cannot be installed on this Z97-A system (in signature). (And another system of mine with Asrock Deskmini 310, but that's another issue)

---

When using older OpenCore at commit 1338b0c:

 

After rebooting by clicking "Restart" on the update pane, only the "macOS Installer" is selectable from the OpenCore picker. When I select "macOS Installer", the Apple logo and progress bar shows. After just a bit more than 50% of the progress bar is done, the system reboots itself, returning to the OpenCore menu with only the "macOS Installer", so I can't get back into the OS.

 

---

Then I compiled the latest OpenCore at commit 60b42e5, hoping that it might be a known issue that's being fixed. The new version can show both "macOS Installer" and the "macOS" boot entry, which is great, or I had to use a Clover USB disk to boot back to macOS.

 

But using the latest OpenCore gives the same result, selecting "macOS Installer" boots into the installer DMG as shown in verbose mode (with "-v keepsyms=1 debug=0x100" boot-args). After around 50% of the progress bar (non-verbose mode) or after NTP service has been ran (verbose mode), the system came to a stop for a while, then went into a black screen without rebooting (guessing it could be because of the debug=0x100 boot-arg, without this boot-arg it would just reboot like it did in non-verbose mode). Since it turns into a black screen, no further logs can be seen on the screen, and I can't really spot anything wrong with the earlier logs, that's why I'm wondering if there's a way to save verbose mode boot log into a file.

THere is no log, so i can't read the log. But you say you can't boot into recovery partition too. Maybe your issues are about
1. Old kext version (just make sure you have used latest version of necessary kext)
2. Take a look at this options. Maybe you will understand

20 minutes ago, justin said:

 

 

Yes, me too. with 7/23 version, it shows. with 8/6 version, it shows unless SetupAppleMap=YES SetupAppleSlide=YES. but SetupAppleMap=YES SetupAppleSlide=YES brings more issue to me: 

 

 

What's your options about this?? YES or NO???

I have set YES

[justin]

4 minutes ago, Andres ZeroCross said:

What's your options about this?? YES or NO???

I have set YES

 

Tried YES, it does not help. 

[maddie]

5 minutes ago, Andres ZeroCross said:

THere is no log, so i can't read the log. But you say you can't boot into recovery partition too. Maybe your issues are about
1. Old kext version (just make sure you have used latest version of necessary kext)
2. Take a look at this options. Maybe you will understand

What's your options about this?? YES or NO???

I have set YES

 

1. I have the latest kexts. All the kexts are compiled altogether when I compile OpenCore.

2. I have the AvoidHighAlloc option set to false. Should I try to enable it?

[Andres ZeroCross]

4 minutes ago, justin said:

 

Tried YES, it does not help. 

I don't know if this will help, but i always clean NVRAM with "CleanNvram.efi" after change configuration about NVRAM stuff

Edited August 7, 2019 by Andres ZeroCross

[justin]

Just now, Andres ZeroCross said:

I don't know if this will help, but i always clean NVRAM with "CleanNvram.efi" before change configuration about NVRAM stuff

 

I have the same habit as you, i even cut off the power cable after clean nvram. i always do that before i try new versions of OC. 

[Andres ZeroCross]

2 minutes ago, maddie said:

 

1. I have the latest kexts. All the kexts are compiled altogether when I compile OpenCore.

2. I have the AvoidHighAlloc option set to false. Should I try to enable it?

To avoid WRONG STEP, you need to upload Verbose log / photo.
You didn't follow my requestment above too. How can i analyze your problem / give solution?

[justin]

About latest OC, here is my understanding, don't know if i'm correct:

 

1. (( 30%  (assume) code of FwRuntimeServices.efi + Booter/Quirks )) Replaces AptioMemoryFix.efi

2. The rest of 70% code of FwRuntimeServices.efi Replaces VariableRuntimeDxe.efi from AUDK. 

[maddie]

10 minutes ago, Andres ZeroCross said:

To avoid WRONG STEP, you need to upload Verbose log / photo.
You didn't follow my requestment above too. How can i analyze your problem / give solution?

 

Sure, here are the photos for the verbose log. Sorry for the small text, it's a 4k monitor. Is there a way to save this verbose log into a file?

 

 

1.HEIC

2.HEIC

Also, my current config.plist, with board info redacted.

 

 

config.plist

[Andres ZeroCross]

7 minutes ago, maddie said:

 

Sure, here are the photos for the verbose log. Sorry for the small text, it's a 4k monitor. Is there a way to save this verbose log into a file?

 

 

1.HEIC

2.HEIC

Also, my current config.plist, with board info redacted.

 

 

config.plist

Log is completed except about IGPU power mangement, but it shouldn't prevent you from boot to desktop / instalation progress.

I assumed you have used dual GPU (IGPU haswell + RX 580), RX 580 without WhateverGreen get black screen here.

Here is my conclusions,,
1. What version of your lilu.kext???
2. What version of your WhateverGreen.kext??

[maddie]

2 minutes ago, Andres ZeroCross said:

Log is completed except about IGPU power mangement, but it shouldn't prevent you from boot to desktop / instalation progress.

I assumed you have used dual GPU (IGPU haswell + RX 580), RX 580 without WhateverGreen get black screen here.

Here is my conclusions,,
1. What version of your lilu.kext???
2. What version of your WhateverGreen.kext??

1. Lilu is 1.3.8, compiled from repository.

2. WhateverGreen is 1.3.1, compiled from repository.

 

I do have iGPU enabled on Haswell platform, configured as connector-less and RX 580, running with WhateverGreen. I can boot into macOS just fine, just not the installer.

[Andres ZeroCross]

2 minutes ago, maddie said:

1. Lilu is 1.3.8, compiled from repository.

2. WhateverGreen is 1.3.1, compiled from repository.

 

I do have iGPU enabled on Haswell platform, configured as connector-less and RX 580, running with WhateverGreen. I can boot into macOS just fine, just not the installer.

Please use this, and report for the result

config.plist

[Andres ZeroCross]

11 minutes ago, maddie said:

1. Lilu is 1.3.8, compiled from repository.

2. WhateverGreen is 1.3.1, compiled from repository.

 

I do have iGPU enabled on Haswell platform, configured as connector-less and RX 580, running with WhateverGreen. I can boot into macOS just fine, just not the installer.

And i still curious about "unloaded of WhateverGreen.kext", just try this Lilu.kext and WhateverGreen.kext. I have used it and working fine here with Mojave 18G87

Note : You said about debug=0x100 prevent reboot in your PC,, if it's the case then when you boot itu macOS partition you will see "Crash Report about kernel panic". debug=0x100 is preventing system reboot from kernel panic only. If you don't see any crash report when you have login to your mac partition, then it mean "there is no kernel panic".

 

Archive.zip

Edited August 7, 2019 by Andres ZeroCross

[maddie]

11 minutes ago, Andres ZeroCross said:

And i still curious about "unloaded of WhateverGreen.kext", just try this Lilu.kext and WhateverGreen.kext. I have used it and working fine here with Mojave 18G87

Note : You said about debug=0x100 prevent reboot in your PC,, if it's the case then when you boot itu macOS partition you will see "Crash Report about kernel panic". debug=0x100 is preventing system reboot from kernel panic only. If you don't see any crash report when you have login to your mac partition, then it mean "there is no kernel panic".

 

Archive.zip

 

Just compared and applied the changes from your config.plist from the previous post, it's still the same.

 

IgnoreInvalidFlexRatio is required to get my system to boot, so I left it enabled.

 

The WhateverGreen and Lilu also doesn't seem to make any difference here..

 

Where did you see the "unloaded of WhateverGreen.kext" in the screen shot? I can't seem to find it.

 

And about the crash report thing you've mentioned, actually I didn't see a crash report when I boot back into macOS, so maybe it's not really a kernel panic, it just froze there without any display..

[Andres ZeroCross]

1 minute ago, maddie said:

 

Just compared and applied the changes from your config.plist from the previous post, it's still the same.

 

IgnoreInvalidFlexRatio is required to get my system to boot, so I left it enabled.

 

The WhateverGreen and Lilu also doesn't seem to make any difference here..

 

Where did you see the "unloaded of WhateverGreen.kext" in the screen shot? I can't seem to find it.

 

And about the crash report thing you've mentioned, actually I didn't see a crash report when I boot back into macOS, so maybe it's not really a kernel panic, it just froze there without any display..

I just remove "unused properties in your IGPU for connector-less" platform.

About "unloaded of WhateverGreen.kext" is just my opinion, black screen after verbose, no display is issues in AMD GPU without WhateverGreen.kext. Here is another step to make sure of it.

Just use IGPU, remove your AMD card. And use normal ig-platform-id. Can you continue installation of update???