Administrators Hervé Posted July 31, 2017 Administrators Share Posted July 31, 2017 No, the FakeSMC patch of the D630 pack does include the PCI id of the GPU. You just missed it. NVS 135m carries device id 042b, so it's clearly different from the NVS 160M which you state to carry id 06eb. Read the thread with more attention... Link to comment Share on other sites More sharing options...
griftopia Posted August 1, 2017 Author Share Posted August 1, 2017 Sorry I see that now. And I changed it. However, when I did I got a kernel dump on startup. Attaching my info.plist here. I found the GPUId in only one place. Info.plist.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted August 1, 2017 Administrators Share Posted August 1, 2017 Seems Ok to me. Make sure to repair permissions and rebuilt your cache after you modify the FakeSMC kext. Link to comment Share on other sites More sharing options...
griftopia Posted August 5, 2017 Author Share Posted August 5, 2017 Okay so I was still loading from E/E with kernel booster kexts = yes, until I got things working. For some reason correcting the patch to match GPU Id in E/E kernel dumps. So now I turned the kernel flag = no, and then moved all my kexts to S/L/E including the patch fix for GPU Id. This time my machine booted fine, but not sure it was faster. Regardless, at least it booted. The problem is it has not fixed my Chrome issue. What else can I try? PS : Also I left my laptop alone for couple of hours, expecting it to be sleeping, but when I come back there was some kernel panic crash. When I rebooted, my CPU and GPU temperatures were much higher. I'm afraid I might have made things worse with the FakeSMC patch. Also my screen randomly blanks out and then comes back... Link to comment Share on other sites More sharing options...
Administrators Hervé Posted August 5, 2017 Administrators Share Posted August 5, 2017 Revert to your original settings then. Link to comment Share on other sites More sharing options...
griftopia Posted August 5, 2017 Author Share Posted August 5, 2017 I posted this in the e6500 forum. Could my problem be I haven't done following yet? sudo pmset hibernatemode 0sudo pmset hibernatefile /dev/nullsudo rm -f /var/vm/sleepimage Not sure if they go hand in hand. Of course, my Google Chrome problem still persists, so dunno what to do about that Finally, when you say revert back, it would go to the D630 GPU Id. Clearly I should completely remove the patch right? Couldn't possible help using D630 patch for e6500. Link to comment Share on other sites More sharing options...
griftopia Posted August 5, 2017 Author Share Posted August 5, 2017 I solved my problem. Hope it helps someone. The problem really is searching for problem with Google, With google, with right term for Google go to chrome://flags Disable "Accelerated 2D canvas". Once you get there, then you can set hardware acceleration off. then renable 2d canvas. In settings now some stuff still has artifacts, but you can get by. Phew! Now I actually am using Google Canary, because I thought maybe they fixed some issues, but it should work for google as well. Link to comment Share on other sites More sharing options...
griftopia Posted September 5, 2017 Author Share Posted September 5, 2017 Just wanted to provide an update. The chrome issue occurs only on NVidia GPUs not on Intel GPUs. Just in case anyone has reached the same conclusion and knows a permanent fix for it. Google Chrome will not always retain the setting to disable 2d acceleration. So it's a pain some times. Link to comment Share on other sites More sharing options...
Recommended Posts