It upgraded normally here. No issues.Is it safe to upgrade ?
Same for me - upgrade went smoothlyIt upgraded normally here. No issues.
Big problem at my side: the update itself went smooth as usual with the latest OCLP 1.4.1 but after update to 12.7.4 I lost all networking, both Ethernet and Airport. DHCP can't get IP address from router. I booted Windows - everything works fine, I booted Big Sur from another SSD - it works, even Monterey Recovery boot has Safari in safe mode that works, but Monterey - no go!Is it safe to upgrade ?
What am I missing?
Yes, sorry! However, if I can ask - it is valuable information if 12.7.4 works ok on manually-configured OC Mac Pro 5.1 in the network part? Because if it works, it means it's probably an OCLP problem after all - because now I've seen at least a dozen users have the same problem. Thank you very much!You should ask this on a thread that people uses OCLP, no? Not here, where we don't use it…
…12.7.4 works ok on manually-configured OC Mac Pro 5.1 in the network part?
Thanks a lot! It seems that it's a rather nasty OCLP bug. I used manually configured OC for a long time and then switched to OCLP for easy updates, but it seems there is very unpleasant downside too.12.7.4 works as expected with manually configured OC, no networking problems.
Well I finally had the time and patience to try my RX 580 in place of my RX Vega 56.Not at present. I can make that happen soon.
However - my monitor is an Apple Cinema Display and I was not having issues with my RX580. I only noticed the issues when I tried OCLP/Sonoma. I will probably have to try my RX580 again and check everything.
I appreciate the ideas and things to check.
Regards,
sfalatko
We had a beautiful run, I’ll be upgrading to Studio M3 this summer. I got the Studio M2 last year but decided to refund it and wait another year to get the M3 instead, since we still had security updates on current cMP.To make matters worse, is not just the missing AVX 2.0 support, but some other modern x86 instuctions sets
Nobody uses OCLP in this thread, please ask your questions into right place. Edit: sorry about the double post, I see the same mention was raised by @tsialex.Big problem at my side: the update itself went smooth as usual with the latest OCLP 1.4.1 but after update to 12.7.4 I lost all networking, both Ethernet and Airport.
OCLP cannot boot Mojave, since it spoofs a newer version of Mac. You have to use option-boot to get Mojave.I´ve built an OCLP Ventura installer on a Mojave start volume. So far everything is working well in Ventura. But I can't boot from Mojave... when I try, the forbidden icon appears. I have read many posts in this thread but things are not clear to me and I am afraid of destroying my system. What do you think would be the easiest way to reboot in Mojave in case there is a problem with the OCLP Ventura volume?
it's off topic as it is OCLP. But anyway, if spoofing is set to none it makes a spoofless approach what can boot Mojave (using the virtualisation method) or configureOCLP cannot boot Mojave, since it spoofs a newer version of Mac. You have to use option-boot to get Mojave.
-no_compat_check
to the boot-args.I would make sure they they are properly seated in the slot, then a deep NVRAM reset. Also someone mentioned something about different OS's on containers having issues.Hi. I am having a strange issue. had about 3 kernel panics which seem related to NVMe controller. The drives on there didn't mount after Mac rebooted itself but when it was shut down for a few minutes and then switched on the PCIe drives mounted. Now the most visible issue is that there are 3 startup partitions on the NVMe's but none were present in the OC bootpicker. They do however appear in System Preference Startup Drive as options.
I recently switched to OC 099 - is there something I could have missed or not copied over which would produce this type of symptom. The config file was untouched but elements from the new OC package were copied over.
Any ideas?
Thanks. Yes I did that but the problem persisted. Both Display Ports showed the issue. I have since changed the cable to a HDMI (a bit too short but all I have right now) and I think that was the problem. I will get a new DP cable as soon as I can.I would make sure they they are properly seated in the slot, then a deep NVRAM reset. Also someone mentioned something about different OS's on containers having issues.