Jump to content

[pre-release] macOS Sonoma

fantomas

By fantomas,
in New Releases and Updates

 Share
1,844 posts in this topic

Recommended Posts

cankiulascmnfye
cankiulascmnfye
Posted
Posted
4 hours ago, AlfredoM said:

I want to draw a brief conclusion about Sonoma Beta1 based on my previous Tests:

 

The Sonoma Beta1 is currently unusable.

 

Almost nothing works, sometimes WLAN, which is a minor matter with Ethernet on the desktop, apart from that.

I'm using OC 0.8.8 and it's ALL absolutely bug free on Ventura, also 13.5 Beta2.

 

For example, why is a normal SSD displayed as NVME in the system information on Sonoma? and the SSD is not visible anywhere.

 

Not a single USB port works (I use the Hackintosh as visible in my signature), although these USBs are all green and visible in

Tool Hackintool, but are not displayed on the desktop and in Disk Utility.

 

I guess it has nothing to do with the fact that I used the migration assistant when installing Sonoma and migrated everything

from Ventura 13.4 to Sonoma or is it because of all these errors with not working USB and missing NvME and SSD I don't think it has anything to do with that.

 

I think you have to seperate the functionality of the OS versus your driver and configuration requirements for it… I mean, I have Sonoma running on my 10 year old Ivy Bridge Laptop (for testing) and besides the WiFi kexts and the graphics acceleration that's missing it is working. It's also working on my 8th Gen Laptop and on my 10th Gen Dektop. And I can't confirm any of the issue you are witnessing.

  • Like 3
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)
2 hours ago, mek21 said:

If any are concerned about Apple's continued use of Broadcom hardware you need only search for the May announcement of a multi-billion dollar contract.

 

And you are very happy if you are a AVGO (Broadcom) stock holder!

Edited by deeveedee
  • Haha 5
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)
48 minutes ago, cankiulascmnfye said:

 

… I mean, I have Sonoma running on my 10 year old Ivy Bridge Laptop (for testing) and besides the WiFi kexts and the graphics acceleration that's missing it is working. It's also working on my 8th Gen Laptop and on my 10th Gen Dektop. And I can't confirm any of the issue you are witnessing.

 

Agreed.  We just installed the initial release of a brand new macOS as we face the inevitable end to Apple's Intel support.  Each day that we can still install macOS on our hacks is a great day (and it's still a great day, even if we can't).  I've said it before and I'll say it again - if you're complaining about issues with installing a brand new macOS Sonoma on Windows Intel hardware, then you need to watch Louis CK's explanation of "A Chair in the Sky."  What we have accomplished here at this stage is incredible.

Edited by deeveedee
  • Like 8
Link to comment
Share on other sites
AlfredoM
AlfredoM
Posted
Posted (edited)
3 hours ago, deeveedee said:

 

Agreed.  We just installed the initial release of a brand new macOS as we face the inevitable end to Apple's Intel support.  Each day that we can still install macOS on our hacks is a great day (and it's still a great day, even if we can't).  I've said it before and I'll say it again - if you're complaining about issues with installing a brand new macOS Sonoma on Windows Intel hardware, then you need to watch Louis CK's explanation of "A Chair in the Sky."  What we have accomplished here at this stage is incredible.

yes you are right @deeveedee

 

I have now made another blank installation and still have the same problem.

 

1. No USB port works, although the ports used are green in Hackintoshtool and are also recognized, but no USB device is available on the desktop or in Disk Utility.

 

2. Only the partitions on the NvME or SSD are visible and also in Disk Utility where the Sonoma is installed. The 2nd Win (NTFS) NvME is visible in the

system properties but not physically available. Also the Sata3 SSD is not visible in Disk Utility.

 

Should it really be because of the OC 0.8.8?

 

That means yes, everything we did with OC 0.8.8 in Ventura, Monterey, Big Sur etc. is now obsolete and invalid for Sonoma ???

Alos then yes OC 0.9.3 e.g. would have to be completely rebuilt in order to work with Sonoma. Is that the case and what has been fundamentally changed, e.g.

that all NvME and SSD drives are recognized. Wouldn't that also change with OC 0.8.8?

 

Thanks for help on this.

Edited by AlfredoM
  • Like 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted

@AlfredoM - Perhaps your best option is to remove your machine's personal data from the config.plist i.e S/N, ROM etc zip and upload your EFI Folder here so that all files and kexts can be updated and then you can try it on a spare USB Drive and see what results you get.

  • Like 2
Link to comment
Share on other sites
AlfredoM
AlfredoM
Posted
Posted
9 minutes ago, eSaF said:

@AlfredoM - Perhaps your best option is to remove your machine's personal data from the config.plist i.e S/N, ROM etc zip and upload your EFI Folder here so that all files and kexts can be updated and then you can try it on a spare USB Drive and see what results you get.

I don't dare.... because if you see that I'm still using old FakeSMC instead of VirtualSMC (I use it because the sensors aren't recognized in iStat with VirtualSMC,

but with FakeSMC they are), then you might say that's the reason is, but this is definitely NOT the case, because Ventura 13.5 Beta2 and 13.4 and all other macOS on the "old" FakeSMC work perfectly!!!

 

Ok I can do it tomorrow, upload my EFI as it works perfectly with Ventura and all other macOS.

I know that e.g. Chris1111 once saw my EFI in his forum and only complained that everything was supposedly wrong,

although everything runs perfectly on my Hackintosh (see signature).

 

@eSaFCan I send it to you as a PM first?

Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 hour ago, AlfredoM said:

@eSaFCan I send it to you as a PM first?

If you feel more comfortable that way, then yes I will look at it for you and make any adjustments/corrections for you to try.

  • Like 1
Link to comment
Share on other sites
DMhackintosh
DMhackintosh
Posted
Posted (edited)
12 hours ago, Cyberdevs said:

You can either select the xcode Command Line tools under xcode's Preferences -> Locations -> Command Line Tools or download and install the Command Line Tools for Sonoma and you'll be able to install anything that requires the command line tools.

 

Thank you

12 hours ago, Cyberdevs said:

You can either select the xcode Command Line tools under xcode's Preferences -> Locations -> Command Line Tools or download and install the Command Line Tools for Sonoma and you'll be able to install anything that requires the command line tools.

 

9 hours ago, fantomas said:

 

Hi,

You have to install Command Line_Tools_for_Xcode_15_beta.dmg manually

 

 

Thank you 

clubdj_—_-zsh_—_80×24.png

Edited by DMhackintosh
  • Like 3
Link to comment
Share on other sites
cankiulascmnfye
cankiulascmnfye
Posted
Posted (edited)
5 hours ago, AlfredoM said:

Should it really be because of the OC 0.8.8?

 

YES! Your OpenCore build is half a year old – refer to the OpenCore changelog and see how many features have been introduces and/or modified since then.

 

And: don't use Hackintool for analyzing port functionality, use IO Registry Explorer!

 

Are you using a USB Port map kext?

If so,which SMBIOS was it created under?

Did your switch the SMBIOS since then?  If you did, then the won't work any longer! You need to add the new SMBIOS to the "model" property inside the info.plist

And use latetest nighty builds of kexts for beta OSes which can be found on Dortania's Build repo: https://dortania.github.io/builds/?viewall=true

Point being: if you want to use the newest isht you have to follow the technological developments and utilize them!

Edited by cankiulascmnfye
  • Like 5
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
7 hours ago, AlfredoM said:

although everything runs perfectly on my Hackintosh (see signature).

Your claim is this but by whose standard? My standard is........The moment I push the ON button on my machine, it takes 45 seconds with 4 versions of OS X in a multi-booting configuration as well as Win11 to arrive at the Desktop and that includes entering my P/W.

So my standard is a maximum of 1 minute, anymore than that I search the boot logs for possible hangups in the booting stage.

 

Claiming your system runs perfect with old OC files and kexts is quite a bold one, as @cankiulascmnfye points out you are missing out on the tremendous progress and added features made by the OC Developers since the OC 0.8.8 build.

At the end of the day, if you're happy then by all means.

  • Like 4
Link to comment
Share on other sites
surenmunoo
surenmunoo
Posted
Posted
9 hours ago, AlfredoM said:

I don't dare.... because if you see that I'm still using old FakeSMC instead of VirtualSMC (I use it because the sensors aren't recognized in iStat with VirtualSMC,

but with FakeSMC they are), then you might say that's the reason is, but this is definitely NOT the case, because Ventura 13.5 Beta2 and 13.4 and all other macOS on the "old" FakeSMC work perfectly!!!

 

Ok I can do it tomorrow, upload my EFI as it works perfectly with Ventura and all other macOS.

I know that e.g. Chris1111 once saw my EFI in his forum and only complained that everything was supposedly wrong,

although everything runs perfectly on my Hackintosh (see signature).

 

@eSaFCan I send it to you as a PM first?

I use the new updated virtualsmc.kext and get all sensor, temp readings from iStat on Ventura 13.5 and Sonoma

Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)

It looks like zxystd's BrcmPatchRAM updates to BluetoolFixup have merged with Acidanthera's branch.

 

EDIT: At the time of this post, the changes are still being merged.  If you're waiting for this fix to appear in the Acidanthera version, best to monitor the commits or wait for the Acidanthera release.

 

EDIT2: This topic has already been beaten to death in this thread, but just be sure sure it's put to rest, BrcmPatchRAM is for Bluetooth, not Wi-Fi.

Edited by deeveedee
  • Like 3
  • Thanks 3
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted (edited)
7 hours ago, deeveedee said:

It looks like zxystd's BrcmPatchRAM updates to BluetoolFixup have merged with Acidanthera's branch.

 

EDIT: At the time of this post, the changes are still being merged.  If you're waiting for this fix to appear in the Acidanthera version, best to monitor the commits or wait for the Acidanthera release.

 

Im test here and with Airport kext for intel not work even BT. 

 

Already work fenvi t1919? I remove to not get conflict with intel wireless and BT, but works only on Ventura. Thanks! 

Edited by Max.1974
  • Like 1
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted
14 minutes ago, Max.1974 said:

 

Im test here and with Airport kext for intel not work even BT. 

 

Already work fenvi t1919? I remove to not get conflict with intel wireless and BT, but works only on Ventura. Thanks! 

Use itlwil kext AND Heliport app, Works GREAT, 

This ONLY Gets Wifi Working

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted (edited)
2 hours ago, cankiulascmnfye said:

@Max.1974 It's merged: https://github.com/acidanthera/BrcmPatchRAM/commit/2305aaa145a0021559f444d33a5adaacb6469050 (see changelog at the end)

 

 

 

Thanks a lot my friends!!! In fact, I get wireless and BT intel working on Ventura 13.4, and once time I get Airdrop working. I think I lost configuration, and loose Airdrop working in intel. 

 

In Sonoma, unfortunately im not get wireless or BT working with Airport or itlwm :( 

 

But still waiting for great work from Coders. 

 

 

2 hours ago, STLVNUB said:

Use itlwil kext AND Heliport app, Works GREAT, 

This ONLY Gets Wifi Working

 

Edited by Max.1974
  • Like 2
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted (edited)

Hi all

 

Just to report, I have EFI OC 0.9.4 that works all in Ventura Beta 13.5 3 and wi-fi, bluetooth, Airdrop, ethernet... etc.

 

My kexts is mixed from intel and Broadcom Fenvi T-1919

 

Just waiting for magic hands of ours Coders. Anyone have problems with last Ventura and Broadcom Pcie cards?

 

<edit<. Not boot in Sonoma except if im deleted AirportBrcmFixup.kext 

 

Thanks God for Good people  like all of you, in special @deeveedee that said to me about config.plist Kernel patch 

 

Now boot both system Ventura and Sonoma with Broadcom Card Fence T-1919

 

 

image.thumb.png.f583d570fa0e13879363fcdf7d2c53fe.png

 

 

But on Ventura all right 

 

If someone want suggest something, please, speak about it, and  I not use wi-fi intel because will not work Airdrop that's essencial on my job. 

 

My Kexts print and my boot args:

 

-lilubeta -alcbeta -revbeta -wegbeta alcid=12 watchdog=0 agdpmod=pikera npci=0x2000 keepsyms=1

 

 

 

Captura de Tela 2023-06-16 às 15.03.18.png

 

 

 

 

Captura de Tela 2023-06-16 às 15.18.18.png

Captura de Tela 2023-06-16 às 11.31.55.png

Edited by Max.1974
  • Like 7
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted
15 minutes ago, PMheart said:

To those who get kernel panic with AirportBrcmFixup — what kind of error did you encounter?

 

Hi my friend, im get Black Screen from my RX 6900 XT and make loop infinity turn on / off monitor, and I saw (I guess) when im deleted AirportBroadcomFixup so I can boot on Sonoma beta 1

 

32 minutes ago, Moviemakergr said:

@Max.1974

I have delete all the bootargs -(allbeta) with latest versions Dev kexts and working fine.

 

Im update all kexts too, but to Sonoma only boot with this args. 

 

Thanks all for help!!!

 

 

  • Like 2
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...