OpenCore General Discussion

[theroadw]

I'm using 1.3 stable and latest heliport, but refind was the one I had to go back to vers.0.12.0 as the newer versions didn't work with my Laptop

Edited May 14, 2021 by theroadw
add refind version

[SavageAUS]

Is there an option in OpenCore’s config to block OS updates? The latest beta would not appear until I booted an older version of clover.


Sent from my iPhone using Tapatalk

[mhaeuser]

@SavageAUS No. Are you sure your SMBIOS is configured correctly? What's the state of SIP?

[SavageAUS]

[mention=1083558]SavageAUS[/mention] No. Are you sure your SMBIOS is configured correctly? What's the state of SIP?

Smbios is / should be correct (iservices work). SIP was / is disabled.


Sent from my iPhone using Tapatalk

[mhaeuser]

Just now, SavageAUS said:

SIP was / is disabled.

Is it the exact same value as with Clover? Disabled SIP can bork updates.

[SavageAUS]

Is it the exact same value as with Clover? Disabled SIP can bork updates.

Yes exactly the same smbios and sip setup.


Sent from my iPhone using Tapatalk

[deeveedee]

@SavageAUS You've received some good responses to your questions.  It's easy to forget to express appreciation for the help.  Just a friendly reminder about the really simple "thanks" and "like" emojis at the bottom right of each post.

 

[mhaeuser]

@SavageAUS Hmm, still possible it's a sort of staged rollout, I don't know how Apple decides who gets which update when. As nobody else reported issues and afaik a few people upgraded already, I'd probably blame it and ask you to keep an eye in it (and wait a few days next time) in the future.

[Pavo]

@SavageAUS the APFS seal can also effect updates not showing up, check your seal to see if its broken or not. Use diskutil apfs list to check if snapshot is sealed or not.

[SavageAUS]

[mention=1083558]SavageAUS[/mention] Hmm, still possible it's a sort of staged rollout, I don't know how Apple decides who gets which update when. As nobody else reported issues and afaik a few people upgraded already, I'd probably blame it and ask you to keep an eye in it (and wait a few days next time) in the future.

Yeah I was assuming the same thing, so I waited an extra day and it still did not appear in system preferences until I booted back to my old clover EFI. So within 5 minutes it was not appearing then it was....Coincidental? Perhaps. Error on my behalf? Perhaps. I was just reporting what was happening to my machine at the time.
I appreciate the responses.


Sent from my iPhone using Tapatalk

[HenryV]

csr-active-config change to 6708000 in OC made the difference when updates didn't show.

[ghost8282]

33 minutes ago, HenryV said:

csr-active-config change to 6708000 in OC made the difference when updates didn't show.

Sorry may be (and probably it is) a stupid question, but why we need this into opencore? can't we just disable or enable sip through terminal?

[Avery B]

8 minutes ago, ghost8282 said:

Sorry may be (and probably it is) a stupid question, but why we need this into opencore? can't we just disable or enable sip through terminal?

There are specifically a few bits being set within csr-active-util (thus disabling that part of SIP) that can cause issues.
Iirc, specifically CSR_ALLOW_UNAUTHENTICATED_ROOT (bit 11) and CSR_ALLOW_APPLE_INTERNAL (bit 4) I've heard can cause issues, though admittedly I haven't really looked into it.
You can find out what all the different SIP values do here. CSR_DISABLE_FLAGS looks like the flags that get set when you just disable SIP through terminal.
Note that these are all bitmasks - if you want to convert them more closely to a value your used to, use a calculator to set whatever bits you want to use (both Windows and macOS have a programmer mode which allows you to set each bit specifically).
You'll get a hex value out of it, and if you swap the endianness, you'll get a value you can put into OC.

For example, if you have 0x00000608, (bit 3, 9, and 10 set), swapping the endiannes makes it 0x08060000 (split it into pairs of digits - 00 00 06 08, then reverse the order of those pairs. 00 00 06 08 -> 08 06 00 00 -> 0x08060000)
 

[ghost8282]

Hi all!

today is test day

As my signature suggests, I'm running mac os big sur on qemu.

The hard drive of this virtual machine was a sparse image file, a vdisk.

Today I tried to passthrough to the virtual machine my Marvell sata controller, so to get rid of the sparse image file, and have mac os installed in a more native hackintosh.

Before switching, I added the 3rd party sata kext to opencore and booted from the sparse image file: my marvell 88SE9230 sata controller was recognized, without nothing attached, ok that's good.

I backupped the sparse image file, deleted the partition of the disk in which the sparse image file was, and restored the backupped sparse image file to this hard drive (ssd), connected to the marvell controller, with dd command.

Booted and forced the opencore bootpicker to show: all entries related to mac os were there: primary BigSur disk and recovery partition.

However,

1- if I select Big Sur the system doesn't boot, without verbose after some time I have the prohibited symbol with the link to apple support for startup: with verbose mode on I have the last lines with "CNTL Auth fail"

2- I can boot into recovery but utility disk doesn't show my sata disk...

 

I'm attaching the opencore debug log, last line is "AmiShimTimerBoostExit changed current period to 100000"

I cannot find why the disk isn't detected by mac os, maybe you can help me in fixing this.

 

Thanks and have a good day!

 

Nevermind! I solved it by changing the target of the sata controller in libvirt to Bus 0x01, before it was on bus 0x00 and it didn't start

opencore-2021-05-15-120302.txt

Edited May 30, 2021 by ghost8282

[jinbingmao]

Changed OpenCanopy preferred image set to `Acidanthera\GoldenGate`。 

 

PickerVariant   

• Default — Acidanthera\GoldenGate.

•  

[Guest 5T33Z0]

I had an idea for an ease of use configuration feature in OpenCore - a field called "CPU Family" or something like that. This should contain fixed rules/presets for booter and kernel quirks. For example you enter `CometLake`or `Skylake`and it automatically enables the necessary quirks for the chosen CPU family in th background.

[Matgen84]

40 minutes ago, 5T33Z0 said:

I had an idea for an ease of use configuration feature in OpenCore - a field called "CPU Family" or something like that. This should contain fixed rules/presets for booter and kernel quirks. For example you enter `CometLake`or `Skylake`and it automatically enables the necessary quirks for the chosen CPU family in th background.

 

Have a look to Pavo-IM/OC-Gen X ont Github.  I don't test or use it.

Edited May 15, 2021 by Matgen84

[STLVNUB]

1 hour ago, 5T33Z0 said:

I had an idea for an ease of use configuration feature in OpenCore - a field called "CPU Family" or something like that. This should contain fixed rules/presets for booter and kernel quirks. For example you enter `CometLake`or `Skylake`and it automatically enables the necessary quirks for the chosen CPU family in th background.

Actually the whole plist should work off SMBIOS selection, automatically,  comparing real HW to fit the selected SMBIOS Family Apple HW

Edited May 15, 2021 by STLVNUB

[STLVNUB]

23 minutes ago, STLVNUB said:

Actually the whole plist should work off SMBIOS selection, automatically,  comparing real HW to fit the selected SMBIOS Family Apple HW

Now lets sit back and watch my post get shot down in flames

[mhaeuser]

@5T33Z0 Cannot work because they vary based on device (board) vendor and sometimes even revision.

 

1 hour ago, STLVNUB said:

Now lets sit back and watch my post get shot down in flames

In that case, why do you not just refrain from posting to this thread and spare us from your "ideas"?

[MacUser2525]

6 hours ago, Matgen84 said:

 

Have a look to Pavo-IM/OC-Gen X ont Github.  I don't test or use it.

I do it works flawlessly, except the default language always being Russian... I posted the change needed for English (US) in the thread for it on here.

 

 

[deeveedee]

On 5/15/2021 at 1:03 PM, STLVNUB said:

Actually the whole plist should work off SMBIOS selection, automatically,  comparing real HW to fit the selected SMBIOS Family Apple HW

 

The idea of having OC auto configure based on @5T33Z0 's "CPU family" or your SMBIOS is an interesting suggestion and is somewhat consistent with the OC sanity checker; however, it's an idea that runs counter to one of the core OC principles: Don't "hide" anything from the user.  One of the challenges that OC developers had with CLOVER was the number of "hidden" and "automatic" operations performed behind the scenes by CLOVER.  In my own experience, a competent product management team continues to encourage new ideas and never shoots them "down in flames."

Edited May 17, 2021 by tonyx86
corrected typo

[STLVNUB]

1 hour ago, tonyx86 said:

 

The idea of having OC auto configure based on @5T33Z0 's "CPU family" or your SMBIOS is an interesting suggestion and is somewhat consistent with the OC sanity checker; however, it's an idea that runs counter to one of the core OC principals: Don't "hide" anything from the user.  One of the challenges that OC developers had with CLOVER was the number of "hidden" and "automatic" operations performed behind the scenes by CLOVER.

Good documentation to spell out in plain English what any "hidden" options do and when.

 

[HenryV]

On 5/14/2021 at 6:13 PM, ghost8282 said:

Sorry may be (and probably it is) a stupid question, but why we need this into opencore? can't we just disable or enable sip through termina

Have found that once the installation snapshot is altered and a new boot snapshot is created, Big Sur has KP'd without altering the csr-active-config in Open Core.  

[ghost8282]

6 hours ago, HenryV said:

Have found that once the installation snapshot is altered and a new boot snapshot is created, Big Sur has KP'd without altering the csr-active-config in Open Core.  

 

Thanks HenryV, I think I had that issue too at the first big sur betas when all was quite new about the seal and I had kp too after breaking the seal, which I solved by not breaking the seal  ; thanks for adding this, it may be useful in the future.