Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Today
  3. So this product just blew my mind! I've never seen these before but i purchased one from https://www.monduo.co/ £660 including FedEx Shipping and glad i did, thought i'd post to see if anyone had seen them before. The color, resolution, brightness all matched across every display, you can't tell them apart.Brilliant it is to finally find something on the market that works! it has unique software that works in sync with your mac, no changing individual screen settings. so just pressing the brightness up and down will adjust it across every display instantly, and its shocking cheap! 🙂
  4. Intel Virtualization Technology MUST be enabled. It is VT-x not VT-d. Package C state limit I think should be disabled.
  5. Have you tried Resetting NVRAM? EDIT: If not that, could it be the OCLP-Version NVRAM entry in your OC config.plist? I don't remember whether I tried running without changing this, since I've changed the OCLP-Version entry when I started using OCLP 0.6.1.
  6. I used OCLP 0.6.1 to patch my Haswell computer that I am running as a Mac mini. Now, whenever I boot up, I am getting this message and would like to know what is causing it. Any suggestions for what I can do to make it stop. BTW, my EFI is set up for both Clover and OC and I use the boot selector that comes bundled with Clover to choose my boot loader. Typically, I use OC to boot and am using the most current version of both Clover and OC. I do not know what OCLP wants to change in my OC EFI. It is working fine now so I am reluctant to allow OCLP to make changes. What change does OCLP want to make?
  7. As a general rule, the changes that OCLP makes to NVRAM in OC need to be converted to boot args for Clover.
  8. Now everything works except the touchpad. The touchpad type I have is I2C HID and the brand does not appear in the device manager. Touchpad BIOS name: \_SB.PCI0.I2C0.TPD0 config.plist
  9. If you noticed that my USBPorts.kext/Contents/Info.plist specifies PortType where it should be specifying UsbConnector, and you noticed that I am specifying PortType = 2 where I should be specifying UsbConnector=255, you are right. I was playing with various USB port mappings and port type guesses in an attempt to solve non-working BlueTooth in Monterey and Ventura. I am continuing to experiment with USB port type specifications (none of which fix Bluetooth in Monterey and Ventura) and I do expect to post an updated EFI with a revised USBPorts.kext. What is interesting is that USB ports on this hack work fine despite what appears to be incorrect port type specification. EDIT: My current USBPorts.kext is attached. USBPorts.kext.zip
  10. So no freeze now??? Which method did you use to fix it?? Mostly IHD 4600 Desktop is working fine in macos monterey maybe it's your IHD 4400
  11. Need help with sleep and wake functionality. System is stable no issues, except sleep, manual sleep or auto sleep (system does go to sleep as per the power settings) But wakes to black screen. Attached is the complete EFI folder along with NVRAM folder. Have disabled: Enable Power Nap Wake for network access Tried to create NVRAM.plist but no luck, on the boot screen greeted with "OCVAR: Emulated NVRAM load failed - Not Found" 427714616_BootFolder.zip
  12. 1. Add -wegnoegpu boot arg. External graphics devices that are not supported in macOS must be disabled. 2. igfxmetal=1 is unnecessary, so remove it. Keep the -igfxblr and igfxonln=1 boot args. 3. Remove all frambuffer-conX connector patch properties. 4. In Kernel - Add, move the order of loading WhateverGreen.kext between Virtual SMC and AppleALC. 5. Remove all ACPI Rename patches related to Audio and USB. Not required for your laptop specification and some are automatically renamed by Lilu and Lilu Plugins. 6. If you are using USB Port Map Kext (e.g. USBMap.kext, USBPorts.kext, etc.), set the XhciPortLimit to False.
  13. Just to confirm. There's no support for "Automatic MDI/MDIX crossover at all speeds of operation" in this I219V driver? Therefore a crossover cable is required if I'd like to share the internet connection from a hackintosh?
  14. Use bios/uefi i full default, just enable VT-d and set ur xmp EFI.zip Remap USB https://www.olarila.com/topic/14220-hackintosh-usb-port-mapping-guide-2021-2022-2023/
  15. Yesterday
  16. Hey @Daniel Ribeiro here in the international section, please post only in English. 🙂 To post in Portuguese, there's a Português forum. But only for members. Thank you
  17. I just tested this hack's WebCam in Zoom when running Ventura 13.2 - It works! The Webcam on this hack does work in Ventura, it is the Photo Booth app that has the camera problem. For those who want to conduct Zoom meeting with their HackBookPro6,2 running MacOS Ventura, this hack works perfectly!
  18. @slice If I don't use oclp it stays on black screen after apple logo
  19. Fala mano, blz? Cara, entao, consegui uma config que ficou bem legal agora... tem rodado liso e consigo já trabalhar nela, vou trabalhar durante a semana e no FIM‑DE‑SEMANA pretendo refinar algumas coisas como boot e mapeamento USB! Algo que tem me intrigado é sobre o Wi-Fi e Blutetooth que uso uma plaquinha TP Link Archer TX50E V2 que engloba os dois, o bluetooth tem funcionado até que Ok já o Wi-Fi quando eu conecto qualquer rede ele simplesmente reboota meu sistema... sabe de alguma coisa??? ENGLISH Man, so, I got a config that looks nice now... it's been running smooth and I can already work on it, I'm going to work during the week and on the WEEKEND I intend to refine some things like the boot and USB mapping! Something that has intrigued me is about Wi-Fi and Bluetooth that I use a TP-Link Archer TX50E V2 plate that encompasses both, the Bluetooth has been working until Ok now the Wi-Fi is when I connect any network it reboots my system... Do you know something???
  20. When amfi is fully or partially disabled, dialogs for application accessibility permissions may be suppressed. For example, after disabling amfi using boot-arg amfi=0x80, when you run an app that requires Camera access, your app will be denied Camera access, because the Camera permission dialog never appears for you to approve Camera access. Here is a solution that worked for me.
  21. When using amfi_get_out_of_my_way=1 or amfi=0x80 boot-args to disable or partially disable amfi, accessibility permission dialogs (e.g., camera and microphone permission dialogs) are suppressed. When you run an app that requires these permissions, the app will be repeatedly denied these accessibility permissions without allowing you to approve them. Here is a solution that worked for me. Download tccplus here Give Execute permissions to tccplus (chmod +x tccplus) Identify the fully qualified name of the app that needs accessibility approvals (e.g., for Microsoft Remote Desktop, the app name is /Applications/'Microsoft Remote Desktop.app' Use the following command to obtain the Bundle Identifier for your app identified in Step 3: "grep 'BundleIdent' -A 1 /Applications/<APPLICATION NAME>/Contents/Info.plist" (without double quotes) (e.g., for Remote Desktop, run the terminal command "grep 'BundleIdent' -A 1 /Applications/'Microsoft Remote Desktop.app'/Contents/Info.plist" (without the double quotes) ) Using the Bundle Identifier obtained in Step 4, run the terminal command "tccplus add <ACCESSIBILITY> <Bundle Identifier>" (without double quotes). To grant Camera and Microphone permissions to Remote Desktop, execute the following: tccplus add Camera com.microsoft.rdc.macos tccplus add Microphone com.microsoft.rdc.macos For each permission granted, you will see a response similar to the following: Successfully added Camera approval status for com.microsoft.rdc.macos Successfully added Microphone approval status for com.microsoft.rdc.macos Now when you run your application, you won't be warned about Accessibility permissions. EDIT: When I ran Zoom to prepare for a Zoom call, Zoom would not access my camera or microphone (and I was not prompted to allow Camera and Microphone permissions). I executed the following terminal commands to grant Camera and Microphone access to Zoom: tccplus add Camera us.zoom.xos tccplus add Microphone us.zoom.xos After executing these commands, Camera and Microphone worked as expected in Zoom (running in Big Sur). EDIT2: If after granting permissions, you decide to deny accessibility permissions, change the accessibility permissions in System Preferences > Security and Privacy.
  22. If the trackpad works, then it doesn't need patches. OpenCore is complaining because RMISMBus needs both VoodooRMI and VoodooSMBus to exist. If your using the trackpad in I2C mode, just disable RMISMBus in your config.plist. RMISMBus and RMII2C are how VoodooRMI attaches to VoodooSMBus and VoodooI2C respectively, so you only need one enabled anyways. Edit: You can probably disable VoodooPS2Mouse and VoodooPS2Trackpad as well. I know the VRMI docs say to leave those enabled, but those are mostly for SMBus devices.
  23. Hi, yes - SATA = AHCI mode - Secure Boot = Disable if need - CSM = Disable with AMD cards tried varies variants
  1. Load more activity
  • Create New...