Mykola told me this problem only happens on Macs with GCN dGPU + Skylake iGPU. I think it's most likely due to the problem being related to HEVC and my MacBook doesn't support hardware HEVC encode/decode...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Switch from 13.5b1 zu b2 went fine on my haswell MM 7,1. Did amfipass post patch again and everything is like it should be.
My broadwell MBA 7,2 doesnˋt find OTA update 13.5b2 -neither with revert post patch nor with post patched.
My broadwell MBA 7,2 doesnˋt find OTA update 13.5b2 -neither with revert post patch nor with post patched.
OK, so the issue is real ...
My iMac (17,1) doesn't support hardware encode, but the R9 M390 was able to support HEVC hardware decode in supported Monterey.
With OCLP Ventura, videos are rendered in low res when viewing in Photos.app and most apps that are decoding videos with hardware are impacted.
It's the main issue for me.
@dhinakg @ASentientBot
As FYI:
Funny enough, this started happening on my machine with the Apple Magic Mouse as well after updating to 13.4 using 0.6.6 Issue is system wide
Edit: Repatched with 0.6.5, issue remains. I get a feeling this is an issue related to 13.4 whatsoever since Bluetooth also disconnects without root patches installed.
___
Also since patching with 0.6.6 Kernelpanics seemingly related to HD4000 driver appeared:
panic(cpu 0 caller 0xffffff80005b3b93): Kernel trap at 0xffffff7f96c1c509, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffffb0b6f49360, CR3: 0x0000000004a94000, CR4: 0x00000000001626e0
RAX: 0x00000000002540d8, RBX: 0x0000000014900360, RCX: 0x000000000000e241, RDX: 0xffffffc4a833fc40
RSP: 0xffffffc4a833fd90, RBP: 0xffffffc4a833fdc0, RSI: 0xffffffc4a833fcc0, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000008, R11: 0x000000000000000a
R12: 0x0000000000000000, R13: 0x00000000002540d8, R14: 0xffffffb0b65f9000, R15: 0xffffffa9de1d8000
RFL: 0x0000000000010246, RIP: 0xffffff7f96c1c509, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffffb0b6f49360, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1
Panicked task 0xffffff96adb77698: 292 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffffa047539598, Frame : Return Address
0xffffffc4a833f750 : 0xffffff800046f4fd mach_kernel : _handle_debugger_trap + 0x4ad
0xffffffc4a833f7a0 : 0xffffff80005c3c54 mach_kernel : _kdp_i386_trap + 0x114
0xffffffc4a833f7e0 : 0xffffff80005b36d9 mach_kernel : _kernel_trap + 0x3c9
0xffffffc4a833f840 : 0xffffff800040f951 mach_kernel : _return_from_trap + 0xc1
0xffffffc4a833f860 : 0xffffff800046f7dd mach_kernel : _DebuggerTrapWithState + 0x5d
0xffffffc4a833f950 : 0xffffff800046ee87 mach_kernel : _panic_trap_to_debugger + 0x1a7
0xffffffc4a833f9b0 : 0xffffff8000bdceab mach_kernel : _panic + 0x84
0xffffffc4a833faa0 : 0xffffff80005b3b93 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffffc4a833fc20 : 0xffffff80005b3884 mach_kernel : _kernel_trap + 0x574
0xffffffc4a833fc80 : 0xffffff800040f951 mach_kernel : _return_from_trap + 0xc1
0xffffffc4a833fca0 : 0xffffff7f96c1c509 com.apple.driver.AppleIntelHD4000Graphics : __ZN20IGHardwareRingBuffer15dumpBatchBufferER14debugRegistersP20ResourceCacheElement + 0x117
Last edited:
Same for me, same machine iMac 17,1 but M395… Hope for a fix, but nevertheless wonderful work of the devs.
Apple systems are always focused on IQSV and the features of discrete graphics cards have long been removed from the system. But they can be returned manually.
To do this, you need to follow two steps. First, enter the commands from this list.
Here is the list of commands
And now the second step. In order for them to work, you need to create and then boot a kext, in which you need to register the properties previously removed by Apple. Here, on the example of Baffin or Elesmere.
There is no executable in kext, only info.plist.
It boots, I use it for my old system.
I'm afraid my poor knowledge of english will not allow me to explain this more clearly.
I'll include this kext for reference. If it suits someone, you can use it.
I just want to say that this problem is being solved and I don't think the OCLP development team should be dealing with it.
I have a question regarding the 2012-13 A1398, which uses a proprietary SATA SSD.
The speed of the SSD has noticeably decreased.
Has anyone experienced this and may know a solution?
P.S. Some huge pictures turned out, for which I apologize, and I also apologize if this is not interesting to anyone.
To do this, you need to follow two steps. First, enter the commands from this list.
Here is the list of commands
And now the second step. In order for them to work, you need to create and then boot a kext, in which you need to register the properties previously removed by Apple. Here, on the example of Baffin or Elesmere.
There is no executable in kext, only info.plist.
It boots, I use it for my old system.
I'm afraid my poor knowledge of english will not allow me to explain this more clearly.
I'll include this kext for reference. If it suits someone, you can use it.
I just want to say that this problem is being solved and I don't think the OCLP development team should be dealing with it.
I have a question regarding the 2012-13 A1398, which uses a proprietary SATA SSD.
The speed of the SSD has noticeably decreased.
Has anyone experienced this and may know a solution?
P.S. Some huge pictures turned out, for which I apologize, and I also apologize if this is not interesting to anyone.
Last edited:
Viewed grey screen too. But I tried to install Ubuntu and Windows on my Macbook Pro 7,1 (mid-2010, 13-inch) - and Citrix working on both of them. I recommend.
Has anyone been able to update their mac to the latest Ventura 13.5 beta 2? Did the AMFIPass Beta Test need to run again?
Thanks
Thanks
What I think is the problem is that it's trying to use hardware HEVC decode but it's broken, I think this mostly explains why Chrome takes a while to load, it tries to use the decoder and gives up after some time, not sure if there are any crash logs. I've gone through something similar while fixing Polaris VA.
Unfortunately there is nothing I can do to help without an affected machine.
I hope this can be fixed... for now I am using windows 11 with OCLP 0.6.7 in my mid-2011 27inch iMac because my AirPods Pro 2 works flawlessly in that system.
It was necessary to immediately show this image.
This is the famous Sony Swordsmith - is a promotional video in Ultra-HD reproduced by Baffin.
This is a little strange for me, because I shared this experience a year ago. But the community rejected him
This is the famous Sony Swordsmith - is a promotional video in Ultra-HD reproduced by Baffin.
This is a little strange for me, because I shared this experience a year ago. But the community rejected him
EDIT: Leaving this post for others who may have experienced this problem. I was able to restore proper macOS upgrade behavior (13.2.1 -> 13.4) by resetting NVRAM a few times. After resetting NVRAM, I am now seeing the 13.4 macOS upgrade after disabling "Kernel > Patch: Disable _csr_check() in _vnode_check_signature"
After resetting NVRAM, the OCLP 0.6.7b2 EFI works as-is with no changes.
===================================
My MBP6,2 is running Ventura 13.2.1 booting with OC 0.9.2, AMFI and LV Enabled, AMFIPass.kext injected. All appears to be running well for me. I noticed that after enabling AMFI and LV with the required EFI updates, I was no longer seeing prompts to upgrade from 13.2.1 -> 13.4. I isolated this to the kernel patch "Kernel > Patch: Disable _csr_check() in _vnode_check_signature" in OC config.plist. When I restore this patch (which was removed when AMFI/LV was enabled), I see 13.2.1->13.4 upgrade prompts again and permission prompts (e.g., Camera, Microphone) still work.
Is anyone else noticing this? I have reported this on Discord.
After resetting NVRAM, the OCLP 0.6.7b2 EFI works as-is with no changes.
===================================
My MBP6,2 is running Ventura 13.2.1 booting with OC 0.9.2, AMFI and LV Enabled, AMFIPass.kext injected. All appears to be running well for me. I noticed that after enabling AMFI and LV with the required EFI updates, I was no longer seeing prompts to upgrade from 13.2.1 -> 13.4. I isolated this to the kernel patch "Kernel > Patch: Disable _csr_check() in _vnode_check_signature" in OC config.plist. When I restore this patch (which was removed when AMFI/LV was enabled), I see 13.2.1->13.4 upgrade prompts again and permission prompts (e.g., Camera, Microphone) still work.
Is anyone else noticing this? I have reported this on Discord.
Last edited:
I have updated all my Mac laptops to Ventura 13.5 Beta (22G5038d) without issue. I never did the AMFIPass Beta Test. I just updated to OCLP 0.6.6 and had no issue with the updating process. For me it was all a smooth update then I performed the usual root patches and was all set.
Thanks, did you perform the exact same procedures as for the first time of using the AMFIpass?
I had the AMFIpass applied before upgrading OTA (+11Gb) to 13.5B2 (22G5038d). Upon reboot, OCLP prompted me to reinstall the post-patch which I did and so far so good. I did not take the nightly OCLP, still using the AMFIpass version. Hoping the Devs incorporate/merge it for the next nightly/version.
Upgraded from Monterey to Ventura (13.4) with latest OCLP 0.6.6 and it's running flawlessy this side on my MacPro 6,1.
Only hiccup I ran into was during the install process it would pop up with a software update error. I can't recall the exact wording, but it was pretty late in the install process after a couple of reboots.
I first did a soft shutdown and retried again, but it persisted. Eventually I found that you need to reset PRAM if this happens, so did that and the install finished. Not sure if this might be helpful to other people experiencing the same issue.
Really great keeping these old Macs going, thanks a lot!
Only hiccup I ran into was during the install process it would pop up with a software update error. I can't recall the exact wording, but it was pretty late in the install process after a couple of reboots.
I first did a soft shutdown and retried again, but it persisted. Eventually I found that you need to reset PRAM if this happens, so did that and the install finished. Not sure if this might be helpful to other people experiencing the same issue.
Really great keeping these old Macs going, thanks a lot!
macBook Pro 11.3
Update 13.5 Beta (225038d) AMFIPass patcher all done, symply reinstall RootPatch after updated
Thanks @dhinakg
Update 13.5 Beta (225038d) AMFIPass patcher all done, symply reinstall RootPatch after updated
Thanks @dhinakg
If you have any related crash logs, that could help understand what's happening.