[pre-release] macOS Sequoia

[Stefanalmare]

55 minutes ago, bluenote56 said:

 

Hi may I ask how you patched? OCLP or what? Thanks

 

 

42 minutes ago, AlfredoM said:

I would be interested in that too.
Does your nVidia graphics card work with full graphics acceleration?
Thanks for the info on that.

 

It is OCLP compiled from source/development, bypassing the 2 restrictions. All on: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

Full acceleration.

 

41 minutes ago, deeveedee said:

@bluenote56 and @AlfredoM It would be a good idea to post your NVidia graphics card / chipset with your questions.  @Stefanalmare's GT 710 was natively supported by macOS through Big Sur (without the need for "web drivers").   Not all Nvidia are equal.  For example, I still can't patch my Nvidia Tesla graphics with OCLP.  Chances are, if your Nvidia graphics was last officially supported in High Sierra, it still won't work in Sequoia with OCLP (not yet).

 

It works with all Metal 3802, but in my case, not on the rigs that need KDK.

[bluenote56]

1 hour ago, deeveedee said:

@bluenote56 and @AlfredoM It would be a good idea to post your NVidia graphics card / chipset with your questions.  @Stefanalmare's GT 710 was natively supported by macOS through Big Sur (without the need for "web drivers").   Not all Nvidia are equal.  For example, I still can't patch my Nvidia Tesla graphics with OCLP.  Chances are, if your Nvidia graphics was last officially supported in High Sierra, it still won't work in Sequoia with OCLP (not yet).

 

1 hour ago, deeveedee said:

@bluenote56 and @AlfredoM It would be a good idea to post your NVidia graphics card / chipset with your questions.  @Stefanalmare's GT 710 was natively supported by macOS through Big Sur (without the need for "web drivers").   Not all Nvidia are equal.  For example, I still can't patch my Nvidia Tesla graphics with OCLP.  Chances are, if your Nvidia graphics was last officially supported in High Sierra, it still won't work in Sequoia with OCLP (not yet).

 

Hi, I wrongly assumed it was enough from my signature. Anyway I use Nvidia 780 and 770 (Kepler) which work perfectly with OCLP till Sonoma. I didn't remember that 710 works outb. Therefore I must wait.

[Andrw0380]

17 hours ago, eSaF said:

I don't know what exactly your problem is.

I just had a Quick Look at your EFI Folder and in the kext tree, you have the USB.kext first.

 

I don't know if it is still relevant but the golden rule is Lilu.kext should always be the first kext.

Maybe if I knew a bit more of your problem, I could offer a possible solution.

My issue is I can't enable or use Bluetooth as anytime I try and enable it, the toggle goes in the off position and in System Information, it shows BRCM_4350C2 instead of Third Party Dongle like it did in Sonoma. I've just tried the BT kexts from @CloverLeaf with removing 'lilubetall' boot-args and still no BT. Thanks @CloverLeaf for providing your EFI folder.

Edited September 1, 2024 by Andrw0380

[Andrw0380]

6 hours ago, deeveedee said:

Thanks to help from @CloverLeaf, I figured out why my Intel Bluetooth wasn't working in Sequoia Beta.  I was testing non-zxystd Bluetooth kext builds that others had built.  It turns out that if I use the "official" zxystd Sequoia Bluetooth kext builds and Shanee's Bluetoolfixup.kext (without -lilubetaall) or Acidanthera's BluetoolFixup.kext (with -lilubetaall as @acquarius13 said), Intel Bluetooth is working for me with Intel 9560.

 

See details here.  Intel Bluetooth is now working for me with Sequoia Beta 8 and Intel 9560.

 

 

EDIT: @eSaF FYI - Lilu.kext only needs to be injected before Lilu-dependent kexts.  Unless someone develops a USB port map kext that depends on Lilu, USB port map kexts and other kexts that do not depend on Lilu can be injected before Lilu.kext without issues.

Hey man, do you have the zxystd's Sequoia Bluetooth kexts handy that I can try and see if that fixes my issue? I don't see them officially released on here or Github and only see the commit to support Sequoia which have to be built manually?

[strangeron]

16 minutes ago, Andrw0380 said:

Hey man, do you have the zxystd's Sequoia Bluetooth kexts handy that I can try and see if that fixes my issue? I don't see them officially released on here or Github and only see the commit to support Sequoia which have to be built manually?

Could it be a problem that there are Lilu 1.6.6 and BlueToolFixup 2.6.7 in the config.plist, while Lilu 1.6.8 and BlueToolFixup 2.6.9 are in the kexts folder?

[cankiulascmnfye]

Regarding Ivy Bridge: iGPU patching does not work – even if you build it from source (Sequoia Development branch)

 

[cankiulascmnfye]

2 hours ago, Stefanalmare said:

It is OCLP compiled from source/development, bypassing the 2 restrictions.

 

Which Restrictions are you referring to exactly? Building from sequoia source didnt allow patching Intel HD 4000

[Stefanalmare]

17 minutes ago, cankiulascmnfye said:

 

Which Restrictions are you referring to exactly? Building from sequoia source didnt allow patching Intel HD 4000

 

1.  Bypass "3802 patchability check": in sys_patch/detections/detect.py line 724 commented out the return False.

2. Re-compile the privileged-helper-tool with make debug (Terminal), removes Dortania signing.

Like I said, all is here: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

[Andrw0380]

52 minutes ago, strangeron said:

Could it be a problem that there are Lilu 1.6.6 and BlueToolFixup 2.6.7 in the config.plist, while Lilu 1.6.8 and BlueToolFixup 2.6.9 are in the kexts folder?

That is just a comment so it shouldn't affect loading kexts. I've just noticed that when I do a cold boot, IntelBluetoothFirmware doesn't load in kextstat, but when I boot into Windows and do a restart into Mac, then it loads, but still no BT, so it appears like an issue with my 0032 BT firmware loading on the Mac. I've tried building both IntelBTPatcher and IntelBluetoothFirmware from the official Github source, with using the BlueToolFixup that was posted here, but that didn't work.

[deeveedee]

2 hours ago, eSaF said:

Thanks for the clarification.

I tend to stick to the old school Dortania way which hasn't failed me as yet. 

Please forgive my misunderstanding - I thought you were saying that Lilu.kext needed to be injected before USBPorts.kext in order for USBPorts.kext to work properly.  I'll interpret that to mean that I'm too young to know the "old school" way, since I've never heard of it.  

 

2 hours ago, bluenote56 said:

Hi, I wrongly assumed it was enough from my signature. Anyway I use Nvidia 780 and 770 (Kepler) which work perfectly with OCLP till Sonoma. I didn't remember that 710 works outb. Therefore I must wait.

Please accept my apology for not inspecting your signature.  I need to make that a habit, since it's not my first time.  Sorry about that.

 

2 hours ago, Andrw0380 said:

Hey man, do you have the zxystd's Sequoia Bluetooth kexts handy that I can try and see if that fixes my issue? I don't see them officially released on here or Github and only see the commit to support Sequoia which have to be built manually?

See here.  Login to GitHub to download the build.

 

EDIT: @bluenote56 Just to clarify, I didn't say that NVidia 710 (Kepler Metal 3802) was supported natively in Sequoia, I said it was supported natively in Big Sur.  If you have a NVvidia Kepler Metal 3802 graphics card, then by all means, please test the OCLP nightly to see if you can duplicate Stefanalmare's success.

Edited September 1, 2024 by deeveedee

[Max.1974]

On 8/31/2024 at 9:59 PM, Andrw0380 said:

Obrigado pela informação. Acabei de tentar com aquele boot-args e, infelizmente, nenhuma mudança. É estranho o fato de que todos os 3 kexts estão carregados e eu não mudei meu mapa SMBIOS ou USB Port quando fiz a atualização, então é estranho que de repente não esteja funcionando, especialmente depois de fazer algumas redefinições da NVRAM. Eu tenho Wi-Fi funcionando, pois apenas a BT não está funcionando na placa AX210 no meu laptop Dell Inspiron 7567.

 

Anexei minha pasta OC com meu config.plist. Eu removi a seção genérica exclusiva do SMBIOS para o meu sistema e tive que remover o 'itwlm.kext' e o 'IntelBluetoothFirmware.kext', pois o tamanho do arquivo compactado era muito grande para aqui, mas esses kexts estão no meu OC na pasta Kexts que está sendo usada.

OC.zip 4,79 MB·10 downloads

 

Hi @Andrw0380 

 

All good? I looked at your config.plist and noticed that there are 2 keys missing and modified two others if you want to test.

 

Here your config.plist 

 

config.plist.zip

 

 

 

Modifications:

 

ExtendBTFeatureFlags     Bolean     true

 

Spoiler

 

 

XhciPortLimit      Bolean     true

 

Spoiler

 

 

 

 

 

 

 

 

I add 2 keys that important in Nvram 

 

NVRAM > 7C436110-AB2A-4BBB-A880-FE41995C9F82

 

bluetoothExternalDongleFailed    data    <00>

 

bluetoothInternalControllerInfo    data     <00000000 00000000 00000000 0000>

 

 

Spoiler

 

 

Hope you can fix that 

 

 

 

Need fix your internal ports to 255 in USB mapping. 

 

 

If you want try this version of IntelBluetooth v2.4.0 

 

https://github.com/OpenIntelWireless/IntelBluetoothFirmware/releases/tag/v2.4.0 

 

 

Check here too:

 

https://github.com/perez987/Intel-AX210-wifi6-on-macOS-Sonoma#installing-wifi-module 

 

 

Edited September 2, 2024 by Max.1974

[AlfredoM]

5 hours ago, Stefanalmare said:

 

 

It is OCLP compiled from source/development, bypassing the 2 restrictions. All on: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

Full acceleration.

 

 

It works with all Metal 3802, but in my case, not on the rigs that need KDK.

works ???? with GeForce GTX 780M in my iMac late 2013 -27 Inch ?

Edited September 1, 2024 by AlfredoM

[AlfredoM]

5 hours ago, Stefanalmare said:

 

 

It is OCLP compiled from source/development, bypassing the 2 restrictions. All on: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

Full acceleration.

 

 

It works with all Metal 3802, but in my case, not on the rigs that need KDK.

Can you please tell me how I can do this for my Keppler nVidia GTX 780M (in the iMac late 2013 with i7 Intel CPU (27 inches)

so that I finally get full graphics support?
Thanks for that.

[Andrw0380]

4 hours ago, Max.1974 said:

 

Hi @Andrw0380 

 

All good? I looked at your config.plist and noticed that there are 2 keys missing and modified two others if you want to test.

 

Here your config.plist 

 

config.plist.zip 5.94 kB · 5 downloads

 

 

 

Modifications:

 

ExtendBTFeatureFlags     Bolean     true

 

  Reveal hidden contents

 

 

XhciPortLimit      Bolean     true

 

  Reveal hidden contents

 

 

 

 

 

 

 

 

I add 2 keys that important in Nvram 

 

NVRAM > 7C436110-AB2A-4BBB-A880-FE41995C9F82

 

bluetoothExternalDongleFailed    data    <00>

 

bluetoothInternalControllerInfo    data     <00000000 00000000 00000000 0000>

 

 

  Reveal hidden contents

 

 

Hope you can fix that 

 

 

 

Need fix your internal ports to 255 in USB mapping. 

 

 

If you want try this version of IntelBluetooth v2.4.0 

 

https://github.com/OpenIntelWireless/IntelBluetoothFirmware/releases/tag/v2.4.0 

 

 

Check here too:

 

https://github.com/perez987/Intel-AX210-wifi6-on-macOS-Sonoma#installing-wifi-module 

 

 

Thanks so much man as I now have working BT! I've added those config.plist changes with the IntelBluetoothFirmware build that was on the official Github page that @deeveedee provided above your comment and everything now works! 

 

I did take a look at the USBPort map and on my Dell Inspiron 7567, the BT adapter and the Camera is connected to port 0x04 and 0x0C which I did have mapped to internal (255) port. I just wanted to make sure per your comment if that is correct and what port map changes were you referencing? Also if I have the USBPorts.kext active, do I still need the XhciPortLimit key set to true? Just wanting to know for future reference so I know I'm running the config properly.

[Max.1974]

26 minutes ago, Andrw0380 said:

Muito obrigado, cara, como agora tenho BT trabalhando! Eu adicionei essas alterações do config.plist com a compilação IntelBluetoothFirmware que estava na página oficial do Github que @deeeveedee forneceu acima do seu comentário e tudo agora funciona!

 

Eu dei uma olhada no mapa USBPort e no meu Dell Inspiron 7567, o adaptador BT e a câmera estão conectados às portas 0x04 e 0x0C que eu mapeei para a porta interna (255). Eu só queria ter certeza de que, de acordo com o seu comentário, se isso está correto e a quais mudanças no mapa do porto você estava se referindo? Além disso, se eu tiver o USBPorts.kext ativo, ainda preciso que a chave XhciPortLimit seja definida como verdadeira? Só quero saber para referência futura para que eu saiba que estou executando a configuração corretamente.

 

You can try use XHCIPortlimit true first, and after this not work, try false (not recommended) but tell me what keys you add to fix? I prepare your config.plist to working. 

 

Yes im absolutely sure that 255 is internal ports. Usbports use SMBIOS, check inside the plist. Every time that you change SMBIOS, if you are using USBPorts.kext you need change SMBIOS too. 

 

Im using to fix old HDD compile RHUB ports, but laptop maybe not need that. Always use to internal ports like Bluetooth Broadcom, intel AX that not is CNvio, but you can use too. 

 

In my desktop I have been used both: Broadcom Bluetooth and isolated intel BT, using Intel Wireless or OCLP, you choose that as you want. 

 

Enjoy it! 

Edited September 2, 2024 by Max.1974

[Max.1974]

For exemple 

 

 

[Andrw0380]

26 minutes ago, Max.1974 said:

 

You can try use XHCIPortlimit true first, and after this not work, try false (not recommended) but tell me what keys you add to fix? I prepare your config.plist to working. 

 

Yes im absolutely sure that 255 is internal ports. Usbports use SMBIOS, check inside the plist. Every time that you change SMBIOS, if you are using USBPorts.kext you need change SMBIOS too. 

 

Im using to fix old HDD compile RHUB ports, but laptop maybe not need that. Always use to internal ports like Bluetooth Broadcom, intel AX that not is CNvio, but you can use too. 

 

In my desktop I have been used both: Broadcom Bluetooth and isolated intel BT, using Intel Wireless or OCLP, you choose that as you want. 

 

Enjoy it! 

Here is my updated config.plist with working Wi-Fi and BT. I've cleaned it up and removed the old entries of kexts I had set to disable when I first posted it. I believe the fix was using the proper BT kexts with adding the NVRAM BT entries as I didn't have that before in my config.plist.

 

I've also posted my USBPorts.kext which has my laptop ports are broken down as follows:

- External USB 3 ports for USB 2.0 devices use connectors 0x01-0x03, 0x07 (USB Card Reader) and USB 3.0 devices connect to 0x11-0x13

- Internal ports are 0x04 (Bluetooth Adapter) and 0x0C (Internal Camera)

 

The Dell Inspiron 7567 only has a USB 3.0 Controller for it's ports so that's why I've set all the external ports to value 3 and internal ports to 255 as per best practices. Thanks again everyone for helping me get this to work! 

config.plist USBPorts.kext.zip

Edited September 2, 2024 by Andrw0380

[Max.1974]

Its seems to me is all right now! 🤩 

 

 

[cankiulascmnfye]

8 hours ago, Stefanalmare said:

 

1.  Bypass "3802 patchability check": in sys_patch/detections/detect.py line 724 commented out the return False.

2. Re-compile the privileged-helper-tool with make debug (Terminal), removes Dortania signing.

Like I said, all is here: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

 

Okay, thanks. I have got to figure wherer this line went, because the detect.py file was removed/replaced in the latest commit: "patchsets: Implement new patch detection architecture"

[bluenote56]

8 hours ago, eSaF said:

No worries, I think it is well known that I am probably the oldest here on IM, Quite a fossil actually. 

You're in good company my friend, mostly because I'm a modest man 😅

[bluenote56]

8 hours ago, deeveedee said:

Please forgive my misunderstanding - I thought you were saying that Lilu.kext needed to be injected before USBPorts.kext in order for USBPorts.kext to work properly.  I'll interpret that to mean that I'm too young to know the "old school" way, since I've never heard of it.  

 

Please accept my apology for not inspecting your signature.  I need to make that a habit, since it's not my first time.  Sorry about that.

 

See here.  Login to GitHub to download the build.

 

EDIT: @bluenote56 Just to clarify, I didn't say that NVidia 710 (Kepler Metal 3802) was supported natively in Sequoia, I said it was supported natively in Big Sur.  If you have a NVvidia Kepler Metal 3802 graphics card, then by all means, please test the OCLP nightly to see if you can duplicate Stefanalmare's success.

Yor're very welcome and there's no problem at all. Concerning Nvidia 710 I got it but my reply was incomplete. btw I tried the OCPL nightly but it get the same issue like many others ( it doesn't work) so I decided to wait. 

[Henties]

8 hours ago, eSaF said:

No worries, I think it is well known that I am probably the oldest here on IM, Quite a fossil actually. 

I am not so sure, I am vintage April 45 and still going strong.

 

Greetings Henties

[robi62]

@Stefanalmare

It is OCLP compiled from source/development, bypassing the 2 restrictions. All on: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

Full acceleration.

I have no idea how to do that and dont have xcode installed … can you share you recompiled version????

[Stefanalmare]

28 minutes ago, robi62 said:

@Stefanalmare

 

It is OCLP compiled from source/development, bypassing the 2 restrictions. All on: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/

Full acceleration.

I have no idea how to do that and dont have xcode installed … can you share you recompiled version????

 

Sorry, it is against the developers policy. If you can't compile according with your needs, for sure if you have trouble you can't deal with it. Sorry! Better wait a bit.

[robi62]

@Stefanalmare

No worries I understand 👍