Other Optimizations possible? Razer Blade 15

[NONITS]

I don't really have an issue but since I have basic experience in hackintoshing I wanted to submit my PR files for the review of more experienced group members here.

I followed @vettz500 awesome guide along with some inputs from @stonevil's posts to get my blade to where it is now which is really I think as perfect as it can get.

I just wanted to check if I have any conflicts or anything else I can optimize here? I'm particularly interested in further improving battery life. Right now I get a little over 6 hours thanks to voltage shift and having my CPU friend configured to maximum battery life. Im just wondering if I can push for more hours? maybe hit a 7 - 8 hour sweet spot so I don't need to lug the ginormous power adapter around.

Any suggestion or opinion is most welcome - I'm looking at this as an opportunity to learn as well.

 

[Feartech]

I don't really have an issue but since I have basic experience in hackintoshing I wanted to submit my PR files for the review of more experienced group members here.

I followed @vettz500 awesome guide along with some inputs from @stonevil's posts to get my blade to where it is now which is really I think as perfect as it can get.

I just wanted to check if I have any conflicts or anything else I can optimize here? I'm particularly interested in further improving battery life. Right now I get a little over 6 hours thanks to voltage shift and having my CPU friend configured to maximum battery life. Im just wondering if I can push for more hours? maybe hit a 7 - 8 hour sweet spot so I don't need to lug the ginormous power adapter around.

Any suggestion or opinion is most welcome - I'm looking at this as an opportunity to learn as well.

you seem to have a kext issue:

kxld[as.vit9696.VirtualSMC]: The following symbols are unresolved for this kext:
kxld[as.vit9696.VirtualSMC]:     KernelPatcher::routeMultipleLong(unsigned long, KernelPatcher::RouteRequest*, unsigned long, unsigned long long, unsigned long, bool, bool)
Link failed (error code 5).
Prelink failed for as.vit9696.VirtualSMC; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for ru.usrsse2.SMCLightSensor; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for as.vit9696.SMCProcessor; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for ru.usrsse2.SMCBatteryManager; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for ru.joedm.SMCSuperIO; aborting prelink.
Failed to generate prelinked kernel.
Child process /usr/sbin/kextcache[840] exited with status 71.
Error 107 rebuilding /System/Library/PrelinkedKernels/prelinkedkernel

check your kextcache output

debug=0x100 boot argument should be removed
nvidiaweb=true argument is not applicable and should be removed
nvda_drv=1 should also be removed as there are no web drivers available on Mojave

you have 2 PNLF aml's in patched, you should only need 1

you could also look into disabling your nvidia card:

[Guide] Disabling discrete graphics in dual-GPU laptops

Overview The purpose of this guide is to show you how to disable the discrete graphics device with DSDT/SSDT edits in "switched" dual-GPU laptops (eg. Intel+Nvidia[Optimus] and Intel+Radeon). Because only the Intel device can be used in these laptops, the discrete device is generally left...

www.tonymacx86.com

 

[NONITS]

you seem to have a kext issue:

kxld[as.vit9696.VirtualSMC]: The following symbols are unresolved for this kext:
kxld[as.vit9696.VirtualSMC]:     KernelPatcher::routeMultipleLong(unsigned long, KernelPatcher::RouteRequest*, unsigned long, unsigned long long, unsigned long, bool, bool)
Link failed (error code 5).
Prelink failed for as.vit9696.VirtualSMC; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for ru.usrsse2.SMCLightSensor; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for as.vit9696.SMCProcessor; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for ru.usrsse2.SMCBatteryManager; omitting from prelinked kernel.
Can't use /Library/Extensions/VirtualSMC.kext - not linked.
Prelink failed for ru.joedm.SMCSuperIO; aborting prelink.
Failed to generate prelinked kernel.
Child process /usr/sbin/kextcache[840] exited with status 71.
Error 107 rebuilding /System/Library/PrelinkedKernels/prelinkedkernel

check your kextcache output

debug=0x100 boot argument should be removewas for hogh se
nvidiaweb=true argument is not applicable and should be removed
nvda_drv=1 should also be removed as there are no web drivers available on Mojave

you have 2 PNLF aml's in patched, you should only need 1

you could also look into disabling your nvidia card:

[Guide] Disabling discrete graphics in dual-GPU laptops

Overview The purpose of this guide is to show you how to disable the discrete graphics device with DSDT/SSDT edits in "switched" dual-GPU laptops (eg. Intel+Nvidia[Optimus] and Intel+Radeon). Because only the Intel device can be used in these laptops, the discrete device is generally left...

www.tonymacx86.com

Thanks @Feartech for the quick response! I'll check the PNLF files and remove the boot args (the guide I was following was for high sierra and it had the nvidia card working through hdmi).

I'm pretty sure the nvidia card is disabled through a patched SSDT though.

As for the prelinked errors I have not encountered those before. Can you direct me to resources I can use to fix it?

 

[FreeJHack]

Spoiler: kernel_log

2019-09-18 23:37:23.580563+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.580564+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.580567+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.GFX0]
2019-09-18 23:37:23.580567+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.GFX0]
2019-09-18 23:37:23.719761+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719762+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719768+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.RP05.PXSX]
2019-09-18 23:37:23.719769+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.RP05.PXSX]
2019-09-18 23:37:23.719787+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719787+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719788+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed
2019-09-18 23:37:23.719789+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed
2019-09-18 23:37:23.719791+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_SB.PCI0.RP04.PXSX] (Node ffffff8031632b70)
2019-09-18 23:37:23.719791+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_SB.PCI0.RP04.PXSX] (Node ffffff8031632b70)

...even ACPI errors...
Look at your kernel_log file.

 

[NONITS]

Spoiler: kernel_log

2019-09-18 23:37:23.580563+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.580564+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.580567+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.GFX0]
2019-09-18 23:37:23.580567+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.GFX0]
2019-09-18 23:37:23.719761+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719762+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719768+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.RP05.PXSX]
2019-09-18 23:37:23.719769+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_SB_.PCI0.RP05.PXSX]
2019-09-18 23:37:23.719787+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719787+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-09-18 23:37:23.719788+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed
2019-09-18 23:37:23.719789+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed
2019-09-18 23:37:23.719791+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_SB.PCI0.RP04.PXSX] (Node ffffff8031632b70)
2019-09-18 23:37:23.719791+0800 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_SB.PCI0.RP04.PXSX] (Node ffffff8031632b70)

...even ACPI errors...
Look at your kernel_log file.

Thanks! I'll look for which SSDT those devices are in although I'm doubtful I can fix them. For ACPI patching I only know how to fix it when it doesnt compile - these errors are new to me

 

[NONITS]

@Feartech I found a post about the prelinked error with virtual SMC. I just needed to update Lilu. I removed the Nvidia boot args and the extra PNLF SSDT.

It looks like I'm getting ACPI errors like @freejack pointed out but I have no idea how I can address those