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.

arosania

macrumors member
Apr 8, 2010
40
52
Barranquilla, Colombia
Anyone having the problem installing apps with dmg? Error DIsk image operation failed error 153.
Tried several, all the same.
Using the latest branch for Sonoma
Hi,

This happened to me. It happens with the DMGs that have the quarantine attribute set at download (for me, all of them xD):

Code:
-[DiskImageMounterDelegate application:openURLs:]_block_invoke: Failed to attach <private>: Error Domain=com.apple.DiskImages2.ErrorDomain Code=153 "Disk image operation failed with error code 153" UserInfo={DIErrorVerboseInfo=Failed to quarantine device, error=0xe00002c2, NSLocalizedDescription=Disk image operation failed with error code 153}

You can check the attributes with xattr -l <DMG name>:

Code:
xattr -l Additional_Tools_for_Xcode_12.5.dmg
com.apple.FinderInfo:
com.apple.diskimages.fsck: <9?H @???*vP???34.
com.apple.diskimages.recentcksum: i:71352412 on 93EC4DB0-2A8F-4B9C-AF0C-D126DB62AA45 @ 1621629960 - CRC32:$B9BE333F
com.apple.metadata:kMDItemDownloadedDate: bplist00?3A?,)?>?

com.apple.metadata:kMDItemWhereFroms: bplist00?_xhttps://download.developer.apple.com/Developer_Tools/Additional_Tools_for_Xcode_12.5/Additional_Tools_for_Xcode_12.5.dmg_7https://developer.apple.com/download/more/?=for%20Xcode
               ?
com.apple.quarantine: 0083;60a81c08;Safari;F591962B-D7BD-4A9E-A5E0-D250C8E6429B

If the file has it, as in this case you can just remove it with unqt, like so:

Code:
unqt Additional_Tools_for_Xcode_12.5.dmg

After that, the DMG will mount normally.

Cheers!
 

LuckyOldMan

macrumors newbie
Mar 22, 2018
28
42
Drielanden
How do you re-install the older version?
In the same way as Install before. You open the Patcher.app, determine the target (ESP) and install.
The flow log displayed shows that another OCLP is found, removed and the current one is installed. Then reboot and after that the post-install

I downloaded it (0.6.8) but
.. that is not the correct version. You need version 0.6.9n from the Sonoma branch, which you can find at the appropriate location.
Read the entire article carefully - then you will find what you are looking for. ;)
 

javinv

macrumors member
Nov 29, 2014
69
68
In the same way as Install before. You open the Patcher.app, determine the target (ESP) and install.
The flow log displayed shows that another OCLP is found, removed and the current one is installed. Then reboot and after that the post-install


.. that is not the correct version. You need version 0.6.9n from the Sonoma branch, which you can find at the appropriate location.
Read the entire article carefully - then you will find what you are looking for. ;)
I currently have installed the last version (0.6.9n); a couple messages ago, someone explained that the graphic problems of a cMP were solved downgrading to 0.6.8. That's why I wanted to downgrade to that version, to test if my situation would improve as well (since my MacBookPro14,3 was initially supported after 0.6.8).

I will try it and share if it works.

Thank you
 

LuckyOldMan

macrumors newbie
Mar 22, 2018
28
42
Drielanden
someone explained that the graphic problems of a cMP were solved downgrading to 0.6.8.
It wasn't necessary for me to step back to 0.6.8 because I was using 0.6.9n (Version August 23rd) the last weeks until yesterday without graphics problems and after the graphics problems with 0.6.9n (Version September 1st.) I installed it again - see #898.

But thanks for the hint about these messages.
 
  • Like
Reactions: NataliaC and javinv

javinv

macrumors member
Nov 29, 2014
69
68
It wasn't necessary for me to step back to 0.6.8 because I was using 0.6.9n (Version August 23rd) the last weeks until yesterday without graphics problems and after the graphics problems with 0.6.9n (Version September 1st.) I installed it again - see #898.

But thanks for the hint about these messages.
Ah sorry I didn't realized it was you (the same with the cMP).

Thank you for replying back.

So, you did update to 0.6.9n , the graphics did not work properly so you went back to 0.6.8.

I meant I was trying to replicate what you described, but without having tested 0.6.8 before.

I will let you know if it works.
 
  • Like
Reactions: NataliaC

javinv

macrumors member
Nov 29, 2014
69
68
I don't see anywhere that someone claimed to revert to 0.6.8 for Sonoma. Could it be that you misunderstood?
I think I misunderstood "I then re-installed the patcher from August 23rd. and now the color reproduction is correct.".

So, is there anything I can do to solve my external display problem? or something I could try to help find a solution? I'm willing to test anything if it helps the development, I installed it on a no "daily driver" Mac.
 

deeveedee

macrumors 65816
May 2, 2019
1,452
2,115
Peoria, IL United States
@javinv - Since I started using OCLP (with Big Sur) on my MBP6,2, I have twice experienced graphics anomalies after a macOS upgrade. In my case, following the upgrade, the screen would blank and unblank as though sleeping and waking. In both cases, a reboot resolved the problem. I never spent more time trying to resolve the problem that resolved itself.

If a reboot does not resolve your graphics problem, have you tried resetting NVRAM? If not, you may want to wait for a formal Sonoma release, since Sonoma is still an unreleased Beta OS. I'm not spending any time debugging Sonoma Beta issues. Especially since OCLP 0.6.9n for Sonoma is still Beta, too.
 

javinv

macrumors member
Nov 29, 2014
69
68
@javinv - Since I started using OCLP (with Big Sur) on my MBP6,2, I have twice experienced graphics anomalies after a macOS upgrade. In my case, following the upgrade, the screen would blank and unblank as though sleeping and waking. In both cases, a reboot resolved the problem. I never spent more time trying to resolve the problem that resolved itself.

If a reboot does not resolve your graphics problem, have you tried resetting NVRAM? If not, you may want to wait for a formal Sonoma release, since Sonoma is still an unreleased Beta OS. I'm not spending any time debugging Sonoma Beta issues. Especially since OCLP 0.6.9n for Sonoma is still Beta, too.
Thank you; Yes I tried reseting NVRAM.

I will wait for the next update or maybe try a clean install.
 

deeveedee

macrumors 65816
May 2, 2019
1,452
2,115
Peoria, IL United States
The Sonoma branch of OCLP has been updated; dated 9-10-23.
The Regular Ventura, etc. branch has been updated too, dated 9-9-23, although the date and info on the page is still not up to date, which should follow in good time.
Am I reading correctly that the change is the addition of experimental non-metal support?

Screen Shot 2023-09-10 at 6.42.53 AM.png
 

deeveedee

macrumors 65816
May 2, 2019
1,452
2,115
Peoria, IL United States
I downloaded and built the latest Sonoma-development branch (I built it myself since I wasn't sure if the pre-built nightly build contained the non-metal changes). I am running Sonoma 14.0 Beta 7 and posting this in Safari over Wi-Fi on my MBP6,2 (non-metal NVidia Tesla). Well done, Devs!

EDIT: Sonoma 14.0 Beta performance on my MBP6,2 is outstanding.
 
Last edited:

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
Indeed very well done, developers!

Similarly here on MBP5,2 with today's sonoma-development branch. Built from source and re-post-patched the 14.0b7 installation on external SSD
--> transparency is there, Dock edges look fine, Safari renders well (writing from Safari), good graphics speed.
I've bought this MBP just 14 years ago, what a birthday present!

And this Sonoma support of non-Metal systems comes even before Sonoma is released.
 

Attachments

  • Bildschirmfoto 2023-09-10 um 22.33.06.png
    Bildschirmfoto 2023-09-10 um 22.33.06.png
    30.1 KB · Views: 72

javinv

macrumors member
Nov 29, 2014
69
68
I think my problem is related to the Polaris GPU.

When the Intel one is in use, it can sleep and resume normally.

As soon as an external display is connected, the Polaris gpu is activated, thus loosing all image in both the internal and external display.

If the external display is connected on boot, the built-in display starts flickering after the login screen. If at this point, I disconnect and reconnect, I loose the built-in display but the external one works on Polaris... but it won't resume from sleep (the computer does, but with no image in none of the displays!).

Finally, it can't resume on Polaris even without any external display connected.

So sadly, MacBookPro14,3, doesn't look very usable right now. Really sad because the rest works better than with any other OS before!

I hope this helps someone!
 

Sven G

macrumors 6502
Jun 3, 2012
430
885
Milan, EU
Had almost forgotten about this glitch, but it is fixed in the latest OCLP 0.6.9 for Sonoma developer beta, and Compressor now works correctly, without giving this error message:

IMG_0048.png
 
Last edited:

Vacusuck

macrumors member
Aug 8, 2020
55
23
This might have been brought up, but for giggles, I tried updating my iMac 13,1 (2012) to Sonoma P7 using the 0.6.8 installer. Almost made it but it locks up after about the fifth reboot. It never recovers and just hangs on the loading progress Apple boot screen. Is 0.6.9 the best route to go? I couldn't figure out how to compile/build 0.6.9 so I'll just wait until it's officially released. Unless, there's another route to go.
 

LuckyOldMan

macrumors newbie
Mar 22, 2018
28
42
Drielanden
macOS 14.x @iMac 18.3-05a.jpg


The current status of my iMac 18.3 @ sonoma is as follows:

macOS 14 DP7 @iMac18.3-01.png

macOS 14 DP7 @iMac18.3-02.png
macOS 14 DP7 @iMac18.3-03.png
macOS 14 DP7 @iMac18.3-04.png

As far as I can tell, everything works and you can't call it "lame".
In this respect, it is definitely a device for 2023 and longer and you don't have to worry about the "loss" of security updates. This will work for quite a long time. ;)
 

Vacusuck

macrumors member
Aug 8, 2020
55
23
You're the first to ask this. Read this in its entirety.

if TLDR, download OCLP 0.6.9 Sonoma-Development build by clicking "Nightly.link: OpenCore-Patcher.app (Sonoma Development)" in that document.
Not sure if you're kidding, I can't be the only person who's brought this up. Anyway, it worked! My 2012 iMac is up running Sonoma. Now, it's not too stable (finder locking up and timing out back to the login screen) but I will chalk that up to it still being a beta build. Great work guys, thanks so much.
 

amaze1499

macrumors 65816
Oct 16, 2014
1,192
1,221
Not sure if you're kidding, I can't be the only person who's brought this up. Anyway, it worked! My 2012 iMac is up running Sonoma. Now, it's not too stable (finder locking up and timing out back to the login screen) but I will chalk that up to it still being a beta build. Great work guys, thanks so much.
No kidding. From what I gather, you did use the wrong OCLP build previously. If the "system" does not run stable, create a new user and try to reproduce the issues there. Let me know the results. See what you can gather from the logs in console at that time. Maybe I can point you in the right direction. I assume that iMacs HD has been upgraded to SSD?
 

amaze1499

macrumors 65816
Oct 16, 2014
1,192
1,221
Out of curiosity, not a problem, but perhaps someone has a quick fix for this one:

Most widgets on this MBP show as completely blank. This is one exists since Ventura. Issue can be reproduced in freshly installed system and a new user, in both light and dark mode. Maybe it's unique to this MacBook 9,2?
 

Attachments

  • Screenshot 2023-09-12 at 13.26.11.png
    Screenshot 2023-09-12 at 13.26.11.png
    41.7 KB · Views: 62
Last edited:
  • Like
Reactions: grumpy_Garrett

jshayya0184

macrumors member
Jun 8, 2022
38
50
Out of curiosity, not a problem, but perhaps someone has a quick fix for this one:

Most widgets on this MBP show as completely blank. This is one exists since Ventura. Issue can be reproduced in freshly installed system and a new user, in both light and dark mode. Maybe it's unique to this MacBook 9,2?
No, I have a MacBookAir7,2 I've had the same issue since Ventura.
 
  • Like
Reactions: amaze1499

deeveedee

macrumors 65816
May 2, 2019
1,452
2,115
Peoria, IL United States
More non-metal updates in the latest Sonoma-development commit

Screenshot 2023-09-12 at 9.44.52 AM.png


EDIT: I applied post-install patches to my MBP6,2 using the new OCLP 0.6.9 sonoma-development 09.12.23 and I don't notice any macOS or Safari differences. In order to make sure I had the latest commit, I build OCLP from the sonoma-development branch myself and did not use the pre-built download. I'm not sure if this was an illusion, but it seemed to me that Wi-Fi and Nvidia Tesla post-install patches applied much faster with the new OCLP 09.12.23 than with the 09.10.23 version of OCLP 0.6.9 Sonoma-development build.

Screenshot 2023-09-12 at 10.06.32 AM.png
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.