[pre-release] macOS Ventura

[aben]

No issues with Private Relay here on my Dell machine. Beta 3.

[PoMpIs]

21 minutes ago, Hervé said:

This new option is indeed activated by default, whether it be the LAN or the Wireless interface... so? No relation to Private Relay if that's what you had in mind. Has no influence on the iCloud service whether enabled or not.

https://support.apple.com/en-gb/HT212614

 

ah!! ok... i'm not interested in having any of that active 

[deeveedee]

I prefer to restrict the data that I share with Apple and others, yet somehow during the Ventura Beta install and upgrade process, I had inadvertently enabled "Share Mac Analytics" and was fortunate to stumble upon this as I was checking my settings.   I believe that this setting changed when I applied Ventura Beta 3 Update (22A5295i) after installing the initial Ventura Beta 3.  If this is something that concerns you, you may want to check your own Privacy settings in Ventura Beta.

 

Privacy & Security: Analytics & Improvements

Spoiler

 

[Guest ricoc90]

I believe sharing Mac analytics is enabled per default on Developer Beta's. 

According to the License Agreement (haha who ever reads those?!):
 

8. Consent to Collection and Use of Data.
8.1 Pre-Release Software for Apple’s Operating Systems (e.g., versions of iOS, watchOS, iPadOS,
tvOS, and macOS). In order to provide, test and help Apple, its partners, and third party developers
improve their products and services, and unless you opt out in the pre-release versions of Apple's
operating system, as applicable, you acknowledge that Apple and its subsidiaries and agents will be
collecting, using, storing, transmitting, processing and analyzing (collectively, “Collecting”) diagnostic,
technical, and usage logs and information from your devices or computers that are running such prerelease versions of Apple’s operating system software as part of this Beta Program. This information will
be Collected in a form that does not personally identify you and may be Collected from your devices or
computer at any time. The information that would be Collected includes, but is not limited to, general
diagnostic and usage data, various unique device identifiers, various unique system or hardware
identifiers, details about hardware and operating system specifications, performance statistics, and data
about how you use your devices, computer, system and application software, and peripherals, and, if
Location Services is enabled, certain location information. You agree that Apple may share such
diagnostic, technical, and usage logs and information with partners and third party developers for
purposes of allowing them to improve their products and services that operate on or in connection with
Apple-branded products. By installing or using pre-release versions of Apple’s operating system
software on your devices or computers, you acknowledge and agree that Apple and its
subsidiaries and agents have your permission to Collect all such information and use it as set
forth above.

 

[aufuk1]

6 hours ago, deeveedee said:

 

@aufuk1 Did this error occur with previous versions of macOS (before Ventura)?  You're posting in a Ventura pre-release thread, so I'm just checking.  If this error is not unique to Ventura and you do experience this error in mature releases of macOS (e.g. Big Sur, Monterey), it's best to resolve issues like this with a stable macOS release (just my opinion) and not in a Beta version of macOS.

 

In your OC config.plist,  you enable the kexts listed below.  How did you determine that your rig needs all of these kexts?

• Item 5: VoodooI2C.kext/Contents/PlugIns/VoodooInput.kext
• Item 6: VoodooPS2Controller.kext/Contents/PlugIns/VoodooInput.kext
• Item 7: VoodooRMI.kext/Contents/PlugIns/VoodooInput.kext
• Item 14: VoodooInput.kext
• Item 15: VoodooI2C.kext/Contents/PlugIns/VoodooGPIO.kext
• Item 16: VoodooI2C.kext/Contents/PlugIns/VoodooI2CServices.kext
• Item 17: VoodooI2C.kext
• Item 18: VoodooI2CHID.kext
• Item 19: VoodooPS2Controller.kext
• Item 20: VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Keyboard.kext
• Item 21: VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Trackpad.kext
• Item 22: VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Mouse.kext
• Item 23: VoodooSMBus.kext
• Item 24: VoodooRMI.kext
• Item 25: VoodooRMI.kext/Contents/PlugIns/RMISMBus.kext

 

EDIT: In my HP laptop (a different model), I inject only VoodooPS2Controller kexts (no RMI or I2C kexts or SMBUs kexts).  I also block Apple's I2C kexts with the following:

 

Block Apple I2C kexts

  Reveal hidden contents

 

EDIT2: I forgot to mention that while I was reviewing your config.plist, I noticed that you enable ECEnabler.kext and you inject Device EC with your SSDT-EC-USBX.aml SSDT.  I don't use ECEnabler.kext so I'm not sure, but is this the correct use of ECEnabler.kext?   After reading about ECEnabler.kext, I see that your use of the kext and SSDT are perfectly acceptable (if they are necessary).

 

You will want to resolve this in a different thread (not in the Ventura pre-release thread).

 

Hi,

 

No problem on Monterey. It gives this error on Ventura installation. Actually my screen is not touchscreen. I got the efi folder from this address.

I removed VoodooI2C.kext and VoodooI2CHID.kext. I did the other operation but it still didn't work.

 

 

https://github.com/XXCoreRangerX/Hackintosh-HP-EliteBook-840-G4

Edited July 20, 2022 by aufuk1

[aufuk1]

6 hours ago, ricoc90 said:

They're collectables! Gotta collect them all! 

In all seriousness, 
@aufuk1 Determine if your trackpad is SMBus or l2c, then keep its respective kexts and get rid of the others. See https://github.com/VoodooSMBus/VoodooRMI#compatibility
 

Anyway this isn't really the place for it, so you might want to open your own thread for it since it's not Ventura related

 

Thanks

 

 

 

[Ellybz]

Unavailable Private relay - 

Same story on X299. ( OSX Ventura is still vanilla on my system ).

I even tried toggling on/off combinations WFI & Ethernet. 

 

 I can still use my VPN in the future so no big deal for now . ( VPN not installed yet on Ventura ).

 

Edited July 20, 2022 by Ellybz

[PoMpIs]

I'm not going to use private relay, but if it helps you, today I rebooted on my i5 to update monterey that I have on another SSD, and I tried to activate private relay, and everything went well:

 

But now when I return to Ventura it has stopped working 😆

 

 

I use the same EFI for both systems 🤷‍♂️

[miliuco]

@PoMpIs

It's the same for me, it's working on Monterey but not on Ventura.

[Extreme™]

@Ellybz

 

Hi,

 

no problem with private relay in Ventura Beta 3 and X299 Sage 10G. 

[PoMpIs]

5 hours ago, Extreme™ said:

@Ellybz

 

Hi,

 

no problem with private relay in Ventura Beta 3 and X299 Sage 10G. 

 

Is it a clean install of Ventura, or have you upgraded from Monterey to Ventura?

Because if you update from Monterey to Ventura private relay still works in beta 3

[deeveedee]

With regard to @aufuk1 's issue here, I noticed that I was not able to block the loading of a kext in Ventura Beta 3 with OC 0.8.3.  It was an experiment that I was doing and was not important, so I discounted the issue as my own user error and never tried again.  Has anyone else noticed a problem with blocking kexts in Ventura via OC's Kernel > Block mechanism (Strategy: Disable)?

 

I tried to block with SIP enabled and with SIP disabled and found that the particular kext I was testing was still loading.  Again, I dismissed this as my own user error and am now wondering if in fact this is something new with OC and Ventura.   Thank you.

 

EDIT: I briefly looked through OC issues and found this.

Edited July 21, 2022 by deeveedee

[rafale77]

2 hours ago, deeveedee said:

With regard to @aufuk1 's issue here, I noticed that I was not able to block the loading of a kext in Ventura Beta 3 with OC 0.8.3.  It was an experiment that I was doing and was not important, so I discounted the issue as my own user error and never tried again.  Has anyone else noticed a problem with blocking kexts in Ventura via OC's Kernel > Block mechanism (Strategy: Disable)?

 

I tried to block with SIP enabled and with SIP disabled and found that the particular kext I was testing was still loading.  Again, I dismissed this as my own user error and am now wondering if in fact this is something new with OC and Ventura.   Thank you.

 

EDIT: I briefly looked through OC issues and found this.

I was going to ask whether the blocking worked on Monterey. My attempts indeed also failed there...

[Ellybz]

9 hours ago, Extreme™ said:

@Ellybz

 

Hi,

 

no problem with private relay in Ventura Beta 3 and X299 Sage 10G. 

I'm still looking for the issue. It's also unavailable with Monterey. ( System settings incompatible ). The presence of the I210 or intelAX200 might be the culprit.

Switching today to BCM94360 ( Waiting for the card ).  Enough with the Intel BT/WiFi B.S. 🤬

Edited July 21, 2022 by Ellybz

[Extreme™]

4 hours ago, PoMpIs said:

 

Is it a clean install of Ventura, or have you upgraded from Monterey to Ventura?

Because if you update from Monterey to Ventura private relay still works in beta 3

Clean install of Ventura first beta became beta 3 with the updates. 

[Extreme™]

48 minutes ago, Ellybz said:

I'm still looking for the issue. It's also unavailable with Monterey. ( System settings incompatible ). The presence of the I210 or intelAX200 might be the culprit.

Switching today to BCM94360 ( Waiting for the card ).  Enough with the Intel BT/WiFi B.S. 🤬

I am with Fenvi-T919. But honestly it does not fully satisfy me and I decided to buy the original Apple bcm943602cdp card. The card has arrived. I am waiting for the adapter..

[PC IT]

Hi to all, I am still having the same black screen issue on my Skylake using the latest kexts and oc 8.3, smbios 14.1, what happen is when the system boots to the black screen the display is only if i connect an external hdmi which is working perfectly, i wish someone can log into my pc via team viewer to check if any solution for the internal display, the display is working properly in Monerey but with Ventura it isnt.

 

Any suggestions, anyone can help me solving this issue. with many thanks.

on Monterey, display and hdmi working perfectly.

on Ventura , only external hdmi display works, internal display shows a black screen.

 

[Ellybz]

9 hours ago, Extreme™ said:

I am with Fenvi-T919. But honestly it does not fully satisfy me and I decided to buy the original Apple bcm943602cdp card. The card has arrived. I am waiting for the adapter..

I hear you. I did the switch today with BCM94360NG ( on M.2 adapter ). Wifi & BT are working OOB ( Including Airdrop ) but I'm not happy. 🙁

 

Good news (first) : IPhone camera continuity works with Ventura and this feature is amazing! . (IOS 16 )

 

Bad news : Universal control with IPad Pro (3rd Gn) is not working . IPad screen turns black or does not work when  I try to connect it. (Same story with Monterey). IOS 15.5. I would really like to use Universal control of Keyboard+mouse between the Hack & the IPad. Handoff/Cursor & Keys are ✅ on IPad

 

 

This might be off topic but If someone has successfully achieved Universal Control with Ipad, could you please provide your infos ( BCM No /Kext/ SMBIOS/IOS Version /Etc). I would really appreciate it. Thank you. 

 

Private relay is still DOA with Ventura Beta3 & new WiFi/BT card.

 

 

 

Edited July 22, 2022 by Ellybz

[surenmunoo]

1 hour ago, Ellybz said:

I hear you. I did the switch today with BCM94360NG ( on M.2 adapter ). Wifi & BT are working OOB ( Including Airdrop ) but I'm not happy. 🙁

 

Good news (first) : IPhone camera continuity works with Ventura and this feature is amazing! . (IOS 16 )

 

Bad news : Universal control with IPad Pro (3rd Gn) is not working . IPad screen turns black or does not work when  I try to connect it. (Same story with Monterey). IOS 15.5. I would really like to use Universal control of Keyboard+mouse between the Hack & the IPad. Handoff/Cursor & Keys are ✅ on IPad

 

 

This might be off topic but If someone has successfully achieved Universal Control with Ipad, could you please provide your infos ( BCM No /Kext/ SMBIOS/IOS Version /Etc). I would really appreciate it. Thank you. 

 

Private relay is still DOA with Ventura Beta3 & new WiFi/BT card.

 

 

 

If I am correct you would need IGPU for that to work. 

[Extreme™]

@Ellybz

 

I understand. I will mount the new card via pcie slot I was told that doing this via M.2 adapter causes not perfect Bluetooth behavior in Hackintosh.

[aben]

16 hours ago, PC IT said:

Hi to all, I am still having the same black screen issue on my Skylake using the latest kexts and oc 8.3, smbios 14.1, what happen is when the system boots to the black screen the display is only if i connect an external hdmi which is working perfectly, i wish someone can log into my pc via team viewer to check if any solution for the internal display, the display is working properly in Monerey but with Ventura it isnt.

 

Any suggestions, anyone can help me solving this issue. with many thanks.

on Monterey, display and hdmi working perfectly.

on Ventura , only external hdmi display works, internal display shows a black screen.

 

 

Hello again! 

 

I believe I have possibly discovered the reason why your LVDS panel goes blank when using KBL framebuffers. Context: I had a look into your display's native EDID (extracted from the IOREG you shared earlier in the thread, thanks for that) and ran a few test runs; it looks like KBL's LVDS connectors actually fails to activate LVDS panels that have screen dimensions of a 17-inch defined in its native EDID. (most likely there was no reason for Apple to include support for 17inch LVDS panels by the time KBL generation was introduced)

To further prove above theory and potentially solve your issue, I have attached a .plist file below for your convenience, which contains your display's EDID modified to dimensions natively supported by KBL profiles. To inject rectified EDID, you'll need to copy/include the property AAPL00,override-no-connect with its corresponding value to your iGPU device location PciRoot(0x0)/Pci(0x2,0x0) under DeviceProperties of your config.plist. Theoretically, this should, at the least, help activate your LVDS panel on Ventura.

Good luck!

EDID_17inch.plist

Edited July 22, 2022 by aben

[Guest ricoc90]

8 hours ago, Ellybz said:

This might be off topic but If someone has successfully achieved Universal Control with Ipad, could you please provide your infos ( BCM No /Kext/ SMBIOS/IOS Version /Etc). I would really appreciate it. Thank you. 

As surenmunoo correctly mentioned, you indeed would need an iGPU.

[rafale77]

23 minutes ago, ricoc90 said:

As surenmunoo correctly mentioned, you indeed would need an iGPU.

And I will third that. @EllybzSee my sig for an example of working UC.

Edited July 22, 2022 by rafale77

[pietralbino]

Salve, HD 4600 con Ventura ancora incompatibile? 

[Pavo]

22 hours ago, Extreme™ said:

I am with Fenvi-T919. But honestly it does not fully satisfy me and I decided to buy the original Apple bcm943602cdp card. The card has arrived. I am waiting for the adapter..

You do realize that the Fenvi-T919 actually uses a real Apple Wi-Fi/BT card correct?