Jump to content

OpenCore General Discussion


dgsga
8,774 posts in this topic

Recommended Posts

Developers - thank you to those who stepped up and delivered OC 0.8.0.  The upgrade from OC 0.7.9 was effortless (I'm still performing manual updates without a configurator - just my preference).  To perform the upgrade, I applied the changes here.

  • Like 3
Link to comment
Share on other sites

Hello everyone.
Perhaps it is a problem because Japanese users do not know about it.
However, the administrator of a well-known Japanese forum has pointed out the following problem

In Sample.plist NVRAM / Add / 7C436110-AB2A-4BBB-A880-FE41995C9F82, the entry #INFO (prev-lang: kbd) is not taken to mean commented out, causing it to not start.

 Normally, I would fix a new OpenCore with the results of Ocvalidate, not from Sample, but the administrator there does not seem to have done so.

 What do you think? I feel like it would be nice if I could add a few comments, but I also think it's a bit nosy.

Thank you

 

Link to comment
Share on other sites

Guest 5T33Z0

@deeveedee According to the documentation, this quirk enables full functionaliy of Bluetooth including Continuity (I guess on modules which don't work out of the box) so that Airdrop and Handoff work (again).

Link to comment
Share on other sites

4 hours ago, deeveedee said:

@miliuco and @5T33Z0 - thank you for the responses - I appreciate that you made the effort.  I didn't word my question well.  I'd like to know what was broken in ExtendBTFeatures quirk that required the fix in this commit.

Hi - If I may, I'd say it wasn't really broken as such, this Fix is more of an improvement??!!

  • Like 1
Link to comment
Share on other sites

22 hours ago, deeveedee said:

Does anyone know what this 0C 0.8.1 commit actually fixes for the ExtendBTFeatureFlags quirk?


I'm no developer but my understanding, from looking at the code, is that another (Version 3) BTFeatureFlag patch (OC quirk introduced with v0.6.2 which had replaced BT4LEContinuityFixup) was added to now help patch identifier: com.apple.iokit.IOBluetoothFamily's kernel base/function: __ZN17IOBluetoothDevice25setDeviceSupportedFeatureEj (most likely a new (or existing) class of function found in newer macOS releases that is responsible for proper BT functionality) which, I believe, would be considered an improvement in the case certain BT features (like Watch Unlock) were broken for users on newer macOS release due to this function not being patched yet.

Also, the changelog's wording for the commit was later corrected to improved instead of fixed.

Edited by aben
  • Like 3
Link to comment
Share on other sites

Guest 5T33Z0

Today the replacement GPU for my dead GTX760 arrived: Saphire RX580 Nitro+

The Adrenaline App says this card uses 256 MB of rezisable BAR.

Since my previous GPU didn't support this feature, do I have to change anything in the BIOS or Config - or both? I always found these settings confusing since there are 2 options in OC: ResizeGPUBars and ResizeAppleGPUBars.

Thanks.

Link to comment
Share on other sites

@eSaF and @aben - all good guesses.  Thanks.

 

Had I known that the commit only "improved" the kext instead of "fixing" it, I'd never have asked. LOL.  Much clearer.  Now I just need to figure out which macOS versions are "newer."

Edited by deeveedee
Link to comment
Share on other sites

@5T33Z0

You must enable ReBAR in Bios, usually it is near Above 4G Decoding, if Above 4G is disabled, Resizable Bar is hidden.

OpenCore config.plist: ResizeAppleGpuBars = 0 (to be able to boot macOS with ReBAR enabled in BIOS) and ResizeGpuBars = -1 (to prevent macOS from passing its ReBAR settings to Windows).

Nothing more.

My old XFX RX 580 had the same scores in Windows and macOS in benchmarks with or without ReBAR.

 

Edited by miliuco
  • Like 3
Link to comment
Share on other sites

28 minutes ago, deeveedee said:

@eSaF and @aben - all good guesses.  Thanks.

 

Had I known that the commit only "improved" the kext instead of "fixing" it, I'd never have asked. LOL.  Much clearer.  Now I just need to figure out which macOS versions are "newer."


Of course, unless stated or reported, one can only make a calculated guess at best here since there is no pre-defined/easy way of finding out what exactly are the contents or feature-set of this particular macOS BT function that was patched unless one has reported or experienced running into an issue for eg: a BT feature like Watch Unlock, when using a particular Apple Watch model, was all of a sudden acting broken on a newer macOS build that was updated on a hackintosh system fitted with a particular BT module that is reliant on OC’s current ExtendedBTFeatureFlag patches for the Watch Unlock functionality. Only in such situations, can the affected user actually find out if any particular unknown BT function, that requires patches, is being called by the OS via debugging ofcourse. Therefore, directly consulting with the user/developer who helped create the patch is the only way to actually know what exactly was the particular patch for and the macOS version this function was found as well.
Again, my best guess here with “newer” would be macOS 12 😂

Link to comment
Share on other sites

Guest 5T33Z0
48 minutes ago, miliuco said:

@5T33Z0

You must enable ReBAR in Bios, usually it is near Above 4G Decoding, if Above 4G is disabled, Resizable Bar is hidden.

OpenCore config.plist: ResizeAppleGpuBars = 0 (to be able to boot macOS with ReBAR enabled in BIOS) and ResizeGpuBars = -1 (to prevent macOS from passing its ReBAR settings to Windows).

Nothing more.

My old XFX RX 580 had the same scores in Windows and macOS in benchmarks with or without ReBAR.

 

Thanks.I did follow your instructions. Unfortunately, the GPU kept hanging at the Apple Logo while the system still booted to the desktop in the background. Since the card has 256 MB I also tried 8, but this didn't work either. I've disabled ReBAR again for now. I have no No patience to fiddle around with that stuff at the moment.

Link to comment
Share on other sites

@5T33Z0

That bug suggests misconfiguration in config.plist.

 

According to the OpenCore developers, ResizeAppleGpuBars has to be 0 (ReBAR enabled in BIOS) or -1 (ReBAR disabled in BIOS). No other value is recommended because macOS does not boot well.

 

ResizeGpuBars is always -1 which means that OpenCore does not pass to Windows ReBAR settings when Windows boots from OpenCore.

 

I did the test of booting macOS with the RX 580 GPU and ReBAR enabled and it booted fine on condition of having ResizeAppleGpuBars = 0.

 

But note 2 things:
- macOS does not benefit from this option, the quirks were added so that Windows users could have ReBAR enabled without having to disable it every time they run macOS
- Windows benefits from this option but in my opinion only with powerful GPUs, specifically 6800 and 6900.

Link to comment
Share on other sites

Guest 5T33Z0

@miliuco

I can only set ReBAR to "Auto" in BIOS. The rest of the values for the config were entered as suggested. But since it doesn't seem beneficial to use ReBAR on the RX580 I leave it disabled.

Link to comment
Share on other sites

@5T33Z0

Here are my settings running a quad Monitor setup, booting OSX (Monterey & Mojave ), Linux & Windows. Not a single glitch. :thumbsup_anim:

 

Above 4G Decoding : Disabled ( No difference of performance noted when engaged. Some rx580 users reported issues when enabled )

ResizeAppleGpuBars : -1

ResizeGpuBars = -1

agdpmod=pikera 

Edited by Ellybz
  • Like 1
Link to comment
Share on other sites

@Ellybz

I haven't noted difference when Above 4G enabled, as you. If Above 4G is disabled, ReBAR can't be enabled. When ReBAR disabled, the 2 GpuBars quirks must be -1.

 

@5T33Z0

My old RX 580 also worked better (or so it seemed to me) with agdpmod=pikera although this boot arg is intended for 5000 and 6000 series.

Edited by miliuco
  • Like 1
Link to comment
Share on other sites

25 minutes ago, 5T33Z0 said:

agdpmod=pikera is for navi gpu's but the rx580 is a polaris card.

With multiple monitors, my 38" Monitor stays black at the OSX login without it. 

Edited by Ellybz
  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

Toggle SIP flavours

 

About this note in the changelog:

"Added optional Enabled and Disabled flavours for Toggle SIP (allows theme designers to provide distinct icons)"

I see that the new ToggleSipEntry.efi driver has the same 4 properties of the rest of drivers (Arguments, Comment, Enabled, Path).

How is flavours set for this menu entry?

 

Link to comment
Share on other sites

Asking to myself.

It's an automated process. No need to set flavours for Toggle SIP.

  • If there is an icon named NVRAMTool.icns >> this icon is picked for all NVRAM tools (NVRAMReset and Toggle SIP)
  • If there are 2 icons named ResetNVRAM.icns and ToggleSip.icns >> each of them is picked for its related tool
  • If there are none of these icons, the generic Tool.icns is picked.

Source: Flavours.md file.

 

@blackosx @chris1111 and other artists: have a look into these changes.

 

Edited by miliuco
  • Like 3
Link to comment
Share on other sites

4 hours ago, miliuco said:

Asking to myself.

It's an automated process. No need to set flavours for Toggle SIP.

  • If there is an icon named NVRAMTool.icns >> this icon is picked for all NVRAM tools (NVRAMReset and Toggle SIP)
  • If there are 2 icons named ResetNVRAM.icns and ToggleSip.icns >> each of them is picked for its related tool
  • If there are none of these icons, the generic Tool.icns is picked.

Source: Flavours.md file.

 

@blackosx @chris1111 and other artists: have a look into these changes.

 

Hi @miliuco 😄 Yea  I build latest OC then created the ToggleSip.icns

Looks ok to me latest change

attaching here the Icons working with Flavours-AppleMonterey, Flavours-AppleDisk theme EDIT ** (I Add to Github on both themes)

ToggleSip.icns.zip

 

24012252.thumb.png.57b31dbf5b76cdfe0ed901e4c36556f1.png

 

Edited by chris1111
I Add to Github on both themes
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...