Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

Elende
Elende
Posted
Posted

Dear all,

 

I'm quite new to OpenCore and try to get it work on my Hackintosh.

My config is quite common:

  • Asus Z170 ProGaming board
  • Intel Core i5 6600K CPU
  • AMD Radeon 5700 GPU (but it is disconnected at the moment until I manage to update to Catalina last version)
  • USB Steelseries Keyboard

I folowed the Insanelymac tutorial to prepare my open core EFI folder.

All is fresly downloaded from yesterday

Opencorepkg 0.5.1

with kext:

  • lilu,
  • whatever green,
  • applealc,
  • virtualsmc,
  • smcprocessor
  • smcsuperio

The driver I added are:

  • Apfsdriverloader
  • FwRuntimeservices
  • UsbKbDxe
  • VBoxHfs
  • VirtualSMC

And I use the ACPI files:

  • SSDT-EC-USBX
  • SSDT-PLUG

All of them are the latest released.

I've configured my config.plist according to the Skylake recommendation.

 

I've attached my config.plist

I manage to see the bootloader with the different partitions but when it comes to select the one the keyboard is not responding even so backlighted.

Any idea?

Andrey1970
Andrey1970
Posted
Posted (edited)

@Elende

Don't use UsbKbDxe.efi and KeySupport=yes at the same time.

Delete UsbKbDxe.efi or set all NO in Input section. (Decide as works for you better.)


Replace VBoxHfs.efi on HfsPlus.efi

VBoxHfs.efi it is license it is pure, but it is very slow therefore problems with boot RecoveryHD (dmg).

Edited by Andrey1970
navmessier63
navmessier63
Posted
Posted
 
 
 
 
 
3
On 10/21/2019 at 1:35 PM, NavHac said:

Hi, trying to move my old build from clover to opencore. But opencore just freeze "Prelinked status - Success" nothing happened after that, the Same machine is booting Catalina just fine with clover.

Attached screenshot of last error, my config.plist, last opencore boot log and EFI directory.

Need help in diagnosing what I am doing wrong.

 

 

config.plist

EFI.zip

opencore-2019-10-21-074411.txt

 

Not able to boot till yet. Any help?

Leoyzen
Leoyzen
Posted
Posted

Cound someone just give a more specific description about what is "AppleBootPolicy"?

There is little information about it, I don't know whether we should use it in a hackintosh VM.

The offical description is here: "Ensures APFS compatibility on VMs or legacy Macs"

FrodoKenny
FrodoKenny
Posted
Posted

Does anybody know how boot selection is supposed to work and why it doesn't work with emulated nvram (i.e. using LegacyEnable and LogoutHook, tried with and without DisableVariableWrite)?

 

I have a B360 mainboard, so no native working nvram in macOS. NVRAM is working under Windows 10 with the startup disk selection in the bootcamp control panel, and when I use that it sets Boot0080 and BootOrder appropriately. Under macOS, however, startup disk only seems to set efi-boot-device. Boot0080 does not change, nor is it created when it doesn't exist, while from what I read that is expected to happen?

 

(I'd specifically like macOS updates to reboot to the installer and back again automatically)

Pavo
Pavo
Posted
Posted

Emulated NVRAM doesn’t work that way, it does what is outlined in the nvram.plist file. So..... in order for that to work, you would have to have something that will write to the nvram.plist every time you did an update or used Startup Disk for the boot order to change in the nvram.plist file. 

  • Like 1
AliPas52
AliPas52
Posted
Posted (edited)
46 minutes ago, NavHac said:

Not sure what works for me will work for you. Share your config and hardware info.

 

Gigabyte GA-B360N WIFI | i3 8100 | 16GB DDR4-2400 | RX 570 4GB | its my hardware

opencore-2019-10-30-173832.txt

Edited by AliPas52
Hackintosh Tech
Hackintosh Tech
Posted
Posted
7 hours ago, Andrey1970 said:

@Elende

Don't use UsbKbDxe.efi and KeySupport=yes at the same time.

Delete UsbKbDxe.efi or set all NO in Input section. (Decide as works for you better.)


Replace VBoxHfs.efi on HfsPlus.efi

VBoxHfs.efi it is license it is pure, but it is very slow therefore problems with boot RecoveryHD (dmg).

Why is VboxHFS in the sampleconfig.plist if we are suppose to use HFSPlus? or did i miss read what you said.

obus
obus
Posted
Posted (edited)

Question to the Devs!

 

Where should I install 3rd party kext.

As I understand from Clover all 3rd party kext should be installed in L/E except for basic/critical kext you need for booting into MacOS Installer,Recovery or Updater, kexts like FakeSMC and some other kext we need injected before running them. 

Shall we have the same approach in OC or is it good enough to just keep the kexts in EFI/OC/Kexts?

For me everything is working with the kexts in EFI/OC/Kexts but what is the most correct way?

Edited by obus
mhaeuser
mhaeuser
Posted
Posted (edited)

@MacPato™ HFSPlus is proprietary and not licensed for redistribution, but superiour performing

@obus I have heard the LE recommendation a bunch but never once a satisfying argument for that. We recommend injection especially looking into the future and in regards to SIP state.

Edited by Download-Fritz
  • Like 2
zaborrilla
zaborrilla
Posted
Posted (edited)

Hi,

 

I recently switched from Clover to OpenCore, everything works great (sleep, power management, etc ...) and I decided to stay with OC. Today I updated from 10.15 to 10.15.1 and in one of the several reboots of the upgrade procedure I got the error showed in the attached jpg.

 

It was not a big problem because simply rebooting, entering manually in the picker and selecting the disk "Install macOS" made the update to continue and the process went ok.

 

In my pursuit for the perfect vanilla system I wonder if this is the expected behavior or if I should modify any option to avoid that error. I have searched info about the error but I have not found anything that seems relevant.

 

I take this opportunity to thank the entire community, especially the developers for these incredible tools.

 

Regards

screenshot.jpg

Edited by zaborrilla
corrected typo
vandroiy2012
vandroiy2012
Posted
Posted

Ha-ha. Native Apple Bless protocol works 100%. Tried to update your AMI firmware with Apple ROM:hysterical:

 

It happened because of outdated Apple Boot ROM version in OpenCore. Either you use outdated BIOSVersion with Automatic-false in PlatformInfo->SMBIOS, or (if you use Automatic=true) BIOSVersion in OpenCore sources are outdated.  

  • Like 2
  • Sad 1
Andrey1970
Andrey1970
Posted
Posted (edited)
2 hours ago, MacPato™ said:

Why is VboxHFS in the sampleconfig.plist if we are suppose to use HFSPlus? or did i miss read what you said.

 

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Sample.plist#L726

We can't load HfsPlus.efi on AppleSupportPkg, but you know where to take it.

Edited by Andrey1970
zaborrilla
zaborrilla
Posted
Posted
1 hour ago, vandroiy2012 said:

Ha-ha. Native Apple Bless protocol works 100%. Tried to update your AMI firmware with Apple ROM:hysterical:

 

It happened because of outdated Apple Boot ROM version in OpenCore. Either you use outdated BIOSVersion with Automatic-false in PlatformInfo->SMBIOS, or (if you use Automatic=true) BIOSVersion in OpenCore sources are outdated.  

 

Thanks for the explanation! I use Automatic=true, so it must be the second. I use OpenCore version 0.5.2, from the recent release of Acidanthera Github, maybe Apple released recently a new firmare for macmini8,1 (that is what I use). Anyway, I will see what will happen at the next update.

 

Regards!

nefilim
nefilim
Posted
Posted
36 minutes ago, canyondust said:

Updated to  OC 0.5.2, brilliant. No more random cursor and faster boot.

 

What need to be set to see the output of VerifyMsrE2? I can launch it, but the screen remains black for a few seconds and then returns to the boot manager...

 

Thanks!

Added in Tools? I used it just last night with OC 0.5.2 and it showed me the expected output (locked!) 

  

                        <dict>
                                <key>Arguments</key>
                                <string></string>
                                <key>Name</key>
                                <string>VerifyMsrE2</string>
                                <key>Comment</key>
                                <string>Not signed for security reasons</string>
                                <key>Enabled</key>
                                <true/>
                                <key>Path</key>
                                <string>VerifyMsrE2.efi</string>
                        </dict>

 

justin
justin
Posted
Posted (edited)
2 hours ago, canyondust said:

Updated to  OC 0.5.2, brilliant. No more random cursor and faster boot.

 

What need to be set to see the output of VerifyMsrE2? I can launch it, but the screen remains black for a few seconds and then returns to the boot manager...

 

Thanks!

 

You can add OpenCore Shell.efi to tools, Launch shell, manually execute  VerifyMsrE2.efi (it is located in fs0:/EFI/OC/Tools/ or fs1:/EFI/OC/Tools/) in the shell. 

Edited by justin
  • Like 1
canyondust
canyondust
Posted
Posted
2 hours ago, nefilim said:

Added in Tools? I used it just last night with OC 0.5.2 and it showed me the expected output (locked!) 

  


                        <dict>
                                <key>Arguments</key>
                                <string></string>
                                <key>Name</key>
                                <string>VerifyMsrE2</string>
                                <key>Comment</key>
                                <string>Not signed for security reasons</string>
                                <key>Enabled</key>
                                <true/>
                                <key>Path</key>
                                <string>VerifyMsrE2.efi</string>
                        </dict>

 

Yep, it’s in config.plist and enabled, shows up in the picker, I can select it, but it doesn’t seem to print any output to screen, just goes back to picker after about 10s

birdbird
birdbird
Posted
Posted

 

On 10/28/2019 at 9:15 AM, kjp4756 said:

I had some similar issues with my new XFX RX580.  Mine had a newer GOP driver dated may of this year.  Wouldn't boot mac os at all.  I then flashed the xfx bios from tech power up and got corrupted graphics with that.  I ended up going with a sapphire bios and now things are perfect.  It was Sapphire.RX580.8192.180719.rom from tech power up.  

I tried that and it didn't work with my card.  I tried a few others and they either borked graphics or didn't solve the problem.  Finally I found a utility to add/fix the UEFI GOP and that didn't do much.  I'm starting to think this long pause is just due to the fact that I have like 8 various hard drives, some for other OSs (like the Linux I'm using now), some for backups, some as fusion drives, etc, which are making it take a year to parse all of them.

 

On 10/28/2019 at 6:53 AM, n.d.k said:

try copy this config.plist setting for ivybridge board.

Thanks, I'll do this next.  I suspect there's some issue during/after kext loading which is causing the final failure to boot.  Hopefully this plist will help!

Elende
Elende
Posted
Posted

@Andrey1970 Thank you very much. It was indeed an issue with UsbKbDxe.efi and HFSPlus is way faster.

Sadly I'm stuck just a bit further down:

On the Mojave recovery partition it block at the line 

apfs_module_start:1683 load: com.apple.filesystems.apfs ...

And if I'm starting on the Catalina partition I end in a Kernel Panic shortly after 

HID Legacy shim 2

Does it ring any bell?

Any recommendation?

 Share
Go to topic listing
×
×
  • Create New...