Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
Sign in to follow this  
Ciro82

Spleep Enabler - DFI LanParty DK P45T2RS

12 posts in this topic

Recommended Posts

Come da titolo, funziona tutto tranne lo sleep enabler.

Avete qualche idea? 

Grazie in anticipo :)

 

EDIT: aggiungo, per quanto riguarda invece voodoomonitor, esiste una versione funzionante per 10.8.4? 

Share this post


Link to post
Share on other sites
Advertisement

Admin e Moderatori, chiudete pure.... vedo che nessuno è in grado di darmi una mano... GRAZIE

Mi dispiace, ma non conosco la tua scheda; immagino tu abbia provato tutti gli sleepenablers presenti in rete (e forse anche quello che metto in allegato) senza successo.

Se non funziona penso che l'unica cosa da provare sia estrarre ed editare il DSDT, ma il risultato non è assicurato

 

PS. Admin e moderatori NON sono al servizio di ogni richiesta e NON hanno tutte le risposte ad ogni singolo problema; ognuno decide in base alle proprie conoscenze e capacità se intervenire in un topic anche in base alle possibilità di successo in tempi ragionevoli.

SleepEnablerNG.kext.zip

Share this post


Link to post
Share on other sites

 @carbo178 intanto ti ringrazio per la risposta, il mio era un invito a chiudere il post, non volevo assolutamente che Admin o Mod mi rispondessero in merito al problema.

P.S. provato il kext e non va ;)

Share this post


Link to post
Share on other sites

Potremmo provare col dsdt ma non ti assicuro nulla; estrailo con questo codice da terminale poi comprimilo ed allegalo

 

perl -e 'open(CMD, "ioreg -lw0 \| grep DSDT|") or die; while()

{ chomp; if($_ =~ /\"DSDT\.?\d?\"=]*)>/) { $buff = $1; open(PIP,

"|xxd -r -p > ~/Desktop/dsdt.aml") or die; print PIP "$1"; } }'

Share this post


Link to post
Share on other sites

Carbo178 io ho già il DSDT editato da me, non ho nessun kext aggiuntivo installato per le varie periferiche, è tutto funzionante da DSDT. 
Se vuoi dagli un'occhiata, te lo allego  ;)

dsdt.aml.zip

Share this post


Link to post
Share on other sites

-Delirio- ti ringrazio molto, ma purtroppo mi da KP CPU2... ci rinuncio, non è poi così fondamentale lo STOP.

Mentre per quanto riguarda voodoomonitor ho risolto usando la versione per Lion.

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoticons maximum are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • AFAIK, the THB_C header on the motherboard has nothing to do with USB. It's a GPIO, though its use is undocumented.   On Gigabyte and ASRock at least, if you do not connect the THB header, then the TB card won't activate at all, and the BIOS will not show a Thunderbolt entry...   I'm rather amazed that it would work for you in macOS, I'm 99.99% sure your TB is now broken in windows however (and the TB card won't even appear)...   I'm on a different problem now, since I added a 2nd nvidia 1080Ti, just having the TB SSDT causes a kernel panic at boot
    • Why is it im getting Kermel panic if i use Clover's ACPI>DSDT>Fixes>FakeLPC
    • Allan are you still there
    • SUCCESS!!! Finally all my THUNDERBOLT devices are hotpluggable!!   The solution is unbelievable, seems to work on all chipsets without using SSDT, and shifts the focus on the cause of all problems Thunderbolt: the cable THB_C!! Already in my previous post I noticed strange behavior by inserting the _DSM method in DSB2: PCIHotplugcapable Zero.
      Since then I've been trying to figure out how the XHC controller affected the Thunderbolt hotplug, until Crismac2013 suggested I disconnect the THB_C cable from the motherboard.
      Once disconnected, it was enough to add as an arbitrary inject my first Thunderbolt address (PXSX): <dict> <key>Comment</key> <string>PCI THUNDERBOLT 15d3 first entry</string> <key>CustomProperties</key> <array> <dict> <key>Disabled</key> <false/> <key>Key</key> <string>PCI-Thunderbolt</string> <key>Value</key> <integer>1</integer> </dict> <dict> <key>Disabled</key> <false/> <key>Key</key> <string>IOName</string> <key>Value</key> <string>pci-bridge</string> </dict> </array> <key>PciAddr</key> <string>01:00.00</string> </dict> and it works!! Now I have also added my last SSDT to get PCI information on System info.
      I suspect, however, that in this way the USB-C functionality will be lost, you should do a test!
      In any case this is a huge step forward and makes it obvious that we need to work on XHCs controller to solve the problems with the hotplug with THB_C cable connected.  
    • Normal, rotational hard drives doesn't have attributes for life... (not even all ssds have it).


×