Jump to content

[pre-release] macOS Sonoma


1,844 posts in this topic

Recommended Posts

5 minutes ago, matgeo said:

I'm opted in sonoma developer beta. But no update.

I have a laptop. 

Isn't this going to be a problem?

Change it to MacBookPro15,x and you can revet back to your original config once you update it. Save your current config before making any changes to SMBIOS.

Link to comment
Share on other sites

41 minutes ago, miliuco said:

My z390 also needs to set iMac19,1 to get the update. iMacPro1,1 or MacPro1,1 don't show it.

I guess you use RestrictEvents
try using the boot-args revpatch=

 

  • memtab - enable memory tab in System Information on MacBookAir and MacBookPro10,x platforms
  • pci - prevent PCI configuration warnings in System Settings on MacPro7,1 platforms
  • cpuname - custom CPU name in System Information
  • diskread - disables uninitialized disk warning in Finder
  • asset - allows Content Caching when sysctl kern.hv_vmm_present returns 1 on macOS 11.3 or newer
  • sbvmm - forces VMM SB model, allowing OTA updates for unsupported models on macOS 11.3 or newer
  • f16c - resolve CoreGraphics crashing on Ivy Bridge CPUs by disabling f16c instruction set reporting in macOS 13.3 or newer
  • none - disable all patching
  • auto - same as memtab,pci,cpuname, without memtab and pci patches being applied on real Macs

revpatch=auto / sbvmm ... It should work

  • Like 8
Link to comment
Share on other sites

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

Just like the last Beta I had to change from 20,1 to 19,1 to get this update. Man I hate the swopping and changing just for these increments specially when I don't get the full package.......Hint, hint like Ventura. :wink_anim:

 

@antuneddu This bootarg revpatch=auto / sbvmm - is it entered as such or just revpatch=auto?

Spoiler

1370263501_Screenshot2023-07-05at20_16_35.png.1e201db05987dc43314b4987a0b26b2d.png

 

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

41 minutes ago, eSaF said:

Just like the last Beta I had to change from 20,1 to 19,1 to get this update. Man I hate the swopping and changing just for these increments specially when I don't get the full package.......Hint, hint like Ventura. :wink_anim:

 

@antuneddu This bootarg revpatch=auto / sbvmm - is it entered as such or just revpatch=auto?

  Reveal hidden contents

1370263501_Screenshot2023-07-05at20_16_35.png.1e201db05987dc43314b4987a0b26b2d.png

 

 

Example for RestrictEvents.kext boot-args:

 

1.png

Edited by Stefanalmare
  • Like 7
  • Thanks 1
Link to comment
Share on other sites

2 hours ago, antuneddu said:

I guess you use RestrictEvents
try using the boot-args revpatch=

 

  • memtab - enable memory tab in System Information on MacBookAir and MacBookPro10,x platforms
  • pci - prevent PCI configuration warnings in System Settings on MacPro7,1 platforms
  • cpuname - custom CPU name in System Information
  • diskread - disables uninitialized disk warning in Finder
  • asset - allows Content Caching when sysctl kern.hv_vmm_present returns 1 on macOS 11.3 or newer
  • sbvmm - forces VMM SB model, allowing OTA updates for unsupported models on macOS 11.3 or newer
  • f16c - resolve CoreGraphics crashing on Ivy Bridge CPUs by disabling f16c instruction set reporting in macOS 13.3 or newer
  • none - disable all patching
  • auto - same as memtab,pci,cpuname, without memtab and pci patches being applied on real Macs

revpatch=auto / sbvmm ... It should work

 

Thanks for info. RestrictEvents.kext and revpatch=sbvmm bootargs work for my Asus Vivobook i7-10870h. oc 0.9.4

  • Like 8
Link to comment
Share on other sites

1 hour ago, miliuco said:

@eSaF

 

revpatch=sbvmm plus RestrictEvents, ofc. 

Thanks for the info but I am not using RestrictEvents so was wondering if the boot-arg would still work for me and 20,1 for updates instead of keep changing to 19,1.

  • Like 3
Link to comment
Share on other sites

1 hour ago, eSaF said:

Thanks for the info but I am not using RestrictEvents so was wondering if the boot-arg would still work for me and 20,1 for updates instead of keep changing to 19,1.

This boot arg only works if RestrictEvents is loaded. Really we haven’t need this kext out of MacPro7,1 SMBIOS. But @antuneddu proposes this as a way to get software updates on Sonoma when it fails. 
Add RestrictEvents and the boot arg to get updated and remove both later. Keeping your current SMBIOS.

 

Edited by miliuco
  • Like 7
  • Thanks 2
Link to comment
Share on other sites

Well, as expected in my hacks, the update does not appear, only in the i3 that has smbios 19.2

 

 

But if I get the beta in one of my Ventura installations at 13600k without using "revpatch=sbvmm" 🤷‍♂️

 

661486842_Capturadepantalla2023-07-06alas0_24_01.png.93ff6456a041f660b16fdf681c39b5f4.png

  • Like 3
Link to comment
Share on other sites

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