NVMeFix

[zebalo]

hello, got pointed here from tonymax86 since I face the same problem. Crash after wake from sleep with Samsung 970 Evo Plus. Here is my logs:

panic(cpu 8 caller 0xffffff7f8989d231): nvme: "Fatal error occurred. CSTS=0x0 US[1]=0x0 US[0]=0x21 VID=0x144d DID=0xa808
. FW Revision=2B2QEXM7\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 8), Frame : Return Address
0xffffff874bd3ba40 : 0xffffff80061215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff874bd3ba90 : 0xffffff800625a405 mach_kernel : _kdp_i386_trap + 0x155
0xffffff874bd3bad0 : 0xffffff800624bf8e mach_kernel : _kernel_trap + 0x4ee
0xffffff874bd3bb20 : 0xffffff80060c7a40 mach_kernel : _return_from_trap + 0xe0
0xffffff874bd3bb40 : 0xffffff8006120c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff874bd3bc40 : 0xffffff8006121087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff874bd3bc90 : 0xffffff80068c2d8c mach_kernel : _panic + 0x54
0xffffff874bd3bd00 : 0xffffff7f8989d231 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController8PolledIOEhP18IOMemoryDescriptorjyy18IOPolledCompletionjPKhm.cold.1
0xffffff874bd3bd20 : 0xffffff7f89888362 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffff874bd3be80 : 0xffffff7f898881a9 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController11ThreadEntryEv + 0x303
0xffffff874bd3bec0 : 0xffffff8006163545 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffff874bd3bf40 : 0xffffff8006163071 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffff874bd3bfa0 : 0xffffff80060c713e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[1CB1ACD2-15BF-3954-9968-BBB705F5ABD1]@0xffffff7f8987a000->0xffffff7f898bcfff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[64DD6A97-6E35-3BF4-AA75-46EFC42F574B]@0xffffff7f87533000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[6F96761B-C218-30A8-BECC-1EAD32E53D47]@0xffffff7f86b31000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[8E2FD14C-DB62-3304-8180-4298D14369E1]@0xffffff7f877ad000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[21A82F8D-A39D-3A9C-90B0-7563A3336B16]@0xffffff7f86d17000
            dependency: com.apple.iokit.IOReportFamily(47)[28F06131-E9AB-3980-9175-6B4EAB4326EE]@0xffffff7f86ed3000

BSD process name corresponding to current thread: kernel_task
Boot args: -v keepsyms=1

Mac OS version:
19E2269

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar  4 22:47:48 PST 2020; root:xnu-6153.101.6~16/RELEASE_X86_64
Kernel UUID: 7559A1A8-B300-3BC5-900F-5ED91F3197C7
Kernel slide:     0x0000000005e00000
Kernel text base: 0xffffff8006000000
__HIB  text base: 0xffffff8005f00000
System model name: MacPro7,1 (Mac-24AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 51249401960

I tried with version 1.0.1 and 1.0.2, same outcome. 

 

Thanks for looking into this!

[MacKonsti]

40 minutes ago, zebalo said:

hello, got pointed here from tonymax86 since I face the same problem. Crash after wake from sleep with Samsung 970 Evo Plus.

Although I am not expert and can't help you on this, have you updated your 970 Evo Plus with the latest firmware from Samsung? It is supposed to solve a lot of problems. I read this on the other forum where I posted for the Intel NUC hackintosh... it was marked by everyone as super-important to update.

[J1mmyS]

Wake from sleep results in KP for me too. This is happening with Samsung 970 Evo NVMe drive.

 

NVMeFix 1.0.2

apst=true

no NVMePMProxy entry in ioreg

Spoiler

panic(cpu 12 caller 0xffffff7f8c24a231): nvme: "Fatal error occurred. CSTS=0x0 US[1]=0x0 US[0]=0xda VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 12), Frame : Return Address
0xffffffa3df873a40 : 0xffffff800a5215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffffa3df873a90 : 0xffffff800a65a3c5 mach_kernel : _kdp_i386_trap + 0x155
0xffffffa3df873ad0 : 0xffffff800a64bf7e mach_kernel : _kernel_trap + 0x4ee
0xffffffa3df873b20 : 0xffffff800a4c7a40 mach_kernel : _return_from_trap + 0xe0
0xffffffa3df873b40 : 0xffffff800a520c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffffa3df873c40 : 0xffffff800a521087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffffa3df873c90 : 0xffffff800acc2c7c mach_kernel : _panic + 0x54
0xffffffa3df873d00 : 0xffffff7f8c24a231 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController8PolledIOEhP18IOMemoryDescriptorjyy18IOPolledCompletionjPKhm.cold.1
0xffffffa3df873d20 : 0xffffff7f8c235362 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffffa3df873e80 : 0xffffff7f8c2351a9 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController11ThreadEntryEv + 0x303
0xffffffa3df873ec0 : 0xffffff800a563545 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffffa3df873f40 : 0xffffff800a563071 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffffa3df873fa0 : 0xffffff800a4c713e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[3DB9BFC6-422F-39A2-A445-AB2732CE5BFC]@0xffffff7f8c227000->0xffffff7f8c269fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5EF51D44-9FC7-357F-9FB7-3468FD748382]@0xffffff7f8af88000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f8b101000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[6B3E9057-454A-3220-8AE3-424808CDA9E5]@0xffffff7f8b309000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[425BC668-32EC-368C-B4EB-CF8510846BEE]@0xffffff7f8ae65000
            dependency: com.apple.iokit.IOReportFamily(47)[337B24B2-0261-3521-8D1B-23387FC1D657]@0xffffff7f8b030000

BSD process name corresponding to current thread: kernel_task
Boot args: darkwake=8 keepsyms=1 alcid=7

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide:     0x000000000a200000
Kernel text base: 0xffffff800a400000
__HIB  text base: 0xffffff800a300000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 925022550754

 

 

NVMeFix 1.0.1

apst=true

NVMePMProxy entry found in ioreg

Spoiler

panic(cpu 0 caller 0xffffff7f93c4a231): nvme: "Fatal error occurred. CSTS=0x0 US[1]=0x0 US[0]=0xda VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 0), Frame : Return Address
0xffffff83c6fe3a40 : 0xffffff8011f215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff83c6fe3a90 : 0xffffff801205a3c5 mach_kernel : _kdp_i386_trap + 0x155
0xffffff83c6fe3ad0 : 0xffffff801204bf7e mach_kernel : _kernel_trap + 0x4ee
0xffffff83c6fe3b20 : 0xffffff8011ec7a40 mach_kernel : _return_from_trap + 0xe0
0xffffff83c6fe3b40 : 0xffffff8011f20c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff83c6fe3c40 : 0xffffff8011f21087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff83c6fe3c90 : 0xffffff80126c2c7c mach_kernel : _panic + 0x54
0xffffff83c6fe3d00 : 0xffffff7f93c4a231 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController8PolledIOEhP18IOMemoryDescriptorjyy18IOPolledCompletionjPKhm.cold.1
0xffffff83c6fe3d20 : 0xffffff7f93c35362 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffff83c6fe3e80 : 0xffffff7f93c351a9 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController11ThreadEntryEv + 0x303
0xffffff83c6fe3ec0 : 0xffffff8011f63545 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffff83c6fe3f40 : 0xffffff8011f63071 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffff83c6fe3fa0 : 0xffffff8011ec713e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[3DB9BFC6-422F-39A2-A445-AB2732CE5BFC]@0xffffff7f93c27000->0xffffff7f93c69fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5EF51D44-9FC7-357F-9FB7-3468FD748382]@0xffffff7f92988000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f92b01000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[6B3E9057-454A-3220-8AE3-424808CDA9E5]@0xffffff7f92d09000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[425BC668-32EC-368C-B4EB-CF8510846BEE]@0xffffff7f92865000
            dependency: com.apple.iokit.IOReportFamily(47)[337B24B2-0261-3521-8D1B-23387FC1D657]@0xffffff7f92a30000

BSD process name corresponding to current thread: kernel_task
Boot args: darkwake=8 keepsyms=1 alcid=7

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide:     0x0000000011c00000
Kernel text base: 0xffffff8011e00000
__HIB  text base: 0xffffff8011d00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 251395398470

 

 

EDIT: okay so switching the drive to another m.2 socket solved it.

Originally, Samsung drive was in socket 1 and Kingston drive in socket 2, after reversing their placements the KP is gone and system wakes up OK.

Edited May 26, 2020 by J1mmyS
update

[zebalo]

@MacKonsti yes updated to the latest firmware. 

@J1mmyS I will definitely try - although I've got Samsung NVMEs in both sockets.... 

[tmbt]

On 5/23/2020 at 12:47 AM, 978b029efa981d618699b09868 said:

I will fix re-enabling APST after sleep anyway, because it is a legitimate bug, but if older version of the kext does not help you, then this won't help you either.

 

Debug log should be working, without it I can't tell what is happening after waking.

I tried to use  DebugEnhancer.kext too without luck. If i use this command line in terminal :

log show --style syslog --last boot --predicate "process == \"kernel\" and eventMessage CONTAINS[c] \"nvme\"" --info --debug

 

all i got is this : 

Quote

Mattias-MacBook-Pro:~ mattia$ log show --style syslog --last boot --predicate  "process == \"kernel\" and eventMessage CONTAINS[c] \"nvme\"" --debug --info

Filtering the log data using "process == "kernel" AND composedMessage CONTAINS[c] "nvme""

Timestamp                       (process)[PID]    

2020-05-27 14:43:04.810522+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:04.812780+0200  localhost kernel[0]: (IONVMeFamily) AppleNVMe Assert failed: ( 0 != data )

2020-05-27 14:43:04.812785+0200  localhost kernel[0]: (IONVMeFamily) file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.270.1/IONVMeController.cpp

2020-05-27 14:43:04.814164+0200  localhost kernel[0]: (IONVMeFamily) virtual IOReturn IONVMeController::CreateSubmissionQueue(uint16_t, uint8_t)::2784:SQ index=0 entrysize=64

2020-05-27 14:43:04.814170+0200  localhost kernel[0]: (IONVMeFamily) virtual IOReturn IONVMeController::CreateSubmissionQueue(uint16_t, uint8_t)::2784:SQ index=0 entrysize=64

2020-05-27 14:43:04.814626+0200  localhost kernel[0]: (IONVMeFamily) virtual IOReturn IONVMeController::CreateSubmissionQueue(uint16_t, uint8_t)::2784:SQ index=1 entrysize=64

2020-05-27 14:43:04.814631+0200  localhost kernel[0]: (IONVMeFamily) virtual IOReturn IONVMeController::CreateSubmissionQueue(uint16_t, uint8_t)::2784:SQ index=1 entrysize=64

2020-05-27 14:43:04.824818+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:04.883103+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:04.892801+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:04.898564+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:04.899063+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:04.899737+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:08.555326+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:08.596461+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:08.598996+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:08.732927+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:08.733702+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:08.788306+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:09.044832+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:09.417069+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:09.544620+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:09.793998+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:09.794398+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:09.885656+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:10.609089+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:10.635201+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:12.994565+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:20.452864+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:21.704771+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

2020-05-27 14:43:21.707070+0200  localhost kernel[0]: Couldn't alloc class "NVMeFix"

I'm using the 1.0.1 NvmeFix debug version AND the Boot Args in OpenCore config.plist as you can see from the screenshot. I tried also to use the Opencore Debug version just in case ... but with the same result. 

What else can i do ?

[Paksman]

Even though NVMePMProxy entry is not in ioreg and APST = true, NVMeFix.kext still manages to lower temperature on my 960 EVO by 4-5 °C according to HWMonitorSMC2. Also, with latest commit https://github.com/acidanthera/NVMeFix/commit/009a13233f04484907dcac348bd6bfe1ee1db2a0 KP. I can provide logs if any developer is willing to look into.

Edit:

Fixed in https://github.com/acidanthera/NVMeFix/commit/cbebc4cf84ae2284c4e94bf29fadd449d8134e2c

Thanks !

Edited June 2, 2020 by Paksman

[tmbt]

On 5/23/2020 at 12:47 AM, 978b029efa981d618699b09868 said:

I will fix re-enabling APST after sleep anyway, because it is a legitimate bug, but if older version of the kext does not help you, then this won't help you either.

 

Debug log should be working, without it I can't tell what is happening after waking.

Hi,

i'm still struggling to make NVME power management after sleep. I will execute more tests on my side but i would like to understand if you think the problem is the NVME controller or is my NVME disk because i can't change the controller but i could think to change the disk if you could suggest a model that will work for sure.

 

Thanks

Mattia

 

[herb2k]

Trying to run this on my MacBook Pro (not a Hack) with an Intel SSD, KEXT loads but no NVMePMProxy, debug log (and posted more details to bugtracker).

 

2020-06-12 16:42:57.825242-0700  localhost kernel[0]: (Lilu) NVMeFix     nvmef: @ (DBG) processKext com.apple.iokit.IONVMeFamily
2020-06-12 16:42:57.825353-0700  localhost kernel[0]: (Lilu) NVMeFix     nvmef: @ (DBG) handleControllers for 1 controllers
2020-06-12 16:42:57.825362-0700  localhost kernel[0]: (Lilu) NVMeFix     iokit: @ (DBG) getOSData vendor-id has 8086 value
2020-06-12 16:42:57.825369-0700  localhost kernel[0]: (Lilu) NVMeFix     iokit: @ (DBG) getOSData vendor-id has 8086 value
2020-06-12 16:42:57.825375-0700  localhost kernel[0]: (Lilu) NVMeFix     iokit: @ (DBG) getOSData device-id has F1A8 value
2020-06-12 16:42:57.825384-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Reading OEM info from IODT
2020-06-12 16:42:57.825391-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Failed to find IODeviceTree:/efi/platform OEMProduct
2020-06-12 16:42:57.825397-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Failed to find IODeviceTree:/efi/platform OEMVendor
2020-06-12 16:42:57.825403-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Failed to find IODeviceTree:/efi/platform OEMBoard
2020-06-12 16:42:57.825408-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Reading OEM info from NVRAM
2020-06-12 16:42:57.825427-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Failed to find LiluVendorGuid:oem-product
2020-06-12 16:42:57.825449-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Failed to find LiluVendorGuid:oem-vendor
2020-06-12 16:42:57.825457-0700  localhost kernel[0]: (Lilu) NVMeFix    quirks: @ (DBG) Failed to find LiluVendorGuid:oem-board
2020-06-12 16:42:57.825465-0700  localhost kernel[0]: (Lilu) NVMeFix     nvmef: @ (DBG) Property ps-max-latency-us not found for parent service
2020-06-12 16:42:57.828418-0700  localhost kernel[0]: (Lilu) NVMeFix     nvmef: @ (DBG) Identified model INTEL SSDPEKNW512G8                     (vid 0x8086)
2020-06-12 16:42:57.838592-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) APST status 0
2020-06-12 16:42:57.838602-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) Configuring APST
2020-06-12 16:42:57.838630-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) Set entry 3 to 0x2bc20
2020-06-12 16:42:57.838640-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) Set entry 2 to 0x1f418
2020-06-12 16:42:57.838648-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) Set entry 1 to 0x1f418
2020-06-12 16:42:57.838657-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) Set entry 0 to 0x1f418
2020-06-12 16:42:57.838679-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) APST enabled: max PS = 4, max round-trip latency = 14000us
2020-06-12 16:42:57.858924-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) APST status 1
2020-06-12 16:42:57.869035-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) entry 4 : 0x0
2020-06-12 16:42:57.869051-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) entry 3 : 0x2bc20
2020-06-12 16:42:57.869066-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) entry 2 : 0x1f418
2020-06-12 16:42:57.869076-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) entry 1 : 0x1f418
2020-06-12 16:42:57.869087-0700  localhost kernel[0]: (Lilu) NVMeFix      apst: @ (DBG) entry 0 : 0x1f418

 

[herb2k]

15 hours ago, herb2k said:

Trying to run this on my MacBook Pro (not a Hack) with an Intel SSD, KEXT loads but no NVMePMProxy, debug log (and posted more details to bugtracker).

 

 

Looks like it's working correctly, from bugtracker:

 

ps-max-latency-us is a property that may be injected by the user. The kext does not publish it by itself, and uses a default value instead.

NVMePMProxy is a class responsible both for re-enabling APST after sleep, and active NVMe PM (if the latter is used; by default, APST is preferred). Ver. 1.0.2 had a bug where NVMePMProxy would not get initialised, and so APST would be disabled after sleep. This should be fixed in master (i.e. in the next release).

NVMeFix class is there only to follow the convention of Lilu plugins. It does not do anything.

[tmbt]

Hi guys,

here is my final post on this issue. I've finally solved it. I was not able to check log output using OpenCore but when i booted using Clover i finally got them :

2020-06-14 13:37:31.861605+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for IOMediaBSDClient
2020-06-14 13:37:31.862593+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for IOMediaBSDClient
2020-06-14 13:37:31.863485+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for IOMediaBSDClient
2020-06-14 13:37:31.886153+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for IOMediaBSDClient
2020-06-14 13:37:31.886726+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for AppleAPFSVolumeBSDClient
2020-06-14 13:37:31.886887+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for AppleAPFSVolumeBSDClient
2020-06-14 13:37:31.887033+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for AppleAPFSVolumeBSDClient
2020-06-14 13:37:31.887129+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for AppleAPFSVolumeBSDClient
2020-06-14 13:37:34.131941+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) processKext com.apple.iokit.IONVMeFamily
2020-06-14 13:37:34.132005+0200  localhost kernel[0]: (kernel) NVMeFix    disasm: @ (DBG) Offset 0xac for result
2020-06-14 13:37:34.132010+0200  localhost kernel[0]: (kernel) NVMeFix    disasm: @ (DBG) Offset 0x10a for command
2020-06-14 13:37:34.132018+0200  localhost kernel[0]: (kernel) NVMeFix    disasm: @ (DBG) Offset 0xc0 for prpDescriptor
2020-06-14 13:37:34.132023+0200  localhost kernel[0]: (kernel) NVMeFix    disasm: @ (DBG) Offset 0x269 for ANS2MSIWorkaround
2020-06-14 13:37:34.132036+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) handleControllers for 1 controllers
2020-06-14 13:37:34.132043+0200  localhost kernel[0]: (kernel) NVMeFix     iokit: @ (DBG) getOSData vendor-id has 15B7 value
2020-06-14 13:37:34.132049+0200  localhost kernel[0]: (kernel) NVMeFix     iokit: @ (DBG) getOSData vendor-id has 15B7 value
2020-06-14 13:37:34.132055+0200  localhost kernel[0]: (kernel) NVMeFix     iokit: @ (DBG) getOSData device-id has 5003 value
2020-06-14 13:50:29.238716+0200  localhost kernel[0]: (kernel) NVMeFix        pm: @ (DBG) powerStateDidChangeTo 0x0
2020-06-14 13:50:29.238720+0200  localhost kernel[0]: (kernel) NVMeFix        pm: @ (DBG) Ignoring transition to non-usable state 0x0
2020-06-14 13:51:08.114031+0200  localhost kernel[0]: (kernel) NVMeFix        pm: @ (DBG) powerStateDidChangeTo 0x2
2020-06-14 13:51:08.114205+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) APST status 0
2020-06-14 13:51:08.114213+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) Configuring APST
2020-06-14 13:51:08.114263+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) Set entry 3 to 0x99220
2020-06-14 13:51:08.114270+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) Set entry 2 to 0x2bc18
2020-06-14 13:51:08.114277+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) Set entry 1 to 0x2bc18
2020-06-14 13:51:08.114295+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) Set entry 0 to 0x2bc18
2020-06-14 13:51:08.114303+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) APST enabled: max PS = 4, max round-trip latency = 49000us
2020-06-14 13:51:08.114575+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) APST status 1
2020-06-14 13:51:08.114795+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) entry 4 : 0x0
2020-06-14 13:51:08.114803+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) entry 3 : 0x99220
2020-06-14 13:51:08.114811+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) entry 2 : 0x2bc18
2020-06-14 13:51:08.114817+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) entry 1 : 0x2bc18
2020-06-14 13:51:08.114824+0200  localhost kernel[0]: (kernel) NVMeFix      apst: @ (DBG) entry 0 : 0x2bc18
2020-06-14 13:53:37.257040+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for IOMediaBSDClient
2020-06-14 13:53:37.257052+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) handleControllers for 1 controllers
2020-06-14 13:53:37.257456+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) matchingNotificationHandler for IOMediaBSDClient
2020-06-14 13:53:37.257466+0200  localhost kernel[0]: (kernel) NVMeFix     nvmef: @ (DBG) handleControllers for 1 controllers

This showed me that power management for my NVMe drive was working even after wake so i focused on the rest of my hardware and find out i got a power leak on my trackpad after sleep (now solved). So this kext was working find from the beginning!

The only question to address from the author is why we can't see (i'm not the only one if you read this thread from the beginning) kext logs even when using debug version with the right boot argument .

 

Thanks for the support anyway !

 

Mattia

 

[978b029efa981d618699b09868]

7 hours ago, tmbt said:

The only question to address from the author is why we can't see (i'm not the only one if you read this thread from the beginning) kext logs even when using debug version with the right boot argument .

 

The kext is not doing anything special for logging. Rather, this seems to be a bootloader-specific issue. If you consistently get missing logs with any other kexts when using OpenCore, then you should submit an OpenCore issue.

[herb2k]

8 hours ago, tmbt said:

Hi guys,

 

This showed me that power management for my NVMe drive was working even after wake so i focused on the rest of my hardware and find out i got a power leak on my trackpad after sleep (now solved). So this kext was working find from the beginning!

The only question to address from the author is why we can't see (i'm not the only one if you read this thread from the beginning) kext logs even when using debug version with the right boot argument .

 

Thanks for the support anyway !

 

Mattia

 

Which version are you using?

[tmbt]

On 6/14/2020 at 10:41 PM, herb2k said:

 

Which version are you using?

I tried all the NVMeFix versions and used all the OpenCore versions since the very beninning. I used to build them by myself and occasionally used the official versions. 

 

 

[tmbt]

On 6/14/2020 at 9:22 PM, 978b029efa981d618699b09868 said:

 

The kext is not doing anything special for logging. Rather, this seems to be a bootloader-specific issue. If you consistently get missing logs with any other kexts when using OpenCore, then you should submit an OpenCore issue.

To be honest i never have to check for other kext logs except from VoodooI2C kext and haven't had any issue with that log. 

Thanks anyway for your help.

 

Mattia

 

[Toroop]

Hi any idea on when version 1.0.3 will be released?

I have great battery life until the computer goes to sleep and I think the fix is in 1.0.3 for this.

Thanks

[Paksman]

6 hours ago, Toroop said:

Hi any idea on when version 1.0.3 will be released?

I have great battery life until the computer goes to sleep and I think the fix is in 1.0.3 for this.

Thanks

Here you go. Compiled from latest source, release version.

NVMeFix.kext.zip

[Toroop]

On 7/16/2020 at 5:31 PM, Paksman said:

Here you go. Compiled from latest source, release version.

NVMeFix.kext.zip

That's great thanks very much!!

[Potato007]

Hi,

I'm using a Sabrent Rocket Q 2TB on ASrock B550M iTX/AC motherboard with AMD Ryzen 9 3950x.

 

As Intel Power Gadget is not working with AMD hackintosh and AMD Power Gadget does not display info regarding the power consumption of NVMe, how can I check the power consumption?

 

IORegistryExplorer shows the APST property after the kext is installed. 

 

I get this output with smartclt, but it does not reflect the actual Watt value.

 

 

 

 

smartctl 7.1 2019-12-30 r5022 [Darwin 19.6.0 x86_64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Sabrent Rocket Q
Serial Number:                      A18507061E5D02091072
Firmware Version:                   RKT30Q.1
PCI Vendor/Subsystem ID:            0x1987
IEEE OUI Identifier:                0x6479a7
Total NVM Capacity:                 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
Number of Namespaces:               1
Local Time is:                      Sat Sep 12 17:03:16 2020 CEST
Firmware Updates (0x12):            1 Slot, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005d):     Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     75 Celsius
Critical Comp. Temp. Threshold:     80 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     7.13W       -        -    0  0  0  0        0       0
 1 +     5.29W       -        -    1  1  1  1        0       0
 2 +     4.36W       -        -    2  2  2  2        0       0
 3 -   0.0490W       -        -    3  3  3  3     2000    2000
 4 -   0.0018W       -        -    4  4  4  4    25000   25000

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
 

 

[978b029efa981d618699b09868]

On 9/12/2020 at 6:06 PM, Potato007 said:

 

As Intel Power Gadget is not working with AMD hackintosh and AMD Power Gadget does not display info regarding the power consumption of NVMe, how can I check the power consumption?

You can't really check it directly unless your computer has dedicated voltage and current sensors for SSD. You could try and compare battery life to get an idea whether APST is helpful.

[indiekiduk]

On 5/25/2020 at 1:09 PM, zebalo said:

hello, got pointed here from tonymax86 since I face the same problem. Crash after wake from sleep with Samsung 970 Evo Plus. Here is my logs:

panic(cpu 8 caller 0xffffff7f8989d231): nvme: "Fatal error occurred. CSTS=0x0 US[1]=0x0 US[0]=0x21 VID=0x144d DID=0xa808
. FW Revision=2B2QEXM7\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 8), Frame : Return Address
0xffffff874bd3ba40 : 0xffffff80061215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff874bd3ba90 : 0xffffff800625a405 mach_kernel : _kdp_i386_trap + 0x155
0xffffff874bd3bad0 : 0xffffff800624bf8e mach_kernel : _kernel_trap + 0x4ee
0xffffff874bd3bb20 : 0xffffff80060c7a40 mach_kernel : _return_from_trap + 0xe0
0xffffff874bd3bb40 : 0xffffff8006120c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff874bd3bc40 : 0xffffff8006121087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff874bd3bc90 : 0xffffff80068c2d8c mach_kernel : _panic + 0x54
0xffffff874bd3bd00 : 0xffffff7f8989d231 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController8PolledIOEhP18IOMemoryDescriptorjyy18IOPolledCompletionjPKhm.cold.1
0xffffff874bd3bd20 : 0xffffff7f89888362 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffff874bd3be80 : 0xffffff7f898881a9 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController11ThreadEntryEv + 0x303
0xffffff874bd3bec0 : 0xffffff8006163545 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffff874bd3bf40 : 0xffffff8006163071 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffff874bd3bfa0 : 0xffffff80060c713e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[1CB1ACD2-15BF-3954-9968-BBB705F5ABD1]@0xffffff7f8987a000->0xffffff7f898bcfff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[64DD6A97-6E35-3BF4-AA75-46EFC42F574B]@0xffffff7f87533000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[6F96761B-C218-30A8-BECC-1EAD32E53D47]@0xffffff7f86b31000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[8E2FD14C-DB62-3304-8180-4298D14369E1]@0xffffff7f877ad000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[21A82F8D-A39D-3A9C-90B0-7563A3336B16]@0xffffff7f86d17000
            dependency: com.apple.iokit.IOReportFamily(47)[28F06131-E9AB-3980-9175-6B4EAB4326EE]@0xffffff7f86ed3000

BSD process name corresponding to current thread: kernel_task
Boot args: -v keepsyms=1

Mac OS version:
19E2269

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar  4 22:47:48 PST 2020; root:xnu-6153.101.6~16/RELEASE_X86_64
Kernel UUID: 7559A1A8-B300-3BC5-900F-5ED91F3197C7
Kernel slide:     0x0000000005e00000
Kernel text base: 0xffffff8006000000
__HIB  text base: 0xffffff8005f00000
System model name: MacPro7,1 (Mac-24AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 51249401960

I tried with version 1.0.1 and 1.0.2, same outcome. 

 

Thanks for looking into this!

 

 

Same crash here on 10.15.6 with ADATA XPG SX8200 Pro 1TB. Was doing really heavy reading/writing around 100GB over an hour or so.

 

panic(cpu 0 caller 0xffffff7f9f458231): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x27 VID=0x1cc1 DID=0x8201
. FW Revision=R0906I\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320

 

[Mazots]

Hi, does anyone know when 1.0.4 will be released to public? It’s not available on the download page

[Andrey1970]

2 hours ago, Mazots said:

Hi, does anyone know when 1.0.4 will be released to public? It’s not available on the download page

https://github.com/acidanthera/bugtracker/issues/1168

[maleorderbride]

A Samsung PM983 appears to panic on shutdown each time (without this kext), and if I install the current NVMeFix and Lilu then IOAHCIBlockStorage panics on startup. This is on an ASUS X299 Deluxe II in 10.15.7 using Clover.

 

Shutdown panic (received at next startup):

panic(cpu 0 caller 0xffffff7f85431231): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0xae VID=0x144d DID=0xa808
. FW Revision=EDB5002Q\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 0), Frame : Return Address
0xffffff875a0db9e0 : 0xffffff800191a65d
0xffffff875a0dba30 : 0xffffff8001a54a75
0xffffff875a0dba70 : 0xffffff8001a465fe
0xffffff875a0dbac0 : 0xffffff80018c0a40
0xffffff875a0dbae0 : 0xffffff8001919d27
0xffffff875a0dbbe0 : 0xffffff800191a117
0xffffff875a0dbc30 : 0xffffff80020c1abc
0xffffff875a0dbca0 : 0xffffff7f85431231
0xffffff875a0dbcc0 : 0xffffff7f8541c362
0xffffff875a0dbe20 : 0xffffff8002032329
0xffffff875a0dbe90 : 0xffffff8002032249
0xffffff875a0dbec0 : 0xffffff800195c605
0xffffff875a0dbf40 : 0xffffff800195c131
0xffffff875a0dbfa0 : 0xffffff80018c013e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[28183FA3-6A50-3611-BC20-A0717B657AAC]@0xffffff7f8540e000->0xffffff7f85450fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5922E20B-D148-30DC-ABBA-0E99B3BE6940]@0xffffff7f83196000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f82331000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[D9C4809C-7B20-3663-A9C8-4DBC261AAD86]@0xffffff7f832b6000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[3581A46A-F3F3-3CE7-BA52-7046E8D66C32]@0xffffff7f823b0000
            dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7f8248f000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 darkwake=0

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide:     0x0000000001600000
Kernel text base: 0xffffff8001800000
__HIB  text base: 0xffffff8001700000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)

 

Startup panic:

panic(cpu 2 caller 0xffffff8005a469aa): Kernel trap at 0xffffff800602e9b7, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000031, CR3: 0x000000001ef29000, CR4: 0x00000000003626e0
RAX: 0x0000000000000001, RBX: 0xffffff80a8a512d0, RCX: 0x0000000002000000, RDX: 0x0000000003000000
RSP: 0xffffff875590bcd0, RBP: 0xffffff875590bd20, RSI: 0xffffff80a89ed4b0, RDI: 0xffffff80a8a51af0
R8:  0x0000000000000000, R9:  0x0000000000000000, R10: 0x0000000000000001, R11: 0xffffff80a854f9c0
R12: 0xffffff800648b0c8, R13: 0x0000000000000000, R14: 0xffffff80a8a51af0, R15: 0x0000000000000000
RFL: 0x0000000000010202, RIP: 0xffffff800602e9b7, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x0000000000000031, Error code: 0x0000000000000002, Fault CPU: 0x2, PL: 0, VF: 1

Backtrace (CPU 2), Frame : Return Address
0xffffff875590b730 : 0xffffff800591a65d 
0xffffff875590b780 : 0xffffff8005a54a75 
0xffffff875590b7c0 : 0xffffff8005a465fe 
0xffffff875590b810 : 0xffffff80058c0a40 
0xffffff875590b830 : 0xffffff8005919d27 
0xffffff875590b930 : 0xffffff800591a117 
0xffffff875590b980 : 0xffffff80060c1a6c 
0xffffff875590b9f0 : 0xffffff8005a469aa 
0xffffff875590bb70 : 0xffffff8005a466a8 
0xffffff875590bbc0 : 0xffffff80058c0a40 
0xffffff875590bbe0 : 0xffffff800602e9b7 
0xffffff875590bd20 : 0xffffff7f8891bcff 
0xffffff875590bd50 : 0xffffff7f889225d3 
0xffffff875590bd80 : 0xffffff7f8892887d 
0xffffff875590bdb0 : 0xffffff7f889217ad 
0xffffff875590bde0 : 0xffffff8006007576 
0xffffff875590be40 : 0xffffff80060070b1 
0xffffff875590bef0 : 0xffffff800600644e 
0xffffff875590bf50 : 0xffffff8006008c06 
0xffffff875590bfa0 : 0xffffff80058c013e 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAHCIBlockStorage(316.100.5)[95318F66-9008-34C3-A08A-3665ABBC11C1]@0xffffff7f8891b000->0xffffff7f88942fff
            dependency: com.apple.iokit.IOAHCIFamily(290.0.1)[6130982A-0A17-32D1-BDA5-57132BACE589]@0xffffff7f888f0000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[10E46031-889C-3FB7-8B4B-0DECAB5AE325]@0xffffff7f86c43000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[CB3CB8CA-881A-37F3-A96B-8063CAF0476D]@0xffffff7f86265000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 darkwake=0 

Mac OS version:
19H2

Kernel version:
Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64
Kernel UUID: 05D51A3D-3A87-3FF0-98C3-9CF3827A3EDD
Kernel slide:     0x0000000005600000
Kernel text base: 0xffffff8005800000
__HIB  text base: 0xffffff8005700000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: NO (0xe00002d8)

Any boot flags worth trying, or other info you would like me to post? Thanks!

[indiekiduk]

It happens on my ADATA SX8200 Pro 1TB after I've driven it hard for a few hours so I'm wondering if the issue is caused by overheating or when a cleanup routine is executed like TRIM perhaps.

[irfan67670]

Hi,

Not sure if i should ask my question in this forum, please guide me to the right link if this is not the place for it.

I have an Catalina installed on a sata ssd, and a secondary Intel H10 NVME ssd, applied nvmefix. System looks pretty stable as long as i don't put it to sleep, and I can use the nvme for regular work.

 

My only problem currently seems to be the fans. If i boot clover with "nvme=-1", then the nvme is completely invisible to system and the cpu fans work as normal

When i remove that flag, and my nvme is visible, even if i don't use it at all, the cpu fans keep making noise almost all the time.

The other issue is after wake from sleep, the system hangs a few minutes later with screen stuck completely and no panic, have to hard restart, although i don't care about it, as i don't put my system to sleep.

So my only issue is the fans constantly making noise.

 

I know intel nvme's are worst contenders for mac (right?), but i just want to know if this is something i can solve easily or not. Maybe someone else had the same issue and got it resolved.

 

Let me know what kind of information i need to provide, i can use all the hack tools quite well, just dont know where to log for the info that maybe needed to fix.

 

Thanks all.