hello... first let me thank you all for the great work! Its fantastic how many brilliant minds are working together on this
I have managed to get Catalina running on my ASUS X299 Gaming E II - i9-10900X pretty nicely. As far I can tell, everything works besides the sleep... I have created custom USB map and applied the entire OpenCore getting stared guide so far but it didn't help. I think I have two issues:
1) Desktop wakes immediately after sleep - an evergreen. Couldn't figure out yet why in this particular case. However, there is a strange thing with my board: USB header HS07 seems to serve as HUB for several ports, including the internal one which is used by the bluetooth card...Is that weird?
log show --style syslog | fgrep "Wake reason" gives me
Code:
2020-05-23 22:15:10.209837+0200 localhost powerd[100]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2020-05-23 23:27:29.840562+0200 localhost powerd[103]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2020-05-24 08:41:09.089974+0200 localhost powerd[103]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2020-05-24 09:48:47.063815+0200 localhost powerd[103]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
not so helpful
2) Crash after wake: My setup is crashing after waking from sleep with a kernel panic:
Code:
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-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 51249401960
I assume something with my Samsung Evo 970 Pro (updated to latest firmware). So far I couldn't observe any issues with them besides after sleep.
Would be awesome if someone of you could guide me into some direction what to do next... Thanks a lot!
