Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

stinga11
stinga11
Posted
Posted

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>

 

  • Like 2
Matgen84
Matgen84
Posted
Posted

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
gengik84
Posted
Posted

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
Pavo
Posted
Posted (edited)
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 by Pavo
  • Like 1
Pavo
Pavo
Posted
Posted
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.

  • Like 2
Matgen84
Matgen84
Posted
Posted (edited)
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 by Matgen84
Pavo
Pavo
Posted
Posted
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.

  • Like 2
justin
justin
Posted
Posted
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. :)

  • Confused 1
Pavo
Pavo
Posted
Posted
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. 

  • Thanks 1
justin
justin
Posted
Posted
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. 

Pavo
Pavo
Posted
Posted
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
Matgen84
Posted
Posted (edited)
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 by Matgen84
obus
obus
Posted
Posted (edited)
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:thumbsup_anim:

 

 

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 by obus
mhaeuser
mhaeuser
Posted
Posted

@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?

  • Like 2
MacPato
MacPato
Posted
Posted (edited)
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 by MacFriedIntel
Pavo
Pavo
Posted
Posted
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.

NorthAmTrans
NorthAmTrans
Posted
Posted (edited)

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

Edited by NorthAmTrans
Pavo
Pavo
Posted
Posted (edited)
37 minutes ago, meaganmargaret said:

 

Understandable.....here you go.......also, the AML that initiates the wireless/BT card is:  SSDT-X299-ARPT.aml

 

OC_EFI.zip

 

EDIT:  But do other folks have BT working?  Pavo, do you?

Here is your issue

1NotvnE.png

1. You have renames in the ACPI>Patch in the config and specifically you are renaming PC00 to PCI0, renames should not be done in the config using Patch section, this has been stated over and over in this thread and also stated in the OpenCore documentations. 

2. While you are patching the ACPI tables with the rename of PC00 to PCI0 your SSDT Scope is _SB.PCI0.RP19 which is not matching the ACPI table path.

3. You are also doing a device rename of PXSX to ARPT in the SSDT itself.

 

What I suggest you do is remove all the renames in the ACPI>Patch section and change all your SSDTs to match against the scope of  \_SB.PC00.xxx.

 

Attached is your OC EFI with everything fixed.

OC_EFI.zip

Edited by Pavo
  • Like 1
Wackymac
Wackymac
Posted
Posted
1 hour ago, Pavo said:

Here is your issue

1NotvnE.png

1. You have renames in the ACPI>Patch in the config and specifically you are renaming PC00 to PCI0, renames should not be done in the config using Patch section, this has been stated over and over in this thread and also stated in the OpenCore documentations. 

2. While you are patching the ACPI tables with the rename of PC00 to PCI0 your SSDT Scope is _SB.PCI0.RP19 which is not matching the ACPI table path.

3. You are also doing a device rename of PXSX to ARPT in the SSDT itself.

  

What I suggest you do is remove all the renames in the ACPI>Patch section and change all your SSDTs to match against the scope of  \_SB.PC00.xxx. 

 

Attached is your OC EFI with everything fixed.

OC_EFI.zip

buy you cannot rename pc00 to pci0 in the ssdt though... can you elaborate on why this rename is not needed?

Pavo
Pavo
Posted
Posted
24 minutes ago, Wackymac said:

buy you cannot rename pc00 to pci0 in the ssdt though... can you elaborate on why this rename is not needed?

Because its the original device name in the ACPI tables. There is not need to rename PCI bus device name. 

  • Confused 1
zisqo
zisqo
Posted
Posted

 

1 hour ago, Wackymac said:

ok i guess ill go about cutting back further :( i just like some of the renames for cosmetic reasons :(

 

there are good enough for 2 options and other options better to remove but don't worry because  of working fine. trust me.

1. PCI00 to PCI0

2. LPC0 to LPCB

 

so start up without BT's ssdt and inject a PciRoot id and device properties in DeviceProperties.

the Hackintool will export that information to plist file. : )

 

 

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