Jump to content
emilevirus

HP 17-by0062st won't shutdown properly

30 posts in this topic

Recommended Posts

 

When I turn off MacOS, my laptop is left on with the HDD LED on. I have patched USB ports and they work fine. Even sleep works fine. I'm unsure if I forgot to patch something. CPU power management seems to work. Not quite sure what's causing it. I've tried FixShutdown on Clover, but it didn't work.
Thanks

Specs:

HP 17-by0062st

i5-8250U 

UHD 820

8 GB RAM

Share this post


Link to post
Share on other sites
Advertisement

Not sure if that's related, but I'm getting kernel panic after a few hours.

Spoiler

Anonymous UUID:       0F64914B-39CB-A307-3652-FEE8E6EB184A

Fri Jan 11 08:37:58 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f9943b172): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x37 VID/DID=0x576210ec
. FW Revision=V9001b19\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.230.1/IONVMeController.cpp:5327
Backtrace (CPU 0), Frame : Return Address
0xffffff9135baba10 : 0xffffff80169aeafd 
0xffffff9135baba60 : 0xffffff8016ae85a3 
0xffffff9135babaa0 : 0xffffff8016ad9fca 
0xffffff9135babb10 : 0xffffff801695bca0 
0xffffff9135babb30 : 0xffffff80169ae517 
0xffffff9135babc50 : 0xffffff80169ae363 
0xffffff9135babcc0 : 0xffffff7f9943b172 
0xffffff9135babe20 : 0xffffff801705dd87 
0xffffff9135babe90 : 0xffffff801705dca9 
0xffffff9135babec0 : 0xffffff80169eaf65 
0xffffff9135babf40 : 0xffffff80169eab15 
0xffffff9135babfa0 : 0xffffff801695b0ce 
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[E3F646E0-5B0C-3ABC-88D1-728309F221C8]@0xffffff7f99426000->0xffffff7f99465fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A69BF990-ABB3-3731-A7A2-9C1FB76BCF6F]@0xffffff7f97b3e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[7EA30FDD-A2FB-390F-99DD-42BC19691BB4]@0xffffff7f97295000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[E68F9756-227E-3378-8E22-F37409594A7F]@0xffffff7f97c77000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[7D6A3E9B-D1CD-3F8B-9800-C4B943806679]@0xffffff7f97974000
            dependency: com.apple.iokit.IOReportFamily(47)[75A625B5-0DEB-343A-A723-9D72533F098C]@0xffffff7f973db000

BSD process name corresponding to current thread: kernel_task
Boot args: lilucpu=8 

Mac OS version:
18C54

Kernel version:
Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64
Kernel UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9
Kernel slide:     0x0000000016600000
Kernel text base: 0xffffff8016800000
__HIB  text base: 0xffffff8016700000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 5142554559841
last loaded kext at 249129503850: com.apple.filesystems.msdosfs    1.10 (addr 0xffffff7f999e2000, size 69632)
last unloaded kext at 127097894849: com.apple.driver.AppleIntelLpssGspi    3.0.60 (addr 0xffffff7f9908b000, size 45056)
loaded kexts:
(none)

EOF
Model: MacBookPro14,1, BootROM 184.0.0.0.0, 4 processors, Intel Core i5, 1.80 GHz, 8 GB, SMC 2.43f6
Graphics: Intel UHD Graphics 620, Intel UHD Graphics 620, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR4, 2400 MHz, Ramaxel Technology, RMSA3260NA78HAF-2400
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: HGST HTS541010B7E610, 1 TB
Serial ATA Device: hp       DVDRW GUE1N
USB Device: USB 3.0 Bus
USB Device: Bluetooth Radio
USB Device: HP TrueVision HD Camera
Thunderbolt Bus: 
 

 

Share this post


Link to post
Share on other sites

I had this same problem when I first purchased my current laptop.  I believe the problem I had was that I had used a tutorial I found on this forum and, while it worked great to get macOS installed and running, it had extra kexts that my laptop didn't need and they screwed some things up, like shutdown.  As I recall, it was the IntelGraphicsDVMTFixup.kext that was the culprit for me.  I believe its capabilities are now a part of Whatevergreen.kext.  I use that kext without any problem but hopefully, this will give you some ideas as to your problem.

Share this post


Link to post
Share on other sites
5 hours ago, mnfesq said:

I had this same problem when I first purchased my current laptop.  I believe the problem I had was that I had used a tutorial I found on this forum and, while it worked great to get macOS installed and running, it had extra kexts that my laptop didn't need and they screwed some things up, like shutdown.  As I recall, it was the IntelGraphicsDVMTFixup.kext that was the culprit for me.  I believe its capabilities are now a part of Whatevergreen.kext.  I use that kext without any problem but hopefully, this will give you some ideas as to your problem.

Did you apply any DSDT patch? Your laptop seems very similar to mine.

Share this post


Link to post
Share on other sites
1 hour ago, emilevirus said:

Did you apply any DSDT patch? Your laptop seems very similar to mine.

 

Yes, but none of the patches were related to the shutdown issue.  I renamed devices, added a PNLF device, shut off my DGPU, patched my battery settings and set the brightness keys.

 

Use the RunMe app and post the results here.

 

RunMe.app.zip

 

Edited by mnfesq

Share this post


Link to post
Share on other sites

Everything worked out of the box on mine, even the battery. And I'm only using essential kexts, AppleALC, SmartTouchpad, RTL8111, Whatevergreen & FakeSMC. I don't really see what could cause this...

Share this post


Link to post
Share on other sites
Just now, emilevirus said:

Everything worked out of the box on mine, even the battery. And I'm only using essential kexts, AppleALC, SmartTouchpad, RTL8111, Whatevergreen & FakeSMC. I don't really see what could cause this...

 

Why do you need Whatevergreen?

Share this post


Link to post
Share on other sites
51 minutes ago, emilevirus said:

Isn't it needed for Intel UHD?

EDIT: Won't boot without it

 

It is needed for UHD display but not for UHD620 GPU.  Just Inject Intel in Clover and use Fake ID in Intel GFX 0x59168086 in Clover.  Whatevergreen does take care of that but it does a lot more and it may (or maybe not) be causing your shutdown problem.

 

Until I have more info from the RunMe app, I'm just guessing and don't really want to do that anymore. 

 

Edited by mnfesq

Share this post


Link to post
Share on other sites
11 hours ago, mnfesq said:

 

It is needed for UHD display but not for UHD620 GPU.  Just Inject Intel in Clover and use Fake ID in Intel GFX 0x59168086 in Clover.  Whatevergreen does take care of that but it does a lot more and it may (or maybe not) be causing your shutdown problem.

 

Until I have more info from the RunMe app, I'm just guessing and don't really want to do that anymore. 

 

That's weird. I am sure I had attached it in the first post.

Send me Emiles-MacBook-Pro.zip

Share this post


Link to post
Share on other sites
3 hours ago, emilevirus said:

That's weird. I am sure I had attached it in the first post.

Send me Emiles-MacBook-Pro.zip

 

Try using the DSDT.aml and SSDT-3.aml in Clover/ACPI/Patched.  Use the new config.plist.  You still have lots of entries in config.plist that seem to be unnecessary to me.  Also, I would consider removing your AppleHDA patches and just use the Lilu plug-in AppleALC.kext instead.  Lastly, I have had better results using VirtualSMC and its plug-ins instead of FakeSMC.

 

Archive.zip

Edited by mnfesq

Share this post


Link to post
Share on other sites
5 hours ago, mnfesq said:

 

Try using the DSDT.aml and SSDT-3.aml in Clover/ACPI/Patched.  Use the new config.plist.  You still have lots of entries in config.plist that seem to be unnecessary to me.  Also, I would consider removing your AppleHDA patches and just use the Lilu plug-in AppleALC.kext instead.  Lastly, I have had better results using VirtualSMC and its plug-ins instead of FakeSMC.

 

Archive.zip

It won't boot. Says Local APIC Error

Share this post


Link to post
Share on other sites
8 hours ago, emilevirus said:

It won't boot. Says Local APIC Error

 

So check the LAPIC box in Clover Kernel and Kext Patches.  Funny, I thought HP finally stopped having that problem.  I don't have it with my laptop.

Share this post


Link to post
Share on other sites
17 minutes ago, mnfesq said:

 

So check the LAPIC box in Clover Kernel and Kext Patches.  Funny, I thought HP finally stopped having that problem.  I don't have it with my laptop.

Now I'm getting could not register with Framebuffer driver

Share this post


Link to post
Share on other sites
1 hour ago, emilevirus said:

Now I'm getting could not register with Framebuffer driver

 

Try installing a newer version of Clover and, when you do, check the box to install EmuVariableUefi-64.  See if that helps.

Share this post


Link to post
Share on other sites
10 hours ago, mnfesq said:

 

Try installing a newer version of Clover and, when you do, check the box to install EmuVariableUefi-64.  See if that helps.

Same thing. 

Share this post


Link to post
Share on other sites
6 hours ago, emilevirus said:

Same thing. 

 

Looks like the Device ID should be 0x19168086 and the ig-platform-id should be 0x19160000.  Sorry about that.

 

EDIT:  Interestingly, the 1916 data worked for you previously but it is really intended for the desktop version of UHD 620.  The laptop version should use 5916.  I'm not sure why this is the case for you.  If you want to try using 5916, try it without Whatevergreen.

Edited by mnfesq

Share this post


Link to post
Share on other sites
1 hour ago, mnfesq said:

 

Looks like the Device ID should be 0x19168086 and the ig-platform-id should be 0x19160000.  Sorry about that.

 

EDIT:  Interestingly, the 1916 data worked for you previously but it is really intended for the desktop version of UHD 620.  The laptop version should use 5916.  I'm not sure why this is the case for you.  If you want to try using 5916, try it without Whatevergreen.

I've removed Whatevergreen and put 1916. I'm getting a kernel panic as it failed to map device 5916 to gpu, but it's 1916 in the config. Is 5916 somewhere else?

Edited by emilevirus

Share this post


Link to post
Share on other sites
32 minutes ago, emilevirus said:

I've removed Whatevergreen and put 1916. I'm getting a kernel panic as it failed to map device 5916 to gpu, but it's 1916 in the config. Is 5916 somewhere else?

 

It's in 2 places -- Device ID and ig-platform-id.

Share this post


Link to post
Share on other sites
1 hour ago, emilevirus said:

It booted. I needed to add FakePCIID.kext. Still won't shut down though.

 

Does shutdown problem persist when not using Whatevergreen?  If so, please post output of RunMe again.

Edited by mnfesq

Share this post


Link to post
Share on other sites
39 minutes ago, emilevirus said:

 

OK, here's what I'd like you to do.  Remove Whatevergreen and HibernateFixup from Clover kexts.  Use the custom DSDT and SSDT-3 in Clover/ACPI/Patched.  If it boots, ok and shutdown does not work, run RunMe again and post it.  The RunMe you sent shows that you booted with Whatevergreen and that you didn't use the DSDT and SSDT I customized.

Share this post


Link to post
Share on other sites
14 minutes ago, mnfesq said:

 

OK, here's what I'd like you to do.  Remove Whatevergreen and HibernateFixup from Clover kexts.  Use the custom DSDT and SSDT-3 in Clover/ACPI/Patched.  If it boots, ok and shutdown does not work, run RunMe again and post it.  The RunMe you sent shows that you booted with Whatevergreen and that you didn't use the DSDT and SSDT I customized.

I had removed Whatevergreen. I've readded your DSDT and still

Send me Emiles-MacBook-Pro.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×