Have you tried latest (14.1) Lightroom Classic on your 6,1?The end of the road on this machine is Photoshop 2024
Have you tried latest (14.1) Lightroom Classic on your 6,1?The end of the road on this machine is Photoshop 2024
The problem is that Ventura and Sonoma are going hand in hand, we risk having to go back to Monterey (last only Intel) to have a stable and functioning system... but that's fine too, OCLP is an exceptional Team.Thank you for this insightful explanation! This really hits the nail on the head and explains exactly what I'm experiencing.
The AVX2 dependency makes perfect sense because:
- The older version (5.521.0) works perfectly fine
- The new version crashes immediately at startup
- It works on my MacBook Pro (Haswell CPU with AVX2)
- It's a 3D modeling software that would benefit greatly from AVX2 instructions
This discovery might actually mark a significant turning point for Mac Pro 5,1 users. While OCLP has done an amazing job keeping our machines running modern macOS versions, the lack of AVX/AVX2 support represents a hardware limitation that no software patch can overcome. As both Apple and third-party developers increasingly rely on these CPU instructions in their frameworks and applications, we might be facing a gradual but inevitable decline in software compatibility.
Some examples where this might become relevant:
- Modern development frameworks (like newer versions of SwiftUI)
- 3D modeling and video editing software
- Future versions of creative applications
- Machine learning and AI tools
- Modern games and graphics applications
This doesn't mean our Mac Pros will stop working overnight, but it suggests that even with OCLP's excellent work, we're approaching a natural end-of-life situation - not because of macOS compatibility, but because of fundamental CPU architecture requirements in modern software.
I'll stick to using Shapr3D on my MacBook Pro or keep using the older version that still works, but this experience has helped me understand the longer-term implications for Mac Pro 5,1 usage.
Thanks again for helping me understand the root cause - this information will surely be valuable for other Mac Pro 5,1 users in planning their future upgrade paths.
It's fine to do the resets and those don't require reloading root patches.Is it okay to try doing a SMC and PRAM (if needed) reset to see if that will cure my Wi-Fi turning on and off, on one of my machines and will I need to do anything else on the OCLP side, like redoing the root patches?
The Wi-fi stays connected but completely loses internet and when it is running speeds are kinda slow many times. I am sitting right next to a 1.2 Gbps gateway. All other devices, the speeds are fine and steady.
It seems like one or two OCLP updates a while back the issue began. It was fine on the native OS and I think on OCLP 2.0.1 but since that, it has been problematic. I thought it might be Sequoia but now starting to think that might not be it.
Thanks, in advance....
Thanks Kivo, no this computer has been in this location for a long time, unless I go portable. i am very familiar with RF. by right next to it, I mean like 2 feet away. this is definitely a change from either Sequoia (did not have it with Sonoma), or a change in OCLP.....It's fine to do the resets and those don't require reloading root patches.
You say you are right next to a 1.2Gbps gateway. Did the problem start after moving the computer and gateway right next to each other? Having the two radios extremely close can cause the type of issue you describe. It's not that common, but you can overload the receiver if the other transmitter is close enough or high powered enough.
It could also be a sequoia issue, but hopefully it's something that has an easy fix.
That's pretty close. I would always use a cable at that distance myself. Check the RSSI. If it's near -30dBm or higher it could be causing an issue. You'd have to find the specs on the particular chip to know for sure if that's above the safe limit, but I generally avoid having them so close together. I've never experienced burn out on computer wifi, but I have seen it on other hardware so I would think it's possible to detune or fry a receiver over time with too hot a signal. Just a thought. I might be overthinking it. 🤷♂️by right next to it, I mean like 2 feet away.
The problem you are discussing, @macamazing, has also been happening to me, since I installed Sequoia, and it occurs some time after I turn on my Mac, especially after long periods of sleep, when I wake up the Mac. Some downloads become very slow, as if I were using an old ADSL line of 128 Kb/sec or close to it....Thanks Kivo, no this computer has been in this location for a long time, unless I go portable. i am very familiar with RF. by right next to it, I mean like 2 feet away. this is definitely a change from either Sequoia (did not have it with Sonoma), or a change in OCLP.....
Thanks!
sudo ifconfig en1 down ; sudo ifconfig en1 up ; sudo pkill Wi-Fi
Interesting, will try this if I see these issues again, thanks!Open Terminal and type:
Code:sudo ifconfig en1 down ; sudo ifconfig en1 up ; sudo pkill Wi-Fi
Probably mirroring with Sequoia we can forget about it on Macs with Kepler series video cards... However, never say never...Interesting, will try this if I see these issues again, thanks!
BTW. All our Macs run flawlessly ATM. The one "luxury" item that I miss and need regularly is the new screen mirroring functionality. I can not get that to work under 15.2 on a rMBP 10,1 (works on the others incl. MBA 7,2).
Have tried what works on the rMBP using 15.1 and also on Sonoma: to set Advanced/FeatureUnlock to partial but that no longer works. If anyone comes across a fix I would appreciate it.
A generally agree with your sentiment, but mirroring worked on Sequoia 15.1.Probably mirroring with Sequoia we can forget about it on Macs with Kepler series video cards... However, never say never...
In my case iPhone mirroring no longer works using Reflector 4.
If in two future major updates of Sequoia and of OCLP these problems have not been fixed, including the Preview problems I desxcribed earlier, I will almost certainly go back to macOS Sonoma with which everything worked perfectly.
But it would be a defeat... Too bad.... :-(
No 14.1 cannot be installed, "Processor with Advanced Vector Extensions 2 (AVX2) support required"... So the last version that can run on a 6,1 is Lightroom Classic 14.0.1.Have you tried latest (14.1) Lightroom Classic on your 6,1?
Hi @OKonnel Yes, I have the forest wallpaper which is fine and to be honest I'm not too bothered about not having the dynamic wallpaper. I didn't realise that Apple had moved to a different format for this, so another thing that will impact full functionality on our Macs, which are already running well behind from T1, T2 and now Silicon.Ho @Marfan-58! We meet from time to time!
Sequoia's original / final dynamic background doesn't work, and if you're really interested you might be able to find the version distributed with the early betas around, since it's created in .HEIC format, like the earlier dynamic versions. (Or I can send it to you privately). But both the final version and the beta are very ugly, and maybe that's why our "Sir iMacs" refuse to start them
Instead, if you haven't noticed, the standard background with the Sequoia forest works just fine! It comes alive when you freeze the screen or wake it up from sleep and changes position in the Desktop.
That said, the only thing that worries me as I work is the Histogram malfunction in Preview and the bug that causes the image to disappear if you press "Auto Levels" or touch the two sliders at the ends.
Preview is an original and important part of macOS and I hope the OCLP’s Developers will fix this Metal issue (which the powerful Kepler video cards in our 14,2 iMacs can overcome), as they did with Chess, Music and FreeForm.
This machine has been in that spot for over 1.5 years and has never been an issue, until after an update. thanks for the tips though....That's pretty close. I would always use a cable at that distance myself. Check the RSSI. If it's near -30dBm or higher it could be causing an issue. You'd have to find the specs on the particular chip to know for sure if that's above the safe limit, but I generally avoid having them so close together. I've never experienced burn out on computer wifi, but I have seen it on other hardware so I would think it's possible to detune or fry a receiver over time with too hot a signal. Just a thought. I might be overthinking it. 🤷♂️
Yes, this is exactly what i am seeing. When I do a reboot, the speed will jump back up to 400 mbps and then trails off after time to nothing. I will try your suggestions but obviously this is a temporary fix..The problem you are discussing, @macamazing, has also been happening to me, since I installed Sequoia, and it occurs some time after I turn on my Mac, especially after long periods of sleep, when I wake up the Mac. Some downloads become very slow, as if I were using an old ADSL line of 128 Kb/sec or close to it....
I am speculating that the problem is caused by poor handling of Wi-Fi Channel switching when a Channel's frequencies are disturbed or very busy and the Mac no longer makes an automatic switch. Perhaps this is why the following solution, to restore fast Wi-Fi, works instead of having to restart the Mac:
Open Terminal and type:
Press enter, put in the password, and press enter.Code:sudo ifconfig en1 down ; sudo ifconfig en1 up ; sudo pkill Wi-Fi
Perhaps This command "refreshes" the connection [it's actually three commands in a row, separated with ;], but don't ask me why it works... as this was suggested to me in Discord and I think the problem is known to Developers.
If you have time you can do these tests:
command seems to work even without adding:
; sudo pkill Wi-Fi
after the first two commands. Or you can try giving only the command:
sudo pkill Wi-Fi
which stops the Wi-Fi process and restarts it immediately, as you can check in Activity Monitor.
Keep us informed
NOTE: This procedure turns off and on the Mac's Wi-Fi network adapter, so be careful not to break the network connection while you are working online on some file or project, as you may risk losing data.
Did you create the USB installer with OCLP? I believe I read that is the recommended way to proceed.Note: The only way I get it to work is by Installing 15.1.1 first than Updating to 15.2 via the Install app.
I tried this in the past and no go, but i'll try it again today.Did you create the USB installer with OCLP? I believe I read that is the recommended way to proceed.
Might help with prepping kexts and the like.