Jump to content

[pre-release] macOS Sonoma

fantomas

By fantomas,
in New Releases and Updates

 Share
1,844 posts in this topic

Recommended Posts

BALDY_MAN
BALDY_MAN
Posted
Posted
1 minute ago, Cyberdevs said:

@BALDY_MAN

That error is because you've booted from an efi folder other than the one you've used to install or boot Sonoma initially from.

o dear I can't remember  which on I used . I have a few of them I will have a sort though the ones I have. thank for your help

  • Sad 3
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
4 minutes ago, BALDY_MAN said:

o dear I can't remember  which on I used . I have a few of them I will have a sort though the ones I have. thank for your help

That's a pickle!

AFIAK The only way to find which one is the right one is to boot with them one by one and go to Disk Utility and if there's a -snapshot after the Sonoma APFS volume is the wrong one. The correct one should only have two volumes and no snapshot after them

  • Like 3
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
8 minutes ago, Cyberdevs said:

That error is because you've booted from an EFI folder other than the one you've used to install or boot Sonoma initially from.

use your original EFI.

Yes Sir!!! That's why I keep two EFI Folders (and updated with latest OC files and kexts) at the ready, One to force updates and the other to get my WIFI Connection operational again.

  • Like 3
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
Just now, eSaF said:

Yes Sir!!! That's why I keep two EFI Folders (and updated with latest OC files and kexts) at the ready, One to force updates and the other to get my WIFI Connection operational again.

I personally prefer to revert the patches, get the update and install it and then re-apply the patches ;)

 

  • Like 3
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 minute ago, Cyberdevs said:

I personally prefer to revert the patches, get the update and install it and then re-apply the patches ;)

That's all good and well but my 20,1 SmBIOS choice won't allow me to do that.

  • Sad 1
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)

I upgraded my HackBookPro6,2 from Sonoma Beta 4 -> Beta 5 without any issues.  I launched the upgrade and left it unattended.  The upgrade was complete when I returned, so I don't know how long or how many reboots.  Here are some specifics about my upgrade / configuration:

  • My OC 0.9.4 EFI has AMFI and Library Validation full enabled with AMFIPass.kext 1.3.1 and -amfipassbeta boot-arg.  AMFI remained enabled during the upgrade and after.  I never need to disable AMFI on this hack.
  • I connected my hack to wired Ethernet during the upgrade, since I suspected that the update would break Wi-Fi (until OCLP patches were re-applied) and just wanted to make sure I maintained a network connection during the upgrade and during OCLP post-install patching
  • When I first attempted the upgrade, the macOS Installer was stuck in a boot-loop.  I needed to enable kernel patches here in order to perform the upgrade.  After the upgrade completed, I removed the kernel patches (I keep two config.plists just for this reason)
  • I launched the upgrade via macOS OTA.  OTA downloaded the full installer (I did not revert root patches before upgrading)
    Spoiler

    Screenshot2023-08-08at2_07_22PM.png.2e4d885c8f77e8045c868448239c3d57.png

     

  • After the upgrade completed, OCLP automatically prompted me to re-apply post-install patches for NVidia Tesla and Wi-Fi.  My EFI includes an ACPI patch which spoofs my BCM 94352HMB Wi-Fi IOName as "pci14e4,43a3" to permit OCLP patcher to detect my Wi-Fi.  This is a permanent ACPI patch that remains during normal operation, since it only affects OCLP patching and does not affect normal Wi-Fi operation.
    Spoiler

    Screenshot2023-08-08at4_10_56PM.png.531e8c1fe26fcda0d6b4e3a0ad379e5c.png

  • After OCLP's post-install patches installed, I rebooted and once again had working Wi-Fi.
    Spoiler

    Screenshot2023-08-08at4_16_31PM.png.ecc3096bf54ec12e165add0537bfe51e.png

This upgrade from Beta 4 -> Beta 5 was painless.  As expected, NVidia Tesla does not yet have full graphics acceleration and won't until OCLP Devs tackle non-metal patching for NVidia Tesla.

 

About This Hack

Spoiler

Screenshot2023-08-08at4_38_45PM.png.f94f46f8c87d1df0914d11422122af86.png



Well done, OCLP Devs!

 

EDIT: I am posting this with Firefox running in Sonoma 14.0 Beta5 over Wi-Fi.  Sonoma / Firefox is incredibly responsive, even though OCLP patching for full NVidia Tesla graphics acceleration is not yet complete.  Sonoma Beta5 is more responsive on this hack than Sonoma Beta4.

 

My configuration is as follows:

  • Dell Latitude E6410, Nvidia Tesla Graphics
  • SMBIOS MBP6,2
  • Open Core 0.9.4
    • Wi-Fi IOName spoofed as "pci14e4,43a3" for OCLP post-install Wi-Fi patches)
    • VMM kernel patches for Sonoma upgrade (removed after the upgrade)
    • AMFI and Library Validation fully enabled (AMFIPass.kext 1.3.1, -amfipassbeta boot-arg)
Edited by deeveedee
  • Like 3
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 minute ago, Cyberdevs said:

Why not?

T2 Chip???!!! But on reflection I am offered the incremental Updates with RE kext plus boot-arg so that shouldn't be the problem.

I think the problem is, I tend to remove the kext and the boot-arg after the update.

What I will test next Beta, is leave the kext and boot-arg in place, revert the Patch and see what the result is.

Thanks for the simple idea.

  • Like 4
Link to comment
Share on other sites
matxpa
matxpa
Posted
Posted

Hi

 

Full DL Sonoma 14.0 beta5 (23A5312d)

 

Prepare to download the files.   macOS Sonoma beta 14.0 (23A5312d) ........... 2023-08-08 17:05:07 .. 12.86 GB .. 042-27162

 

mkdir /tmp/042-27162

 

curl -L --progress-bar https://swdist.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/042-27162.English.dist -o  /tmp/042-27162/042-27162.English.dist
curl -L --progress-bar https://swcdn.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/BuildManifest.plist -o /tmp/042-27162/BuildManifest.plist
curl -L --progress-bar https://swcdn.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/Info.plist -o /tmp/042-27162/Info.plist
curl -L --progress-bar https://swcdn.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/InstallInfo.plist -o /tmp/042-27162/InstallInfo.plist
curl -L --progress-bar https://swcdn.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/MajorOSInfo.pkg -o /tmp/042-27162/MajorOSInfo.pkg
curl -L --progress-bar https://swcdn.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/UpdateBrain.zip -o /tmp/042-27162/UpdateBrain.zip
curl -L --progress-bar https://swcdn.apple.com/content/downloads/26/36/042-27162-A_4GKRLRWELJ/qyzyo86g692wlsewkyclfk686op47kuq5c/InstallAssistant.pkg -o /tmp/042-27162/InstallAssistant.pkg

 

sudo installer -pkg  /tmp/042-27162/InstallAssistant.pkg -target /

 

ls -ltr /Applications | tail -1
drwxr-xr-x   3 root     wheel    96  8 aoû 22:42 Install macOS Sonoma beta.app
 

Regards

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted

@eSaF

MacPro7,1 and iMacPro1,1 also have the T2 chips but the same procedure applies to both of them. I've almost spent a whole day testing installing and updating Sonoma on two different rigs using both SMBIOS settings and the only thing that was required was to add the RestricEvents.kext and the revpatch=sbvmm boot args with reverting the root patches before performing the update.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
cankiulascmnfye
cankiulascmnfye
Posted
Posted
1 hour ago, Cyberdevs said:

@eSaF

MacPro7,1 and iMacPro1,1 also have the T2 chips but the same procedure applies to both of them. I've almost spent a whole day testing installing and updating Sonoma on two different rigs using both SMBIOS settings and the only thing that was required was to add the RestricEvents.kext and the revpatch=sbvmm boot args with reverting the root patches before performing the update.

 

I never revert root patches prior to updating. And I've been applying root patches on my Laptop eversince Monterey. Simply because the full installer is downloaded everytime on a system with applied root patches because this breaks the security seal of the volume. So updating/upgraiding  in this case completely reinstalls macOS as a whole anyway.

 

  • Like 3
Link to comment
Share on other sites
Henry2010
Henry2010
Posted
Posted (edited)

I can confirm that no OTA with just revpatch=sbvmm and SIP partly disabled when using iMac Pro 2017 SMBIOS.

Will change it to iMac 19,1 later.

 

EDIT

iMac19,1 now. But, oh my bad. Didn't switch the update channel from Public to Dev.

Will try again next time (or next week?) with the old iMac Pro 2017 SMBIOS.

Edited by Henry2010
  • Like 1
Link to comment
Share on other sites
CloverLeaf
CloverLeaf
Posted
Posted (edited)

Beta 5 definitely feels snappier! :) 

 

Notifications are FIXED - ✓

My laptop is operating at normal temperatures again hovering around 47'C browsing/lite use and ~70'C under load  (25'C room temp) - ✓

 

GPU spikes when using and after closing Apple TV app still persist - X

Airportitlwm is broken and prevents the system to boot - X

 

I can say this update is more + than - since we have alternatives for the Wi-Fi functionality.

Edited by CloverLeaf
  • Like 4
Link to comment
Share on other sites
pico joe
pico joe
Posted
Posted
2 hours ago, Henry2010 said:

I can confirm that no OTA with just revpatch=sbvmm and SIP partly disabled when using iMac Pro 2017 SMBIOS.

Will change it to iMac 19,1 later.

 

EDIT

iMac19,1 now. But, oh my bad. Didn't switch the update channel from Public to Dev.

Will try again next time (or next week?) with the old iMac Pro 2017 SMBIOS.

no problem here with iMac Pro .. still get OTA (1.2 gb), 1. revert patch 2. boot-args: amfi 0x80 revpatch=sbvmm 3. secure boot: Disabled

  • Like 3
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)

As I mentioned before, I need to add these VMM kernel patches to my OC 0.9.4 config.plist in order to perform macOS installs (and now I discover I also need them for upgrades) on my hack (MBP6,2).  

  • Reroute kern.hv_vmm_present patch (1)
  • Reroute kern.hv_vmm_present patch (2) Legacy
  • Reroute kern.hv_vmm_present patch (2) Ventura

These kernel patches are supposed to be replaced by RestrictEvents.kext 1.1.2 with NVRAM value revpatch=sbvmm.  

 

I am finding that even with RestrictEvents.kext 1.1.2 and revpatch=sbvmm, I still need the VMM kernel patches to install and upgrade macOS.  Without the kernel patches, my hack detects the OTA update and I can download the update, but the update's macOS Installer gets stuck in a boot-loop.  If I enable the kernel patches, the macOS installer isn't stuck in a boot-loop.

 

Is anyone else seeing this by any chance?

 

I have confirmed that RestrictEvents.kext 1.1.2 is loaded:
 

Spoiler

Screenshot2023-08-08at9_58_11PM.thumb.png.bf840d28c95f077da2a1ef054b4d043c.png.afd3c0fed4fff8e54a0fdf5818aea507.png

 

and NVRAM contains revpatch=sbvmm

Spoiler

Screenshot2023-08-08at9_54_15PM.png.5a0db61a2342ac6621e496e315b0fce1.png.dca06bd09d6b89463143946103651826.png

 

Thanks in advance for any tips / advice.  My config.plist is attached.  I'm not sure that RestrictEvents.kext ever worked for me after I removed the VMM kernel patches.  Thank you.

config.plist.zip

Edited by deeveedee
  • Like 2
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...