Vitor-RT
commented
5 months ago I was able to check and look deeper and it wasn't related to this Kext. Thanks.
Closed Vitor-RT closed 5 months ago
Vitor-RT
commented
5 months ago I was able to check and look deeper and it wasn't related to this Kext. Thanks.
macOS Version
Sonoma
What is your CPU's model?
AMD Ryzen 5 3500U - iGPU/APU Vega 8
Please describe the behaviour in detail.
I have a Lenovo ideaPad s145 notebook and I have two storage devices on it. The first is an nvme on which I have Windows 11 installed and the second is a SSD Kingston SQ500S37/480G on which I have macOS installed in one partition and Debian in another. I'm doing a series of checks to adjust my newly installed macOS and I noticed that TRIM was not activated on the SSD I use on macOS, it was only active by default on nvme. I did some research on the internet and found the command "sudo trimforce enable", so, after finding the command, I activated it in the Terminal which asked me to restart the system. However, shortly after restarting the system and logging into my account, the system had a Kernel Panic. I tried to make some changes to my config.plist but nothing resulted. I started checking and disabled NootedRed and activated WhateverGreen, and restarting again with this modification the system stopped having the Kernel Panic. Taking advantage of the situation, that the system stopped having Kernel Panic, I disabled WhateverGreen's trimforce and kext at the same time as I activated NootedRed again. After the restart requested by trimforce, the Kernel Panic did not happen again. If you could try to replicate and test, seeing if something similar happens on your system and finding a solution for it, I would be very grateful.
What should've happened instead?
System using NootedRed with TRIM enabled on SSD running without Kernel Panic reported.
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
Kernel Panic.zip
Bug report submission terms