Im sorry, this might be a stupid question from my lenguaje barrier but what exactly do you mean by this
Last edited:
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
I think he means "on hearing the Gong" sound, the normal bong sound on start up.
I have that turned off in the Sound settings, but many leave it on.
I believe he means you have to hold option right on chime sound at start
MBA 6,1, 13.4 and OCLP 0.6.6 release. Getting the familiar keyboard shortcut crash with various apps, same error report for each. I need to look back to see how this was resolved.
Prior to this error, I was getting Preview crashing while trying to crop an image, and Image Capture crashed while trying to dump iPhone photos into a new folder.
Now I am getting the same report error when using Command-Q to quit anything.
UPDATE: A restart solved the Preview cropping crash, but when drawing the box, only the blue dots show, not the dotted outline. Also solved for now is the keyboard shortcut crash when copying/pasting and quitting apps – except OCLP just crashed when I quit it after checking settings.
The latest Photoshop is suddenly giving the graphics error we have seen before. I do not see any available Graphics settings options.
Update 2: A second round of root patching solved the app crash and PS graphics errors, the missing Preview crop outline as well as an issue with System Settings not displaying options under certain categories.
Also, should "Host Model" be set to my actual computer ID (MacBookAir6,1)? I did not customize OCLP at all.
**********************
The error report from earlier:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_MEMORY_ERROR at 0x00007ff910e16000
Exception Codes: 0x000000000000000a, 0x00007ff910e16000
Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10
Terminating Process: exc handler [5774]
VM Region Info: 0x7ff910e16000 is in 0x7ff910df8000-0x7ff910e1b000; bytes after start: 122880 bytes before end: 20479
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
unused __TEXT 7ff910d8d000-7ff910df8000 [ 428K] r-x/r-x SM=COW ...ed lib __TEXT
---> __TEXT 7ff910df8000-7ff910e1b000 [ 140K] r-x/r-x SM=COW ...A/SidecarCore
__TEXT 7ff910e1b000-7ff910e1f000 [ 16K] r-x/r-x SM=COW ...NonBaseSystem
Kernel Triage:
APFS - (arg = 0xffffff8000080000) Encountered a compressed data hash mismatch
VM - (arg = 0x0) Page has restart bit set
APFS - (arg = 0xffffff8000080000) Encountered a compressed data hash mismatch
VM - (arg = 0x0) Filesystem pagein returned an error in vnode_pagein
VM - (arg = 0x0) Page has error bit set
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Prior to this error, I was getting Preview crashing while trying to crop an image, and Image Capture crashed while trying to dump iPhone photos into a new folder.
Now I am getting the same report error when using Command-Q to quit anything.
UPDATE: A restart solved the Preview cropping crash, but when drawing the box, only the blue dots show, not the dotted outline. Also solved for now is the keyboard shortcut crash when copying/pasting and quitting apps – except OCLP just crashed when I quit it after checking settings.
The latest Photoshop is suddenly giving the graphics error we have seen before. I do not see any available Graphics settings options.
Update 2: A second round of root patching solved the app crash and PS graphics errors, the missing Preview crop outline as well as an issue with System Settings not displaying options under certain categories.
Also, should "Host Model" be set to my actual computer ID (MacBookAir6,1)? I did not customize OCLP at all.
**********************
The error report from earlier:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_MEMORY_ERROR at 0x00007ff910e16000
Exception Codes: 0x000000000000000a, 0x00007ff910e16000
Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10
Terminating Process: exc handler [5774]
VM Region Info: 0x7ff910e16000 is in 0x7ff910df8000-0x7ff910e1b000; bytes after start: 122880 bytes before end: 20479
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
unused __TEXT 7ff910d8d000-7ff910df8000 [ 428K] r-x/r-x SM=COW ...ed lib __TEXT
---> __TEXT 7ff910df8000-7ff910e1b000 [ 140K] r-x/r-x SM=COW ...A/SidecarCore
__TEXT 7ff910e1b000-7ff910e1f000 [ 16K] r-x/r-x SM=COW ...NonBaseSystem
Kernel Triage:
APFS - (arg = 0xffffff8000080000) Encountered a compressed data hash mismatch
VM - (arg = 0x0) Page has restart bit set
APFS - (arg = 0xffffff8000080000) Encountered a compressed data hash mismatch
VM - (arg = 0x0) Filesystem pagein returned an error in vnode_pagein
VM - (arg = 0x0) Page has error bit set
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Attachments
Last edited:
That's right guys. I clarified that need to press the Option key on the startup chime (also called Gong) because some OCLP installers (it happens to me sometimes too...) forget that when the Mac restarts need to press Option key, hold it until the EFIBoot icon appears, select it (actually it already is) and so to press Enter key to activate a new OCLP Build.
OTA update from 13.2.1 and OCLP 0.6.6 on MBA 7,2 (with AMFI Pass whether needed or not!) to 13.4 with OCLP 0.6.7n (with AMFI Pass) was successful and quite fast.
For 13.4 you need AMFIpass, if you want AMFI enabled.
The best way is probably to try running apps that need AMFI enabled. You can perform a couple of tests to make sure you're not disabling AMFI and that you are loading Dhinak's AMFIPass:
There are other ways to determine status, but this is what I do. In terminal:
Code:
nvram -p | grep amfiIf this returns nothing, you don't have amfi=0x80 or amfi_get_out_of_my_way=1 boot-args
Code:
kextstat -a | grep AMFIThis should return status showing AMFIPass.kext has loaded
I see multiple people mentioning issues here earlier with a Radeon RX 580 resulting in a black screen with latest OCLP/Ventura versions. Unfortunately none seem to post how they have resolved it.
Have the following: Mac pro 4,1, flashed to 5,1 with RX 580, fresh install of Monterey or Ventura using OCLP 0.6.6: Installation of Ventura 13.4 completes, I can go through the wizard and reboot as much as I want when running OpenCore from the USB drive.
As soon as I install OpenCore on my SSD, the progress bar hangs indefinitely at boot. Verbose mode gives an empty black screen after not showing any error and hangs. If at that point I swap the GPU with my GT120, I'm able to boot into macOS.
When booting from the USB drive again (by doing a PRAM reset and first booting with only the USB drive) everything works and root patches are installed.
With the GT120, after installing OpenCore to the SSD I'm able to boot into Ventura/Monterey without issues. I can run the root patches and everything works fine. As soon as I swap with the RX580, I get a stuck loading bar or black screen (in verbose mode) at the end of booting into macOS.
Already tried the following:
- Reverted the root patches: working with GT120, black screen with RX 580 or R9
- Re-applied the root patches using GT120: same result
- Tried OCLP 0.6.5 and the 0.6.7 beta: same result
- When the screen is black, the machine is pingable and screen sharing asks for a username/password but never actually connects
- NVMRAM reset
- SMC reset
- Recreated the installer and did multiple re-installs
- Removed all other devices (NVMe drive, USB3 card,...)
- GPU works perfectly fine in Windows 11
Anyone has an idea?
EDIT:
After writing this, I figured it was clear that there is something different with OpenCore on the USB drive and what gets built and written to the USB drive after installation. I created OpenCore on the USB drive on another device (2019 MacBook Pro) by selecting Mac Pro 5,1. The same gets selected when building OpenCore from the Ventura install on the Mac Pro itself but still I'm not able to boot with that using the RX 580.
I forced the Mac to boot from the USB drive as follows (as I don't see the bootloader and can't use that to select where to boot from, and am no longer able to get to macOS):
- Removed the SSD
- Did a PRAM reset with the USB drive connected
- Let the Mac boot OpenCore from the USB drive (this is now set as the default in PRAM/NVRAM apparently
- Reconnected the SSD
- The Mac boots OpenCore from the USB drive (I can tell as the Ventura installer is the default option here)
- Selecting my SSD here leads to a successful boot
Then I mounted both EFI partitions (from the USB drive and SSD) and copied the contents over to the desktop for later comparison.
When done, I copied the contents of the EFI of the USB over to the EFI on the SSD and rebooted without the USB drive.
And... macOS booted flawlessly.
Here's a screenshot from what I did exactly:
So clearly the difference is with some files/settings that are getting written/build from Ventura. I'll do a comparison when I have some more time.
Have the following: Mac pro 4,1, flashed to 5,1 with RX 580, fresh install of Monterey or Ventura using OCLP 0.6.6: Installation of Ventura 13.4 completes, I can go through the wizard and reboot as much as I want when running OpenCore from the USB drive.
As soon as I install OpenCore on my SSD, the progress bar hangs indefinitely at boot. Verbose mode gives an empty black screen after not showing any error and hangs. If at that point I swap the GPU with my GT120, I'm able to boot into macOS.
When booting from the USB drive again (by doing a PRAM reset and first booting with only the USB drive) everything works and root patches are installed.
With the GT120, after installing OpenCore to the SSD I'm able to boot into Ventura/Monterey without issues. I can run the root patches and everything works fine. As soon as I swap with the RX580, I get a stuck loading bar or black screen (in verbose mode) at the end of booting into macOS.
Already tried the following:
- Reverted the root patches: working with GT120, black screen with RX 580 or R9
- Re-applied the root patches using GT120: same result
- Tried OCLP 0.6.5 and the 0.6.7 beta: same result
- When the screen is black, the machine is pingable and screen sharing asks for a username/password but never actually connects
- NVMRAM reset
- SMC reset
- Recreated the installer and did multiple re-installs
- Removed all other devices (NVMe drive, USB3 card,...)
- GPU works perfectly fine in Windows 11
Anyone has an idea?
EDIT:
After writing this, I figured it was clear that there is something different with OpenCore on the USB drive and what gets built and written to the USB drive after installation. I created OpenCore on the USB drive on another device (2019 MacBook Pro) by selecting Mac Pro 5,1. The same gets selected when building OpenCore from the Ventura install on the Mac Pro itself but still I'm not able to boot with that using the RX 580.
I forced the Mac to boot from the USB drive as follows (as I don't see the bootloader and can't use that to select where to boot from, and am no longer able to get to macOS):
- Removed the SSD
- Did a PRAM reset with the USB drive connected
- Let the Mac boot OpenCore from the USB drive (this is now set as the default in PRAM/NVRAM apparently
- Reconnected the SSD
- The Mac boots OpenCore from the USB drive (I can tell as the Ventura installer is the default option here)
- Selecting my SSD here leads to a successful boot
Then I mounted both EFI partitions (from the USB drive and SSD) and copied the contents over to the desktop for later comparison.
When done, I copied the contents of the EFI of the USB over to the EFI on the SSD and rebooted without the USB drive.
And... macOS booted flawlessly.
Here's a screenshot from what I did exactly:
So clearly the difference is with some files/settings that are getting written/build from Ventura. I'll do a comparison when I have some more time.
Last edited:
You are awesome!
Update: MacBook Air 2012 / macOS Monterey 12.6.6 + AMFI Pass to Ventura 13.4 working!
Thanks guys!
Update: MacBook Air 2012 / macOS Monterey 12.6.6 + AMFI Pass to Ventura 13.4 working!
Thanks guys!
I just want to confirm as I have been updating through "software update" on my 11,4 but have a question. Right now I'm listed as a Beta tester and I'm on 13.3.1 but I don't want to install 13.5 Beta (only option) on my MacBook Pro. However, I did download 13.4 from "Mr Macintosh's" website. I extracted the package and it's in applications. Do I simply double click and install? Or do I have to install onto a USB and install through that?
BTW, I'm running OCLP 0.6.6
BTW, I'm running OCLP 0.6.6
Using MacBook Pro mid 2014 15 “ i7 broken screen using a usb to 13.4 patched no problems updating with AMFIPass OCLP 6.7 from 13.2.1 .
For this last round of OS update I first tried the flash drive route but couldn't successfully build one (I reported this a couple pages back), so I used the 13.4 installer I had downloaded through OCLP and ran it straight from Applications, after having built and installed the latest Open Core using 0.6.6 release.
It took a couple of extra manual restarts and one extra root patch to get things fully sorted.
BTW, I take a moderate approach to OCLP: I don't install macOS betas (I do this on a supported 2020 M1 MBP) and I don't use nightly or beta OCLP, but I do keep up with any development news.
Last edited:
If you do not follow the proper order, you will break your install. You turned off AMFI while you still had old root patches and that is why it is stuck. The process is there for a reason, people!
No, it should be loaded.
It seems like I need to clarify this: AMFIPass is not intended to fix any end user issues that I know of, besides
- adb breaking (it seems adb has some issue when AMFI is disabled?)
- Hypervisors not working (again, an issue with AMFI being disabled)
And as a general reminder: if you are posting that something is crashing, it is going to be incredibly hard to get to the bottom of it without crash reports.
Last edited:
After update to 13.4, not only new AppleTV+ content is not viewable, now after opening AppleTV App, the whole system freezes. I need to switch off... I guess it's because I tried to play some new content immediately after the update and now the show is presented in the "main" screen of the AppleTV app as a proposal and the whole system freezes after a few seconds.
Do you also discover that after 13.4+?
iMac 17,1, OCLP 0.6.7 AMFIpass
Do you also discover that after 13.4+?
iMac 17,1, OCLP 0.6.7 AMFIpass
OCLP 0.6.7Beta2 is working much better than I expected. First, let me say that I'm am not asking for support for my hackintosh and I fully understand that OCLP developers are not supporting hackintoshes.
That said...
I am now booting and running Ventura on my dMBP6,2 using my OCLP 0.6.7Beta2 EFI (AMFI and Library Validation fully ENABLED). My current Ventura volume was previously installed with AMFI disabled and Library Validation disabled and patched with OCLP 0.6.6 (Release). After updating my EFI (to enable AMFI and enable Library Validation), I booted Ventura and applied post-install patches using OCLP 0.6.7Beta2 (after changing Settings > Host Model to "MacBookPro 6,2"). 0.6.7 post-install patches applied without any issues and now Ventura is running perfectly (for my purposes). I am able to transition existing volumes from AMFI-disabled/Library-Validation-Disabled to AMFI-enabled/Library-Validation-enabled without issues. I understand that this is just an indicator of progress and may not be true with future versions of OCLP. To me, this is an incredibly positive development.
Set Target Model
Re-apply 0.6.7 Post-install patches over 0.6.6 patches
Post-install patches applied with no issues
That said...
I am now booting and running Ventura on my dMBP6,2 using my OCLP 0.6.7Beta2 EFI (AMFI and Library Validation fully ENABLED). My current Ventura volume was previously installed with AMFI disabled and Library Validation disabled and patched with OCLP 0.6.6 (Release). After updating my EFI (to enable AMFI and enable Library Validation), I booted Ventura and applied post-install patches using OCLP 0.6.7Beta2 (after changing Settings > Host Model to "MacBookPro 6,2"). 0.6.7 post-install patches applied without any issues and now Ventura is running perfectly (for my purposes). I am able to transition existing volumes from AMFI-disabled/Library-Validation-Disabled to AMFI-enabled/Library-Validation-enabled without issues. I understand that this is just an indicator of progress and may not be true with future versions of OCLP. To me, this is an incredibly positive development.
Set Target Model
Re-apply 0.6.7 Post-install patches over 0.6.6 patches
Post-install patches applied with no issues
Last edited:
Installed 13.4 from Mr Macintosh’s site and all went well. Simply downloaded, opened Zip file which extracted to applications and double clicked to install.
The prevailent issues wth Ventura 13.4 and beyond on un-supp Macs is AppleTV, slow Bluetooth KB connect; these two issues were not present with 13.2.1. 🧐
My Ventura baseline is 13.2.1 patched with OCLP 0.6.7Beta2, booting with OC 0.9.2 (AMFI and Library Validation both ENABLED). Works great.
With AMFI enabled, I'm receiving permission prompts again!
Last edited:
13.2.1 appears bug-free, overall.
Hello.
I have strange values when I measure the disk speed with "blackmagic disk speed test".
I have this system.
- Mac pro late 2013
- Xeon processor with 6 cores
- Dual AMD Firepro D500
- 16 GB of RAM
This computer came to me without an SSD, so with an adapter i installed a KINGSTON SNV2S2000G on it.
When I made a test of the disk speed, i notice that:
- Reading speed is up and down. Suddenly he starts writing and then it's like he stops. The average speed is now 116 MB/Sec, although I have had much worse readings (40 MB/Sec).
- The read speed seems OK (1345MB/Sec without jumps).
I think that it must be cause by anything related with opencore legacy patcher, because i have windows installed in this disk too and i didn't notice speeds problems in windows (I wil search any program similar for windows to make the test).
¿Anybody know any problem with the disk speed in this model?
Thanks.
I have strange values when I measure the disk speed with "blackmagic disk speed test".
I have this system.
- Mac pro late 2013
- Xeon processor with 6 cores
- Dual AMD Firepro D500
- 16 GB of RAM
This computer came to me without an SSD, so with an adapter i installed a KINGSTON SNV2S2000G on it.
When I made a test of the disk speed, i notice that:
- Reading speed is up and down. Suddenly he starts writing and then it's like he stops. The average speed is now 116 MB/Sec, although I have had much worse readings (40 MB/Sec).
- The read speed seems OK (1345MB/Sec without jumps).
I think that it must be cause by anything related with opencore legacy patcher, because i have windows installed in this disk too and i didn't notice speeds problems in windows (I wil search any program similar for windows to make the test).
¿Anybody know any problem with the disk speed in this model?
Thanks.