OpenCore General Discussion

[maddie]

On 5/21/2019 at 12:39 AM, steve3d said:

as for my boot screen resolution, I have a log entry says:

00:000 00:000 OC: Missing GOP on ConsoleOutHandle, will install - Unsupported

I think this is the problem that I always have such low resolution, and of course, I have ProvideConsoleGop = true set in my config.plist

 

I have i9-9900k with igpu enabled and radeon vii only.

 

and also, it seems the latest version of opencore already fixed my z390 board shutdown. now I can shutdown/reboot, will try another z390 board tomorrow.

 

EDIT: Debug version can properly shutdown, release version still reboot when shutdown.

 

Did you manage to solve the resolution problem? I'm having the same problem here with my Z370 build, with iGPU and Vega 64.

 

 

SOLVED: The culprit was the SanitiseClearScreen option, disabling it makes the resolution look perfect!

Edited August 12, 2019 by maddie
Solved

[Andrw0380]

3 hours ago, Pavo said:

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

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.

Hey thanks for that. I was wondering the data fields for OemTableId and TableSignature, how will I translate the following SSDTs into the proper values to put in there? I'm sorry I am new to OpenCore as been using Clover awhile and this is the last thing I need to get working. The values Clover wants is String Values, but OpenCore needs data values which I don't where to get them for these files.

SSDT.zip

Edited August 12, 2019 by Andrw0380

[maddie]

13 minutes ago, NorthAmTrans said:

 

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

 

To be brutally honest, it doesn't seem that you put much effort into your config.plist  :x

After each OpenCore update, you have to check the Configuration.pdf from the repository to see if there's any changes to the config.plist. Like the Booter quirks I've mentioned, which is new in v0.0.4, was missing in your config.plist. It seems your version was from on or before v0.0.3, which also lacks the AvoidHighAlloc UEFI quirk.

 

I've added them for you and enabled some useful options in it. You might want to take a look before you're applying the changes.

config.plist

[NorthAmTrans]

12 minutes ago, maddie said:

 

To be brutally honest, it doesn't seem that you put much effort into your config.plist  :x

After each OpenCore update, you have to check the Configuration.pdf from the repository to see if there's any changes to the config.plist. Like the Booter quirks I've mentioned, which is new in v0.0.4, was missing in your config.plist. It seems your version was from on or before v0.0.3, which also lacks the AvoidHighAlloc UEFI quirk.

 

I've added them for you and enabled some useful options in it. You might want to take a look before you're applying the changes.

config.plist

 

Never mad at honesty here.

 

I've been keeping it super minimal while I get a grip on everything. I hope that didn't come off as lazy. Hell, I was happy to get a boot and have all my ACPI, Drivers, and Kexts load.

 

You're right, I grabbed the 0.0.4 boot and OpenCore.efi but didn't think to update config. 

 

I'm going to give this a look over and boot and report back. Thanks!

[maddie]

Just now, NorthAmTrans said:

 

Never mad at honesty here.

 

I've been keeping it super minimal while I get a grip on everything. I hope that didn't come off as lazy. Hell, I was happy to get a boot and have all my ACPI, Drivers, and Kexts load.

 

You're right, I grabbed the 0.0.4 boot and OpenCore.efi but didn't think to update config. 

 

I'm going to give this a look over and boot and report back. Thanks!

 

Always read the configuration carefully for every option in the config.plist. I know it's quite tedious, but it's necessary

 

You have a very similar build as mine, I have high hopes that it would work. Good luck!

[NorthAmTrans]

6 minutes ago, maddie said:

 

Always read the configuration carefully for every option in the config.plist. I know it's quite tedious, but it's necessary

 

You have a very similar build as mine, I have high hopes that it would work. Good luck!

 

Well thanks for the help. Everything loaded to my liking! I'll read more next update and hopefully help some along with the way. I'll also do some reading on how to get a boot log and make sure everything is going swell in boot.

[stinga11]

I have only been using Opencore for a couple of days and I must say that it is fantastic. Having a memory fixer built into the code is wonderful. But one of the things I miss most is an option that clover have, to upload the disks with legacy windows, does Opencore not have something similar?

 

This is the option I am talking about:

	<key>Boot</key>
	<dict>
		<key>Legacy</key>
		<string>LegacyBiosDefault</string>
		<key>LegacyBiosDefaultEntry</key>
		<integer>2</integer>
	</dict>

 

[Matgen84]

Hi @Pavo Developer Team

 

I would try a clean offline installation of Catalina Beta 5: in the future, it will be possible with Install macOS.app (Configuration.pdf only mentions Recovery method for create USB).

 

Thanks

[gengik84]

Where is the problem with createInstallMedia?

Apple give an official method for make the installer 

You need to have installer in /Applications folder or change path

Change "installer name" and "volumes name"

https://support.apple.com/el-gr/HT201372

sudo /Applications/Install\ macOS\ Catalina\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/your_volumes_name

[Pavo]

9 hours ago, Matgen84 said:

Hi @Pavo Developer Team

 

I would try a clean offline installation of Catalina Beta 5: in the future, it will be possible with Install macOS.app (Configuration.pdf only mentions Recovery method for create USB).

 

Thanks

I’m confused??? What does making a MacOS installer USB have to do with OpenCore?

Edited August 13, 2019 by Pavo

[justin]

25 minutes ago, Pavo said:

I’m confused??? What does making a MacOS installer USB have to do with OpenCore?

 

See this

[Pavo]

17 minutes ago, justin said:

 

See this

That looks like its for booting a custom Recovery, not booting from the original installer that is made from the app that is created by using createmediainstaller. I have not had any issues installing MacOS with OC using the original installer, Recovery Internet install that is booted from the original Recovery partition that is made from the installer itself. So again I am still confused on what this has to do with OC. Looks more of how to use custom installers with OC which should not be recommended.

[Matgen84]

10 minutes ago, Pavo said:

That looks like its for booting a custom Recovery, not booting from the original installer that is made from the app that is created by using createmediainstaller. I have not had any issues installing MacOS with OC using the original installer, Recovery Internet install that is booted from the original Recovery partition that is made from the installer itself. So again I am still confused on what this has to do with OC. Looks more of how to use custom installers with OC which should not be recommended.

 

For now, as I says before, OC can't install macOS "Off-Line" (createinstallmedia method). The bootloader use dmg Restore method by extract Recovery boot image folder: but it's "Online" (tool dedicated). I hope it will be different in Release OC version. 

 

EDIT: I don't try it: maybe, the temporary solution is to convert InstallmacOS.app to dmg. 

https://www.winytips.com/convert-macos-app-to-bootable-dmg-iso/

Edited August 13, 2019 by Matgen84

[Pavo]

5 minutes ago, Matgen84 said:

 

For now, as I says before, OC can't install macOS "Off-Line" (createinstallmedia method). The bootloader use dmg Restore method by extract Recovery boot image folder: but it's "Online" (tool dedicated). I hope it will be different in Release OC version. 

It absolutely can be used to boot the (createinstallmedia method) and it also can be used to boot the Recovery partition of an existing macOS install and you can use internet recovery method or Time Machine restore method to install macOS. This is the only methods that Apple uses and should be the only methods used to install or recover macOS installs.

[justin]

18 minutes ago, Pavo said:

That looks like its for booting a custom Recovery, not booting from the original installer that is made from the app that is created by using createmediainstaller. I have not had any issues installing MacOS with OC using the original installer, Recovery Internet install that is booted from the original Recovery partition that is made from the installer itself. So again I am still confused on what this has to do with OC. Looks more of how to use custom installers with OC which should not be recommended.

 

A custom recovery is needed when one does not have a macOS environment or when one wants to install older version of macOS.

[Pavo]

1 minute ago, justin said:

 

A custom recovery is needed when one does not have a macOS environment or when one wants to install older version of macOS.

A custom recovery environment should not be needed if one does not have a macOS environment. Either they should use a VM of macOS to create the installer or OC needs to create something similar to Internet booting that real macs have. I am pretty positive that OC devs would not suggest or approve the use of a custom recovery environment because its a security concern. CreateInstallMedia has been around for creating a installer since Mountain Lion as far as I can remember, maybe ever further back. 

[justin]

1 minute ago, Pavo said:

A custom recovery environment should not be needed if one does not have a macOS environment. Either they should use a VM of macOS to create the installer or OC needs to create something similar to Internet booting that real macs have. I am pretty positive that OC devs would not suggest or approve the use of a custom recovery environment because its a security concern. CreateInstallMedia has been around for creating a installer since Mountain Lion as far as I can remember, maybe ever further back. 

 

 

Aha, the custom recovery downloads 400-500M dmg file directly from Apple server. And the method is from OC release/Utility/Recovery. 

[MacPato]

I also installed a new install using Opencore without an issue, whats the big deal here?

[Pavo]

1 minute ago, justin said:

 

 

Aha, the custom recovery downloads 400-500M dmg file directly from Apple server. And the method is from OC release/Utility/Recovery. 

Then they have already addressed the issue and have provided an approved method. 

[Matgen84]

3 minutes ago, justin said:

 

 

Aha, the custom recovery downloads 400-500M dmg file directly from Apple server. And the method is from OC release/Utility/Recovery. 

 

Right.

 

InstallmacoS.app downloads from Appstore 6,8Go. Custom Recovery method needs internet connection, as I says before, to install macOS. CreateInstallMedia not.

Edited August 13, 2019 by Matgen84

[MacPato]

[obus]

On 8/13/2019 at 5:48 PM, justin said:

Aha, the custom recovery downloads 400-500M dmg file directly from Apple server. And the method is from OC release/Utility/Recovery. 

 

For those how are noob:s like me and don't want to put embarresing questions about things that seems obvious for most of the people on this forum.  

Credits for this guide goes to cattyhouse alias @justin on GitHub and translation from Chinese to English goes to Google translate

 

 

OpenCore installs various versions of macOS from Recovery's DMG
advantage

No need to download macOS installation files from the App Store
There is no requirement for the operating platform, as long as you can run the php command, so you can operate on Linux/Windows/macOS or even on a Linux server.
The download volume is very small, Recovery is only 400~500M
Support for the installation of various versions of macOS, solving the problem that is difficult to obtain in the old version of macOS
Disadvantage

Need to know how to configure OpenCore, you must configure it in advance. In fact, it is not a disadvantage, because even if you use the method of making a boot disk, you still need to configure OpenCore to start the computer.
After entering the installation interface, you need to connect to the network. The subsequent installation process needs to get the required files from Apple's server, usually running your bandwidth, so it is not a disadvantage.
step

Configure EFI for OpenCore

Download Recovery DMG

Get php script

Get the reference file for downloading the command of DMG

Take the Linux/macOS platform below, download the Mojave DMG as an example, go to the folder where the retain_recovery.php is located, and run the reference recovery_urls.txt:

Php obtain_recovery.php 00000000000KXPG00 Mac-7BA5B2DFE22DDD8C

Will download 2 files, RecoveryImage.dmg and RecoveryImage.chunklist

Prepare a USB flash drive with a capacity of 1GB or more and format it into Fat32 format.

Copy OpenEore's EFI to the root directory of the USB flash drive

Create a folder name in the root directory of the USB drive: com.apple.recovery.boot

Copy RecoveryImage.dmg and RecoveryImage.chunklist to com.apple.recovery.boot

Name the startup file

Create a new hidden file under the folder com.apple.recovery.boot .contentDetails
Content can be written casually, such as Mojave Boot From Recovery, the name will appear on the OpenCore boot menu.
The file structure on the final USB drive looks like this:

EFI
    ├── BOOT
    ├── OC
Com.apple.recovery.boot
    ├── RecoveryImage.chunklist
    └── RecoveryImage.dmg
    └── .contentDetails
Start the computer with a USB flash drive and select Mojave Boot From Recovery. Then you will enter the normal installation interface.

Edited August 15, 2019 by obus

[mhaeuser]

@Matgen84 createinstallmedia is supported just fine and validated by many users. If you have a specific problem, please elaborate.

@justin I think the 'custom' part is a bit abused here, probably @Pavo expected some botchered install method, like the old BaseSystem+Packages nonsense. Apple Recovery DMG ofc is not 'custom', but apparently not Matgen's problem either.

@MacFriedIntel May I ask you to not clutter the topic?

[MacPato]

51 minutes ago, Download-Fritz said:

@Matgen84 createinstallmedia is supported just fine and validated by many users. If you have a specific problem, please elaborate.

@justin I think the 'custom' part is a bit abused here, probably @Pavo expected some botchered install method, like the old BaseSystem+Packages nonsense. Apple Recovery DMG ofc is not 'custom', but apparently not Matgen's problem either.

@MacFriedIntel May I ask you to not clutter the topic?

How have i cluttered the topic, with my emoji lol dude seriously come on. really?, @Download-Fritz seeing as your a guy that excepts criticism may i ask you get a sense of humour? 

Edited August 13, 2019 by MacFriedIntel

[Pavo]

1 minute ago, meaganmargaret said:

Bluetooth Problems....

 

Can't get bluetooth to work on Opencore.  Same system, if booted with Clover, Bluetooth works and works well.  I boot OC from a USB drive, and it works and works well, but......

 

System Info:  X299 Asus Prime Deluxe with two SSDs installed.  One is Mojave, and one is Catalina.  Same result whether booting to Mojave or Catalina.  On Clover, BT works.  On OC, BT doesn't.

 

No special kexts are loaded for BT on either installation, only an AML for the BCM94360CD wireless/BT combo card.

 

Does anyone know of any issues with BT on OC?  Is BT on OC working for others?

Without seeing your SSDT and config, can't really tell if its a SSDT issue or a config issue.