BALDY_MAN Posted July 17, 2022 Share Posted July 17, 2022 (edited) Abit late to the party with my Z97 Hack. its all sunny I'm my Hackintosh Garden Thanks to bisdak4920 for sharing his EFI. for my Z97 Hack Edited July 17, 2022 by BALDY_MAN 7 Link to comment Share on other sites More sharing options...
SavageAUS Posted July 17, 2022 Share Posted July 17, 2022 Has anyone noticed there hard drive filling up on Ventura? In particular the cache folder located in your home directory-> Library. I have 100GB partitioned for it and it’s consistently filling up. Link to comment Share on other sites More sharing options...
aufuk1 Posted July 17, 2022 Share Posted July 17, 2022 (edited) On 6/30/2022 at 11:11 PM, chris1111 said: HP Elitebook 840 G4 everithings work well Dont worry be Happy To make batterie working you need to setup config like that Hi chris1111 Can you share your efi folder with us Edited July 17, 2022 by aufuk1 1 Link to comment Share on other sites More sharing options...
iCanaro Posted July 18, 2022 Share Posted July 18, 2022 On 7/14/2022 at 7:22 PM, Slice said: Clover WIKI OC configuration pdf 1 Link to comment Share on other sites More sharing options...
Shaneee Posted July 19, 2022 Share Posted July 19, 2022 Any one else had issues with Private Relay? Same issue on a clean install and when upgraded from Monterey where it worked without issue. This has happened on all the betas so far, 1 Link to comment Share on other sites More sharing options...
Shaneee Posted July 19, 2022 Share Posted July 19, 2022 The strange part is this is the updated system from Monterey where it worked just fine. 1 Link to comment Share on other sites More sharing options...
aufuk1 Posted July 19, 2022 Share Posted July 19, 2022 (edited) Hi, how can i fix this error Error: appleintellpssi2ccontroller ftimerservicematching timed out My screen is not touchscreen. I don't know how to remove everything related to VoodooI2C HP 840 G4, i7 7600U, HD Graphics 620, 16 gb ram Efi folder https://easyupload.io/7c78hj Edited July 19, 2022 by aufuk1 Link to comment Share on other sites More sharing options...
surenmunoo Posted July 19, 2022 Share Posted July 19, 2022 8 hours ago, Shaneee said: Any one else had issues with Private Relay? Same issue on a clean install and when upgraded from Monterey where it worked without issue. This has happened on all the betas so far, Mine works fine, Link to comment Share on other sites More sharing options...
miliuco Posted July 19, 2022 Share Posted July 19, 2022 @Shaneee It happens to me also. I think there is a system setting that prevents Private Relay to turn on. But I don't know what is causing this. 1 1 Link to comment Share on other sites More sharing options...
eSaF Posted July 19, 2022 Share Posted July 19, 2022 (edited) 34 minutes ago, miliuco said: @Shaneee It happens to me also. I think there is a system setting that prevents Private Relay to turn on. But I don't know what is causing this. I don't know if this has any effect or prevention of non working of Private Relay but I just check that setting on my machine and also found I could not activate it. What I did was insure it was activated on my iPhone and then got it to activate on the machine I don't know know why that should be, what would be the outcome if I didn't own or use an iPhone??!! Anyway it is now working I think as it is reported still in Beta stage. Edit: Ok Ive done some more digging and found despite my initial statement, it is not available on my machine as shown by the added attachments. Spoiler Edited July 19, 2022 by eSaF 5 Link to comment Share on other sites More sharing options...
PoMpIs Posted July 19, 2022 Share Posted July 19, 2022 (edited) @Shaneee @miliuco It works for me..... But it is not something that I do not care that I will not use I already take care of blocking content with a PC converted into a NAS ( UNRAID), with PiHole, and Nextcloud as my personal cloud Edited July 19, 2022 by PoMpIs 4 Link to comment Share on other sites More sharing options...
Slice Posted July 20, 2022 Share Posted July 20, 2022 On 7/18/2022 at 11:52 AM, iCanaro said: OC configuration pdf Sorry I not agree. EnableSafeModeSlide cause Mojave to panic. I had to disable this quirk and both system now works. ProtectMemoryRegions is safe quirk needed for those who uses CSM. 2 Link to comment Share on other sites More sharing options...
Irish_Man Posted July 20, 2022 Share Posted July 20, 2022 @Shaneee you using VPN or some kind of ad block? Link to comment Share on other sites More sharing options...
miliuco Posted July 20, 2022 Share Posted July 20, 2022 2 hours ago, Irish_Man said: @Shaneee you using VPN or some kind of ad block? I don’t have VPN or adblock. SIP and gatekeeper enabled. Even checked /etc/pf.conf file to see if there is a strange line that don't match the default macOS ones (read somewhere as related with Private Relay error). Same error as @Shaneee and @eSaF 1 Link to comment Share on other sites More sharing options...
eSaF Posted July 20, 2022 Share Posted July 20, 2022 13 minutes ago, miliuco said: I don’t have VPN or adblock. SIP and gatekeeper enabled. Even checked /etc/pf.conf file to see if there is a strange line that don't match the default macOS ones (read somewhere as related with Private Relay error). Same error as @Shaneee and @eSaF Yea I also went through those checks, still a no go for enabling Private Relay. 3 Link to comment Share on other sites More sharing options...
deeveedee Posted July 20, 2022 Share Posted July 20, 2022 (edited) On 7/19/2022 at 9:56 AM, aufuk1 said: Hi, how can i fix this error Error: appleintellpssi2ccontroller ftimerservicematching timed out My screen is not touchscreen. I don't know how to remove everything related to VoodooI2C HP 840 G4, i7 7600U, HD Graphics 620, 16 gb ram @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 Spoiler 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). Edited July 20, 2022 by deeveedee 2 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted July 20, 2022 Share Posted July 20, 2022 2 minutes ago, deeveedee said: How did you determine that your rig needs all of these kexts? 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 Link to comment Share on other sites More sharing options...
iCanaro Posted July 20, 2022 Share Posted July 20, 2022 7 hours ago, Slice said: Sorry I not agree. EnableSafeModeSlide cause Mojave to panic. I had to disable this quirk and both system now works. ProtectMemoryRegions is safe quirk needed for those who uses CSM. I agree with you, if your system works with a different setting from mine, I have no objection. With EnableSafeModeSlide enabled my mojave on Z370 starts and runs smoothly. I checked, my BIOS is set for UEFI boot, so CSM is disabled, consequently ProtectMemoryRegions is set to No as well 1 Link to comment Share on other sites More sharing options...
PoMpIs Posted July 20, 2022 Share Posted July 20, 2022 @miliuco @eSaF .... But this limit IP tracking is activated by default? ... I do a clean installation and I have this on ethernet: and in the Lenovo 520s the same... it limits the tracking by default ¿?¿? I had no idea about that option. 🤷♂️ Link to comment Share on other sites More sharing options...
aben Posted July 20, 2022 Share Posted July 20, 2022 No issues with Private Relay here on my Dell machine. Beta 3. 5 Link to comment Share on other sites More sharing options...
PoMpIs Posted July 20, 2022 Share Posted July 20, 2022 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 Link to comment Share on other sites More sharing options...
deeveedee Posted July 20, 2022 Share Posted July 20, 2022 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 1 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted July 20, 2022 Share Posted July 20, 2022 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. Link to comment Share on other sites More sharing options...
aufuk1 Posted July 20, 2022 Share Posted July 20, 2022 (edited) 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 Link to comment Share on other sites More sharing options...
aufuk1 Posted July 20, 2022 Share Posted July 20, 2022 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 Link to comment Share on other sites More sharing options...
Recommended Posts