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.

zfrogman

macrumors regular
Aug 17, 2019
114
147
EU
Hello Howser,
Thanks for your reply I had tried this back with 10.13.3 with no result. Doesn't hurt to try again possible with another USB stick; never know. Will keep you posted. Best.
Update Cannot boot into safe mode: Acting on Howser's suggestion to reinstall OS, I recreated the USB installer using 0.6.7 and Ventura 13.4. I. Installed Opencore to disk. I was able to access Safe Boot without needing to reinstall Ventura OS. Thanks Howser for your suggestion. Much appreciated
 
  • Like
Reactions: houser

lovecd

macrumors regular
Aug 14, 2022
165
14
Trying to create Ventura installer from open core legacy patch for my 2012 iMac 27” desktop, but always receive this error, see attached. Does anyone know solutions?

Thanks,
 

Attachments

  • IMG_8544.jpeg
    IMG_8544.jpeg
    938.5 KB · Views: 196
  • IMG_8544.jpeg
    IMG_8544.jpeg
    938.5 KB · Views: 57

iPlasm

macrumors member
Aug 20, 2020
42
27
I faced this issue again just last evening when keyboard commands crashed an app. Then I recalled having to go back and adjust the Feature unlock setting. It of course resolved the problem once again since I recently updated my EFI using the 0.6.7 release on 13.4.

This is a good opportunity to ask: Why after making this adjustment does OCLP not reflect the change in Settings afterwards (even though it seems to stick in reality)?

The app won't remember the last changes you made, only at the time you've set the settings or changes in the Opencore.

I was tricked in the first time, I thought the Opencore did not made change or missed but I actually done it and Opencore did it. it is supposed to Opencore to show changes you made and not get confused. using version of 0.6.1

By the way, I am very thankfully for the OpenCore team as I have never seen an easier way to renew your Mac
 

hal90088

macrumors member
Oct 4, 2018
58
52
I found another problem with the webcam audio. I'm running OCLP in a 2012 Mac Mini. The system runs perfect. But today i connected to the computer a USB Webcam. This is the webcam that I plug in


The video signal is OK, but I have problems with the audio signal. The microphone have a good sound, but it seems that "something" is not capable to proccess the audio signal as fast than the voice requires. I hear clicks and software distorsions. Echo sometimes... Its a software problem. If I connect the webcam to the same computer running windows the sound is correct. In the box i can see that it's compatible with mac.

I apply the method described in this page.


(sudo sqlite3...)

Is there any fix for this problem?
 
Last edited:

phaser32

macrumors member
Apr 1, 2023
39
12
hi guys,
I would like to ask you for support for an anomaly from which I can't figure it out. I have a macbook pro 8.2 OCLP 0.6.7 and Ventura 13.4 (just updated).
Everything seems to work fine except Fusion (Wmware). Before I had version 13.2 and OCPL 0.6.1 and everything worked fine. I saw a few posts related to this issue and they mentioned the AMFI. Currently in the OCLP settings the AMFI is disabled.
When I try to open the vm it just says "Impossible to start vm", probably because of AMFI.
Would someone have the patience to explain to me how to get out of this problem?
Thx for attention
Warm regards
Ale
 

friviera

macrumors newbie
Sep 26, 2019
4
1
Hello, I am running Ventura 13.4 on a 15" MacBook Pro mid 2010 (with Nvidia+Intel graphics)
and I'm having an issue with it.
I can't use the integrated iSight and also in Anydesk it keeps asking to be allowed to capture the screen.
(I tried a couple of times to re authorize it without success)
I read that this could be related to the SIP settings applied by OCLP but didn't dare to play with it.
(0x803 setting in OCLP)
Is there any way to solve this ?
Thanks
 

davidlv

macrumors 68020
Apr 5, 2009
2,291
874
Kyoto, Japan
hi guys,
I would like to ask you for support for an anomaly from which I can't figure it out. I have a macbook pro 8.2 OCLP 0.6.7 and Ventura 13.4 (just updated).
Everything seems to work fine except Fusion (Wmware). Before I had version 13.2 and OCPL 0.6.1 and everything worked fine. I saw a few posts related to this issue and they mentioned the AMFI. Currently in the OCLP settings the AMFI is disabled.
When I try to open the vm it just says "Impossible to start vm", probably because of AMFI.
Would someone have the patience to explain to me how to get out of this problem?
Thx for attention
Warm regards
Ale
Resolved here: https://github.com/dortania/OpenCore-Legacy-Patcher/releases/tag/amfipass-beta-test
Be sure to follow the instructions exactly.
 
Last edited:

rehkram

macrumors 6502a
May 7, 2018
856
1,193
upstate NY
Hi!
I use a MacBook pro Mid 2012 (Model 10.1). I had Ventura 13.3 and OpenCore Legacy Patcher 0.65 installed and everything worked great. From the beginning, I was at Monterey for unsupported Macs and they regularly updated to Version Ventura 13.3. I didn't read the news related to Ventura 13.4 and now I have a problem and stuck with the patch on Graphics: Nvidia Kepler and Intel Ivy Bridge. The graphics are horrendously slow because it apparently doesn't use an accelerator. Any advice on how I can fix the problem. Thanks in advance
I have the same mid 2012 rMBP10,1 and it's working great with 13.4 + OCLP 6.7. Make sure you're on OCLP 6.7, if not, install it. Did you apply the OCLP post install patches that includes the ones for Kepler and HD4000?
 

makra

macrumors 6502
Dec 29, 2020
370
385
Northern Germany
Hello, I am running Ventura 13.4 on a 15" MacBook Pro mid 2010 (with Nvidia+Intel graphics)
and I'm having an issue with it.
I can't use the integrated iSight and also in Anydesk it keeps asking to be allowed to capture the screen.
(I tried a couple of times to re authorize it without success)
I read that this could be related to the SIP settings applied by OCLP but didn't dare to play with it.
(0x803 setting in OCLP)
Is there any way to solve this ?
Thanks
Try to search for tccplus here.
 

hal90088

macrumors member
Oct 4, 2018
58
52
I found another problem with the webcam audio. I'm running OCLP in a 2012 Mac Mini. The system runs perfect. But today i connected to the computer a USB Webcam. This is the webcam that I plug in


The video signal is OK, but I have problems with the audio signal. The microphone have a good sound, but it seems that "something" is not capable to proccess the audio signal as fast than the voice requires. I hear clicks and software distorsions. Echo sometimes... Its a software problem. If I connect the webcam to the same computer running windows the sound is correct. In the box i can see that it's compatible with mac.

I apply the method described in this page.


(sudo sqlite3...)

Is there any fix for this problem?
I'm conducting some tests to determine the origin of the problem with audio capture. I notice that if I connect a microphone (Apple headphones) to the microphone input of the Mac Mini, the problem is resolved, and the sound is completely smooth. It seems that the issue lies with the USB devices. I hear a constant 'click, click' sound, in addition to sound distortion. Could it be necessary to apply some sort of driver to solve this issue with USB audio devices?"
 

hal90088

macrumors member
Oct 4, 2018
58
52
I'm conducting some tests to determine the origin of the problem with audio capture. I notice that if I connect a microphone (Apple headphones) to the microphone input of the Mac Mini, the problem is resolved, and the sound is completely smooth. It seems that the issue lies with the USB devices. I hear a constant 'click, click' sound, in addition to sound distortion. Could it be necessary to apply some sort of driver to solve this issue with USB audio devices?"
mmmm... i see this information in this page.


One of the main causes of clicks, pops, errors and dropouts in any digital system is CPU overload or buffer overflow. These problems are most commonly caused by the amount of memory used for the buffer being set too low. Low buffer settings are perfect to keep latency to low and will work well with stripped down projects but as the CPU load increases there is a risk of inducing clicks and pops. To resolve this you should keep a constant eye on the buffer setting and make sure that you raise it as you move through your project and your CPU needs increase. This way you should stay clear of any clicks and pops.

¿Perhaps is a cpu speed problem? All the system seems that run fast.

The problem is in every program that use the webcam's mic (I tried with Facetime, Audacity, and photo booth)
 

luckyduke23

macrumors regular
Mar 28, 2023
158
200
I don't mind doing a clean install, that is what I would prefer to do anyway since I have my data already on a back up drive. I just was curious to see how Ventura worked on my Machine but feel weary about having an unsupported OS running my Machine and potentially corrupting my data over time due to some unforeseen issue.

I may still keep it on Ventura while I play around with it for a few days. I'm amazed how an 11 year old machine is still capable of running it :)
I prefer an officially unsupported OS with latest security patches better than the last official OS that does no longer get security updates...
 

erdfvsdxrfxcf

macrumors newbie
Apr 13, 2023
5
8
Hi, I have some problems with my MacBook Pro (15-inch, Early 2011).
  • A few weeks ago everything was fine. OCLP was installed (at least v0.6.2 with TerraScale 2 Acceleration and Beta Blut enabled) and macOS was running (at least macOS 13.3). My dedicated GPU (dGPU) was still activated.
  • But one day, all of the sudden, I could not pass the login screen anymore. As I remember I didn't install any updates before. But when booting the notebook, I could enter my password, but then the screen stayed black.
  • I first thought that my dGPU was dead. I wanted to disable it in the single user mode, but I could not enter it. Pressing "cmd"+"s" during startup gave me some output, but a few seconds later the machine restarted into recovery mode.
  • Also tried to reset the NVRAM and SMC.
  • Then I tried to clean install the whole Mac. I created a new bootable USB Stick (OCLP v0.6.7 and macOS 13.4). Entered the disk utility app. Wiped the SSD with Disk Utility. Reinstalled macOS from the USB Stick. Created an account. Logged in and everything worked (kind of). Because I had not installed any root patches and had not activated TerraScale 2 Acceleration yet, the whole GUI was extremely slow. But in "About this Mac" I even saw the dGPU. Hence I think it is not dead?!
  • BUT: Then I wanted to install the root patches. After doing that I now have the same issue like before. The system starts as usual, but after entering the password the screen stays black...
Does anyone have the same problem?
---
  • Model Name: MacBook Pro (15-inch, Early 2011)
  • Model Identifier: MacBookPro8,2
  • Processor: 2,2 GHz Quad-Core Intel Core i7
  • Graphics: Intel HD Graphics 3000 512MB & some dGPU
  • macOS: 13.4
  • OCLP: 0.6.7
 
Last edited:

educovas

macrumors regular
Jul 30, 2019
171
532
Curitiba, Brasil
Hi educovas,

back from holidays... Here my google Chrom debug log. Genereated by

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1

If you need any more information, don't hesitate.

iMac 17,1, AMD R9 M395, OCLP 0.6.7 AMFIpass b2, 13.4
That's not useful, unfortunately. Can you see if you have any related logs in /Library/Logs/DiagnosticReports/ and in ~/Library/Logs/DiagnosticReports/ ?
 
  • Like
Reactions: Sanmiguel71

Sanmiguel71

macrumors member
Mar 27, 2019
40
36
That's not useful, unfortunately. Can you see if you have any related logs in /Library/Logs/DiagnosticReports/ and in ~/Library/Logs/DiagnosticReports/ ?
Ok fine. In ~/Library/Logs/DiagnosticReports/ I've got several VTDecoderXPCService logs. I attached the last one from this morning... Thanks in advance
 

Attachments

  • VTDecoderXPCService-2023-06-10-153533.ips.zip
    5 KB · Views: 50

dongnguyxn

macrumors newbie
Jun 11, 2023
4
0
So far 13.2.1 is the latest OS without the LLDB bug caused by the


extracted binaries necessary to fix Metal. It's possible to use dsce 2gb binaries but that's not a good idea. If you need that to be working, downgrade to 13.2.1 for now
Can you explain a bit more why it's not a good idea? What the size of the binaries in total? If it's less than 50gb I would love to give it a try since you can only install Xcode 15 on 13.3+, unless there are other downsides. Even in 13.2.1, you can set breakpoints but lldb would still crash under certain conditions.
Any change this could be an option in OLCB for those who want to do it?
 

educovas

macrumors regular
Jul 30, 2019
171
532
Curitiba, Brasil
Ok fine. In ~/Library/Logs/DiagnosticReports/ I've got several VTDecoderXPCService logs. I attached the last one from this morning... Thanks in advance
Just what I was expecting, Decoder crashes trying to start the HEVC hardware decoder. Just can't figure out why and which VADriver it's using just looking at this log...
Can you explain a bit more why it's not a good idea? What the size of the binaries in total? If it's less than 50gb I would love to give it a try since you can only install Xcode 15 on 13.3+, unless there are other downsides. Even in 13.2.1, you can set breakpoints but lldb would still crash under certain conditions.
Any change this could be an option in OLCB for those who want to do it?
Should be around 20gb, impossible to ship with OCLP, you'd need to do everything by yourself. This should theoretically fix the problem with 13.3+ but if it's crashing with 13.2.1 there might be another similar issue.
 

dongnguyxn

macrumors newbie
Jun 11, 2023
4
0
Should be around 20gb, impossible to ship with OCLP, you'd need to do everything by yourself. This should theoretically fix the problem with 13.3+ but if it's crashing with 13.2.1 there might be another similar issue.
Thank you for the quick reply! Just want to see if I'm understanding this right. So some OCLP dev has to run some command to extract the binaries using dsce and these binaries are shipped with OCLP. When run with the "pad argument", dsce generates 2GB binaries so that's impossible to ship with OCLP?
Is there a guide out there showing how to do this? Can this extraction process even be automated using a script?
 

educovas

macrumors regular
Jul 30, 2019
171
532
Curitiba, Brasil
Thank you for the quick reply! Just want to see if I'm understanding this right. So some OCLP dev has to run some command to extract the binaries using dsce and these binaries are shipped with OCLP. When run with the "pad argument", dsce generates 2GB binaries so that's impossible to ship with OCLP?
Is there a guide out there showing how to do this? Can this extraction process even be automated using a script?
There is no guide and it's not even confirmed that it does fix the problem. ASentientBot thinks that it should but I don't think he tested. Even if it does work, it's impossible to fix 20gb in OCLP. If you do want to test anyways, you'd need the 13.2.1 dyld and extract the GPUCompiler.framework binaries using the pad argument, replace those files in your system partition and create a new snapshot.

I'm not recommending this because there is a high chance to make your system unbootable.
 

dongnguyxn

macrumors newbie
Jun 11, 2023
4
0
There is no guide and it's not even confirmed that it does fix the problem. ASentientBot thinks that it should but I don't think he tested. Even if it does work, it's impossible to fix 20gb in OCLP. If you do want to test anyways, you'd need the 13.2.1 dyld and extract the GPUCompiler.framework binaries using the pad argument, replace those files in your system partition and create a new snapshot.

I'm not recommending this because there is a high chance to make your system unbootable.
That doesn't sound like something I feel comfortable doing, guess I'll stay on Monterey then. Thank you again for answering, really appreciate it!
 

dandeco

macrumors 65816
Dec 5, 2008
1,254
1,052
Brockton, MA
It's actually happened quite a few times since then, maybe once or twice a day. But then I updated this week to OCLP 0.5.2 and the problem seems to have gone away.
It still happens from time to time. Lately as of OCLP 0.6.7., I seem to only get that problem after running the Mac in Target Disk Mode for transferring huge files (like an iMovie of FCP library). I even get the whole kit and caboodle of restart because of a problem error messages to slow me down before I can get down to business! It's like that part in "Jingle All the Way" when Arnold Schwarzenegger's character gets slowed down by a police officer accusing him of driving drunk.
1685903369090-jpeg.2211865
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.