[pre-release] macOS Sonoma

[Henry2010]

12 hours ago, D3v1L said:

iCloud signed or not, is not relevant at all. You use a T2 chip based smbios. For receive incremental ota update, you need to use RestrictEvents.kext with sbvmm boot-args otherwise, you don't give nothing. (or switch to imac19,1 smbios)

 

Thanks a lot, I received the OTA update. If it happened again (SIP is disabled now to kill the pop-ups) I will switch the SMBIOS.

 

Spoiler

A tip to others: do NOT use nightly kext builds on https://dortania.github.io/builds/, except NVMeFix.

At least on my Hack here, it will only enter a restart loop.

 

EDIT

Not a tip. But an observation.

I also tried the nightly kext builds, only because I couldn't get the OTA and the system froze once.

But it didn't help and the hack build entered a restart loop.

 

Edited August 3, 2023 by Henry2010

[cankiulascmnfye]

1 hour ago, Henry2010 said:

A tip to others: do NOT use nightly kext builds on https://dortania.github.io/builds/, except NVMeFix

At least on my Hack here, it will only enter a restart loop.

 

 

 

I have been using these Nightly Builds for 2 or 3 years now. In some rare cases the devs change too much and a kext can cause a Panic. This happened to me once in all this time. I reported it and then the changes were reverted. So using these builds can actually help development. If you want to test the initial release of the newest OS, you need those kexts. If you are a regular user who doesn't run public betas of macOS, your don't need them.  Your tip is misplaced in a thread that's all about using the latest builds of a work-in-progress beta OS. People who use nightly builds should know why they are using them and how to analyze errors once they occur. If you can't do that, you shouldn't use them. And you probably also shouldn't install Public or Developments Betas of macOS as well in this case.

Edited August 3, 2023 by cankiulascmnfye

[Henry2010]

30 minutes ago, cankiulascmnfye said:

 

I have been using these Nightly Builds for 2 or 3 years now. In some rare cases the devs change too much and a kext can cause a Panic. This happened to me once in all this time. I reported it and then the changes were reverted. So using these builds can actually help development. If you want to test the initial release of the newest OS, you need those kexts. If you are a regular user who doesn't run public betas of macOS, your don't need them.  Your tip is misplaced in a thread that's all about using the latest builds of a work-in-progress beta OS. People who use nightly builds should know why they are using them and how to analyze errors once they occur. If you can't do that, you shouldn't use them. And you probably also shouldn't install Public or Developments Betas of macOS as well in this case.

 

So instead of coming to a Hackintosh community, I should just shut up and quit a PUBLIC Beta when I have a problem because I am not as clever as you.

Do I have to tell you why I installed Sonoma in the first place to get your permission?

It was wrong to use the word "tip", I get it. I am going to buy an English dictionary now.

Edited August 3, 2023 by Henry2010

[cankiulascmnfye]

21 minutes ago, Henry2010 said:

 

So instead of coming to a Hackintosh community, I should just shut up and quit a PUBLIC Beta when I have a problem because I am not as clever as you.

Do I have to tell you why I installed Sonoma in the first place to get your permission?

It was wrong to use the word "tip", I get it. I am going to buy an English dictionary now.

 

No, but just because you witnessed an error you should not turn your one-time experience into a general DO NOT USE recommendation! It's unjustified! Just don't make it personal.

Edited August 3, 2023 by cankiulascmnfye

[Henry2010]

17 minutes ago, cankiulascmnfye said:

 

No, but just because you witnessed an error you should not turn your one-time experience into a general DO NOT USE recommendation! It's unjustified! Just don't make it personal.

That I agree. Posts are now folded.

Edited August 3, 2023 by Henry2010

[miliuco]

17 hours ago, Cyberdevs said:

I guess the SMBIOS part is what's different from your experience and mine, I didn't change my config, just reverted the root patches on iMac19,1 SMBIOS and I got the incremental updates.

Maybe due to different systems. You see that if I change to iMac19,1 I also have incremental update, like you.
I'm complaint with this situation because they are small drawbacks compared to having the Fenvi wifi back up and running with Airdrop and the rest.

[Cyberdevs]

Just now, miliuco said:

Maybe due to different systems. You see that if I change to iMac19,1 I also have incremental update, like you.
I'm complaint with this situation because they are small drawbacks compared to having the Fenvi wifi back up and running with Airdrop and the rest.

I did several tests on my KabyLake rig today and the only thing that I had to add to the config to get the incremental updates on MacPro SMBIOS was the revpatch=sbvmm 

[miliuco]

@Max.1974

Fenvi bluetooth doesn't need BlueToolFixup, it works OOTB, so I don't have it. 

[miliuco]

Just now, Cyberdevs said:

I did several tests on my KabyLake rig today and the only thing that I had to add to the config to get the incremental updates on MacPro SMBIOS was the revpatch=sbvmm 

I'll try carefully next beta, on this beta 4 I needed also reverting OCLP changes in config.plist to get the incremental package, revpatch=sbvmm gave to me the full package.

Anyway, it's ok, a few days ago I did not know when I would have (or even if I would have) Wi-Fi with the Fenvi so... 🙂

[Cyberdevs]

3 minutes ago, miliuco said:

I'll try carefully next beta, on this beta 4 I needed also reverting OCLP changes in config.plist to get the incremental package, revpatch=sbvmm gave to me the full package.

Anyway, it's ok, a few days ago I did not know when I would have (or even if I would have) Wi-Fi with the Fenvi so... 🙂

Yes reverting the OCLP patches is necessary to get the incremental updates on all SMBIOS configurations but as far as I've tested there's no need to revert the setting in the config. 

[miliuco]

22 minutes ago, Cyberdevs said:

Yes reverting the OCLP patches is necessary to get the incremental updates on all SMBIOS configurations but as far as I've tested there's no need to revert the setting in the config. 

Ok, understood, let me try in the next beta.

[Cyberdevs]

11 minutes ago, miliuco said:

Ok, understood, let me try in the next beta.

I'm doing another clean install just to make 100% sure.

[Cyberdevs]

@miliuco

Yes that concludes my testings. only revpatch=sbvmm was required on MacPro7,1 SMBIOS. I assume the same applies to iMacPro1,1 as well.

[Max.1974]

3 hours ago, miliuco said:

@Max.1974

Fenvi bluetooth doesn't need BlueToolFixup, it works OOTB, so I don't have it. 

 

Thanks Master my brother!! Saludo Hermano!!

 

 

[Skyfallkavu]

1 hour ago, Cyberdevs said:

@miliuco

Yes that concludes my testings. only revpatch=sbvmm was required on MacPro7,1 SMBIOS. I assume the same applies to iMacPro1,1 as well.

Will test on iMacPro1,1. Just added restrictevents and revpatch=sbvmm. I won't be reverting OCLP patches, but I wouldn't mind if it gives me full package. Previously software update has just been giving me failed to download on all of Sonoma. I've been updating through running the .pkg for each. Now to wait for b5.

[Cyberdevs]

9 minutes ago, Skyfallkavu said:

Will test on iMacPro1,1. Just added restrictevents and revpatch=sbvmm. I won't be reverting OCLP patches, but I wouldn't mind if it gives me full package. Previously software update has just been giving me failed to download on all of Sonoma. I've been updating through running the .pkg for each. Now to wait for b5.

There are few reasons for an update to fail and one of the is the BluetoolFixup.kext being enabled during the update and another one is to booting from another EFI folder that isn't being used for the OS to boot from normally which loads a different APFS snapshot which results to fail while trying to install the update.

[maly70]

i finaly had OCLP patched Sonoma beta4 with my hackintosh

 

Edited August 3, 2023 by maly70

[Skyfallkavu]

3 hours ago, Cyberdevs said:

There are few reasons for an update to fail and one of the is the BluetoolFixup.kext being enabled during the update and another one is to booting from another EFI folder that isn't being used for the OS to boot from normally which loads a different APFS snapshot which results to fail while trying to install the update.

Neither applied to me, I use a Fenvi 919 without any kexts for it (Since I think I don't need them?). Ventura updated delta fine, but even trying to get Sonoma through software update in Ventura would fail. Time will tell.

[surenmunoo]

7 hours ago, miliuco said:

I'll try carefully next beta, on this beta 4 I needed also reverting OCLP changes in config.plist to get the incremental package, revpatch=sbvmm gave to me the full package.

Anyway, it's ok, a few days ago I did not know when I would have (or even if I would have) Wi-Fi with the Fenvi so... 🙂

I use iMac Pro 1.1 and did not revert the OCLP patch to get the incremental update to beta 4 but do have revpatch=sbvmn

[Cyberdevs]

4 hours ago, Skyfallkavu said:

Neither applied to me, I use a Fenvi 919 without any kexts for it (Since I think I don't need them?). Ventura updated delta fine, but even trying to get Sonoma through software update in Ventura would fail. Time will tell.

That's unfortunate.

 Which SMBIOS do you use? and what is the status of SecureBootModel in the config?

[miliuco]

@Cyberdevs

I think that @Skyfallkavu has iMacPro1,1. Yes, SecureBootModel has to have a value other than Disabled to get Ventura, preferably j137 (iMacPro1,1) or j160 (MacPro7,1). But are beta updates enabled in Software Update?

[Cyberdevs]

18 minutes ago, miliuco said:

@Cyberdevs

I think that @Skyfallkavu has iMacPro1,1. Yes, SecureBootModel has to have a value other than Disabled to get Ventura, preferably j137 (iMacPro1,1) or j160 (MacPro7,1). But are beta updates enabled in Software Update?

Yes, exactly, That's why I'm asking about the SecureBootModel's value in config.plist

[televisionadscom]

On 8/1/2023 at 11:37 AM, mnfesq said:

I spent the entire day yesterday - 8 hours straight - configuring my Sonoma installation to run my Broadcom 4352 wifi card.  I used posts of several people as a guide but want to thank @deeveedee for posting his config.plist.  My biggest problem was using the correct (nightly) build of OLCP and the kexts needed for Sonoma wifi.  I also had to revise my SSDT-ARPT.aml because my wifi adapter is on RP06, not RP02, and I had to remove the subsystem ID in the SSDT I downloaded because I have a slightly different 4352 chipset.  I also copied some settings from the DSDT I use to the SSDT-ARPT but these were cosmetic changes only.  It did seem to matter in what order the new kexts were loaded so that took some experimenting for me.  Lastly, I updated to Beta 4 when I was done and once it booted, I received a pop-up from OLCP telling me that I needed to repatch my wifi adapter so I did, rebooted, and everything was functioning.  I am testing things still but the problems I had with AMFI disabled seem to be resolved by using the AMFIPass.kext and the boot-arg to use it on a beta system.  I am a bit concerned that my boot-args are looking like a short novel and I hope to go through them and see whether I can remove any of them.

 

Now, I have a question that has bothered me since I first installed Sonoma.  When I click my mouse button anywhere on the desktop, I get a grayish border around my display and I have no clue what feature causes that or what function it is supposed to serve.  Can someone please explain?  I find it to be a PITA.  Thanks.

I just came across this. I recently got macOS Sonoma installed on my Skylake Lenovo ThinkPad T460 laptop, and I was spending 8 hours also trying to get my DW1560 (which is a Broadcom 4352) WiFi card to work on it! A little PITA 4x more than Ventura last year haha. I'll send you a message but I would like to know further instructions on how did you do it!

[D3v1L]

little software update, Photoshop v25 crash at startup with latest Sonoma beta

[deeveedee]

@televisionadscom Looks like my replies to you were deleted with the recent clean-up.  Here is a simplified Wi-Fi solution for BCM 4352 in Sonoma.