Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Sorry for insist but I don’t know what L/E standard graphic kexts is and where I need to copy. I need more explicit instructions, thanks
The poster ⬇︎⬇︎⬇︎⬇︎ already mentioned this, if you don't know what L/E means you should not be playing with betas.
There was a small mistake though, it should be : /L/E
Believe me i don't like that you brick your mac. As you see nobody reacted to my post cause anyone knows what i mean and doesn't like it. Please stay on the last version working as a lot of people told before. I am not a developer and this is a site about how to boot System on unsupported mac not a support site of how to boot a beta version.....
Thumbs up X 1000
 
Good news for Macs with Ivy Bridge, Haswell and Kepler GPUs:

[…]

  • Resolve boot support for 3802-based GPUs with macOS 13.3
    • Applicable for following GPUs:
      • Intel Ivy Bridge and Haswell iGPUs
      • Nvidia Kepler dGPUs
    • Note: patchset now requires AMFI to be disabled, patchset still in active development to remove this requirement
[…]

… recently from the 0.6.2n changelog:


Let’s also hope that the current requirement of disabling AMFI will be removed, eventually…

:cool::)
 
Thanks to developers 13.3 RC 22E252 now works and root patched succesfully on my mac mini late 2012
Good news for Macs with Ivy Bridge, Haswell and Kepler GPUs:

[…]

  • Resolve boot support for 3802-based GPUs with macOS 13.3
    • Applicable for following GPUs:
      • Intel Ivy Bridge and Haswell iGPUs
      • Nvidia Kepler dGPUs
    • Note: patchset now requires AMFI to be disabled, patchset still in active development to remove this requirement
[…]

… recently from the 0.6.2n changelog:


Let’s also hope that the requirement of disabling AMFI can eventually be superseded…

:cool::)
Thank you it works
 
Good news for Macs with Ivy Bridge, Haswell and Kepler GPUs:

[…]

  • Resolve boot support for 3802-based GPUs with macOS 13.3
    • Applicable for following GPUs:
      • Intel Ivy Bridge and Haswell iGPUs
      • Nvidia Kepler dGPUs
    • Note: patchset now requires AMFI to be disabled, patchset still in active development to remove this requirement
[…]

… recently from the 0.6.2n changelog:


Let’s also hope that the current requirement of disabling AMFI will be removed, eventually…

:cool::)
Thanks, I have

Westmere chips, will the patch work?

Thanks
 
No improvements for chrome startup on my iMac 17.1 5K-27 with m390 GPU
Bad news…
I have the m395, but I'm mainly wanting to make decision going forward. If it's only Chrome based browsers now that are still affected, it's easy enough to just use Firefox, or Safari, as Chrome is only around for testing, not daily use. If the problem is still more serious than that, I need to start planning on what kind of computer I want to eventually replace this iMac with as there is no 27, or larger iMac in the Apple Silicon lineup, and I really don't want another type of mac but a 27' iMac, or even a 30" if Apple does that. It's just been the perfect size and feature set for an all in one.

I still plan on using this iMac until Monterey support runs out, as it's working just fine. It's more after that, that's the question I'm waiting to answer.
 
  • Like
Reactions: hvds
Applied the latest nightly, much better thank to the great Devs.

Transparency doesn't seem to work, and Safari is working *partly or is that because of AMFI?

* Needs to have a window in front otherwise no content shows up, some pages do work, PDF's work as well but that's the same as an unpatched system.
 
  • Like
Reactions: hvds and sinbad21
Applied the latest nightly, much better thank to the great Devs.

Transparency doesn't seem to work, and Safari is working *partly or is that because of AMFI?

* Needs to have a window in front otherwise no content shows up, some pages do work, PDF's work as well but that's the same as an unpatched system.

After applying root patch? Patches where noted as experimental while research continues.
 
There has just been another update on the github well 4 hours ago have you repatched built opencore again and patched efi then root patch.
Pretty sure it is the latest, I patched the OS less than 4 hours ago.


Screenshot 2023-03-23 at 23.00.59.png
 
No go over here with latest 0.6.2n
 

Attachments

  • B7D2B2DE-1483-469B-8724-3496F7751F9D.png
    B7D2B2DE-1483-469B-8724-3496F7751F9D.png
    41.5 KB · Views: 160
  • 8A3854E4-6057-4C3C-A7D1-A193BE973325.png
    8A3854E4-6057-4C3C-A7D1-A193BE973325.png
    40.8 KB · Views: 115
  • 974EEC72-1281-4FF1-9D1E-187585829963.png
    974EEC72-1281-4FF1-9D1E-187585829963.png
    83.5 KB · Views: 117
So, Graphics should be back to normal, still some issues.
For instance, just a while ago finder freezes the whole system, takes
a bit to recover-this several times, takes about 1-2 minutes to completely
vanish.


Screenshot 2023-03-23 at 23.21.12.png
 
So, Graphics should be back to normal, still some issues.
For instance, just a while ago finder freezes the whole system, takes
a bit to recover-this several times, takes about 1-2 minutes to completely
vanish.


View attachment 2177836

again from what I understand the patches are experimental as 13.3 is not actually released don’t expect full support from a nightly build that’s why these patches shouldn’t be used until there’s a full release as posted there’s no reason to install a unreleased version of OCLP or MacOS the patches are more for people that make the mistake of updating when they shouldn’t as of yet but again this has been posted many times.
 
  • Like
Reactions: TimmuJapan
again from what I understand the patches are experimental as 13.3 is not actually released don’t expect full support from a nightly build that’s why these patches shouldn’t be used until there’s a full release as posted there’s no reason to install a unreleased version of OCLP or MacOS the patches are more for people that make the mistake of updating when they shouldn’t as of yet but again this has been posted many times.
I am just reporting what I see, I know what I am doing, been using Macs for a quarter of a decade.

I don't expect anything.
 
Applied the latest nightly, much better thank to the great Devs.

Transparency doesn't seem to work, and Safari is working *partly or is that because of AMFI?

* Needs to have a window in front otherwise no content shows up, some pages do work, PDF's work as well but that's the same as an unpatched system.
I have these issues with my mBP 5,1 2008. With the latest 0.62n MM 7,1 haswell Safari works normal with 13.3 rc.
 
I have these issues with my mBP 5,1 2008. With the latest 0.62n MM 7,1 haswell Safari works normal with 13.3 rc.
Pretty sure Graphic support is still off even though it shows up in System Information.
Tearing and jerky scrolling, even in Finder.
Brave (Browser) seems to work fairly well, slight tearing, smoother scrolling but noticeable.

Screenshot 2023-03-23 at 23.45.47.png
 
Working now, the problem was that patching failed, unable to build new Kernel cache.
I deleted the offending Extension, then tried again and this time opacity is back as well
as a smoother system.
see the difference below.

Screenshot 2023-03-24 at 00.02.36.png
Screenshot 2023-03-24 at 00.33.40.png
 

Attachments

  • Screenshot 2023-03-24 at 00.02.36.png
    Screenshot 2023-03-24 at 00.02.36.png
    50.6 KB · Views: 52
  • Like
Reactions: sinbad21
I have the m395, but I'm mainly wanting to make decision going forward. If it's only Chrome based browsers now that are still affected, it's easy enough to just use Firefox, or Safari, as Chrome is only around for testing, not daily use. If the problem is still more serious than that, I need to start planning on what kind of computer I want to eventually replace this iMac with as there is no 27, or larger iMac in the Apple Silicon lineup, and I really don't want another type of mac but a 27' iMac, or even a 30" if Apple does that. It's just been the perfect size and feature set for an all in one.

I still plan on using this iMac until Monterey support runs out, as it's working just fine. It's more after that, that's the question I'm waiting to answer.
Chrome and Edge show the problem, but I am sure that other apps have also the same issue.
For the moment, I stay on Monterey ...
I will try again when official 0.6.2 is available.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.