OpenCore General Discussion

[justin]

10 minutes ago, FredWst said:

 

Yes I know that.

I just want to explain that before dropping AptioMemoryFix (old OC 0.0.4)  ProvideConsoleGop = false was working fine for me.

And I don't understand why now I need it. if u can explain.

 

Fred 

 

 

 

Because AptioMemoryFix.efi has Provided Console Gop, if you read OC 0.03 docs, you will find out there is a tip for that. Now on OC 0.04, AptioMemoryFix.efi was split into 2 parts, one part became Booter Options, another part was merged into FwRuntimeServices.efi. 

[vandroiy2012]

9 minutes ago, FredWst said:

I just want to explain that before dropping AptioMemoryFix (old OC 0.0.4)  ProvideConsoleGop = false was working fine for me.

And I don't understand why now I need it. if u can explain.

 

Fred 

 

 

 

It is because you didn't read the manual before!!!

 

Before this changes with AMF migrating to OC and FwRuntime there was an explanation about ProvideConsoleGop

 

Here it is:

Quote

2. ProvideConsoleGop
   Type: plist boolean
   Failsafe: false
   Description: macOS bootloader requires GOP (Graphics Output Protocol) to be present on console handle. This option will install it if missing.

   Note: Some drivers, like AptioMemoryFix, may provide equivalent functionality. These drivers are not guaranteed to adhere to the same logic, and if a quirk is necessary, this option is preferred.

 

 Thats why ProvideConsoleGop = false was working fine for you! AMF did the trick. 

[justin]

1 hour ago, Matgen84 said:

 

Right. But:

The question: hackintosh for all or for specialists. A bootoader, this is just my opinion, is not just about specialists. It must be usable by everyone, and the community is used only in case of particular problems. That's because I understand Chris's post. If it takes days, sharp knowledge to parameterize it can affect its dissemination.

 

Just my opinion. A bootloader must remain accessible to the largest number of users 

 

What Boot loader on the planet has so great documentation other than OpenCore? What else does “everyone” need? 

[obus]

Hi all.

I have randomly problems to boot with this message in my logs: OCB: StartImage failed - Aborted.

Is this due to the fact that I don't have ProvideCustomSlide = Yes?

According to the manual the message: "Only N/256 slide values are usable" should be in the log but I can't find that message.

Or could it be that I'am using FakeSMS instead of VirtualSMC?

(I've using FakeSMC because I am running iStat Menus and that app is only working 100% on my rig with just FakeSMC)

opencore-2019-08-12-073639.txt

[Matgen84]

27 minutes ago, justin said:

 

What Boot loader on the planet has so great documentation other than OpenCore? What else does “everyone” need? 

 

Right. Great only english documentation. OC requires a lot of knowledge to only preamble the config.plist. This is not the case for everyone. That's the meaning of my previous post.

 

@justin I like OC 

[FredWst]

2 hours ago, vit9696 said:

@FredWst, not to offend, but you did not even open the docs. Look here:

https://github.com/acidanthera/OpenCorePkg/commit/e611445f46179837d2ad22349c46457226615718#diff-567688bcd4741f8bbfd57acebc9f644cL3031

The warning not to rely on AptioMemoryFix for this behaviour was in the docs for ages, as you see I removed it 5 days ago after AptioMemoryFix died. It is just you that ignored most of the file =)

 

no comment !

I'm certainly too newbie to understand.

 

Fred

 

[artur_pt]

hello @Andrey1970

 

any special quirk for oc 4 in insyde bios ?

 

thanks

[LAbyOne]

4 hours ago, Matgen84 said:

 

Right. But:

The question: hackintosh for all or for specialists. A bootoader, this is just my opinion, is not just about specialists. It must be usable by everyone, and the community is used only in case of particular problems. That's because I understand Chris's post. If it takes days, sharp knowledge to parameterize it can affect its dissemination.

 

Just my opinion. A bootloader must remain accessible to the largest number of users 

"hackintosh for all or for specialists"

Hackintosh as any other Hack can't be for all. ca va sans dire, or for better understandig i'll say, all for hackintosh, and means just what i already said above, first of all you must learn, its the basic rule to do anything in the living world (not only here)

 

You said " That's because I understand Chris's post. If it takes days...." I don't remeber learning to speak took me little time... but now i can speak 5 languages, the same goes for walking an so on....

 

to enter this world without any knowledge and pretending to get through with no hassle  is fantasy

 

you probably just forgot the very early days of clover... it was similar for all coming from Chameleon... it took time and patience,

then appeared different tools to simplify... the tasks

 

What in my opinion fails to be understood here, is OC is still a work in progress and ofc so is its documentation, many things

may vary from a day to another when all this work will finally reach its final stages, maybe we'll also see some automation 

till then the only way is to learn, and it may take days ok but then you'll surely know how to get throug it and possibly also been able to help others and also share your knowledge

a Configurator and a Builder... have already been made

and still some aren't yet happy

[Andrey1970]

1 hour ago, artur_pt said:

hello @Andrey1970

 

any special quirk for oc 4 in insyde bios ?

 

thanks

 

No, imagine that you have APTIO IV, V.

I have no problems with Insyde and OC.

[Andrw0380]

11 hours ago, Andrw0380 said:

Yeah sorry I did research and found the Vanilla Desktop guide for Kaby Lake, but can't find this guide that you mentioned. Do you have a link for reference?

 

Thanks for the suggestion as that did fix the issue! Wanted to ask another question. I was looking at the guides I could find and how do you drop say the PtidDevc and xh_OEMBD ACPI tables? In Clover, I could just define the table names, but with OC in the examples I see to drop CPU tables, you have to define the table numbers. Just wanted to clear up some ACPI errors I see in verbose.

Hey guys, per my last post, was wondering if anyone could point me in the right direction for removing ACPI tables? I've read the configuration.pdf which details what each table needs for the Block section, but if someone could provide me an example for removing the PtidDevc and xh_OEMBD tables as I am getting ACPI errors and had to remove them on Clover.

[Andrey1970]

5 hours ago, obus said:

According to the manual the message: "Only N/256 slide values are usable" should be in the log but I can't find that message.

To see the message about slide, necessary enable ProvideCustomSlide.

If the message is "All slide", disable ProvideCustomSlide.

[Pavo]

11 hours ago, Andrw0380 said:

Yeah sorry I did research and found the Vanilla Desktop guide for Kaby Lake, but can't find this guide that you mentioned. Do you have a link for reference?

 

Thanks for the suggestion as that did fix the issue! Wanted to ask another question. I was looking at the guides I could find and how do you drop say the PtidDevc and xh_OEMBD ACPI tables? In Clover, I could just define the table names, but with OC in the examples I see to drop CPU tables, you have to define the table numbers. Just wanted to clear up some ACPI errors I see in verbose.

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

8 hours ago, FredWst said:

 

@Pavo

 

I read doc but when an option is present since many months how to believe (explain) that it was the issue ?

I just enable ProvideConsoleGop now works fine -v and Apple boot screen. (Strange for an option related to console)

Dont understand the relation between AptioFixMemory and this option.

 

so

with AptioFixMemory : ProvideConsoleGop = false

with FwRuntimeServices : ProvideConsoleGop = true

Works now on all my hack. (Aptio IV or Aptio V)

 

Fred

 

 

AptioFixMemory functions have been split between OpenCore itself and FxRuntimeServices. The function that AptioFixMemory provided for the Apple logo and verbose booting are now part of OpenCore Console protocols.

[obus]

58 minutes ago, Andrey1970 said:

To see the message about slide, necessary enable ProvideCustomSlide.

If the message is "All slide", disable ProvideCustomSlide.

@Andrey1970

So if I understand you correct I should have ProvideCustomSlide enabled with this message in the log?

16:290 00:015 OCABC: Only 174/256 slide values are usable!
16:296 00:005 OCABC: Valid slides - 0-173

Edited August 12, 2019 by obus

[NorthAmTrans]

@Pavo Trying to switch to FWRuntimeservices.efi but it won't boot in this manner. I keep reading the doc but I seem to be missing something. Can you clue me in?

[Andrey1970]

11 minutes ago, obus said:

@Andrey1970

So if I understand you correct I should have ProvideCustomSlide enabled with this message in the log?

16:290 00:015 OCABC: Only 174/256 slide values are usable!
16:296 00:005 OCABC: Valid slides - 0-173

Yes

[maddie]

1 hour ago, NorthAmTrans said:

@Pavo Trying to switch to FWRuntimeservices.efi but it won't boot in this manner. I keep reading the doc but I seem to be missing something. Can you clue me in?

 

You have to get the whole set of OpenCore (BOOTx64.efi, OpenCore.efi etc) that is up to date as the FwRuntimeServices, and enable the necessary Booter quirks in your config.plist to get equivalent functionalities from the legacy AptioMemoryFix.

[NorthAmTrans]

15 minutes ago, maddie said:

 

You have to get the whole set of OpenCore (BOOTx64.efi, OpenCore.efi etc) that is up to date as the FwRuntimeServices, and enable the necessary Booter quirks in your config.plist to get equivalent functionalities from the legacy AptioMemoryFix.

 

Just updated both EFI's with the newest ones. Im a little confused one which booster quirks need to be adjusted. 

[maddie]

1 minute ago, NorthAmTrans said:

 

Just updated both EFI's with the newest ones. Im a little confused one which booster quirks need to be adjusted. 

 

Maybe upload your EFI folder? Also adding your build to your signature would be a big help

[NorthAmTrans]

2 minutes ago, maddie said:

 

Maybe upload your EFI folder? Also adding your build to your signature would be a big help

 

For all the shaming I've done on other forums for people not having their build signature I can't believe I didn't add it here. Shame on me. Updating now, here's the EFI.

EFI.zip

[maddie]

On 5/21/2019 at 12:39 AM, steve3d said:

as for my boot screen resolution, I have a log entry says:

00:000 00:000 OC: Missing GOP on ConsoleOutHandle, will install - Unsupported

I think this is the problem that I always have such low resolution, and of course, I have ProvideConsoleGop = true set in my config.plist

 

I have i9-9900k with igpu enabled and radeon vii only.

 

and also, it seems the latest version of opencore already fixed my z390 board shutdown. now I can shutdown/reboot, will try another z390 board tomorrow.

 

EDIT: Debug version can properly shutdown, release version still reboot when shutdown.

 

Did you manage to solve the resolution problem? I'm having the same problem here with my Z370 build, with iGPU and Vega 64.

 

 

SOLVED: The culprit was the SanitiseClearScreen option, disabling it makes the resolution look perfect!

Edited August 12, 2019 by maddie
Solved

[Andrw0380]

3 hours ago, Pavo said:

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

AptioFixMemory functions have been split between OpenCore itself and FxRuntimeServices. The function that AptioFixMemory provided for the Apple logo and verbose booting are now part of OpenCore Console protocols.

Hey thanks for that. I was wondering the data fields for OemTableId and TableSignature, how will I translate the following SSDTs into the proper values to put in there? I'm sorry I am new to OpenCore as been using Clover awhile and this is the last thing I need to get working. The values Clover wants is String Values, but OpenCore needs data values which I don't where to get them for these files.

SSDT.zip

Edited August 12, 2019 by Andrw0380

[maddie]

13 minutes ago, NorthAmTrans said:

 

For all the shaming I've done on other forums for people not having their build signature I can't believe I didn't add it here. Shame on me. Updating now, here's the EFI.

EFI.zip

 

To be brutally honest, it doesn't seem that you put much effort into your config.plist  :x

After each OpenCore update, you have to check the Configuration.pdf from the repository to see if there's any changes to the config.plist. Like the Booter quirks I've mentioned, which is new in v0.0.4, was missing in your config.plist. It seems your version was from on or before v0.0.3, which also lacks the AvoidHighAlloc UEFI quirk.

 

I've added them for you and enabled some useful options in it. You might want to take a look before you're applying the changes.

config.plist

[NorthAmTrans]

12 minutes ago, maddie said:

 

To be brutally honest, it doesn't seem that you put much effort into your config.plist  :x

After each OpenCore update, you have to check the Configuration.pdf from the repository to see if there's any changes to the config.plist. Like the Booter quirks I've mentioned, which is new in v0.0.4, was missing in your config.plist. It seems your version was from on or before v0.0.3, which also lacks the AvoidHighAlloc UEFI quirk.

 

I've added them for you and enabled some useful options in it. You might want to take a look before you're applying the changes.

config.plist

 

Never mad at honesty here.

 

I've been keeping it super minimal while I get a grip on everything. I hope that didn't come off as lazy. Hell, I was happy to get a boot and have all my ACPI, Drivers, and Kexts load.

 

You're right, I grabbed the 0.0.4 boot and OpenCore.efi but didn't think to update config. 

 

I'm going to give this a look over and boot and report back. Thanks!

[maddie]

Just now, NorthAmTrans said:

 

Never mad at honesty here.

 

I've been keeping it super minimal while I get a grip on everything. I hope that didn't come off as lazy. Hell, I was happy to get a boot and have all my ACPI, Drivers, and Kexts load.

 

You're right, I grabbed the 0.0.4 boot and OpenCore.efi but didn't think to update config. 

 

I'm going to give this a look over and boot and report back. Thanks!

 

Always read the configuration carefully for every option in the config.plist. I know it's quite tedious, but it's necessary

 

You have a very similar build as mine, I have high hopes that it would work. Good luck!

[NorthAmTrans]

6 minutes ago, maddie said:

 

Always read the configuration carefully for every option in the config.plist. I know it's quite tedious, but it's necessary

 

You have a very similar build as mine, I have high hopes that it would work. Good luck!

 

Well thanks for the help. Everything loaded to my liking! I'll read more next update and hopefully help some along with the way. I'll also do some reading on how to get a boot log and make sure everything is going swell in boot.