Jump to content

[Release] macOS Sequoia 15.0


230 posts in this topic

Recommended Posts

With your modified plist something's changed, it says this Mac has 3 Ram slot instead of 12,

on 4 of them is installed a 16gb module, but still non the right way...

The machine works normally though.

Thank you for your time!

 

  • Thanks 1
Link to comment
Share on other sites

4 hours ago, PPCnostalgic said:

You did a very good job, I'm on OpenCore and I have to find a way to replcate what you did with Clover.

Thank you for your hint, I'll try to do something similar with OpenCore..

@PPCnostalgic I worked on replicating the OpenCore memory configuration fix for macpro 7,1 to Clover and I was able to do it and boot from Clover w/o issues using restrictedevents pci boot arg but the memory slot diagram will not look like a real MacPro 7,1, instead will look like a hackintosh MacPro 7,1.

Link to comment
Share on other sites

On 10/4/2024 at 5:48 PM, eSaF said:

This here is a bare bones EFI Folder to hopefully get you up and running.

Clean your NvRAM and try it on a spare USB Drive.

Good luck.

EFI.zip 9.9 MB · 20 downloads

 

Well, after two days of attempts, this is a brief report which I hope can be useful not only for me but also for those with a similar build.

1 There’s no way to make Sequoia boot if I don’t have “amfi_get_of_my_way=1” in nvram

2 In Sonoma WhatsApp and Skype work only if I I don’t have “amfi_get_of_my_way=1” in nvram

Otherwise they don’t.

3 I could successfully allow in Privacy and Security settings Skype and Word to use Microphone and 

Camera after booting Sonoma as per point 2

4 I made a brand new Sequoia ssd to verify if the issues were relating to my main Sequoia build.

Same issues both without OCLP and after applying it.

5 I tried your EFI but it didn’t work. I’m going to try with step by step changes and see what happens.

Anyway after trying the USB with that EFI (and resetting NVRAM twice) it messed up the OCLP 

patches (minor problem). I reapplied.

6 I don’t know why but it randomly takes ages to show a 2 TB/ hd I use to archive music.

This never happened with Monterey

7 Resetting nvram it’s mandatory as you rightly said.

8 Prime video App never works but in browser for reproduction error (who cares after all)

 

So in a nutshell I have the Sonoma build working with Skype (which I use for remote teaching and online working meetings) with  point 2 option and a Sequoia build which is almost useless for me if I don’t fix the problem.

Hackintosh is a passion (everyone here knows it well), that’s why I get mad trying to understand when and where I make mistakes. I can work and enjoy music anyway but you know, “if at first you don't succeed  it’s an understatement here.

Thanks for your help.

 

P.s. (off topic)

Since I can’t get you a beer while listening to good music,  I can send some Italian cooking recipes wherever it can be posted. I’m not very good in hacking but no one has ever complained about my cooking 😄


 

 

 

 

 

 

 

 

 

 

  • Like 1
Link to comment
Share on other sites

1 hour ago, bluenote56 said:

Since I can’t get you a beer while listening to good music,  I can send some Italian cooking recipes wherever it can be posted. I’m not very good in hacking but no one has ever complained about my cooking 😄

Hi, I did say the EFI I posted for you was vanilla where you would have to construct further for your own preferences by adding or deleting.

On another note, I don't doubt in the slightest about your cooking skills which I am sure by the sound of it, is more proficient and tastier than your Hack skills. :thumbsup_anim:

 

Don't give up, you'll get there in the end.

GitHub - https://github.com/topics/hackintosh?o=desc&s=updated - has some examples of your machine specs with working EFI Folders that you can try to see if it can better your situation.

Good luck.

 

  • Haha 1
Link to comment
Share on other sites

2 hours ago, XanthraX said:

Nobody noticed the release of Sequoia 15.01? The update worked flawlessly on my rig. 

Apart from 15.1 Beta (24B5055e) and this one is Public, what is the big difference?

I have it on a USB Drive but yet to install it as I am running 15.1 Beta (24B5055e) at the moment.

  • Like 1
Link to comment
Share on other sites

13 hours ago, LockDown said:

FIXED!!!

Temporarily disabling BlueToolFixup.

 

This appears to be common in the hackintosh community.  I'm not sure if it affects all hack/Mac users the same, but like you, incremental OTA on my HackMini8,1 only works when BluetoolFixup.kext is disabled.  Again, thanks to @ird for enlightening me.

Edited by deeveedee
  • Like 3
Link to comment
Share on other sites

Same thing here as at @LockDown I get incremental updates (doing OCLP revert , I haven't actually applied it lately 🙂 ) but it fails
By disabling BluetoolFixup.kext, everything goes as it should  🤷‍♂️ ( 15.1 Beta 6 )

  • Like 7
Link to comment
Share on other sites

Good evening,


I'm not sure if this is the correct thread for my issue, so I apologize if it's not.
I successfully updated my second Hackintosh to macOS Sequoia, and everything is working perfectly except for one issue: Bluetooth.

I’ve updated all my kexts to the latest versions, but for some reason, I can't activate Bluetooth. Under macOS Sonoma, I used earlier versions of the same kexts without any issues, but on Sequoia, Bluetooth just won't turn on. If I enable it, the toggle stays on for a few seconds and then switches to "Disabled" again.

 


This is what

 log show --last boot | grep -i brcm

shows:
 

2024-10-10 20:41:38.313039+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.lvs1974.AirportBrcmFixup
2024-10-10 20:41:38.313131+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.lvs1974.AirportBrcmFixup) in helper to process load notification
2024-10-10 20:41:38.313537+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmFirmwareStore
2024-10-10 20:41:38.313626+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.acidanthera.BrcmFirmwareStore) in helper to process load notification
2024-10-10 20:41:38.315757+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: com.apple.driver.AirPort.BrcmNIC
2024-10-10 20:41:38.315828+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmPatchRAM3
2024-10-10 20:41:38.315914+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.acidanthera.BrcmPatchRAM3) in helper to process load notification

I did add the following kexts for Bluetooth:
image.thumb.png.0577b411e9fe27e074184cc1691d4cc0.png

bluetoothExternalDongleFailed and bluetoothInternalControllerInfo is also set. 

Bildschirmfoto2024-10-10um20_58_06.thumb.png.2987a1155ab857ce7185eca750329162.png

Port Mapping is also done:

image.thumb.png.92e02045999e0a7147fd6f72b17a1b95.png

image.png.df385f1d13230f5318cc08e4323e4af2.png

image.png.5c2fe86da54bc839e62ca5b70bdddfd4.png

IOReg:

image.thumb.png.b32772dd42fb0d62eb96e8dcdb766ede.png

Any insights or suggestions would be greatly appreciated! Thanks in advance :)

Edited by anullpointerexception
Link to comment
Share on other sites

53 minutes ago, anullpointerexception said:

Good evening,


I'm not sure if this is the correct thread for my issue, so I apologize if it's not.
I successfully updated my second Hackintosh to macOS Sequoia, and everything is working perfectly except for one issue: Bluetooth.

I’ve updated all my kexts to the latest versions, but for some reason, I can't activate Bluetooth. Under macOS Sonoma, I used earlier versions of the same kexts without any issues, but on Sequoia, Bluetooth just won't turn on. If I enable it, the toggle stays on for a few seconds and then switches to "Disabled" again.

 


This is what

 log show --last boot | grep -i brcm

shows:
 

2024-10-10 20:41:38.313039+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.lvs1974.AirportBrcmFixup
2024-10-10 20:41:38.313131+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.lvs1974.AirportBrcmFixup) in helper to process load notification
2024-10-10 20:41:38.313537+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmFirmwareStore
2024-10-10 20:41:38.313626+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.acidanthera.BrcmFirmwareStore) in helper to process load notification
2024-10-10 20:41:38.315757+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: com.apple.driver.AirPort.BrcmNIC
2024-10-10 20:41:38.315828+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmPatchRAM3
2024-10-10 20:41:38.315914+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.acidanthera.BrcmPatchRAM3) in helper to process load notification

I did add the following kexts for Bluetooth:
image.thumb.png.0577b411e9fe27e074184cc1691d4cc0.png

bluetoothExternalDongleFailed and bluetoothInternalControllerInfo is also set. 

Bildschirmfoto2024-10-10um20_58_06.thumb.png.2987a1155ab857ce7185eca750329162.png

Port Mapping is also done:

image.thumb.png.92e02045999e0a7147fd6f72b17a1b95.png

image.png.df385f1d13230f5318cc08e4323e4af2.png

image.png.5c2fe86da54bc839e62ca5b70bdddfd4.png

IOReg:

image.thumb.png.b32772dd42fb0d62eb96e8dcdb766ede.png

Any insights or suggestions would be greatly appreciated! Thanks in advance :)

If you use a dongle USB Bluetooth you need only BlueToolFixup.kext disable other bluetooth kext

  • Like 6
Link to comment
Share on other sites

10 hours ago, chris1111 said:

If you use a dongle USB Bluetooth you need only BlueToolFixup.kext disable other bluetooth kext


I am using a Dell DW1830 NGFF WiFi-Card installed in the Wi-Fi slot on my Motherboard. I don‘t know why its not working, I did install Sonoma yesterday on a spare SSD for testing purposes and Bluetooth and WiFi are working perfectly fine under Sonoma. 

Edited by anullpointerexception
Link to comment
Share on other sites

13 minutes ago, anullpointerexception said:


I am using a Dell DW1830 NGFF WiFi-Card installed in the Wi-Fi slot on my Motherboard. I don‘t know why its not working, I did install Sonoma yesterday on a spare SSD for testing purposes and Bluetooth and WiFi is working perfectly fine under Sonoma. 

It is strange that it is working under Sonoma but not Sequoia.

Maybe for some reason the slot is not powered in Sequoia. In Hackintool, you should be able to see if it is or not.

Link to comment
Share on other sites

Are you using Dual Boot with Windows ? Maybe firmware injection incompatíble with macOS. Are try reset nvram?
 

Maybe you should try this command

 

sudo pkill bluetoothd 

 

And check AirPort kexts if you really need all this 3 versions. 
 

I saw your usb internal ports. Its seems you not need all of them mapping internal. 
 

Check your plist XHCI Port limit is enable and try extract with Hackintool kext under usbmap and them replace it with usbports and SSDTs. 
 

Add device fake ID properties too with compatible for your DW1830. 
 

Use device native number id 

 

Need use too acpi wake your devices xhci 

 

I think you need check here. 
 

Broadcom fix

Edited by Max.1974
Link to comment
Share on other sites

On my HackMini8,1 booting Sequoia 15.1 Beta with OC 1.0.2, Microsoft Remote Desktop (now "Windows App") still has connectivity issues over Ethernet that can be resolved by setting Ethernet to "Inactive" and then back to "Active."  Sequoia 15.0.1 (Release) does not have this issue.  My hack's details are as follows:

 

  • HP EliteDesk 800 G4 Mini with Radeon RX 560x dGPU (Ethernet: Intel i219LM)
  • Open Core 1.0.2, IntelMausi.kext 1.0.7
  • SMBIOS macMini8,1
  • Windows App (MS Remote Desktop) v11.0.5 (2401)
Link to comment
Share on other sites

@anullpointerexception Very nice screenshots.  Unfortunately, not helpful (for me).  I would recommend always posting your EFI when asking for help.  

 

Just a guess since there's not enough information to diagnose - depending on the version of BluetoolFixup.kext that you are using, you may need a Beta boot arg (either use -btlfxbeta or -lilubetaall).  Do you need a beta boot arg?  You can tell if BluetoolFixup.kext is working properly by looking at System Report and confirming that Bluetooth Chipset is reported as "THIRD_PARTY_DONGLE."

 

Screenshot2024-10-11at7_48_59AM.png.5e78466c9616ded279ffe0b102e006d8.png

 

Again, you'll get a lot better support if you post your EFI.  If it's too big to post, post only the OC/config.plist and OC/Kexts.  If still too big, post your EFI to external storage and provide a link.  Less screen shots, more EFI.

 

EDIT: If you determine that the beta boot-arg fixes your problem, you can upgrade to the latest BluetoolFixup.kext 2.6.9 (available in Acidanthera's BrcmPatchRAM package) which natively supports Sequoia without the beta boot-arg.

Edited by deeveedee
  • Like 1
Link to comment
Share on other sites

6 hours ago, anullpointerexception said:


I am using a Dell DW1830 NGFF WiFi-Card installed in the Wi-Fi slot on my Motherboard. I don‘t know why its not working, I did install Sonoma yesterday on a spare SSD for testing purposes and Bluetooth and WiFi are working perfectly fine under Sonoma. 

OK you have a Mini PCI 

Did you try a Reset NVRAM from Opencore

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...