Hello, @telepati I think I have the same issue than you about SystemMemory issue and Nvme kernel Panic
I'm trying to understand the thing I have to fix on my DSDT.dsl but I am quite unsure about it, even when I read this thread ...
And this is what I get when I open my origin DSDT.dsl on Maciasl :
Firmware Error (ACPI): Failure looking up [^GFX0.CLID], AE_NOT_FOUND (20180427/dswload-498)
// Invalid external declaration at AML offset 0x3c2 (see bz1397).
Firmware Error (ACPI): Failure looking up [^^UBTC.MGI0], AE_NOT_FOUND...
Hello again !
So I fixed the prohibitory sign issue, I still have the random crashes,
each report seems to indicate a problem linked to my ssd drive.
I couldn’t understand what was wrong about the drive but I tried several things :
-injecting Sata-unsupported kext but I still got crashes...
My Injectkext seemed to be "Yes", I should have checked this before trying to install FakeSMC.kext and VoodooPS2 on system.
So I guess there is a conflict between my kext in systems and those on my EFI partition ?
I just installed SATA-unsupported.kext via my bootable usb key, still the same issue at start-up.
So I tried to uninstall both FakeSMC.kext and VoodooPS2 controller from L/E but I have the same problem.
I am not sure if I can delete kexts using "rm -Rf" from the bootable key because I still can...
I am now stuck on prohibitory sign at booting...
it happened just after installing VoodooPS2Controller and FakeSMC kexts on system volume.
I tried to uninstalled both of them from my usb boot key with terminal targeting my drive but apparently nothing changed.
This is my verbose mode attached.
I’m having troubles with trackpad in High Sierra but also in Windows 10, it isn’t detected at all.
It was working fine a few hours ago and nothing has changed though.
I noticed however the trackpad was working in the xiaomi boot manager.
On top of this I am experiencing crash...