Basic support for Sonoma and Sequoia

[goodbest]

Head over to this discussion
#1091

Quick fact:
Something works, something not

[Daasin]

Will there be any partial support atleast for Sonoma, even in a separate alpha/experimental release would be amazing 🙏👀 @osy @osy86

[osy]

Sure once @goodbest says this is good enough I'll make a release.

[Daasin]

Edit: I was able to get it to boot in safe-mode once with no wallpaper or acceleration, but normal mode just says "Check device power" on my monitor or is blank

From what I've seen, it doesn't work with AMD Graphics selected in the settings.

I've wrote more about it in the linked issue but I can't quite pinpoint why the screen goes blank with no graphics output after the loading screen. The same modifications I made to the EFI worked with Ventura. 🤔

[Daasin]

@osy @osy86 @goodbest I found a potential fix, there's a modified version of PolarisFixUp that adds Sonoma support/compatibility. Perhaps the version here could be replaced with it?

osy/Polaris22Fixup#22

[Malumen]

@osy @osy86 @goodbest is there any way to integrate new polaris build mentioned by @Daasin and update other data (kexts, itlwm, IntelBluetooth, etc.) into a .pkg and push a new release?

Please and thank you! (I'm hoping to get a few more years out of my unit!! I don't have the money for a replacement computer yet...)

[Malumen]

@goodbest All looks successful? How do we access the improved version for Sonoma? I will upgrade my unit from Monterey 12.7.5 direct to latest Sonoma.

[goodbest]

@goodbest All looks successful? How do we access the improved version for Sonoma? I will upgrade my unit from Monterey 12.7.5 direct to latest Sonoma.

Rules No.1:
Do not upgrade your Apple system unless you need to.

Rules No.2:
Always Backup before action.
You should manually backup your existing EFI, in case you can't boot with the new installer. (i have not tested in Monterey).
You should also install sonoma into a new volume (instead of direct updating the existing system) first.

The installer is expected to work in Ventura and Sonoma (no sequoia support yet) with core function like video, audio, wifi.
But I've not tested with the iServices yet.
And the 2nd ethernet is expected to be not working

[Malumen]

@goodbest All looks successful? How do we access the improved version for Sonoma? I will upgrade my unit from Monterey 12.7.5 direct to latest Sonoma.

Rules No.1: Do not upgrade your Apple system unless you need to.

Rules No.2: Always Backup before action. You should manually backup your existing EFI, in case you can't boot with the new installer. (i have not tested in Monterey). You should also install sonoma into a new volume (instead of direct updating the existing system) first.

The installer is expected to work in Ventura and Sonoma (no sequoia support yet) with core function like video, audio, wifi. But I've not tested with the iServices yet. And the 2nd ethernet is expected to be not working

@goodbest so using your opinion, we should not use Sonoma. Do you know Ventura or Monterey is final good support OS? Maybe I will upgrade to Ventura and never Sonoma. I have some apps and features that now require macOS 13. You think this is OK? Just go to Ventura and stop?

[goodbest]

@goodbest All looks successful? How do we access the improved version for Sonoma? I will upgrade my unit from Monterey 12.7.5 direct to latest Sonoma.

Rules No.1: Do not upgrade your Apple system unless you need to.
Rules No.2: Always Backup before action. You should manually backup your existing EFI, in case you can't boot with the new installer. (i have not tested in Monterey). You should also install sonoma into a new volume (instead of direct updating the existing system) first.
The installer is expected to work in Ventura and Sonoma (no sequoia support yet) with core function like video, audio, wifi. But I've not tested with the iServices yet. And the 2nd ethernet is expected to be not working

@goodbest so using your opinion, we should not use Sonoma. Do you know Ventura or Monterey is final good support OS? Maybe I will upgrade to Ventura and never Sonoma. I have some apps and features that now require macOS 13. You think this is OK? Just go to Ventura and stop?

If you need Ventura, then you can go ahead.
Always backup your data, if you want to come back.

[Baio1977]

Thank's for your job

[Baio1977]

I downloaded your PKG, there are still things to fix:
There are many errors in the config.plist, if you use OCAT you can fix them with 1 click.

I attach the Config.plist corrected by errors, I also added 3 drivers to the config that help the end user with the opencore GUI

Config.plist.zip

[NewBornn]

Based on the latest release,The default brightness is the lowest when the computer is turned on, no matter how much it is adjusted after the computer is turned on. thank you very much for your contribution! the another question is my LG ultrafine Display can not adjust volume,The sound can be made, but the slider to adjust the volume is gray.i would appreciate for your help.

[goodbest]

Based on the latest release,The default brightness is the lowest when the computer is turned on, no matter how much it is adjusted after the computer is turned on. thank you very much for your contribution! the another question is my LG ultrafine Display can not adjust volume,The sound can be made, but the slider to adjust the volume is gray.i would appreciate for your help.

You can try this app for brightness and volume control for external monitor.
https://github.com/MonitorControl/MonitorControl

[goodbest]

I downloaded your PKG, there are still things to fix: There are many errors in the config.plist, if you use OCAT you can fix them with 1 click.

I attach the Config.plist corrected by errors, I also added 3 drivers to the config that help the end user with the opencore GUI

Config.plist.zip

Thank you for your feedbacks and efforts for these updates in config.plist.

• For the missing keys part:
  Since the Hac-Mini project is under less active maintenance, it's very hard and unnecessary to follow every config adjustment from OpenCore project (config key addition, deletion, renaming, etc.)

So I suppose the philosophy that Do not include keys in config.plist if we use their default values is by the original author's design. (Correct me if I'm wrong @osy)

In that case, we can treat these missing keys as warnings, rather than errors.

• For the boot tools option part:
  I think it's great to include these tools, if it's an option a user can choose from.
  Maybe your can make a PR, and include these as a installer option (if you know how to do that).

[NewBornn]

However, the release version of @osy and the non-installer EFI file released by @Baio1977 have no problem with the memory of the display brightness and the support of the sound slider. I have used the latest version config with alcid=22, selected native support for Thunderbolt 3, and selected unique ID in the BIOS.

[goodbest]

However, the release version of @osy and the non-installer EFI file released by @Baio1977 have no problem with the memory of the display brightness and the support of the sound slider. I have used the latest version config with alcid=22, selected native support for Thunderbolt 3, and selected unique ID in the BIOS.

May I know your system version?

It seems that you are not talking about Sequoia？Since the non-installer EFI released by @Baio1977 hasn't included the glitch fix for Sequoia yet at that time. But it's working for you. (this is great!)

There maybe at least 3 potential reasons for your issue.

1. Kext bug (caused by newer version).
   Can you try the old Whatever=v1.6.6, and old AppleALC=v1.9.0 (along with alcid=22) kext please?

https://github.com/acidanthera/WhateverGreen/releases
https://github.com/acidanthera/AppleALC/releases

2. TbT3 bug
   Quite hard to debug

3. PolarisFix bug
   Quite hard to debug.

[Baio1977]

https://github.com/Baio1977/NUC8i7HVK-Hackintosh/releases have you tried this?? Ioreg if start this EFI

[NewBornn]

However, the release version of @osy and the non-installer EFI file released by @Baio1977 have no problem with the memory of the display brightness and the support of the sound slider. I have used the latest version config with alcid=22, selected native support for Thunderbolt 3, and selected unique ID in the BIOS.

May I know your system version?

It seems that you are not talking about Sequoia？Since the non-installer EFI released by @Baio1977 hasn't included the glitch fix for Sequoia yet at that time. But it's working for you. (this is great!)

There maybe at least 3 potential reasons for your issue.

1. Kext bug (caused by newer version).
   Can you try the old Whatever=v1.6.6, and old AppleALC=v1.9.0 (along with alcid=22) kext please?

https://github.com/acidanthera/WhateverGreen/releases https://github.com/acidanthera/AppleALC/releases

2. TbT3 bug
   Quite hard to debug
3. PolarisFix bug
   Quite hard to debug.

Finally, I went back to @Baio1977 's 1.0.1 release, because this version can continue to use my macOS14.5, correct volume adjustment, and will not return to minimum brightness after restart. I tried to downgrade WhateverGreen and AppleALC, but no help. and after changing the version, a card reader icon appeared in the status bar.

I found the pkg file of your installer version and want to try it. thank you for your contribution, respect!

[NewBornn]

https://github.com/Baio1977/NUC8i7HVK-Hackintosh/releases have you tried this?? Ioreg if start this EFI
I went back to your 1.0.1 release,I just replaced the kext file for airportitlwm, I'm not sure if other configurations need to be changed, but it works well now
thank you very much！

[Baio1977]

@goodbest i forked your reposity, I corrected some things, but the PKG always gives me errors, maybe I will be able to fix it, but I have no skills in the field, the creator of the Reposity should fix everything, perhaps when the official release comes out, also if I have my doubts since there was no update for Sonoma, perhaps @osy no longer has this PC.

[goodbest]

@goodbest i forked your reposity, I corrected some things, but the PKG always gives me errors, maybe I will be able to fix it, but I have no skills in the field, the creator of the Reposity should fix everything, perhaps when the official release comes out, also if I have my doubts since there was no update for Sonoma, perhaps @osy no longer has this PC.

Well, you should start the work based on my branch kext_update rather than branch master.
https://github.com/goodbest/HaC-Mini/tree/kext_update

[Baio1977]

https://github.com/Baio1977/HaC-Mini/tree/kext_update
So far I have solved some errors, the install_kexts.sh section needs to be fixed.
The code is more complex we need to add ARCH ,Comment, MaxKernel and MinKernel.

In the screen below how the Config.plist OC 1.0.1 appears and does not generate errors

in the screen below how the Config.plist generated by the PKG appears

[Carnia]

in the screen below how the Config.plist generated by the PKG appears
@Baio1977 @goodbest
I am grateful to see your contribution to this, and I will continue to pay attention to your progress。
thanks again ~

[goodbest]

https://github.com/Baio1977/HaC-Mini/tree/kext_update So far I have solved some errors, the install_kexts.sh section needs to be fixed. The code is more complex we need to add ARCH ,Comment, MaxKernel and MinKernel.

In the screen below how the Config.plist OC 1.0.1 appears and does not generate errors

in the screen below how the Config.plist generated by the PKG appears

I think it's fine if you really want to add these "missing keys" in the config.plist (However in fact, as I stated before, we use these missing keys' default value.)

But I think you don't have to provide the full config.plist into the repo, as the config.plist is actually a template for the sake of lowering maintenance cost. The kext's info (such as MinKernel, MaxKernel) are automatically scanned by install_kext.sh. Moreover, some kexts are not needed (e.g., you have broadcom wifi card, you don't need intel wifi kext), so the target config.plist must be dynamically generated based on user options.

[NewBornn]

https://github.com/Baio1977/NUC8i7HVK-Hackintosh/releases have you tried this?? Ioreg if start this EFI
Thanks for your help.
I changed NVRAM,Misc-Security and Kernel,and when I boot the PC, the process has to be repeated 3-5 times met the apple logo. I am using sonoma14.5.
Config.plist.zip
I would be grateful if you could solve this problem.