Jump to content


  • Content Count

  • Joined

  • Last visited

About PPC970MP

  • Rank
    InsanelyMac Protégé
  1. The WebDrivers are pinned to a single macOS build number. Until there is an official update you can replace Info.plist below this path with the attached version: /System/Library/Extensions/NVDAStartupWeb.kext/Contents This invalidates the signature of the WebDriver but will work as long as loading unsigned kexts is allowed. Before booting with the patched WebDriver rebuilding the kernel cache is required. The WebDrivers should be functional again now. NVDAStartupWeb_2017_004_plist.zip
  2. It seems there is no WebDriver update for 10.11.6 with security patch 2017-004 available yet. For those of you who would like to patch NVDAStartupWeb.kext for the time being the new build number is: 15G17023
  3. Hello fellow Sierra users, maybe someone could help me with a post-installation defect. The problem occurred immediately after upgrading an existing build form ElCap 10.11.6 to Sierra 10.12.6. Overall the installation went all fine, no changes to Clover (4244) config, DSDT or set of additional kexts were required. Except updating to the matching NVDA WebDriver kit and repatching AppleHDA of course. NvidiaGraphicsFixup is not used, also no GPU injection from clover. Now if the DP connected monitor ever enters sleep mode it will not wake up any more. For a few seconds it will leave power saving mode and then return to it with the display staying blank all the time. As in El Capitan system sleep is completely disabled so this is not related to the whole system waking up, just the display. The symptom did not occur a single time while running macOS 10.11. So far I could not find a solution for this problem. However there seems to be a history of similar issues affecting Maxwell cards and DP connected monitors. Any suggestions welcome. Would a switch to a Pascal based NVIDIA GPU probably help to resolve the issue?
  4. PPC970MP


    Hello, I would like to ask if there are any ideas regarding the following (Gigabyte specific) issue: FakeSMC 6.25-12-g2303970.1438 with GPU, CPU and LPC PlugIns and GA-Z97X-Gaming GT board. This Gigabyte board has 2 LPC chips (detected on Windows using HWINFO64 or SIV64): ITE IT8620E-04 Gigabyte Z97X-Gaming GT BIOS F7 Chip ID 86200400 (4) LPC 002E Port 0000 0A35 0A36 and ITE IT8790E-DX Gigabyte Z97X-Gaming GT BIOS F7 Chip ID 87900300 (4) LPC 004E Port 0000 0A45 0A46 The IT8620E is found and temperature readings appear all right. Problem is that all my 3 fans (AIO water pump, front and rear/heat exchanger fans) are attached to the IT8790E headers. So obviously there aren't any fan speed sensors visible with this setup as detection stops after the IT8620E chip is discovered. Moving over to the IT8620E headers is not an option because for reasons unknown this causes random speed jumps and instable fan control. Only the IT8790E fan headers work normally, tried all BIOS settings and also not OS dependent as fans behave not differently when running Windows. I've attempted to add the definitions for the IT8790E controller as another generic/compatible IT87xx chip. Now I'm not a developer but as far as I understood what is going on in SuperIODevice.cpp the case of having more than one IT87xx is not covered. However it would be fine to just attach to the second IT8790E and ignore the primary IT8620E. Would there be a way to enable this kind of 'chip select' in LPCSensors plugin? Thanks.
  5. PPC970MP

    [GUIDE] USB Fix El Capitan 10.11

    Hi, I wonder if anybody tried the same thing or maybe can provide a hint: I've made several attempts to disable USB wake functionality in my Z97 DSDT by modifying related _DSW and _PRW methods. But to no avail as the machine still wakes on any keypress regardless of DSDT changes. As I'm also using USBInjectAll to get USB working in 10.11- could this be the reason for DSDT patches not having any observable effect? In addition I'd like to ask if anyone ran into a similar issue: Sleep/Wake works fine but after the first wake one CPU core is permanently hogged by interrupts generated somewhere in the USB stack. This is clearly USB related and 100% reproducible but so far I was not able to track down the root cause any further.
  6. Wonder if someone has found or needed a solution to a similar problem: I'm using an additional eSATA adapter plugged into a x1 PCIe slot. These ASM106x based controllers seem to work quite well without need for extra drivers. Only issue is that the ports are dead after sleep and require a reboot to work again. Searching for a solution I found some related DSDT code/method fragments which might fix this. However this card is nowhere to be found in my DSDT (at least I could not locate it). It is easy to spot in IOReg though. Closest DSDT device is a PXSX node sitting above the PCI bridge where the adapter is plugged in. Several attempts to add the adapter below the PXSX node failed, at best the card was shown as a kind of dummy device - in addition to the real one - in IOReg and apparently without function. What would be the right approach to define extra PCI adapters in DSDT?