Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,887 posts in this topic

Recommended Posts

NorthAmTrans
NorthAmTrans
Posted
Posted (edited)
28 minutes ago, maddie said:

 

Your 'drivers' and 'kext' folder should be 'Drivers' and 'Kexts'. It's case-sensitive.

And BOOTED. Big thanks.

 

Now to figure out why my ACPI stuff isn’t loading. I’m thinking I mislabeled the folder there as well. 

 

EDIT: Definitely need to change it from Custom to "Add" and I have no idea how I landed there in the first place.

 

Helpful for others who aren't as knowledgable. Im sure its posted it well before this comment but if you're this far in here it is again. https://insanelymacdiscord.github.io/Getting-Started-With-OpenCore/

Edited by NorthAmTrans
Dumb Ass Again
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted
4 hours ago, Pavo said:

I don't know why no one reads the docs. Located under Tips and Tricks in the docs. The key quirk here is ProvideConsoleGop in UEFI quirks.

  


How can I migrate from AptioMemoryFix?
Behaviour similar to that of AptioMemoryFix can be obtained by installing FwRuntimeServices driver and enabling the quirks listed below. Please note, that most of these are not necessary to be enabled. Refer to their individual descriptions in this document for more details.
• ProvideConsoleGop (UEFI quirk) 
• AvoidRuntimeDefrag
• DiscardHibernateMap
• EnableSafeModeSlide
• EnableWriteUnprotector 
• ForceExitBootServices 
• ProtectCsmRegion
• ProvideCustomSlide
• SetupVirtualMap 
• ShrinkMemoryMap

 

@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

 

 

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
12 hours ago, LAbyOne said:

I maybe have misunderstood your point, 

but, hackintosh is not a brand, just a choice anyone make for its own purpose

hence the unavoidable need to understand what they are doing, its something you take on yourself first, then using places like insanelymac you can find help to solve issues, but the base is you have to learn first

Sure Clover simplified the installation providing an installer.... but if you then have to modify your config or any other file you will mount your EFI and make the changes... 

its only a bootloader nothing similar to what dosdude1 did

So i can't really see what would make this one so uncomfortable to set up.

then again I maybe have misunderstood your point...

 

The real problem in my opinion 

is that there are also many people now too *miseducated to be able to give real contribution, quoting what you said " people want things to be easier and faster", well people must understand also that sometimes things are different and require a different spirit.

 

PS

*miseducated = people who just want to find the supper ready, and can't even make a sandwich by themselves :)

 

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 :)

Link to comment
Share on other sites
vandroiy2012
vandroiy2012
Posted
Posted (edited)
2 hours ago, FredWst said:

so

with AptioFixMemory : ProvideConsoleGop = false

with FwRuntimeServices : ProvideConsoleGop = true

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

 

Fred

 

 

 

AptioMemoryFix is deprecated. Part of it migrated to OpenCore and other part to FwRuntimeServices. 

You should not use AptioMemoryFix in OpenCore at all!! Forget about it!!! It is now only for Clover. 

Edited by vandroiy2012
  • Like 2
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted
19 minutes ago, vandroiy2012 said:

 

AptioMemoryFix is deprecated. Part of it migrated to OpenCore and other part to FwRuntimeServices. 

You should not use AptioMemoryFix in OpenCore at all!! Forget about it!!! It is now only for Clover. 

 

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 

 

 

  • Like 1
Link to comment
Share on other sites
vit9696
vit9696
Posted
Posted

@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 =)

  • Like 2
Link to comment
Share on other sites
justin
justin
Posted
Posted
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. 

  • Thanks 1
Link to comment
Share on other sites
vandroiy2012
vandroiy2012
Posted
Posted
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

  1. 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. 

  • Thanks 1
Link to comment
Share on other sites
justin
justin
Posted
Posted
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? 

  • Like 1
  • Haha 1
Link to comment
Share on other sites
obus
obus
Posted
Posted

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

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
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 :)

Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted
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

 

  • Like 1
Link to comment
Share on other sites
LAbyOne
LAbyOne
Posted
Posted
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

  • Like 1
Link to comment
Share on other sites
Andrw0380
Andrw0380
Posted
Posted
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.

Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
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.

  • Like 1
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted
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.

  • Like 2
Link to comment
Share on other sites
obus
obus
Posted
Posted (edited)
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 by obus
Link to comment
Share on other sites
maddie
maddie
Posted
Posted
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.

Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
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. 

Link to comment
Share on other sites
maddie
maddie
Posted
Posted
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 :)

Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
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

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...