[pre-release] macOS Sonoma

[surenmunoo]

1 hour ago, hiphopboy said:

 

In Sonoma its not show on setting

Setting for Natural scrolling is under mouse settings, see below turned on then off

 

 

 

[axonleo]

5 hours ago, aben said:

Assuming you have a SKL machine and a working EFI for Ventura (if not, I'd suggest you do that first), make the following changes: 

• Update OC and kexts
• Add boot-arg: -lilubetaall
• Use a supported SMBIOS for e.g, MacBookPro15,1 (See supported list here)

Note: If attempting to install on an NVMe drive reliant on NVMeFix, then you're out of luck unfortunately as the kext is no longer supported/maintained; use a natively supported NVMe drive (preferably ones with Phison controller, like WD) OR install to SATA drive instead.

omg i hope u are joking  i hope someone will fix or update the nvme kext in opencore cause i did install Sonoma on my NVMe drive Evo 920 and it did install but i cant boot it and get rebooted at this stage, check the image below.

https://imgur.com/a/3WGSIVv

 

 

Is is nvme drive problem or something else ?

booted with oc 0.9.2, -lilubetaall and SMBIOS imac19.1

[bestal]

On 6/6/2023 at 12:31 AM, Stefanalmare said:

Hhehehehhehe, Sonoma on Ivy Bridge. Let's see if OCLP will do the job.

 

  Reveal hidden contents

 

Update: Seems like Polaris (rx 570 4gb), even if OCLP has finished root patching, has no light. Let's wait next OCLP team move. I suspect, CryptexFixup.kext is not yet prepared for Sonoma and his job should be done manually.

 

@Stefanalmare Is the installation successful?

i installed on black screen but it didn't open😔

Could you please share the efi?

 

[D3v1L]

uhmmm i try? xD

 

 

Brave mode-> on?

 

LoL 

maybe i can clone my installation on test ssd and then update it to Sonoma... so i can see what happen with apps...

[aben]

@axonleo

Most Samsung NVMe SSDs do not play well with macOS' NVMe driver. You could try disabling NVMeFix.kext and see if that helps (probably with longer boot times and broken power management), but if it doesn't, then I'm afraid your only options are to either stay back on macOS versions where your current SSD works OR switch to a natively supported drive.

And yes, there are no plans (at the moment) to add support for modern macOS versions to NVMeFix, as it appears the drivers that ship with these newer versions are more complex to work with due to the more proprietary nature of it. The project is essentially considered discontinued (even for macOS Ventura) as confirmed by project lead Vit. You may refer to his comment here: https://github.com/acidanthera/NVMeFix/pull/7#issuecomment-1578275605

Edited June 7, 2023 by aben
typo

[hiphopboy]

1 hour ago, surenmunoo said:

Setting for Natural scrolling is under mouse settings, see below turned on then off

 

 

 

 

on mine it's not show the Mouse option and something relates with Mouse it's not show the Natural Scrolling as before :))

[miliuco]

8 hours ago, PMheart said:

Did you add `-lilubetaall`, or at least `-revbeta` to forcibly load RestrictEvents? I roughly checked the patches, and they seem to be the same.

-revbeta does the trick, you're right: RestrictEvents loaded, no misconfiguration warning, no ghost PCI slots, RAM info ok. 

Thank you!!!

 

Spoiler

 

 

There is one thing that still catches my eye and that doesn't exist in Ventura. In the Apple menu >> About This Mac I can see "1 warning" but the warning is not displayed at boot and About This Mac window doesn't have any place to get a warning. Other than that, everything seems to work fine with RestrictEvents and MacPro7,1 on Sonoma using -revbeta.

 

Spoiler

 

@PoMpIs this is interesting for you.

 

 

@benmacfreak

Please add a signature to your user profile.

 

Edited June 7, 2023 by miliuco

[SavageAUS]

Im using a SATA SSD to test with but my NVME is present the WD SN850X (Ventura) however my WD SN570 does not show or my Samsung 970 EVO Plus, Yes, this has other things done to the kernel "Maxvalue"  that has to be updated or it will not boot + -lilubetaal, NVMeFix.kext disabled (have to remove Samsung NVME if left enabled) 
Wifi is Apple Original BCM 94960CD with bluetooth 

I’ve been using a Samsung 970 (I think) m.2 in my desktop build for years.
I haven’t updated it to Sonoma yet but Ventura works perfectly.
Should be in my signature.


Sent from my iPhone using Tapatalk

[axonleo]

1 hour ago, aben said:

@axonleo

Most Samsung NVMe SSDs do not play well with macOS' NVMe driver. You could try disabling NVMeFix.kext and see if that helps (probably with longer boot times and broken power management), but if it doesn't, then I'm afraid your only options are to either stay back on macOS versions where your current SSD works OR switch to a natively supported drive.

And yes, there are no plans (at the moment) to add support for modern macOS versions to NVMeFix, as it appears the drivers that ship with these newer versions are more complex to work with due to the more proprietary nature of it. The project is essentially considered discontinued (even for macOS Ventura) as confirmed by project lead Vit. You may refer to his comment here: https://github.com/acidanthera/NVMeFix/pull/7#issuecomment-1578275605

That’s just crazy🤦‍♂️ I don’t know if it’s my bad luck or what it is but every hardware that I buy either require lots of fixes or like now with nvmefix stops being developed all the sudden🤦‍♂️

 

I will try all that when I come home from work in 10 hours but for now what nvme drive are natively supported before apple drop them as well after 5 years at least?

[SavageAUS]

Here goes the AMD rig installing on separate SSD.

Specs in sig.

 

Spoiler

 

[SavageAUS]

Below are the kexts I had to disable and also had to disable the ssd for the 6950xt, needed to use the AMDRadeonNavi kext to get graphics to work and to get this to boot properly, still no wifi but bluetooth and everything else works. Now to map my USB ports as the previous SSDT and subparts does not work 
 

Where about a is the AMDRadeonNavi kext from? I’m stuck at EXITBS:START on my amd rig with a rx 6800 xt.

Exit: never mind I’m a dummy. Needed to change max kernel on patches.


Sent from my iPhone using Tapatalk

[PoMpIs]

1 hour ago, miliuco said:

-revbeta does the trick, you're right: RestrictEvents loaded, no misconfiguration warning, no ghost PCI slots, RAM info ok. 

Thank you!!!

 

  Hide contents

 

 

There is one thing that still catches my eye and that doesn't exist in Ventura. In the Apple menu >> About This Mac I can see "1 warning" but the warning is not displayed at boot and About This Mac window doesn't have any place to get a warning. Other than that, everything seems to work fine with RestrictEvents and MacPro7,1 on Sonoma using -revbeta.

 

  Hide contents

 

@PoMpIs this is interesting for you.

 

 

@benmacfreak

Please add a signature to your user profile.

 

@miliuco

Thanks... ... when I get home I'll try "revbeta"...

 

regarding the warning about this mac, it is not removed, it also happens in ventura and earlier with smbios MacPro7,1 if you start without RestrictEvents and without mapping the memory, when loading the system it says "memory modules misconfigured" and a once shown even if you activate RestrictEvents again, that warning does not disappear

[PMheart]

2 hours ago, miliuco said:

-revbeta does the trick, you're right: RestrictEvents loaded, no misconfiguration warning, no ghost PCI slots, RAM info ok. 

Thank you!!!

 

  Reveal hidden contents

 

 

There is one thing that still catches my eye and that doesn't exist in Ventura. In the Apple menu >> About This Mac I can see "1 warning" but the warning is not displayed at boot and About This Mac window doesn't have any place to get a warning. Other than that, everything seems to work fine with RestrictEvents and MacPro7,1 on Sonoma using -revbeta.

 

  Reveal hidden contents

 

@PoMpIs this is interesting for you.

 

 

@benmacfreak

Please add a signature to your user profile.

 

Thanks. Would you mind switching your OS language to English US, and then post the screenshot with warning again?

[SavageAUS]

AMD success.

Everything except WIFI appears to be working.

I am using Ethernet over Power for internet access at the moment until WiFi gets sorted.

Spoiler

 

Edited June 7, 2023 by SavageAUS

[PMheart]

1 minute ago, SavageAUS said:

AMD success.

Everything except WIFI appears to be working.

  Hide contents

 

Kudos. Did you see the above mentioned warning from Apple logo -> About This Mac as well?

[SavageAUS]

Just now, PMheart said:

Kudos. Did you see the above mentioned warning from Apple logo -> About This Mac as well?

Negative, no warning but I have AppleMCEReporterDisabler.kext & RestrictEvents.kext with -revbeta

[aben]

2 hours ago, axonleo said:

for now what nvme drive are natively supported before apple drop them as well after 5 years at least?

Western Digital would be your best bet - either the SN7xx or SN8xx series.

[acquarius13]

 

Z240 workstation. As previously stated, changed SMBIOS from iMac18,1 to iMac19,1, both in ProductInfo and plist of USBPorts.kext

Updated kexts and OpenCore to the latest available release through OCAT.

 

Wifi not working, bluetooth not tested, smooth update from latest Ventura beta

 

UPDATE 8th June: with this configuration, Bluetooth can be switched on manually but, after approx. 5 seconds, turn automatically off, without appearing really working. I’m sure this small issue will be solved. This seems to me something unrelated to my configuration 

 

UPDATE 14th June: with the latest BrcmPatchRAM release and related kexts, Brcm bluetooth came back on board. 

Edited June 14, 2023 by acquarius13

[miliuco]

1 hour ago, PMheart said:

Thanks. Would you mind switching your OS language to English US, and then post the screenshot with warning again?

 

Here you go.

 

Apple menu >> About This Mac >> 1 alert, clicking it opens the About This Mac window where there is not any link to click and open an alert.

 

Spoiler

 

System Settings >> General >> Info, no PCI ghost slots, memory info is ok, clicking on the question mark next to the RAM memory opens the window with information about the memory.

 

Spoiler

 

Memory info after clicking on the question mark, it's good.

 

Spoiler

 

Are these the images you want to see in English?

 

And, if it's useful, this is the warning in English without -revbeta.

 

Spoiler

 

Edited June 7, 2023 by miliuco

[Stefanalmare]

5 hours ago, ruslan61 said:

@Stefanalmare Is the installation successful?

i installed on black screen but it didn't open😔

Could you please share the efi?

 

https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1076

[miliuco]

EDIT: Forget this as there is already a PR by @lorys89 in the repo, my post is redundant.

 

Most probably it isn't so simple but changing the line 504 of RestrictEvents.cpp file and compiling

//KernelVersion::Ventura,
KernelVersion::Sonoma,

all is working without -revbeta as with current RestrictEvents plus -revbeta (also remaining About This Mac >> 1 alert, only issue I see now).

Which is expected since -revbeta allows loading the current kext with Ventura as the top supported system.

 

Edited June 7, 2023 by miliuco

[miliuco]

1 hour ago, SavageAUS said:

Negative, no warning but I have AppleMCEReporterDisabler.kext & RestrictEvents.kext with -revbeta

 

@PMheart

On my Intel system, AppleMCEReporterDisabler.kext doesn't remove About This Mac >> 1 alert text.

Never used this kext before, tried now only to add more info.

[bestal]

22 minutes ago, Stefanalmare said:

https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1076

 

thank you @Stefanalmare

keep waiting

[D3v1L]

...on MacPro7.1 smbios, for remove the alert, simply compile all entries in platform info (datahub, not only generic) and make a well configured custom memory info.......and alert gone....

[Cyberdevs]

21 minutes ago, D3v1L said:

...on MacPro7.1 smbios, for remove the alert, simply compile all entries in platform info (datahub, not only generic) and make a well configured custom memory info.......and alert gone....

Yep that did the trick, thanks.