I have a multiboot system.
One of the installed OS's does not use the NVMe SSD installed on the motherboard at all.
At the time of taking the screenshot, all the SSD partitions are unmounted, so apart from detection, the SSD is mostly unused.
For the unmounted and unused HDDs, I just use hdparm -Y
, but there seems to be nothing in terms of that for the SSD.
And even though I appreciate the additional heat in winters, this is going to be too expensive for me. I'd rather burn some cheap Nichrome than my data storage device.
I checked out a Debian forum thread and from that, I checked the following:
❯ sudo nvme get-feature /dev/nvme0 -f 2 -H
get-feature:0x02 (Power Management), Current value:0x00000004
Workload Hint (WH): 0 - No Workload
Power State (PS): 4
Update: I probably checked that at the wrong time before. Did so again after Sleep and realised the Power State was 0. So just need to make sure the Power State went back to 4 after wake.
I have no active cooling setup for the SSD from my side. This becomes relevant soon.
partitionmanager
, which probably does some reading to check the partition information, at 50°C stage, causes a temperature drop, as shown in the image.partitionmanager
right after reboot, when the temperature is increasing very sloowly, seems to do nothing significant.PS: 4
, so I have the culprit.partitionmanager
after that causes it to go back to PS: 4
So we have a solution! All I need to do is run partitionmanager
on wake. nlol jk
Motherboard: MSI MAG X570S TORPEDO MAX (MS-7D54)
SSD: Samsung 980 512GB (correct firmware, bought long before the fakes started coming out)
Note:
Amds Zero RPM is getting support in 6.13 kernel.
phoronix.com/news/Linux-6.13-A…
Sent out yesterday was an AMDGPU/AMDKFD kernel driver pull request with the last few feature additions and patches slated for the upcoming Linux 6.13 kernel merge windowwww.phoronix.com
Finally, yaay!
Thanks to Wolfgang Müller.
My GPU Zero RPM stayed on until 60°C and considering I lost my laptop to heat just last year, this was pinching me now and then.
Of course a drive heats up with use.
As I explained in the wall of text above, it was heating when NOT in use.
The reason being that after wake from S3 Sleep, it was turning on and not turning back off (as it should because it was NOT MOUNTED).
I just need to check which process is responsible for the SSD's power state management (systemd maybe?) and then see if something can be changed.
:wowie red face: