OpenCore General Discussion

[Pavo]

6 minutes ago, rusty-bits said:

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.

Seems they replaced PlistBuddy with plutil.

[AlGrey]

If I want to MatchKernel version 17. and 18.  can I do it in a single patch or do I have to duplicate the patch and write 17. for one and 18. for the other ?

[DonBronko]

@gengik84

 

Thank you its working now. 

 

[gengik84]

12 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.

Maybe in the future?
for now it is always here

iMacdiGengik84:~ $ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.15
BuildVersion:	19A536g
iMacdiGengik84:~ $  ls /usr/libexec | grep PlistBuddy
PlistBuddy

 

[STLVNUB]

Will this work on a Mac, primarily to change SMBIOS

[vit9696]

@Snikii for Ivy Bridge you need to generate CPU states with something like https://github.com/Piker-Alpha/ssdtPRGen.sh.

 

@STLVNUB, yes, it works fine.

[Sniki]

2 hours ago, vit9696 said:

@Snikii for Ivy Bridge you need to generate CPU states with something like https://github.com/Piker-Alpha/ssdtPRGen.sh.

Hi @vit9696

It's a Haswell laptop not ivy bridge.

Intel Core i5 4300U

[bronxteck]

4 hours ago, STLVNUB said:

Will this work on a Mac, primarily to change SMBIOS

yes i tried it on an imac yesterday. the only thing is you have to hold the option key at boot to load OC first.

[STLVNUB]

5 minutes ago, bronxteck said:

yes i tried it on an imac yesterday. the only thing is you have to hold the option key at boot to load OC first.

I think the idea is to bless bootx64.efi then it loads by itself

 

[bronxteck]

good to know. thanks will try it when i figure out how. i am running Catalina latest beta on that imac with OC 4.0   

[leesureone]

On 8/15/2019 at 10:00 PM, Matgen84 said:

 

Your DSDT is good and effective (idem on CLOVER/ Catalina). I don't want to blame it on OC: I apologize for my comments. (Sorry for my bad english)

 

I was wrong to review the config.plist with Opencore configurator (macKie app) and save it by habit. What must have broken it, maybe.

 

So I want to continue to use DSDT + Config.plist on my Gigabyte Z390 system for testing OpenCore. 

 

Thanks

Hello, I was wondering if you ever got your OC configuration going? I've got the same motherboard and wondering if you would mind sharing your EFI folder?

[bronxteck]

i got the imac to boot to OC directly.

i had to boot to recovery but i had to enable AppleBootPolicy in OC uefi in config.plist to be able to boot recovery from OC.

then i had to run terminal and do

csrutil disable

then reboot into catalina then in terminal use 

sudo bless --device /dev/disk0s1 --file BOOTx64.efi --setBoot

my imac has only one internal drive hence disk0s1

the only weird thing i have noticed is that i had one instance of the machine not wanting to power on and since then my fans have been running full blast since. but the imac does power on and function. also sometimes the apple mouse gets disconnected

 

edit: i did an SMC reset and the fans are back to normal. i powerd off the machine. pulled the power cord for 15 seconds. plugged it back in waited 5 seconds then powered on the imac.

 

Edited August 27, 2019 by bronxteck

[canyondust]

41 minutes ago, bronxteck said:

 

edit: i did an SMC reset and the fans are back to normal. i powerd off the machine. pulled the power cord for 15 seconds. plugged it back in waited 5 seconds then powered on the imac.

 

Were you able to reenable SIP after this?

[bronxteck]

42 minutes ago, canyondust said:

Were you able to reenable SIP after this?

I did not try re enabling sip as. it does not bother me being disabled

[canyondust]

5 minutes ago, bronxteck said:

I did not try re enabling sip as. it does not bother me being disabled

 

I ran SIP disabled for 3 years, and decided to enable it when I moved to OC. The only difference has been theoretical

[tunglamvghy]

On 8/20/2019 at 9:48 PM, tmbt said:

Hi guys,

i've performed a major upgrade from an old OpenCore version 0.2 to the new 0.4. While doing that i also upgraded most of my kexts (Lilu, whatervergreen etc).

After that i'm having a message while loading the MacOS :

Dependency com.apple.iokit.IOHIDSystem fallback to com.apple.iokit.IOHIDSystem succeded. Please fix your kext!

 

It appears while macos is loading on top of the Apple and the loading bar. The system is working as usual but i would like to fix it anyway. 

Could someone please point me on the right direction ?

 

Thanks

Mattia

 

I've the same issue but it stop booting. Have you fix it yet?

Edited August 27, 2019 by tunglamvghy1210

[STLVNUB]

15 hours ago, bronxteck said:

yes i tried it on an imac yesterday. the only thing is you have to hold the option key at boot to load OC first.

Can you please share your OC, mine does nothing

[vit9696]

17 hours ago, Sniki said:

Hi @vit9696

It's a Haswell laptop not ivy bridge.

Intel Core i5 4300U

Hmm, I rechecked your panic screen, and to be honest it does not even look like a CFG Lock (or any MSR stuff), more like dereferencing null pointer. Perhaps you should consider looking somewhere else.

 

16 hours ago, STLVNUB said:

I think the idea is to bless bootx64.efi then it loads by itself

 

Correct, and you use a separate GUID space with FwRuntimeServices.efi to avoid other options getting into your way of running.

[hardcorehenry]

Sorry @PMheart , but I think this fragment has to be corrected:

 

call in XNU kernel. Normally it is only the value of \texttt{EAX} that needs to be taken care of,

which represents the exact CPUID. And the remainders are to be left as zeroes.

For instance, \texttt{A9 06 03 00} stands for CPUID \texttt{0x0306A9} (Ivy Bridge).

A good example can be found at

\href{https://github.com/acidanthera/bugtracker/issues/365}{acidanthera/bugtracker\#365}.

(See \texttt{Special NOTES for Haswell+ low-end})

 

I used to boot my Intel Pentium Haswell with fake CPUID Ivy Bridge 0x0306A0

[PMheart]

33 minutes ago, hardcorehenry said:

Sorry @PMheart , but I think this fragment has to be corrected:

  

call in XNU kernel. Normally it is only the value of \texttt{EAX} that needs to be taken care of,

 which represents the exact CPUID. And the remainders are to be left as zeroes.

For instance, \texttt{A9 06 03 00} stands for CPUID \texttt{0x0306A9} (Ivy Bridge).

A good example can be found at

\href{https://github.com/acidanthera/bugtracker/issues/365}{acidanthera/bugtracker\#365}.

(See \texttt{Special NOTES for Haswell+ low-end})

  

I used to boot my Intel Pentium Haswell with fake CPUID Ivy Bridge 0x0306A0

Hello,

 

Sorry, I didn't quite catch that. Could you please point out the changes that I am supposed to handle? Thanks!

[hardcorehenry]

"For instance, \texttt{A0 06 03 00} stands for CPUID \texttt{0x0306A0} (Ivy Bridge)" , thou I'm not using fake CPUID in favor of cpu family kernel patch(VDA decoding), it was the only fake CPUID I was able to boot my hackintosh

Edited August 27, 2019 by hardcorehenry

[Sniki]

2 hours ago, vit9696 said:

does not even look like a CFG Lock (or any MSR stuff), more like dereferencing null pointer. Perhaps you should consider looking somewhere else.

Thanks @vit9696

Do you have any suggestions/hint on where the problem could be ?

I checked configuration.pdf many times but can't find any reference related to this problem

 

Any idea ?

I had the OC folder attached as well,

Let me know if you need more files/logs for troubleshooting.

Edited August 27, 2019 by Sniki

[tmbt]

5 hours ago, tunglamvghy1210 said:

I've the same issue but it stop booting. Have you fix it yet?

Yes it seems the problem was Rehabman version of voodoops2. Now i'm using Acidanthera version and the error is gone :

https://github.com/acidanthera/VoodooPS2

 

Mattia

Edited August 27, 2019 by tmbt
writing error

[canyondust]

5 minutes ago, bronxteck said:

I did not try re enabling sip as. it does not bother me being disabled

 

I ran SIP disabled for 3 years, and decided to enable it when I moved to OC. The only difference has been theoretical

[D-an-W]

Would anyone know the decimal number to use to in Scan Policy to enable USB scanning but not show EFI please? 

 

I currently have it set at 0 which works but also shows EFI, I also tried 5,177,603 but that didn't show any more and also gave an error before the boot selector screen.