Jump to content

ccozmo

Members
  • Content count

    78
  • Joined

  • Last visited

About ccozmo

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

964 profile views
  1. ccozmo

    Intel Power Gadget 3.5.0

    What about auto sleep when idle ? Mine will sleep if I select sleep, but with IPG running it does not auto sleep. Can you check 'pmset -g'and 'pmset -g assertions' on yours ?
  2. ccozmo

    Intel Power Gadget 3.5.0

    I notice with 3.5.5 it stops the system from sleeping when idle. pmset -g assertions shows the following even with logging turned off on Power Gadget pmset -g assertions 2018-11-10 02:23:54 +0800 Assertion status system-wide: BackgroundTask 0 ApplePushServiceTask 0 UserIsActive 1 PreventUserIdleDisplaySleep 0 PreventSystemSleep 0 ExternalMedia 0 PreventUserIdleSystemSleep 1 NetworkClientActive 0 Listed by owning process: pid 58992(Intel(R) Power Gadget): [0x00009aef0001897b] 03:20:30 PreventUserIdleSystemSleep named: "logging system metrics" Anyone else have this issue or know any work arounds ? I tried 3.5.2, which is the latest version that doesn't cause this problem for me
  3. Still having this issue, reporting files are as per post 5. Can anyone help me to find a way to fix wake / sleep with the NVIDIA in Slot1 (disabled on Mojave) and the Vega in Slot6 ?
  4. Updated above post with correct files, any assistance really appreciated. This wake from sleep not working is really annoying
  5. Thanks, I tried the files you attached but the WAK doesn't comply and the path seems wrong for my NVIDIA which is _SB.PC02.BR2A.SL05 I redid the files from the original link, not sure if they are correct (attached) I am still getting the same issue, wakes and hangs, and when reboot says kernel panic. Attached are the new report logs. Any help really appreciated Thanks Edit: Realised the WAK SSDT was in dsl, not ami. Have retested and still the same. New files uploaded instead debug_30601.zip SSDT_PTSWAK.aml SSDT-nvda-off.aml
  6. Hi @styrian, Thank you for the reply ! Yes that sounds logical that the off method is missing from the SSDT for wake. Sorry I'm not that expert on how to apply to dsl to the SSDT I have. Is there any chance you could help ? The current SSDT is attached. Really appreciate your help SSDT-X299-Nvidia-Disable.aml
  7. I'm having a issues with wake from sleep from Mojave. When I press the keyboard or mouse to wake, the keyboard lights up and fans start and then keyboard lights turn off - screens remain off the whole time. I can't access the system remotely either. The only way is to hard reboot & then on start it tells me it restarted due to kernel panic.I recently added a Vega 56 graphics card to slot 6, and have my GTX1080ti in slot 1. I have upgraded to Mojave and applied the spoof SSDT to disable the NVIDIA from the following thread:https://www.tonymacx86.com/threads/...-only-ran-for-0-seconds-with-dual-gpu.233092/Web drivers are not installed & the NVIDA doesn't show up under graphics cards in system report, I only have the Vega listed and I can see the NIVIDA shown only as #display in PCI devices with no driver loaded.I've tried whatevergreen, but causes issues with rotation settings on 2nd monitor & doesn't fix the problem. Tried different darkwake settings, and quite a few other things with no luck.Would really appreciate any help of guidance on this. Everything else is working fine, except wake.Attached are the problem reporting files Report Files.zip
  8. ccozmo

    Winbond/Nuvoton monitor

    Hi Slice, Is there anything you would like me to test ? I am going on holidays for 3 weeks tomorrow night, so won't be available to test after that Thanks
  9. ccozmo

    Winbond/Nuvoton monitor

    This is the HW sensor output from your bundle and then the one from the other kext I am using. Yours is missing quite a few fields and also the Motherboard, ambient temps & fan speed
  10. ccozmo

    Winbond/Nuvoton monitor

    sudo dmesg
  11. ccozmo

    Winbond/Nuvoton monitor

    Sure - post me the debug ver & instructions on what you want me to do, and I'll test it now Thanks
  12. ccozmo

    Winbond/Nuvoton monitor

    Post Preview Slice, on 07 Dec 2017 - 02:41 AM, said: I tested with this bundle and it's the same, very limited info for motherboard sensors. Syslogs only show: 2017-12-11 13:35:25.406863+0800 localhost kernel[0]: (kernel) W836x: found NCT6796D 2017-12-11 13:35:25.406875+0800 localhost kernel[0]: (kernel) W836x: mother vendor=ASUSTeK COMPUTER INC. product=PRIME X299-DELUXE 2017-12-11 13:35:25.406880+0800 localhost kernel[0]: (kernel) W836x: [Warning] set default configuration And I can confirm the kext is loaded: kextstat | grep W836x 43 0 0xffffff7f8342c000 0x4000 0x4000 org.mozodojo.W836x (1.2.1) 8343C348-CC9F-3303-B836-9999A27725C5 <16 7 5 4 3> I am using the kexts from @interferenc as there are more stats being displayed. It is not built on the datasheet also though, but I have sent it to him. https://github.com/interferenc/HWSensors/tree/master/SuperIOSensors https://www.tonymacx...84#post-1636834 Any ideas why your W836x is not showing sensors for the motherboard ?
  13. ccozmo

    Winbond/Nuvoton monitor

    Still don't see many motherboard values
  14. ccozmo

    Winbond/Nuvoton monitor

    I see the following: 2017-11-30 15:30:33.098694+0800 localhost kernel[0]: (kernel) W836x: found NCT6796D 2017-11-30 15:30:33.098715+0800 localhost kernel[0]: (kernel) W836x: mother vendor=ASUSTeK COMPUTER INC. product=PRIME X299-DELUXE 2017-11-30 15:30:33.098723+0800 localhost kernel[0]: (kernel) W836x: [Warning] set default configuration
  15. ccozmo

    Winbond/Nuvoton monitor

    Hi Slice, That doesn't seem to work, although it is loaded kextstat -l | grep -v "com.apple" 16 3 0xffffff7f831e4000 0xb000 0xb000 org.netkas.FakeSMC (3.5.0) 8F36EF78-E2BD-3B4F-AB1A-8545F12F247B <11 7 5 4 3> 17 0 0xffffff7f831ef000 0x17000 0x17000 org.kozlek.GeforceSensor (1.2.2) 97543082-DFD7-3996-BD45-8BDB79AFA34A <16 12 7 5 4 3> 37 0 0xffffff7f83216000 0x4000 0x4000 org.mozodojo.W836x (1.2.1) A487ECF4-B7A1-3A4C-B1C9-9D5563904275 <16 7 5 4 3> 38 0 0xffffff7f8321b000 0x6000 0x6000 org.slice.IntelCPUMonitor (1.2.2) D7B65D32-2C70-3C44-87C8-104280B1E681 <16 7 5 4 3> 39 1 0xffffff7f83222000 0x15000 0x15000 as.vit9696.Lilu (1.2.0) 3F51CD32-9E7E-35B9-9189-8CEC6588DA05 <7 5 4 3 2 1> 40 0 0xffffff7f83237000 0x6000 0x6000 as.lvs1974.NvidiaGraphicsFixup (1.2.1) B191B66C-7FBD-3ADF-BE62-8F39E06A9583 <39 7 5 4 3 2 1> 46 0 0xffffff7f8323d000 0x2000 0x2000 org.voodoo.driver.VoodooTSCSync (1.1) 0547D0AD-C9FE-3D5A-9CD7-6B90E6BC0335 <7 4 3> 64 0 0xffffff7f83241000 0x14000 0x14000 com.insanelymac.IntelMausiEthernet (2.3.0) F1A5F7D5-D5E2-32F2-A8D6-7888AF6CE27B <63 12 5 4 3 1> 67 0 0xffffff7f83262000 0x22000 0x22000 org.voodoo.driver.VoodooHDA (2.9.0d10) no UUID <66 12 7 5 4 3> 70 0 0xffffff7f83288000 0x1a000 0x1a000 com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <63 12 5 4 3 1> 88 0 0xffffff7f80e8e000 0x1d000 0x1d000 com.razer.common.razerhid (21.15) 70F0750D-8787-3DED-BB02-B2E1A0C12CAB <87 85 57 51 5 4 3> 102 0 0xffffff7f80f21000 0x3000 0x3000 com.nvidia.NVDAStartupWeb (10.2.7) 1F9F1C91-73DC-3C76-AEB8-96D15E24D548 <12 4 3> 110 0 0xffffff7f81a97000 0x4000 0x4000 com.intel.driver.EnergyDriver (2.0) 8937025C-61CA-370A-A1D1-553F373E68C7 <7 5 4 3> 129 2 0xffffff7f80f95000 0x642000 0x642000 com.nvidia.web.NVDAResmanWeb (10.2.7) AC014FD6-0B13-3034-B6CF-9A9BAC54B8B7 <116 112 95 12 7 5 4 3 1> 131 0 0xffffff7f81996000 0xa6000 0xa6000 com.nvidia.web.GeForceWeb (10.2.7) 1D520F73-3D08-31D9-9D2E-4FF6F2E7DFFE <130 129 116 95 12 7 5 4 3 1> 132 0 0xffffff7f815d7000 0x1a7000 0x1a7000 com.nvidia.web.NVDAGP100HalWeb (10.2.7) DD0C2BBD-3256-3D2D-B131-B9663E11ABFB <129 12 4 3> 140 0 0xffffff7f80a22000 0x3f000 0x3f000 com.paragon-software.filesystems.ntfs (26.1.15) E90280EB-E0EC-37BF-BB5E-0AE9592257AF <7 5 4 1> 142 0 0xffffff7f81a9e000 0x2000 0x2000 com.nvidia.CUDA (1.1.0) 4329B052-6C8A-3900-8E83-744487AEDEF1 <4 1>
×