Jump to content

3,286 posts in this topic

Recommended Posts

Advertisement

I've been following OpenCore for some time and want to transition from Clover. Is there any reason not to? Is everything working as it should?

Share this post


Link to post
Share on other sites
8 hours ago, Amateur85 said:

Good question, I know the CPU is a mobile one since it is the same as the macbook pro 2019 so I assume the MB is mobile as well. It this mini pc: https://www.anandtech.com/show/13931/eglobal-nuc-pc-packs-hex-core-i7-8750hk but then it's the 8850h version.  SYWZ S200 series is the MB name. GPU is the internal UHD630.

Thanks Mat, I used the EC SSDT from the vanilla desktop guide, but I reckon this one is more comparable to a laptop and need renaming ec to the right value. I’ll try later.

Share this post


Link to post
Share on other sites

Fixed now memory modules misconfigured

 

MacProMemoryNotificationDisabler

https://github.com/IOIIIO/MacProMemoryNotificationDisabler

Test for MacPro7,1 Debug.zip

Update Lilu.Kext

Thanks Lilu & Team.

Edited by nmano

Share this post


Link to post
Share on other sites
On 2/14/2020 at 3:35 PM, Download-Fritz said:

@mhkmichaell try UnblockFsConnect

@Download-Fritz Thank You! That’s  it!

I must read much more carefull. 
Now I can start playing! 

AAF3BD43-4661-43F9-956C-CA80D475FD04.jpeg
 

 

@telepatithanks!  I will try. But the problem was UnblockFsConnect. In Hp laptop must be set to YES. 

Edited by mhkmichaell

Share this post


Link to post
Share on other sites

Guys, could you please someone confirm me; is ApfsDriverLoader.efi mandatory for OpenCore? if it is why this efi not implemented to OpenCorePkg?

Edited by telepati

Share this post


Link to post
Share on other sites

@MacNB, OpenCore is not starting two times, it is just the way the flow goes, firstly an existing OpenCore instance is looked for, then a new one is allocated on failure.

 

Currently there is no way to redirect early boot text to the log in OpenCore due to not yet loaded configuration. In theory it is possible to store this data to a temporary buffer, but we have not had much need in this so far. Reasonably clean patches implementing this feature is what we can merge though.

 

Release builds should print nothing but warnings and errors (you have a debug build of ApfsImageLoader so you see its prints), this is how we designed OC and all other products. You can check a few pages back for more details on this choice.

 

@telepati, we plan to merge ApfsDriverLoader to OpenCore in the future. For now you have to use it for APFS support.

Share this post


Link to post
Share on other sites

Is there any thoughts of implement :

 

a) choose which config.plist to load (from bootpicker) ?

b) choose which kexts to drop (also from bootpicker) ?

 

 

Share this post


Link to post
Share on other sites

We think these features are impractical and have no plans for them.

 

In case one needs to debug his configuration, he can always boot from USB and configure on a second computer. If this is not an option, there always is UEFI Shell, which provides easy file management enough not only to rename the files, but also edit their contents.

 

This pretty much covers both the need to choose the configuration manually and the need to set different options. Picker GUI is not really meant to be a Flight Control Console, it is meant to be a way to optionally (as normally you hide it by default) provide an approach to choose an operating system to boot in a simple and intuitive way. Just like Apple BootPicker on a Mac.

Share this post


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

Release builds should print nothing but warnings and errors (you have a debug build of ApfsImageLoader so you see its prints), this is how we designed OC and all other products. You can check a few pages back for more details on this choice.

OC was built using @Pavo's OC Builder without debug. I assume ApfsImageLoader is one of the modules in OC and looks it's still built with debug flag (??)

Share this post


Link to post
Share on other sites
On 2/8/2020 at 2:10 PM, nmano said:

9 ACPI Sleep patch

9 ACPI patch for sleep config-OC.plist  All Intel Motherboard. I test X99,X299.

 

210922434_ScreenShot2020-02-08at8_11_30AM.png.dde37014e10c3d945587f88a5490875b.png

 

I have big sleep problems with my Aorus B450i Pro Wifi, Ryzen 3600 build. Testet this sleep patch and also combinations with HibernationFix kext. No progress at all. When I choose sleep the monitor goes black but nothing happens to the machine. Fans still blowing. Then I can not wake the monitor and I have to restart the machine. I am running OC 0.5.5, Catalina 10.15.3

Edited by aslebenoni

Share this post


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

I have big sleep problems with my Aorus B450i Pro Wifi, Ryzen 3600 build. Testet this sleep patch and also combinations with HibernationFix kext. No progress at all. When I choose sleep the monitor goes black but nothing happens to the machine. Fans still blowing. Then I can not wake the monitor and I have to restart the machine. I am running OC 0.5.5, Catalina 10.15.3

These patches will do nothing For AMD hacks. Most the time to enable sleep/wake For AMD hacks, you just need to properly map your USB ports.

Share this post


Link to post
Share on other sites
2 hours ago, Pavo said:

These patches will do nothing For AMD hacks. Most the time to enable sleep/wake For AMD hacks, you just need to properly map your USB ports.

Ok. So I should just remove the patches from config.plist and also the Hibernatiionfixup.kext? I made the first patches with SSDTTime in Windows and moved the files to OC/ACPI . Then I made a SSDT-USB.aml with Hackintool and placed it in the same folder. Should I instead use the USBMap.command to create the file and replace the one from Hackintool? 

Share this post


Link to post
Share on other sites
8 minutes ago, aslebenoni said:

Ok. So I should just remove the patches from config.plist and also the Hibernatiionfixup.kext? I made the first patches with SSDTTime in Windows and moved the files to OC/ACPI . Then I made a SSDT-USB.aml with Hackintool and placed it in the same folder. Should I instead use the USBMap.command to create the file and replace the one from Hackintool? 

Hibernatiionfixup.kext does nothing For AMD hacks, Hackintool doesn't work well with AMD hack to generate USB mapping. You need to do it the old fashion way of mapping. https://github.com/khronokernel/Opencore-Vanilla-Desktop-Guide/blob/master/AMD/AMD-USB-map.md

Share this post


Link to post
Share on other sites
1 hour ago, Pavo said:

Hibernatiionfixup.kext does nothing For AMD hacks, Hackintool doesn't work well with AMD hack to generate USB mapping. You need to do it the old fashion way of mapping. https://github.com/khronokernel/Opencore-Vanilla-Desktop-Guide/blob/master/AMD/AMD-USB-map.md

Thanks. I am trying to follow that guide. Like I wrote before I moved the aml files from SSDTTime into ACPI. Was that correct? .
├── ACPI
│   ├── DSDT.aml
│   ├── SSDT-EC.aml
│   └── SSDT-EC.dsl

Now when I open MaciASL like it says "Open MaciASL on the target machine and you'll be presented with your system DSDT, that simple!" I get an error, see attached screenshot. So where do I get this system DSDT from? I am stuck there since I have nothing to edit!

iASL error.png

xhc.png

Edited by aslebenoni

Share this post


Link to post
Share on other sites

Anybody have any idea why I would lose my USBs after upgrading from 5.4 to 5.6 using the same USB SSDT

Any suggestions how to get them back.

Here I attached my EFI could anyone take a look at it and see where I went wrong please and thanks   

EFI.zip

Edited by galisrule

Share this post


Link to post
Share on other sites
46 minutes ago, galisrule said:

Anybody have any idea why I would lose my USBs after upgrading from 5.4 to 5.6 using the same USB SSDT

Any suggestions how to get them back.

Here I attached my EFI could anyone take a look at it and see where I went wrong please and thanks   

EFI.zip

1434225043_2020-02-1702_34_18.png.aa30aeac28d68fc6c5a19e7701c2f255.png

I see ndk fork, аsk in ndk topic.

 

Share this post


Link to post
Share on other sites

Guys, I tested all outside links in the Doc.pdf and just three of them giving 404 error, need to fix or remove.

 

See VerifyMsrE2 nots for more details. (Page 14) Also "nots" must to "notes"

Use GopUpdate (Page 14)

Known formats are described in macserial. (Page 43)

 

 

Share this post


Link to post
Share on other sites

@Andrey1970 thanks for replying I got both ndk and the original on 2 separate drives and its the same in both even with EnableForAll on or off 

The funniest thing is when I switch back to 5.4 EFI everything works perfect again hmmmmmm  

Edited by galisrule

Share this post


Link to post
Share on other sites
On 5/2/2019 at 12:22 AM, MacFriedIntel said:

Noticed with Opencore, GPU has to be UEFI, Legacy cards such as Nvidia GTX 650 Ti etc OC won't boot. Just Setup a MSI Gaming 5 Z97 with RX560, Booted and Fully Native also displaying Quad-Core Xeon as Processor, as before with clover it was Unknown. Tested with macOS 10.12. :drool:

Hi,

 

I have been trying to install OC on Z97X gaming 5 (Catalina). 

 

Things is i used the sample.plist and then add all the stuff i think is required.

 

So OC runs. I don't get any error messages. and execution seem to have stopped.  See image below

 

Do you have any suggestions ?

 

See here for debug output: https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=343052

and for archive : https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=343053

 

IMG_6429.jpeg

Share this post


Link to post
Share on other sites
8 hours ago, galisrule said:

Anybody have any idea why I would lose my USBs after upgrading from 5.4 to 5.6 using the same USB SSDT

Any suggestions how to get them back.

Here I attached my EFI could anyone take a look at it and see where I went wrong please and thanks   

EFI.zip

NO 0.5.6 release . Bettas can come out 1-3 times a day with changes, if you do not understand what you are doing, then why update. And read the documentation, everything is there.

Share this post


Link to post
Share on other sites

Hey all, just finished my hackintosh install (opencore / catalina).  All seems to be working really well except I ran geekbench 5 gpu test and its showing my 5700 XT hitting max of 875 mhz, is there anything I can look into to fix this?

 

thanks!

 

EFI.zip

Edited by doox00

Share this post


Link to post
Share on other sites

@Pavo I recently used your OCBuilder and selected WITHOUT DEBUG and WITH kexts.

 

1. But I am still getting debug output in the log file. According to @vit9696 it's because ApfsDriverLoader is built WITH debug

2. There's a new IntelMausiEthernet kext v2.5.0 generated that does not inject into the kernel

 

See log:

00:000 00:000 Starting ApfsDriverLoader ver. 2.1.5
01:395 01:395 EfiBootRecord located at: 16973839 block
01:400 00:004 Real image size: 628216
01:407 00:007 Signature verified!
01:791 00:383 EfiBootRecord located at: 0 block
05:140 03:349 EfiBootRecord located at: 16035933 block
05:145 00:005 Real image size: 602936
05:153 00:007 Signature verified!
05:373 00:220 EfiBootRecord located at: 4300351 block
05:378 00:005 Real image size: 583992
05:386 00:007 Signature verified!
11:014 05:628 OC: Prelink injection IntelMausiEthernet.kext (Intel Ethernet LAN) - Invalid Parameter

For 2., I replaced the IntelMausiEthernet kext with v 2.4.1d1 and that one works fine.

 

Does ApfsDriverLoader generate debug out even if not built with debug ?

Want does "Invalid Parameter" mean ?

Share this post


Link to post
Share on other sites
53 minutes ago, MacNB said:

@Pavo I recently used your OCBuilder and selected WITHOUT DEBUG and WITH kexts.

 

1. But I am still getting debug output in the log file. According to @vit9696 it's because ApfsDriverLoader is built WITH debug

2. There's a new IntelMausiEthernet kext v2.5.0 generated that does not inject into the kernel

 

See log:


00:000 00:000 Starting ApfsDriverLoader ver. 2.1.5
01:395 01:395 EfiBootRecord located at: 16973839 block
01:400 00:004 Real image size: 628216
01:407 00:007 Signature verified!
01:791 00:383 EfiBootRecord located at: 0 block
05:140 03:349 EfiBootRecord located at: 16035933 block
05:145 00:005 Real image size: 602936
05:153 00:007 Signature verified!
05:373 00:220 EfiBootRecord located at: 4300351 block
05:378 00:005 Real image size: 583992
05:386 00:007 Signature verified!
11:014 05:628 OC: Prelink injection IntelMausiEthernet.kext (Intel Ethernet LAN) - Invalid Parameter

For 2., I replaced the IntelMausiEthernet kext with v 2.4.1d1 and that one works fine.

 

Does ApfsDriverLoader generate debug out even if not built with debug ?

Want does "Invalid Parameter" mean ?

1. As you can see from the below code snippet ApfsDriverLoader is not being built with DEBUG options. You can look at the code yourself at https://github.com/Pavo-IM/ocbuilder/blob/master/OCBuilder/release.command

applesupportclone
unset WORKSPACE
unset PACKAGES_PATH
cd "${BUILD_DIR}/AppleSupportPkg"
mkdir Binaries >/dev/null || exit 1
cd Binaries >/dev/null || exit 1
ln -s ../UDK/Build/AppleSupportPkg/RELEASE_XCODE5/X64 RELEASE >/dev/null || exit 1
cd .. >/dev/null || exit 1
applesupportudkclone
cd UDK
applesupportpkgclone
ln -s .. AppleSupportPkg >/dev/null || exit 1
make -C BaseTools >/dev/null || exit 1
sleep 1
unset WORKSPACE
unset EDK_TOOLS_PATH
export NASM_PREFIX=/usr/local/bin/
source edksetup.sh --reconfig >/dev/null || exit 1
sleep 1
echo "Compiling the latest commited Release version of AppleSupportPkg..."
build -a X64 -b RELEASE -t XCODE5 -p AppleSupportPkg/AppleSupportPkg.dsc >/dev/null || exit 1

2. All OCBuilder does is clone the repo of the kexts and builds the master branch of that repo. So if there is a kext issue its an issue that the owner of the repo needs to fix, not OCBuilder.

buildrelease() {
  xcodebuild -configuration Release  >/dev/null || exit 1
}

echo "Cloning IntelMausiEthernet repo..."
git clone https://github.com/Mieze/IntelMausiEthernet.git >/dev/null || exit 1
cd "${BUILD_DIR}/IntelMausiEthernet"
echo "Compiling the latest commited Release version of IntelMausiEthernet..."
buildrelease
echo "IntelMausiEthernet Release Completed..."

 

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 DI2edd
      Hi,
       
      I'm writing from a Catalina QEMU/KVM VM which, I must say, works pretty damn well besides the fact that rebooting just doesn't work. But first, a bit of background:
      I'm using OpenCore 0.5.5 through DuetPkg because I'm forced on SeaBIOS (legacy boot) because of legacy IGD passthrough (OVMF doesn't support the semi-hack that's needed for it to function), and that works well enough; I switched from Clover because it didn't allow me to use the "host" cpu model on QEMU, which OpenCore did, and so far so good.
       
      The problem is that, whenever i attempt a reboot, the screen would just turn black and thats's it. I can even see that every 30 seconds it polls the battery's status through ACPI (I modified QEMU for that and left some debugging printfs).
      On the other hand, shutting down works as expected. One thing I noticed is that, on shutdown, I can see the last line of verbose output on the screen is "CPU_HALTED", whereas on reboot I don't get that (don't even know if that's to be expected).
       
      The point is that I'm not even sure this is a bootloader issue, because I booted a Fedora live ISO through OpenCore, and that rebooted with no problems, but at the same time I remember that with Clover I didn't have such an issue. Perhaps it was one of Clover's "Fixes" that is not automatic with OpenCore?
       
      Anyway, I attached my config.plist.
       
      Thank you.
      config.plist
    • By SniperBuddy
      Hello guys,
      I'm relatively new to the world of hackintosh.
      I'm trying to install the latest Mac OS - Catalina with the help of Opencore, however, this is the error that's displayed while booting from the USB:
       
      https://drive.google.com/open?id=1Xd4V2wZ2fEsgRyfVcXlJHXMPGa85g2s3
       
      You can take a look at my config.plist file from here - https://drive.google.com/file/d/17FZpTcVp4RFSaxdm6yW4uELkt7MaLdmt/view?usp=sharing
       
      I'm using the Acer E575 G laptop with Kabylake (i5 7200u)
       
      Any help would be gladly appreciated!
       
      Edit: I've fixed this problem by following this guide completely - https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/intel-config.plist/kaby-lake
       
      This is due to OpenCore being unable to find any drives with the current ScanPolicy, setting to 0 will allow all boot options to be shown
       
       
       
       
       
       
       
    • By DanZiRuleZ
      Dear All, 
       
      trying to install Catalina on my ASUS Z87 Plus, I followed the Haswell guide to the letter, all set up now, USB stick boots ok, Catalina installs on SSD, but then when trying to boot it I am receiving Kernel Panic and no idea how to move forward. 
       
      Have the debug options, but opencore will only dump boot messages where I don't see much sticking out.
       
      My last resort would be just installing clover on the already installed SSD's EFI partition, it at all possible. High Sierra is working fine and I did get Clover with Mojave once but stuck with High Sierra with my GTX960 video card...
       
      Attached is the kernel panic and my EFI setup if anyone can help me troubleshoot.
      Many thanks
      D.
       

      EFI.zip
    • By n.d.k
      After several weeks of testing OC bootloader,  disecting its source code and also Clover's source code as well, I finally switch from Clover to OC as my main bootloader. Wait! don't get the wrong idea that OpenCore is better than Clover. They both work equally well, producing a bootable macOS as an end result with simliar boot time. OC design direction is different with Clover, I believe it's not intended as a Clover replacement, but more narrowing down to macOS specifically. However, macOS is not the only OS that i am using, so, i decided to add some minimal necessary source code modification to the OC to get some of the features I need. I like to share my customized OC forked https://github.com/n-d-k/OpenCorePkg , you have to compile it yourself if you want, i will not provide pre build binary.    
       
      Additional features/changes:
      ============
       
      [ Multi-Boot ]
        - ACPI patches are optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
        - Booter Quirtks, SMBIOS and Device Properties patches will only applied to macOS.
          
      [ Hotkeys ]
        - Full functional Hotkeys [1-9] corresponding to Boot Entry's Index number and dedicated W (Windows) / X (macOS) keys can be used without seeing Boot Picker.
        - While in boot picker, F10 can use to take a snapshot of the screen.
                
      [ Ui Boot Picker ]
        - Bios Date/time, auto boot to the same OS or manual set to always boot one OS mode, and OC version are displayed in boot picker.
        - Auto boot to previous booted OS (if Misc->Security->AllowSetDefault is NO/false).
        - macOS Recovery/Tools Entries are hidden by default, use Spacebar in Boot Menu as a toggle on/off to show/hide hidden entries.
                
      [ Custom Entries ]
         - Custom entries are now listed first in picker menu and by the orders they are appeared in Misc->Boot->Entries, before all other entries.
         - Ability to change entry name found by auto scanner by adding custom entry with the exact same device path,
           this will give users the option to complete change how all boot entries listed in Boot Picker.
          
      [ Others ]
         - No verbose apfs.efi driver loading (if using apfs.efi instead of ApfsDriverLoader.efi).
          - ndk-macbuild.tool script are set to compile with latest edk2 (One can easily set to stable edk2 if prefer).
          - NvmExpressDxe driver build script are also available for system without native nvme support. (Compatible with OC and Clover).
       
      Usage:
       - To build OpenCore, run "./ndk-macbuild.tool" at Terminal (require Xcode and Xcode Command Line Tool installed, and open xcode to accept license agreement before compiling).
       - To build NvmExpressDxe driver, run "./buildnvme.sh".
       
      4k screen resolutions

       
       

       
      Customized by @btwise

       
       
       
    • By Krani93
      Hi guys,
       
      I'm trying to install Catalina on a Lenovo m720q (i5-8600T with B360).
      After some other issues I'm know stuck at attached screen.
      Im using latest opencore version and have my EFI folder attached.
       
      Can someone help me I've got no clue what to try next :/ 
       
       
      Cheers!

      EFI.7z
×