Jump to content

2,521 posts in this topic

Recommended Posts

Posted (edited)
On 8/14/2019 at 8:32 AM, NorthAmTrans said:

Used Debug and Target 67 (bit mask was fun to learn in the doc and with some google) and got my first boot log. Rad. Not sure that's the best value for that but it's what I landed on and seems to have given me a very descriptive log.

 

I see there's a ton of searching going on for my APFS volume. Should I be setting this so boot loader only sees my one APFS drive to avoid needless search and fail? 

 

Also this seems funny to me. Normal?

 

@maddie

Tagging you because you've been super helpful. I just moved OC off my flash drive. Very happy.


18:770 00:057 OC: OcLoadNvramSupport...
18:827 00:057 OC: Invalid nvram data
18:882 00:055 OC: Deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - Not Found
18:939 00:056 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - Success

 

 

 

 

opencore-2019-08-13-222528.txt

 

Totally missed this. I think those warnings should be fine as long as you have working NVRAM. I think it's just being verbose telling you that the NVRAM->Add/Block sections in your config.plist are being parsed.

 

As for the APFS volume scanning, it's fine, don't worry about it.

Edited by maddie

Share this post


Link to post
Share on other sites
Advertisement
11 hours ago, justin said:

 

 

cattyhouse is me. 

 

Is this your repo: https://github.com/cattyhouse/oc-guide

 

I'm so sorry: on my new Z390 Hack, I don't have Internet for the moment. I can't use this recovery internet method. What's a pity :cry: I've internet only by local sharing wifi/ethernet with my previous Hack (Ivybridge).

Share this post


Link to post
Share on other sites
1 minute ago, Matgen84 said:

 

Is this your repo: https://github.com/cattyhouse/oc-guide

 

I'm so sorry: on my new Z390 Hack, I don't have Internet for the moment. I can't use this recovery internet method. What's a pity :cry: I've internet only by local sharing wifi/ethernet with my previous Hack (Ivybridge).


Make USB installer from another mac system. Install OC Bootloader and boot from it. It's simple like that

Share this post


Link to post
Share on other sites
2 minutes ago, Andres ZeroCross said:


Make USB installer from another mac system. Install OC Bootloader and boot from it. It's simple like that

 

I know that. :)

 

But without internet connection on the new Z390 Hack, how I can install macOS with recovery method (dmg file)?

Share this post


Link to post
Share on other sites
27 minutes ago, Matgen84 said:

 

I know that. :)

 

But without internet connection on the new Z390 Hack, how I can install macOS with recovery method (dmg file)?

 

If No internet, no way to install via Recovery method. 

Share this post


Link to post
Share on other sites
9 minutes ago, justin said:

 

If No internet, no way to install via Recovery method. 

 

Do you think with InstallESD.dmg (extract from InstallmacOS.app), I can use OC USB to install Catalina :)

Share this post


Link to post
Share on other sites
32 minutes ago, Matgen84 said:

 

Do you think with InstallESD.dmg (extract from InstallmacOS.app), I can use OC USB to install Catalina :)

 

What's the problem with createinstallmedia method?? Why would you try to do that??

Share this post


Link to post
Share on other sites
38 minutes ago, Matgen84 said:

 

Do you think with InstallESD.dmg (extract from InstallmacOS.app), I can use OC USB to install Catalina :)

Hahaha, you have "Install macOS Catalina Beta.app". Then just make installer with "createinstallmedia" method, then install OC bootloader to it. Boot and install.

What's problem with this???? :D

Share this post


Link to post
Share on other sites
7 minutes ago, maddie said:

 

What's the problem with createinstallmedia method?? Why would you try to do that??

 

Because I can't install with createinstallmedia method

Share this post


Link to post
Share on other sites
Posted (edited)
18 minutes ago, Matgen84 said:

 

Because I can't install with createinstallmedia method

 

What problem did you encounter when you use createinstallmedia method? I think I have yet to see you tell us what's going wrong with it.

 

OK, my bad. The pictures didn't load when I posted above. It's the Z390 rig in your signature? Can you post your OC EFI folder?

Edited by maddie

Share this post


Link to post
Share on other sites
Posted (edited)
27 minutes ago, Andres ZeroCross said:

Hahaha, you have "Install macOS Catalina Beta.app". Then just make installer with "createinstallmedia" method, then install OC bootloader to it. Boot and install.

What's problem with this???? :D

 

Because I can't install with createinstallmedia method. Just my opinion, there is a issue with DSDT or something else. I don't know. (Images below)

00000IMG_00000_BURST20190815171117119_COVER.jpg

00000IMG_00000_BURST20190815171144881_COVER.jpg

DSDT.aml.zip

EFI.zip

Edited by Matgen84
Add DSDT + EFI Folder

Share this post


Link to post
Share on other sites
12 minutes ago, Matgen84 said:

 

Because I can't install with createinstallmedia method. Just my opinion, there is a issue with DSDT or something else. I don't know. (Images below)

00000IMG_00000_BURST20190815171117119_COVER.jpg

00000IMG_00000_BURST20190815171144881_COVER.jpg

DSDT.aml.zip

EFI.zip

This is not a OC issue. OC can in fact install macOS using the createinstallmedia method, if you can’t then it is something that you are doing to your config or ACPI tables that isn’t allowing it to boot. As per to OC docs, you should not be injecting a patched DSDT.

Share this post


Link to post
Share on other sites
3 minutes ago, Pavo said:

This is not a OC issue. OC can in fact install macOS using the createinstallmedia method, if you can’t then it is something that you are doing to your config or ACPI tables that isn’t allowing it to boot. As per to OC docs, you should not be injecting a patched DSDT.

 

OK. Thanks.

 

I use OC USB drive to test OpenCore. I can boot on Catalina HD (CLOVER)

Share this post


Link to post
Share on other sites
28 minutes ago, Pavo said:

This is not a OC issue. OC can in fact install macOS using the createinstallmedia method, if you can’t then it is something that you are doing to your config or ACPI tables that isn’t allowing it to boot. As per to OC docs, you should not be injecting a patched DSDT.

 

DSDT is in OC structure in Configuration Docs. I don't understand. 

 

 

Capture d’écran 2019-08-15 à 18.08.21.png

Share this post


Link to post
Share on other sites
13 minutes ago, Matgen84 said:

 

DSDT is in OC structure in Configuration Docs. I don't understand. 

 

 

Capture d’écran 2019-08-15 à 18.08.21.png

 

Everything in gray background is optional, you don't need them to boot.

 

Just make sure that:

 

1. You have OpenCore correctly installed with above directory structure

2. You have config.plist configured correctly for your hardware, and BIOS settings too

3. Add appropriate EFI Drivers to Drivers folder, and kexts to Kexts folder, and add them into your config.plist

Share this post


Link to post
Share on other sites
4 minutes ago, gengik84 said:

It's only example for efi's structure and it is not mandatory to use dsdt.

 

What do you means 'sorry for my bad english) about DSDT.

 

There is another issue now when I try to install via OC USB.

 

 

2.jpg

Share this post


Link to post
Share on other sites

check your config in PlatformInfo...you have MP 5.1 (Mac-F221BEC8)  now and/or incorrect setting

Please read carefully configuration.pdf and check again yours configuration.

 

Share this post


Link to post
Share on other sites
18 minutes ago, Matgen84 said:

 

What do you means 'sorry for my bad english) about DSDT.

 

There is another issue now when I try to install via OC USB.

 

 

2.jpg


As long as you didn't update your BIOS, just use patched DSDT that i have made.

Your problem above is about USB Limit, just enable limit XCH from your config.plist. Your another problem is SMBIOS,,, Mac-F221BEC8 is not supported by Catalina.
 

Share this post


Link to post
Share on other sites
Posted (edited)

What is this??? DisableIOMapper in Booter? Did you really read doc to edit config.plist??. How can you blame it into patched DSDT????

This is the reason i always refuse to edit DSDT for someone, they change all configuration except DSDT then they blame it into DSDT if there is a mistake with his system

 

image.thumb.png.5135b4d1531f180ab54a8d95bf012c55.png

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
9 minutes ago, Andres ZeroCross said:


As long as you didn't update your BIOS, just use patched DSDT that i have made.

Your problem above is about USB Limit, just enable limit XCH from your config.plist. Your another problem is SMBIOS,,, Mac-F221BEC8 is not supported by Catalina.
 

 

I use your DSDT, enable Limit XCH from config.plist. I don't why SMBIOS is incorrect. Now I put Imac19,1

 

I don't blame your DSDT. :)  I'm just trying to learn, understand what I'm doing with this new bootloader. Even if I make mistakes.

 

I can launch macOS Utilities and try to install Catalina (tomorrow morning).

Share this post


Link to post
Share on other sites

Hi guys!

 

Question about the latest official VirtualSMC version 1.0.7.

 

As soon as a change from version 1.0.6 to 1.0.7 and reboot my hack won't boot to Desktop. It will show Apple logo with boot-progress but after 10 seconds or so my screen goes black and stays black, can't remote login nada. Even after several minutes still black screen.

 

The exact same config except change back to VirtualSMC 1.0.6 from power on to Desktop in about 25 seconds.

This is on Catalina 10.15 Beta (19A526h), latest official OC 0.04 and drivers and kexts.

 

I didn't see anything on the VirtualSMC Github that anything have to be adjusted in config.plist but I have the feeling that VirtualSMC 1.0.7 on my system isn't loading and I don't get why.

 

Any clues? Thanks!

 

Share this post


Link to post
Share on other sites
12 minutes ago, Matgen84 said:

 

I use your DSDT, enable Limit XCH from config.plist. I don't why SMBIOS is incorrect. Now I put Imac19,1

 

I don't blame your DSDT. :)  I'm just trying to learn, understand what I'm doing with this new bootloader. Even if I make mistakes.

 

I can launch macOS Utilities and try to install Catalina (tomorrow morning).


it's better for you to delete DSDT if you don't understand how to edit config.plist. You only blame the patched DSDT. DSDT + Config.plist is a couple. If you put wrong config.plist for DSDT then it will break your system. 

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 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/viewtopic.php?f=28&t=10578
      *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 notiflux
      Unfortunately, this project has come to a halt, at least for now. I don't have enough time to work on the project and it's lacking behind, so please don't use it for configuring OpenCore, it will produce broken configuration files.
      I will leave the source code on GitHub, so in case someone wants to take over the project, they can.
       
      original post:
      OpenCore Configurator Source
    • 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 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  
       
×