Jump to content

[pre-release] macOS Sonoma


1,844 posts in this topic

Recommended Posts

 

32 minutes ago, antuneddu said:

1952078266_Screenshot2023-07-11alle19_25_40.png.8b454ed7343e5fbff2cc0d597913efc0.png

 

Update went ok, had to use revpatch=sbvmm to see the update again but that was expected.

 

I think the time zone settings work correctly now too.

 

751961135_Screenshot2023-07-11at18_53_44.png.bb55deb7736ff05dca237b1a9aea9aa8.png

510649917_Screenshot2023-07-11at18_51_36.png.6ca56d54b0878fa3e72ffcf978eda328.png

Edited by D-an-W
  • Like 4
Link to comment
Share on other sites

@PMheart

About sbvmm and OTA updates, today Sonoma beta 3 build 23A5286i:

  • RE without boot args >> no OTA update
  • RE with bootargs=auto,sbvmmm (or bootargs=memtab,pci,sbvmm) >> I see the OTA update.

OpenCore 0.9.4 + RE 1.1.3 + MacPro7,1. 

System: Z390 + + i9-9900K + RX 6600 XT.

 

Not updated yet in case you need to check any other thing.

Edited by miliuco
  • Like 6
Link to comment
Share on other sites

Done but had to do some summersaults to get the OTA update and bypass the T2 check for the 20,1. So instead of going through the process of signing out from all Apple Services then changing to 19,1 then signing back in as 20,1 once the update is done was too much of a hassle.

Doing the boot-arg coupled with RestrictEvent.kext is less of a headache to keep using Mac Model 20,1.

Spoiler

1274671793_Screenshot2023-07-11at18_09_47.png.ef372ee66b8b09b7f7a30f694d2b581e.png

 

  • Like 6
Link to comment
Share on other sites

14 minutes ago, miliuco said:

@PMheart

About sbvmm and OTA updates, today Sonoma beta 3 build 23A5286i:

  • RE without boot args >> no OTA update
  • RE with bootargs=auto,sbvmmm (or bootargs=memtab,pci,sbvmm) >> I see the OTA update.

OpenCore 0.9.4 + RE 1.1.3 + MacPro7,1. 

System: Z390 + + i9-9900K + RX 6600 XT.

 

Not updated yet in case you need to check any other thing.

Please see whether you can actually do the update. I heard that with auto,sbvmm it manages to download, but failed to install. Thanks!

  • Like 2
Link to comment
Share on other sites

8 minutes ago, PMheart said:

Please see whether you can actually do the update. I heard that with auto,sbvmm it manages to download, but failed to install. Thanks!

simply remove "auto" and use only "sbvmm" on bootarg...only for the time of update...next, after update is complete, remove all bootarg and boot normally ...

  • Like 3
Link to comment
Share on other sites

17 minutes ago, PMheart said:

Please see whether you can actually do the update. I heard that with auto,sbvmm it manages to download, but failed to install. Thanks!

 

It's true, sometimes, with sbvmm shows update with any SMBIOS, but get errors and not finish install. 

 

My Lenovo is only machine with Hack that not have issue, and update normally. Mistery :) 

 

 

Until my MacbookAir 9,1 2020 have issue. 

  • Like 2
Link to comment
Share on other sites

31 minutes ago, PMheart said:

Please see whether you can actually do the update. I heard that with auto,sbvmm it manages to download, but failed to install. Thanks!

 

Update and install went seamlessly with RE latest commit and with boot-arg "revpatch=auto,sbvmm,asset" (SMBIOS MacPro7,1).

 

1 alert still present.

Edited by iGPU
  • Like 2
Link to comment
Share on other sites

1 hour ago, PMheart said:

Please see whether you can actually do the update. I heard that with auto,sbvmm it manages to download, but failed to install. Thanks!

 

Update with no issues with auto,sbvmm.

Remember: MacPro7,1.

 

Edited by miliuco
  • Like 1
Link to comment
Share on other sites

Well, my Lenovo L390 does not want to update, I get this continuously 

 

1403130006_Capturadepantalla2023-07-11alas23_10_17.png.fa2ebdf958b055af027a0a489a55a4da.png

 

 

 

And to my surprise, the Ryzen 1600AF, yes, it has updated perfectly just by using "revpatch=sbvmm" and no warning has come out about this mac...

 

image.png.df9a73e1c31ed6a5d6286eb3235b7eb9.png

 

780591365_Capturadepantalla2023-07-12alas0_48_29.png.722026eebe7710a91d51d0d30df2d8f0.png

 

on the 13600K when using "revpatch=sbvmm" I get the message of unconfigured memory (but the 13600k is no longer going to be used with MacOS, my son has kept it for games) ....

 

So I'm happy with the Ryzen... it works fine, and you don't have to do weird things to update it or messages about things not being configured 😆

 

greetings

 

 

 

Link to comment
Share on other sites

I actually thought that it was beta4, because the first beta3 came out on 5.7 and today is 11.7, so it should be beta4. Ok, only the last letter has changed.

 

I find the installation with the full installer was much shorter with all restarts only 40 minutes and the previous beta3 took me over 1 hour,

with my Hacki1 in the signature.

 

Finally at 2:32 a.m. here in Germany "only" 23 degrees celsius, we had 35 degrees during the day.

Another tropical night here.

 

Here is an article by MacTechNews from Germany:

https://www.mactechnews.de/news/article/Merkwuerdig-Apple-publishes-updated-version-of-the-third-pre-release-of-iOS-17-and-macOS-14-182903.html

Edited by AlfredoM
  • Like 4
Link to comment
Share on other sites

3 minutes ago, hiphopboy said:

 

Same here

 

if you use RestrictEvent with bootarg like "revpatch=auto,sbvmm", try to leave only the sbvmm like pic:

 

image.thumb.png.37f7b0afca00111e9695d8739ba78497.png

 

After update is complete, restore the "older" bootarg

 

Give it a shot...

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...