OpenCore General Discussion

[NorthAmTrans]

@dracoflar, im looking back on an old comment about how my hardware shouldn't need a DSM>XDSM patch. How can I confirm this?

[rusty-bits]

Here is another tool for building OpenCore from the command line that I'm working on if anyone wants to try it out

 

https://github.com/rusty-bits/OC-tool

 

It updates required packages, builds the files, and copies them into an EFI directory

It also makes the required vault files if you have the RequireVault option set in your config.plist

 

Edited September 15, 2019 by rusty-bits
remove unnecessary matter from general discussion

[Erroruser]

1 hour ago, rusty-bits said:

Here is another tool for building OpenCore from the command line that I'm working on if anyone wants to try it out

 

https://github.com/rusty-bits/OC-tool

 

It updates required packages, builds the files, and copies them into an EFI directory

It also makes the required vault files if you have the RequireVault option set in your config.plist

 

  Reveal hidden contents

 

 

i think i rather stick with this one https://github.com/Pavo-IM/ocbuilder

 

[rusty-bits]

On 8/24/2019 at 2:48 PM, errorexists said:

On 8/24/2019 at 1:38 PM, rusty-bits said:

Here is another tool for building OpenCore from the command line that I'm working on if anyone wants to try it out

 

https://github.com/rusty-bits/OC-tool

 

It updates required packages, builds the files, and copies them into an EFI directory

It also makes the required vault files if you have the RequireVault option set in your config.plist

 

i think i rather stick with this one https://github.com/Pavo-IM/ocbuilder

 

I tried that one, but I didn't like it much

-It wants administrator privileges, but I'm not sure why

-It pulls and builds everything, whether you are using it in your EFI or not, makes it a bit slow

-It builds Release, NoOpt, and Debug every time, whether you want them all or not, also makes it a bit slow

-It doesn't make the vault files, I like the RequireVault option, has saved me a couple of times

-It doesn't seem to make a logfile anywhere, but I may have missed that

-It doesn't make an EFI folder that I can just drop in my EFI partition and reboot to try it out

 

Anyways, that's some of the reasons why I wanted to make a simple command line tool that grabs only what you tell it and builds it into a bootable EFI directory

I still need to add on ACPI file handling, not a priority for me yet since I don't use them, but it might be nice to have

And a NoOpt option as well, right now I just have a release and debug option

Also I need to include the Tools folder as well, it's nice to be able to boot into OpenCoreShell

That's next on my agenda

Edited September 15, 2019 by rusty-bits
strikeout incorrect comments

[Proxary]

Hello guys I have successfully  updated my opencore and my settings and now I can boot Without osxfixdrv2.efi them I have removed it but I have only VirtualSMC.efi and all the files from applesupportpkg but when I try to boot I have a panic error but i don’t know from what I hope the are Can fix the problem here a picture as appendix 

[Erroruser]

24 minutes ago, rusty-bits said:

I tried that one, but I didn't like it much

-It wants administrator privileges, but I'm not sure why

-It pulls and builds everything, whether you are using it in your EFI or not, makes it a bit slow

-It builds Release, NoOpt, and Debug every time, whether you want them all or not, also makes it a bit slow

-It doesn't make the vault files, I like the RequireVault option, has saved me a couple of times

-It doesn't seem to make a logfile anywhere, but I may have missed that

-It doesn't make an EFI folder that I can just drop in my EFI partition and reboot to try it out

 

Anyways, that's some of the reasons why I wanted to make a simple command line tool that grabs only what you tell it and builds it into a bootable EFI directory

I still need to add on ACPI file handling, not a priority for me yet since I don't use them, but it might be nice to have

And a NoOpt option as well, right now I just have a release and debug option

Also I need to include the Tools folder as well, it's nice to be able to boot into OpenCoreShell

That's next on my agenda

i think @Pavo would explain that better when he gets the chance

[rusty-bits]

2 minutes ago, errorexists said:

i think @Pavo would explain that better when he gets the chance

I'm not sure what @Pavo would need to explain, his README.md makes it pretty clear what his tool does.

I simply needed something less all encompassing than ocbuilder, but if it works well for you, great! 

[Erroruser]

1 minute ago, rusty-bits said:

I'm not sure what @Pavo would need to explain, his README.md makes it pretty clear what his tool does.

I simply needed something less all encompassing than ocbuilder, but if it works well for you, great! 

works great for many others

[Sniki]

How to solve the problem with Haswell MSR Lock on Laptops so i can boot with OC ?

 

Is there a kernel patch or quirk like there is on clover for this aside from having to mod the bios and remove it ?

 

@vit9696 @PMheart any suggestions ?

Edited August 25, 2019 by "Sniki"

[Andrey1970]

1 hour ago, "Sniki" said:

How to solve the problem with Haswell MSR Lock on Laptops so i can boot with OC ?

 

Is there a kernel patch or quirk like there is on clover for this aside from having to mod the bios and remove it ?

 

@vit9696 @PMheart any suggestions ?

AppleXcpmCfgLock

[Sniki]

26 minutes ago, Andrey1970 said:

AppleXcpmCfgLock

I still get this panic:

 

Lenovo ThinkPad X240 with Core i5 4300U

OC 0.0.4 Release with EFIRuntimeServices.efi (latest release)

 

Attached my OC as well: OC.zip

[Pavo]

16 hours ago, rusty-bits said:

-It wants administrator privileges, but I'm not sure why

-It pulls and builds everything, whether you are using it in your EFI or not, makes it a bit slow

-It builds Release, NoOpt, and Debug every time, whether you want them all or not, also makes it a bit slow

-It doesn't make the vault files, I like the RequireVault option, has saved me a couple of times

-It doesn't seem to make a logfile anywhere, but I may have missed that

-It doesn't make an EFI folder that I can just drop in my EFI partition and reboot to try it out

 

I still need to add on ACPI file handling, not a priority for me yet since I don't use them, but it might be nice to have

Also I need to include the Tools folder as well, it's nice to be able to boot into OpenCoreShell

- It needs administrative privileges, because it checks to see if you have the build tools such as nasm and mtoc are installed and if not, it uses those privileges to install them for you automatically.

- It pulls only the drivers, kexts repos that are commonly used.

- It builds only Release versions.

- It adds all the Utility files that you would need if you need to make vault files. Which is done separately yes. 

- A log file is only made if there is any errors. No reason to make a log file if there is no errors.

- It makes a complete EFI folder that can be dropped into your ESP upon build complete. All you have to do is make your config.plist file.

- All the ACPI files are included in the completed build folder.

- It also includes the ClearNVRAM, MSRCheck and OpenCoreShell in the Tools folder inside the EFI folder upon completing the build.

[Sniki]

5 hours ago, "Sniki" said:

I still get this panic:

 

Lenovo ThinkPad X240 with Core i5 4300U

OC 0.0.4 Release with EFIRuntimeServices.efi (latest release)

 

Attached my OC as well: OC.zip

any idea/suggestion someone ?

[NorthAmTrans]

@sniki you should add your hardware to your signature.

[rusty-bits]

4 hours ago, Pavo said:

- It needs administrative privileges, because it checks to see if you have the build tools such as nasm and mtoc are installed and if not, it uses those privileges to install them for you automatically.

[snip]

- All the ACPI files are included in the completed build folder.

- It also includes the ClearNVRAM, MSRCheck and OpenCoreShell in the Tools folder inside the EFI folder upon completing the build.

Hey @Pavo

Thanks for the reply. Sorry for appearing critical of ocBuilder, the point I was making to @errorexists is that ocBuilder isn't the tool for me. I pretty much live in the terminal even when I'm not remoted in. I wouldn't know the first thing about creating a GUI app.

Your app was one of the inspirations I had for trying to create my own command line tool to build an EFI which is currently a work in progress. I'd love your critique of it if you have time.

 

I tend to shy away from things than need admin privileges. I try to put binaries into /usr/local/bin when possible to avoid the need for admin. As for ACPI and the Tools folder, I'm well aware that ocBuilder takes care of those, the point was that my tool doesn't yet.

 

My tool definitely won't be for everyone. Some people don't like the command line or don't know how to install build tools. That's not a feature I'm ever going to add.

I thought it would be a fun challenge to see if I could make a command line tool that will read the config.plist and then build a complete EFI folder based on it.

 

Anyways, thanks again for the reply, and thanks for all your work! 

[STLVNUB]

22 minutes ago, rusty-bits said:

I thought it would be a fun challenge to see if I could make a command line tool that will read the config.plist and then build a complete EFI folder based on it.

 

 

good job 

[Sniki]

1 hour ago, NorthAmTrans said:

@sniki you should add your hardware to your signature.

Thanks for pointing that out, added my hardware.

 

But im more concerned about my current issue, i read the Configuration.pdf but can't seem to find a reason why i have a kernel panic related to my CPU.

 

Managed to fix everything recently into all my other hardware, it's just this kernel panic that i cannot figure out why it is happening.

Edited August 25, 2019 by Snikii

[NorthAmTrans]

@Snikii of course! 

 

A couple things. Rename patches are frowned on with OC. Someone here with a more articulate answer can fill in the blanks here but the short of it all is that they cause problems and should be avoided. I would go through and figure out which ones are actually necessary and then find some help here about how to make or find a patch for them. 

 

I don't know much about laptops here but for pure lucks sake try setting LegacyEnable to YES.

 

You should join the InsanelHack Discord. There is a channel there for OpenCore Laptops. Best of luck to ya. Report back with some progress!

[DonBronko]

I am not able to load X86 Platform Plugin. With Clover it was working.

 

I edited SSDT-PLUG to match my cpu name with no effect. Can someone point me to the right direction.

 

SSDT-0.aml

DSDT.aml

SSDT-PLUG.aml

Edited August 25, 2019 by Quipper

[gengik84]

@Quipper

Scope (\_SB.PR00)

instead of

Scope (\_PR.PR00)

[Sniki]

15 minutes ago, NorthAmTrans said:

@Snikii of course! 

 

A couple things. Rename patches are frowned on with OC. Someone here with a more articulate answer can fill in the blanks here but the short of it all is that they cause problems and should be avoided. I would go through and figure out which ones are actually necessary and then find some help here about how to make or find a patch for them. 

 

I don't know much about laptops here but for pure lucks sake try setting LegacyEnable to YES.

 

You should join the InsanelHack Discord. There is a channel there for OpenCore Laptops. Best of luck to ya. Report back with some progress!

The core problem is supposed to be somewhere in Quirks not on ACPI Renames as nothing is affecting CPU in terms of ACPI aside the Quirks and other General Options.

 

There is no way to make a laptop work without rename patches at the current stage not even with OC (there are only rare cases).

 

You need to patch EC Registers that are more than 8-bit that are battery related in order to have Battery Status working (whether you use ACPIBatteryManager.kext + FakeSMC.kext or VirtualSMC.kext + SMCBatteryManager.kext).

 

You need to patch/rename GPRW or a _PRW that causes instant wake from sleep.

 

You need to patch/rename ESEL, XSEL, XWAK (if present) as they cause issues with USB Ports

 

You need to patch/rename your Qxx methods for Fn Buttons like brightness and others so they can work natively without the need of 3rd party apps.

 

You need to patch/rename BAT0 and BAT1 notifiers to BATC if your laptop does have dual batteries so you can use SSDT-BATC to merge dual batteries into one and have hotswap functionality as dual battery support on macOS is bugged/not working natively.

 

ETC

 

But yes i do agree that with OC compared to Clover we need less more than we used.

Edited August 25, 2019 by Snikii

[NorthAmTrans]

Hey, fair enough. Point well taken.

 

Im curious here with the value "0" for your Counts in Renames. Is 0=all?

 

 

[Pavo]

1 hour ago, rusty-bits said:

Hey @Pavo

Thanks for the reply. Sorry for appearing critical of ocBuilder.

 

I tend to shy away from things than need admin privileges. I try to put binaries into /usr/local/bin when possible to avoid the need for admin. As for ACPI and the Tools folder, I'm well aware that ocBuilder takes care of those, the point was that my tool doesn't yet.

 

I thought it would be a fun challenge to see if I could make a command line tool that will read the config.plist and then build a complete EFI folder based on it.

 

Anyways, thanks again for the reply, and thanks for all your work! 

Not at all, just some of the things you listed out where wrong and wanted to correct those things for you.

 

Thanks about the /usr/local/bin, I did not realize you did not need root privileges in order to install the build tools inside that location. I have updated my app to remove the root privileges now.

 

I would assume you can do that using /usr/libexec/PlistBuddy, with that being said, Apple has removed that tool from Catalina though.

 

[Proxary]

Hello guys I have a little bit problem when I booting with OpenCore 0.5.0 I don't can select my Recovery hard drive at startup has OpenCore a keyboard lock at startup or not ?

[rusty-bits]

4 hours ago, Pavo said:

I would assume you can do that using /usr/libexec/PlistBuddy, with that being said, Apple has removed that tool from Catalina though.

Nice to hear about ocBuilder, I'm going to check it out again.

 

Yes, I'm using PlistBuddy in the auto branch of my tool.  It reads the Drivers and Kexts from config.plist, then gets the repo url from a repo.plist.

It's working okay, but some of the code still feels quite clunky and needs more work.  

It figures that Apple removed the PlistBuddy tool from Catalina. Thanks a lot, Apple.