OpenCore General Discussion

[davidm71]

Was wondering if anyone knows if its possible to use Opencore on a real mac such as a Macbook Pro and load an updated nvme efi driver to solve the hibernation issue with 3rd party nvme drives? That is instead of flashing the rom with the fixed nvme ffs file convert it to an efi and load it inside opencore...

 

Anyhow change of subject .. Why would anyone want to dual boot Clover with Opencore?? Talk about nvram corruption issues! With some tinkering you can get Opencore to boot Windows no problem. Even still theres the NDK version out there..

 

Thanks

[Andrey1970]

4 hours ago, MacNB said:

E.g., if I made Apple.icns, will OpenCanopy apply that icon to ALL macOS bootable file systems it finds ?

Yes. 

If Apple.icns is absent, then HardDrive.icns is used.

 

4 hours ago, MacNB said:

E.g., if I had .VolumeIcon.icns on a drive AND there was an Apple.icns in OC/Resources/Image folder, which icon take precedence ?

.VolumeIcon.icns

[MacNB]

10 hours ago, Andrey1970 said:

Yes. 

If Apple.icns is absent, then HardDrive.icns is used.

 

.VolumeIcon.icns

 

Thank you. 

It would be worth adding that explanation to the Configuration pdf

[MacNB]

On 5/1/2020 at 1:01 AM, ltooz_audis said:

OK, I finally got the OpenCore to dual boot with Clover for Catalina 15.4+ and Windows

Cheers,

Louis

 

Hmmm. Why would you want to boot Into OpenCore, then into Clover to boot Windows ????

Is this just to show that it can be done (for fun) ?

 

I have Catalina on one drive (that also has OC) and I have another drive with Windows & Mojave (with Clover which is not used anymore -except for emergency).

...and I can boot Windows from OC directly.

Touch wood, Windows is still activated.

 

BTW, I had copied Windows System UUID and used it for macOS System UUID as well.

 

I then ran HwInfo app in Windows to find out what info it had about my Windows now.

This is what I find:

 

 

 

 

 

The only strange thing is HwInfo thinks that the Case Type is a LapTop for an iMacPro.

Not sure if OpenCore is passing this or if the App is defaulting to laptop because no info was passed by OpenCore.

Note: If you set PlatformInfo->Generic->SpoofVendor=No then the all references to Acidanthera will be replaced with Apple BIOS SMBIOS data in the above screenshots (e.g. GIGABYTE in my case).

 

 

Edited May 21, 2020 by MacNB
correction

[naoatsu]

I've bluetooth problems. Everything else in 10.15.4 w/ Opencore 0.5.7 is working fine with my combo wifi card BCM4352  but I can't find the problem why bluetooth (0x0489:0xE07A) is detected 'System Info', under HS07 in hackintool and IOregistryExplorer but bluetooth icon never appear.

I'm using 3 brcmpatch files with injector kexts 2.5.0 and last version, seems in system logs that the fw is uploaded but bluetooth does not work. I've tried vanilla version mojave & catalina.

What's wrong? Anyone could help me please? Thank you.

 

Attached my OC_EFI.

opencore-20200501T161857Z-001.zip

Edited May 1, 2020 by naoatsu

[Andrey1970]

10 minutes ago, MacNB said:

The only strange thing is HwInfo thinks that the Case Type is a LapTop for an iMacPro.

 

Therefore so in real iMacPro1,1.

[MacNB]

37 minutes ago, Andrey1970 said:

 

Therefore so in real iMacPro1,1.

 

Wow that's pretty sloppy of Apple !

Thanks for the info.

 

It's only cosmetic but I guess I can overwrite that by setting PlatformInfo->SMBIOS->ChassisType to a number equal to Desktop ?

 

[RandomDSdevel]

I noticed that the available VirtualSMC release downloads don't include the `VirtualSMC.efi` driver.  It's easy enough to fetch from its location in the repository, but shouldn't it be included?  

 

[topolino1]

2 hours ago, RandomDSdevel said:

I noticed that the available VirtualSMC release downloads don't include the `VirtualSMC.efi` driver.  It's easy enough to fetch from its location in the repository, but shouldn't it be included?  

  

 

 

You haven't needed it since a while. In configuration.pdf it is written like this.

[RandomDSdevel]

3 hours ago, topolino1 said:

You haven't needed it since a while. In configuration.pdf it is written like this.

What if you're using VirtualSMC instead of FakeSMC, and with Clover?  (Or should I ask over in the Clover sub-forum?)  (Edit:  Now I have.)  

Edited May 2, 2020 by RandomDSdevel

[ltooz_audis]

Opencore doesn't show Catalina installation partition on the second boot? There's no option to pick?

[MacNB]

46 minutes ago, ltooz_audis said:

Opencore doesn't show Catalina installation partition on the second boot? There's no option to pick?

 

No need to pick "Instal.." as its automatic if configured.

Working NVRAM ?

 

Did you set following Quirks: ?

 

UEFI->Quirks->RequestBootVarFallback=True 

UEFI->Quirks->RequestBootVarRouting=True 

 

See Configuration.pdf Section 11.12

 

 

 

[ltooz_audis]

Thanks, let me check.

[ltooz_audis]

I have a really big problem with screen flickering black every so often with Haswell HD4400 and HD4600 laptops. The Clover patches work perfectly but I don't know how to patch the OC since it's different, please help me patching these 2:

and the other thing is how to set the timeout 5 seconds to boot to Catalina with open canopy graphics.

Thanks,
Louis

[MacNB]

9 hours ago, ltooz_audis said:

I have a really big problem with screen flickering black every so often with Haswell HD4400 and HD4600 laptops. The Clover patches work perfectly but I don't know how to patch the OC since it's different, please help me patching these 2:

and the other thing is how to set the timeout 5 seconds to boot to Catalina with open canopy graphics.

Thanks,
Louis

 

Those patches will not work because you have not specified in the Identifier field which binary this patch applies to (e.g. driver, kernel, etc).

You have to look at your Clover patches (which you did not post here) and use them as the basis for OC patch.

Besides, if you use Whatevergreen kext, those patches you are trying should not be necessary.

 

If you want timeout on the boot picker to work, you have to build the latest version of OC 0.5.8.

If you do, be warned that the certain fields on the Config files have changed to reflect the changes in the OC features.

You have to read the Differences.pdf file to find what has changed and look at the new Samples.plist file.

 

 

[noreason]

On 4/16/2020 at 7:26 PM, davidm71 said:

 

Are you on 15.4? If so was wondering if you would do me a favor and run the  'CONSOLE' app and check its crash reports and see if you see any mention of your video card at being at fault? I'm having a similar issue and narrowed it down to the drivers for my 5700 XT.

  

Thanks

Totally missed this response somehow, sorry for the delay...

 

I don't get _anything_ in console when I freeze. Really wish i did because though because I'm out of ideas.

[Humanate]

I am successfully running opencore on my rig but I didn't create the EFI, got it from Pastrychef over at TM. I am a real noob when it comes to Opencore and the documentation is hard for me to follow. My question is, if I want to remove kexts, how do I do this? I know where the kexts are in EFI/OC/Kexts - so I can remove from there but do I also need to update my config.plist? Can anyone give me an idiots guide on how to do?

Edited May 2, 2020 by crawfyp1

[Matgen84]

2 minutes ago, crawfyp1 said:

I am successfully running opencore on my rig but I didn't create it, got it from Pastrychef over at TM. I am a real noob when it comes to Opencore and the documentation is hard for me to follow. My question is, if I want to remove kexts, how do I do this? I know where the kexts are in EFI/OC/Kexts - so I can remove from there but do I also need to update my config.plist? Can anyone give me an idiots guide on how to do?

 

Right, if you want to remove kexts from EFI/OC/Kexts, you have to remove in config.plist. For a guide, dortiana support only release: Here

[Paksman]

On 5/1/2020 at 8:03 PM, MacNB said:

 

Wow that's pretty sloppy of Apple !

Thanks for the info.

 

It's only cosmetic but I guess I can overwrite that by setting PlatformInfo->SMBIOS->ChassisType to a number equal to Desktop ?

 

Thanks to @Andrey1970 and this change:https://github.com/acidanthera/MacInfoPkg/commit/a29c9fa2e762cb2c7015a89349f20a8eb5f9934b it is corrected.

[Humanate]

1 hour ago, Matgen84 said:

 

Right, if you want to remove kexts from EFI/OC/Kexts, you have to remove in config.plist. For a guide, dortiana support only release: Here

I have been reading the guide there alot, but much of it is over my head. Let's say I want to remove 2 kexts, VoodoInput.kext and VoodooPS2Controller.kext, shown here:

 

 

So, would I be able to open the config.plist in ProperTree and remove the info shown here:

 

 

Then remove the kexts from EFI/OC/KEXTS, save the config.plist and replace in EFI/OC

 

Is that the right way to do it? Excuse my ignorance, I'm completely new to this

[jon7]

2 hours ago, crawfyp1 said:

I have been reading the guide there alot, but much of it is over my head. Let's say I want to remove 2 kexts, VoodoInput.kext and VoodooPS2Controller.kext, shown here:

 

 

So, would I be able to open the config.plist in ProperTree and remove the info shown here:

 

 

Then remove the kexts from EFI/OC/KEXTS, save the config.plist and replace in EFI/OC

 

Is that the right way to do it? Excuse my ignorance, I'm completely new to this

Remove Kexts from EFI/OC/KEXTS then run Proper Tree click open navigate to config.plist then open snapshot navigate to OC then open clear snapshot navigate to OC and then Save.

[davidm71]

9 hours ago, noreason said:

Totally missed this response somehow, sorry for the delay...

 

I don't get _anything_ in console when I freeze. Really wish i did because though because I'm out of ideas.

 

I had to reinstall for the 3rd time over before I got it working. Just in case the hard drive was to blame I used a Samsung 970 Evo plus. Think it might have helped. Opencore 5.8 may have helped too. SSDT-Time to create three ssdt files also.  Don't give up.

Edited May 3, 2020 by davidm71

[pastrychef]

15 hours ago, crawfyp1 said:

I am successfully running opencore on my rig but I didn't create the EFI, got it from Pastrychef over at TM. I am a real noob when it comes to Opencore and the documentation is hard for me to follow. My question is, if I want to remove kexts, how do I do this? I know where the kexts are in EFI/OC/Kexts - so I can remove from there but do I also need to update my config.plist? Can anyone give me an idiots guide on how to do?

 

Just delete the kexts from /EFI/OC/Kexts/.

 

Then, delete the associated kexts from config.plist > Kernel > Add.

 

The PS/2 kexts you want to remove don't cause any problems and enables the PS/2 port on the motherboard.

[MacNB]

16 hours ago, Paksman said:

Thanks to @Andrey1970 and this change:https://github.com/acidanthera/MacInfoPkg/commit/a29c9fa2e762cb2c7015a89349f20a8eb5f9934b it is corrected.

 

Thanks @Andrey1970. 

Those Type codes now match the SMBIOS Spec Page 37 (that Apple clearly ignored).

 

[braindeadmac]

Hello all. I've been using OpenCore for quite some time. I just attempted to update to OC 0.5.8 from 0.5.3- been delaying since it required quite a few changes to my config.plist and drivers. Everything seems to be OK for the config file, but boot hangs at or right before boot.efi handoff.

 

OC debug log yields

 

1474:351 02:011 OCB: Default DP post-fix remainder - \A49F232C-F82B-4451-B7CB-3F8DF98E929B\System\Library\CoreServices\boot.efi
1475:362 01:011 OCB: Matched default boot option: Vortex
1476:373 01:010 OCB: Initial default is 4
1481:566 05:193 OCB: Should boot from Vortex (T:2|F:0|DEF:0)
1481:582 00:015 OCB: Perform boot Vortex to dp PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,AB-89-B3-91-56-38-25-00)/HD(2,GPT,8A5DA1CB-4307-4108-8722-4956897F9D9A,0x64028,0x77359260)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,7CB88402ADBB6E45B2D155B8D9098808)/\A49F232C-F82B-4451-B7CB-3F8DF98E929B\System\Library\CoreServices\boot.efi (0/0)
1481:596 00:014 OCB: Matching <> args on type 2 0
1481:611 00:015 ASSERT [OpenCore] /tmp/OCBuilder_Clone/OpenCorePkg/UDK/OpenCorePkg/Library/OcMemoryLib/MemoryAttributes.c(283): MemoryAttributesEntry->PhysicalStart < NextGluedAddress
 

I can boot fine when I revert to 0.5.3.  System is ASUS X299 Deluxe, i9-7920x, Radeon Vega FE, 64 GB RAM.

 

Any ideas as to where to start? Is this a bug?

 

Attached config.plist fwiw

config.plist