ulterno

A person, on the Gnome Issue, suggested that terminals inhibit sleep when there is stuff running in them.

Continuing from that discussion, I am trying to understand, at which point it would be desirable to implement said inhibition - terminal emulator, the shell or the program itself

Additionally:

• We want to inhibit when running stuff like pacman, wget, cp or mv
• We don't want to inhibit when running stuff like htop, less, watch

Hopefully we can get better input to the discussion here.

I have been thinking of a controller like this, which would be pretty fun to use for space games.

The ellipsoid marked as "Hand Piece", is supposed to be braced to the frame with motion encoders and need to push back the Hand Piece to the 0 position in case the user stops adding force in any direction.

Additionally, the hand piece can also have 5 buttons, 2 placed for the thumb and 3 placed for the 3 longer fingers each, with the button for the middle finger being a scroll wheel.

This should make up for actions like, Primary and Secondary fire, Target lock and cruise control adjustment, hence freeing the second hand for controlling utilities on the keyboard, or eating snacks. Whichever you prefer.

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.

• I would like the temps to drop down to SYSTIN (≈35°C) levels.
• I know, it's right next to my GPU, but I am not doing anything GPU intensive, the GPU temps are ~37°C ^[apart from GPU memory, which is 48°C due to the awful AMD 7th gen Zero RPM, which has no workarounds on Linux]

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

Showing it is already in the lowest power state.

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.

• Checking the SSD temps (using the same widget as in the image), the temperature on Sensor 2 starts out at ~40°C (after a normal reboot) and slowly increases to >50°C as shown at the start of the graph. Power State (PS) is still 4.

• Running KDE partitionmanager, which probably does some reading to check the partition information, at 50°C stage, causes a temperature drop, as shown in the image.

• Running KDE partitionmanager right after reboot, when the temperature is increasing very sloowly, seems to do nothing significant.

• Turns out that after a few minutes of System Standby, the SSD doesn't return to PS: 4, so I have the culprit.
• Running 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)

Until he actually had to use it.

Took 2 hours of reading through examples just to deploy the site.
Turns out, it is hard to do even just the bash stuff when you can't see the container.