Jump to content

2,147 posts in this topic

Recommended Posts

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

Share this post


Link to post
Share on other sites
Advertisement
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

 

 

Share this post


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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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 

 

 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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. 

Share this post


Link to post
Share on other sites
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. 

Share this post


Link to post
Share on other sites
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? 

Share this post


Link to post
Share on other sites

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

Share this post


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

Share this post


Link to post
Share on other sites
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

 

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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. 

Share this post


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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By clockT
      sono un pò arrugginito ..e volevo chiedere un aiuto su come installare opencore anzichè clover. ho provato ma dopo il post installazione riesco solo a far partire catalina tramite pendrive. quale congifurazione sbaglio?
      EFI.zip

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/download/file.php?id=24376
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By rusty-bits
      Command line tool that will build a working EFI folder based on the settings in the config.plist file.
      https://github.com/rusty-bits/OC-tool
       
       
      you can also copy your config.plist to the RELEASE folder and double-click OC-tool  
      this is the same as running
      ./OC-tool -uo build release from the command line  
       
      see the wiki for more info  
       
      https://github.com/rusty-bits/OC-tool/wiki
       
      added functionality to the -T option  (update ver 1.6pt)  

      TUI (Text based User Interface) now has limited functionality  
      kexts, drivers, tools and quirks can be toggled on or off, then by pressing g an EFI folder will be created based on what you set  
       
       
      working:  
      - BOOT/BOOTx64.efi built automatically  
      - OC/OpenCore.efi build automatically
      - OC/ACPI folder built automatically from settings in ACPI/Add section of config.plist  
      - - the tool can compile .dsl to .aml on the fly if iasl is present, but I recommend compiling them to .aml yourself for the tool to move over  
      - OC/Drivers folder built automatically from settings in UEFI/Drivers section of config.plist  
      - OC/kexts folder built automatically from settings in Kernel/Add section of config.plist  
      - OC/Tools/Shell.efi built automatically from setings in Misc/Tools section of config.plist  
      - OC/vault.plist and OC/vault.sig are built automatically from the Misc/Security/RequireVault setting in config.plist  
      - can specify debug or release version of resources to be built  
      - parses plist files internally, no longer needs to call /usr/libexec/PlistBuddy which may not exist on Catalina  
      - kexts, drivers, tools and quirks can be enabled or disabled before building the EFI by using the -T option  
       
×