[pre-release] macOS Sequoia

[jlrycm]

Hello there! I saw that intlwifi + helliport is working in Sequoia. Is there a airportintel kext nightly build or fork that supports macOS 

Sequoia?

I compiled this airportintel wifi kext a week ago and I’m wondering whether the kext I compiled was already compatible with Sequoia last week.

Edited Sunday at 04:48 PM by jlrycm

[kinhhoang161]

1 hour ago, jlrycm said:

Hello there! I saw that intlwifi + helliport is working in Sequoia. Is there a airportintel kext nightly build or fork that supports macOS 

Sequoia?

I compiled this airportintel wifi kext a week ago and I’m wondering whether the kext I compiled were already compatible with Sequoia last week.

 

Currently, only itlwm.kext + Heliport.app helps you use Intel Wifi on Sequoia. There is no Airportitlwm for this version yet because Dev is busy with work. We still have to wait. There is more that needs to be updated for Airportitlwm, not simply adding Sequoia support for kext

[badbrain]

- WiFi networks are recognized and you can connect to them

- Settings can be customized

- Airplay works

- Airdrop from iPhone to Mac works

- Handoff works

- Continuity camera does not work (system freezes after the connection sound and the screen remains black)

In general, the system is still very unstable after applying the patches. Some apps, such as iMessage or Preview, problems with iCloud. In addition, there are still problems opening files on the system drive - opening files from other drives, however, works without any problems.

Whether new functions such as Rotate WiFI-Address will be available is questionable. Apple has also made changes to the System Preferences app and its extensions.

 

So there's still some work to do and some patience required. A lot more patching is needed than in Sonoma.

 

 

Edited Monday at 08:46 AM by badbrain

[Max.1974]

Congrats! @badbrain are you using special kexts or configuration ? Thanks for sharing! 😉

 

 

[miliuco]

@PoMpIs

The same thing happens to you as those of us who have already tried it. Also, issues with Preview app and others.

[fuzzylogic]

cannot install beta updates despite being enrolled any ideas, i saw the beta under automatic updates but could not turn it on

[eSaF]

9 minutes ago, fuzzylogic said:

cannot install beta updates despite being enrolled any ideas, i saw the beta under automatic updates but could not turn it on

I don't know exactly what is preventing Betas on your rig.

These are what I have that enables them on mine.

Hope this helps.

Spoiler

 

[fuzzylogic]

33 minutes ago, eSaF said:

I don't know exactly what is preventing Betas on your rig.

These are what I have that enables them on mine.

Hope this helps.

  Hide contents

 

not sure i would need AMFIPASS ? its a z390 with the intel onboard graphics

[eSaF]

7 minutes ago, fuzzylogic said:

not sure i would need AMFIPASS ? its a z390 with the intel onboard graphics

So is my Z490 with both onboard and dedicated graphics, try it and see but insure you have a bootable USB just incase you get a panic.

Edited Sunday at 10:05 PM by eSaF

[joevt]

On 6/29/2024 at 7:49 AM, PoMpIs said:

Incredible, the HD620 of the Lenovo L390 is capable of handling the ultrawide monitor (5120x1440@120Hz) 😲

Use https://github.com/joevt/AllRez to discover what's really happening.

 

It's probably a lower resolution. It's possible to do 5120x1440 120Hz using 4:2:2 8bpc but I don't think I've seen that with an Intel GPU.

 

Try 5120x1440 60Hz. That should work without scaling using RGB 10bpc.

 

Edited Monday at 10:05 AM by joevt

[PoMpIs]

1 hour ago, joevt said:

Use https://github.com/joevt/AllRez to discover what's really happening.

 

It's probably a lower resolution. It's possible to do 5120x1440 120Hz using 4:2:2 8bpc but I don't think I've seen that with an Intel GPU.

 

Try 5120x1440 60Hz. That should work without scaling using RGB 10bpc.

 

 

Yes, correct, it works well at 5120x1440@60Hz  👌

 

[PoMpIs]

15 hours ago, miliuco said:

@PoMpIs

The same thing happens to you as those of us who have already tried it. Also, issues with Preview app and others.

 

Yes, it causes a lot of problems, it is very unstable 😅

[jlrycm]

Hello everyone! I copied my Sonoma install to an external disk and after that upgraded it to Sequoia beta 2. I'm booting macOS 15 using clover 5159 and it's working well. I updated lilu and related plugins/kexts to the latest versions and I was able to boot well without lilubetaall boot arg (if I use the boot arg it's not booting). Booting with opencore 1.0.1 was also possible. When booting with clover, the wifi worked using itlwm + helliport. My only question is how do I get rid of the memory module misconfiguration alert.

Edited yesterday at 11:50 AM by jlrycm

[miliuco]

@jlrycm

Are you using MacPro7,1 SMBIOS? You need RestrictEvents.kext.

 

Edited yesterday at 08:07 AM by miliuco

[ivak4eto]

On 6/30/2024 at 8:47 AM, cankiulascmnfye said:

This might be interesting for users with bad laptop speakers: https://github.com/bitgapp/eqMac

Be careful with that app, especially with low end. My gf blew up the speakers with it on her Dell Precision 5510.

[jlrycm]

3 hours ago, miliuco said:

@jlrycm

Are you using MacPro7,1 SMBIOS? You need RestrictEvents.kext.

 

@miliuco Yes, that’s what I’m using and I’m also using restrictedevents kext.

 

Do I need to run the following commands in Terminal to get rid of the alert?

defaults delete com.apple.SlotNotificationsPref memoryBadgeCount
defaults delete com.apple.SlotNotificationsPref expansionBadgeCount

Edited yesterday at 11:50 AM by jlrycm

[Craig Hazan]

Apple Intelligence might not be available in Sequoia yet, but Apples AI Model, M4, is publicly available now and you don't need an M series to run it. I've downloaded Apples text-to-image model and added it to Stable Diffusion.

 

https://github.com/apple/ml-4m?tab=readme-ov-file#4m-text-to-image-specialist-models

Edited yesterday at 12:13 PM by Craig Hazan

[miliuco]

@jlrycm

Yes, run these commands but not always fix the issue in Sonoma and Sequoua. 

 

From OpenCore developers:

 

Removing badges (This works until macOS 13)

If using RestrictEvents to block PCI and RAM configuration notifications, they will go away, but the alert in the Apple menu will stay. To get rid of this alert, run the following commands:

defaults delete com.apple.SlotNotificationsPref memoryBadgeCount
defaults delete com.apple.SlotNotificationsPref expansionBadgeCount

 

Edited yesterday at 01:21 PM by miliuco

[cankiulascmnfye]

3 hours ago, ivak4eto said:

Be careful with that app, especially with low end. My gf blew up the speakers with it on her Dell Precision 5510.

 

Well that's not an issue of the app, that's a layer 8 problem…

[ivak4eto]

22 minutes ago, cankiulascmnfye said:

 

Well that's not an issue of the app, that's a layer 8 problem…

True, what I meant was it would have been great to incorporate two modes: basic/advanced where basic has some sort of limiter, so newbies won't damage their equipment. I personally love it, that's why I installed it on my gf laptop. I'm just trying to warn others what could happen if not careful.

But we're going way off-topic here 🤓 

Edited 23 hours ago by ivak4eto

[deeveedee]

For those who need multiple displays in Sequoia, I have started conducting dual-GPU tests for my hack here.  This is the first that I am testing Radeon graphics in Big Sur or later (my last Radeon experience was with Catalina) and I must say - Sequoia handles dual-GPU (Intel and Radeon) beautifully and seamlessly.  Based on my limited testing, those who need multiple displays do not need to feel limited or constrained by the number of graphics ports on their Radeon dGPU.

 

EDIT: I'm a newbie when it comes to Radeon graphics, so I apologize for what may be a remedial question: Are there any use cases that necessitate configuration of the Intel iGPU as headless when installing a Radeon dGPU?  If so, what breaks if the Intel iGPU is not configured as headless when a Radeon dGPU is installed?

 

I ask only because the hackintosh Radeon guides that I have read specify a headless iGPU configuration when installing a Radeon graphics card.  I never questioned this until I found myself limited by a single dGPU-connected graphics port on my hack.  Now, I am finding that the iGPU can be fully enabled/configured (not headless) and all graphics ports (dGPU-connected and iGPU-connected video ports) benefit from Radeon graphics acceleration.

Edited 22 hours ago by deeveedee

[cankiulascmnfye]

2 hours ago, deeveedee said:

I ask only because the hackintosh Radeon guides that I have read specify a headless iGPU configuration when installing a Radeon graphics card.  I never questioned this until I found myself limited by a single dGPU-connected graphics port on my hack.  Now, I am finding that the iGPU can be fully enabled/configured (not headless) and all graphics ports (dGPU-connected and iGPU-connected video ports) benefit from Radeon graphics acceleration.

 

There's a reason for configuring the iGPU headless - at least when using an iMac SMBIOS: the iGPU is utilized for Intel Quick Sync Video and HEVC encoding/decoding in the case. My RX580 has 4 ports. Why would I use the iGPUs output in this case while sacrificing iQSV and HEVC capabilities, when I could connect 4 displays to the GPU directly?

Edited 20 hours ago by cankiulascmnfye

[deeveedee]

@cankiulascmnfye I didn't question your need for additional graphics ports.  My dGPU has a single DP port, so I can't use headless iGPU if I want multiple displays. 

 

Have you tested your iMac with a non-headless iGPU to demonstrate that  Intel Quick Sync Video and HEVC encoding/decoding does not work (so it only works with iGPU headless configuration)?

 

EDIT: My VideoProc Hardware Info (with non-headless Intel iGPU and Radeon RX 560x):

Spoiler

 

EDIT2: My question could quickly go beyond the scope of this Sequoia thread.  If you have constructive comments / responses, please post them in my hack-specific thread here.  Thank you.

Edited 19 hours ago by deeveedee

[HyperX7]

On 6/30/2024 at 1:39 AM, CloverLeaf said:

 

Yea, I am familiar with the commands but I think that -igfxbrs should be -igfxbls. Correct me if I am wrong.

Yes master! You are right. I was using this command incorrectly. Thank you for the correction.