[Release] macOS Sequoia 15.0

[deeveedee]

Posting this question to satisfy my curiosity... For those who may be having a problem in Sequoia with non-working BlueToolFixup.kext, does the addition of boot-arg

 

-btlfxallowanyaddr

 

fix the problem?  If your Bluetooth chipset needs BlueToolFixup.kext and BlueToolFixup.kext is working properly, you should see that "System Report > Bluetooth > Chipset" = "THIRD_PARTY_DONGLE."

 

Properly working BlueToolFixup.kext: System Report > Bluetooth > Chipset = THIRD_PARTY_DONGLE

[Slice]

15 hours ago, LockDown said:

You mean you can't get incremental update with 19.1 in sequoia without revpatch=sbvbmm?

I have no problem getting incremental even without the flag with 19,1

Do not mix. There is "or".

You can get update with 19,1 in Sonoma but not in Sequoia

or

you can get update with revpatch=sbvbmm in Sequoia no matter of SMBIOS.

[miliuco]

About updates notifications on Sequoia, this is my personal experience.

• No OCLP root-patch
  • Only SMBIOS models that lacks T2 security chip (e.g. iMac19,1) receive notifications of new updates in System Settings. Rest of the models that have T2 chip are only notified if you add:
    • RestrictEvents.kext
    • revpatch=sbvmm in boot args.
  • Updates can be incremental in both cases.
• OCLP root-patch
  • SMBIOS models with T2 chip do not get notifications without RestrictEvents.
  • SMBIOS models without T2 chip get update notifications but incremental updates are lost with this setting (full installation package is downloaded).

This contradicts @Slice statement about iMac19,1 on Sequoia without RestrictEvents. At least with SMBIOS iMac19,1 I can say that I am notified of updates and they are incremental (if I don't have OCLP root patch installed).

 

@LockDown

Yes, you can get updates notifications and updates are incremental without the flag with iMac19,1, except if OCLP root patch is installed.

Edited October 15, 2024 by miliuco
Fix typo

[Slice]

@miliuco,

but I have SMBIOS iMac19,1 and I got updates up to Sonoma and not in Sequoia. What I did wrong?

 

Now I get updates using Clover's trick with Board-ID=VMM-x86_64 that is equivalent to revpatch=smbvmm but without kexts.

[Anto65]

It works here with both : Clover and OC  iMac19,1 

... In download ( Beta7 15.1 )

 

Spoiler

 

                        

 

 

[miliuco]

@Slice

I don't know. I remember that you have iMac19,1 with disabled iGPU in BIOS, right? Maybe is it important for this? Or maybe it's hardware dependant and not all of our systems have the same behaviour.

Edited October 15, 2024 by miliuco
Fix typo

[Slice]

Are you sure you will get update in Sequoia with a SMBIOS and without RestrictEvents.kext? For my experience it is impossible whatever SMBIOS you choose.

[miliuco]

@Slice

Yes, I can confirm that. iMac19,1 with SecureBootModel=x86legacy without RestrictEvents. If I change to any other SMBIOS (iMac20,x, iMacPro1,1 or MacPro7,1) then I do need RestrictEvents and the boot arg.

[chris1111]

3 hours ago, miliuco said:

@Slice

Yes, I can confirm that. iMac19,1 with SecureBootModel=x86legacy without RestrictEvents. If I change to any other SMBIOS (iMac20,x, iMacPro1,1 or MacPro7,1) then I do need RestrictEvents and the boot arg.

I am using iMac19,1 on my main PC SecureBootModel=Disable + RestrictEvents without boot args

Update free 😀

[LockDown]

1 hour ago, chris1111 said:

Update free 😀

☝️means you're not getting update 

[Extreme™]

MacPro7.1:

 

SecureBootModel=Disable + RestrictEvents without boot args

[chris1111]

8 hours ago, LockDown said:

☝️means you're not getting update 

Update free in french = Mise à jour gratuite

So Yes I am getting update with this setup

[Slice]

May be RestrictEvents already has this boot-args by default?

[miliuco]

@Slice

I thank that @lorys89 fork of RestrictEvents does have the boot arg but official version does not.

 

@Extreme™

You are destroying my theory, MP7,1 has a T2 chip and should not be notified of updates 😭

Hackintosh is a complex world.

[deeveedee]

I'm following this discussion with interest.  I think it would be beneficial for everyone if those reporting clarify the version of RestrictEvents.kext, since as @miliuco said, there was an "unofficial" fork that included revpatch=sbvmm by default.

 

EDIT: @Extreme™ is this still the RestrictEvents.kext variant that you are using?

Edited October 19, 2024 by deeveedee

[cankiulascmnfye]

I have this 3 TB Western Digital HDD (WD30ZRCX) which I use for data storage. Eversince macOS Ventura, it takes like 30 minutes until it pops up in the FInder and is accessible. It's formatted in ExFAT and there are no issues with it. It works fine in Windows and according to Crystal Disk Info, it's health is "good". I have a Z490 mainboard. I also have an additional 2TB Seagate HDD in the system formatted in APFS and it just works fine when booting macOS, so I don't thinks it's relatated to missing SATA controller kexts. Anyone had similar issues?

[chris1111]

I am using iMac19,1 on my main PC SecureBootModel=Disable + RestrictEvents.kext without boot args

RestrictEvents.kext V-1.1.5 compile from source origin Acidenthera by me

I never have any issue to update macOS on this PC like this way

 

[Anto65]

RestrictEvents should not be needed with iMac19.1 at least in my case, I always received update notifications... SBM Disabled for sure 🤷

Edited October 19, 2024 by Anto65

[miliuco]

1 hour ago, Anto65 said:

RestrictEvents should not be needed with iMac19.1 at least in my case, I always received update notifications... SBM Disabled

 

It happens to me like you. But I don't need SBM=Disabled, it also works fine with SBM=x86legacy.

 

 

[chris1111]

1 hour ago, Anto65 said:

RestrictEvents should not be needed with iMac19.1 at least in my case, I always received update notifications... SBM Disabled for sure 🤷

So the kext are not need in my case, iMac19.1 do the job 

It would be interesting to know all the smbios that are capable

Edited October 19, 2024 by chris1111

[miliuco]

@chris1111

So far I was thinking that SMBIOS with security chip T2 make the difference. SMBIOS without T2 can get updates notification without RestrictEvents.

[LockDown]

still no fix for bluetoothfixup that breaks incremental update?

[Extreme™]

17 hours ago, deeveedee said:

I'm following this discussion with interest.  I think it would be beneficial for everyone if those reporting clarify the version of RestrictEvents.kext, since as @miliuco said, there was an "unofficial" fork that included revpatch=sbvmm by default.

 

EDIT: @Extreme™ is this still the RestrictEvents.kext variant that you are using?

 

Hello,

 

RestrictEvents 1.1.5 from Dortania here:

 

https://dortania.github.io/builds/?product=RestrictEvents&viewall=true

 

A little video from my Sequoia beta 7

 

https://odysee.com/Untitled:0bc?r=Gdgb3ZTGusE6Zv8FScHnUe2xZ4qFQ7ca

Edited October 20, 2024 by Extreme™

[miliuco]

@deeveedee

RestrictEvents 1.1.5 "official" doesn't include the boot arg, it must be explicitly added, as you already know.

So, if @Extreme™ gets updates notification with MacPro7,1, this RestrictEvents but no boot arg, then there is something I don't understand.

Maybe the rule is not as simple as T2 -> boot arg needed, no T2 -> boot arg not needed.

 

[hardcorehenry]

 

sbvmm can also be under NVRAM>Add>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102...

Spoiler

 

 

Edited October 20, 2024 by hardcorehenry