Jump to content
1709 posts in this topic

Recommended Posts

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.

  • Confused 2
6 hours ago, DMhackintosh said:

I installed Xcode 15beta and I can't install homebrew on sonoma.

Anyone having this problem? and how to fix thank you in advance

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.

  • Like 2
1 hour ago, AlfredoM said:

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.

 

What system? I don’t see it in your signature. I think you did your USB incorrectly. My EFI works flawlessly from High Sierra to Sonoma except for WiFi in Sonoma

  • Like 3

@PoMpIs YAY. I have an Intel AC-9560 as well. And dumb as I am, I ordered another one thinking: "hey, I can put this on in my Ivy Bridge Notebook later for Sonoma"… BUT I forgot: it uses a completely different form factor than what I need. So now I got a spare. :D 

Edited by cankiulascmnfye
  • Haha 3
  • Sad 1
5 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.

If you had homebrew working in Ventrua you can copy over the files from usr/local and the corresponding files from (your username) directory that apply to the brew installed programs.

 

There was no problem using xcode from Ventura after installing Sonoma over Ventura beta 5, and brew apps worked ok after the update.

  • Like 1
3 hours ago, DMhackintosh said:

I installed Xcode 15beta and I can't install homebrew on sonoma.

Anyone having this problem? and how to fix thank you in advance

 

 


X Code Error 1.png

X Code Error 2.png

 

Hi,

You have to install Command Line_Tools_for_Xcode_15_beta.dmg manually

 

  • Like 4
  • Thanks 1
2 hours ago, DrThodt said:

 

Welches System? Ich sehe es nicht in deiner Signatur. Ich denke, Sie haben Ihren USB falsch gemacht. Mein EFI funktioniert von High Sierra bis Sonoma einwandfrei, mit Ausnahme von WLAN in Sonoma

System:  Sonoma 14-Beta1 Mein OC 0.8.8 work in ALL another Ventura, Monterey, BigSur ect

 

2 hours ago, eSaF said:

Sorry to see you're having a bad time with Sonoma. Forgive me if I interpreted your post wrong but  my assumption is your install is half baked by  the results you described.

Have a look at my NVME Connection in System Information (attached pic) and my USB Configuration in Hackintool.

 

I am not in anyway an expert but personally I would start with a clean install oppose to a migratory one, also ditch OC 8.8 regardless how well it is running previous OS X versions, update to the latest released OC version and kexts.

Hope you get sorted with better results.

  Reveal hidden contents

210243353_Screenshot2023-06-14at15_56_58.png.481eddf2f5d021f002a16a6ebd0cd91d.png141272110_Screenshot2023-06-14at16_59_14.png.9b8e3d8b4fe271eb5d6cbdd835c936c8.png

 

Thank You god Friend for yuor Message.

 

Do you think it could be because of the migration?

 

I can't explain myself like that.

 

But ok, I'll do a clean install again

 

And do you think that I should definitely switch from OC 0.8.8 to a higher version?

In my OC 0.8.8 I have all current kextes from 12.6.23 in it.

 

Everything works, even BT, except WLAN, which is not that important on the desktop, thanks to the LAN Ethernet connection.

 

On my orig iMac Sonoma Beta1 with migration from Ventura 13.5 runs fine

  • Like 1
3 hours ago, PoMpIs said:

Well, the Magic trackpad works great too 😁

 

 

 

Nice man!! I need to know if Airdrop works and you using a Heliport or not? Just AirportItlwm.kext enable your wi-fi?

 

7 hours ago, cankiulascmnfye said:

 

255 just enables all available flags. For enabling the Mouse Pointer Control 16 is enough.

 

AirportItlwm = no. You need to use itlwm and HeliPort.

 

For BT you need to use BlueToolFixup from this build for the time beeing until Acidanthera have updated it: https://github.com/zxystd/BrcmPatchRAM/actions/runs/5218453965

 

Download "Artifacts" thingy at the bottom. Requires Githu account

 

 

Many thanks bro!! Its possible are posted BlueToolFixup beta here? 

19 hours ago, ameenjuz said:

I have intel wifi card ax201 working fine on Ventura but Airdrop do not work 

how did you get airdrop working on Intel wifi chipset? 

My card is AX211 from Aorus Z790 Elite AX Gigabyte. 

Edited by Max.1974
  • Like 1
7 minutes ago, Max.1974 said:

 

¡¡Buen hombre!! Necesito saber si Airdrop funciona y si usas un Heliport o no. ¿Solo AirportItlwm.kext habilita tu wi-fi?

 

 

 

¡¡Muchas gracias, hermano!! ¿Es posible que se publique la versión beta de BlueToolFixup aquí?

 

 

No, AirportItlwm.kext doesn't work, so there is no Airdrop...

 

If one day it's compatible, I'll be satisfied... it works very well with Heliport + bluetooth for now

 

BlueToolFixup.kext.zip

 

 

26 minutes ago, AlfredoM said:

System:  Sonoma 14-Beta1 Mein OC 0.8.8 work in ALL another Ventura, Monterey, BigSur ect

 

You have to update the OC, I have tried Sonoma on 5 computers, none of them have any of the failures you mention... only the broadcom 4360 wifi have failed 

Edited by PoMpIs
  • Like 2
  • Thanks 1
23 minutes ago, eSaF said:

Didn't you say you used migration assistant to install Sonoma? There is the possibility that something went amiss between the two in the cross over install.

As a rule I always clean install new OS X version installs on a spare disk, that way I don't carry over any possible glitches from a previous version.

If I do have any glitches I can rule out the possibility that it was brought over from the previous version.

 

Use OCAT to update OC and kexts for latest versions and check for any misalignments in the config.plist.

Thank you, I'll do a clean install on Hackintosh soon.

First with OC 0.8.8 and if the same problems occur again, I will test a newer OC version, but ONLY with Sonoma.

I would like to keep my OC 0.8.8 for Monterey, Ventura etc. because it runs absolutely error-free.

  • Like 1
3 minutes ago, AlfredoM said:

Thank you, I'll do a clean install on Hackintosh soon.

First with OC 0.8.8 and if the same problems occur again, I will test a newer OC version, but ONLY with Sonoma.

I would like to keep my OC 0.8.8 for Monterey, Ventura etc. because it runs absolutely error-free.

upgrade Alfred OC 0.93 is better

  • Like 4
30 minutes ago, PoMpIs said:

 

 

No, AirportItlwm.kext doesn't work, so there is no Airdrop...

 

If one day it's compatible, I'll be satisfied... it works very well with Heliport + bluetooth for now

 

BlueToolFixup.kext.zip 12.44 kB · 2 downloads

 

 

 

You have to update the OC, I have tried Sonoma on 5 computers, none of them have any of the failures you mention... only the broadcom 4360 wifi have failed 

 

Thanks a lot my friend, im trying use your Kexts. 

 

God bless you all!!  

  • Like 3
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
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
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 7
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
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?

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
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 4
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

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
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
Guest
This topic is now closed to further replies.
×
×
  • Create New...