So I currently have it so the macbook running Ubuntu server stays on when shut but the screen stays on which I do not want. How can I have the screen turn off but keep everything running?

as the title is says, I want to disable all methods (buttons, commands, etc.) an unprivileged user have to turn a system into any standby-mode (sleep|hibernate|hybrid) under xfce4. I found out that with a kioskrc file, we can disable to save user sessions.

# /etc/xdg/xfce4/kiosk/kioskrc
[xfce4-session]
SaveSession=NONE

I am familiar with powertop and powerstat, but they appear to measure CPU power consumption. Is there any way to measure the power consumption of a specific PCIe slot?

I have a Lenovo Helix 2, which has busted suspend-to-RAM (S3) support. "Light sleep" mode (S0ix), however, works fine, as tested with echo freeze > /sys/power/state. I can bind the power button to use freeze instead of mem using acpid event handlers, but what I really want to do is get the desktop environment to handle this, since it can do things like "suspend after N minutes of user inactivity" that acpid can't. Unfortunately, the only options the KDE power manager gives me are "Do Nothing", "Lock Screen", "Suspend", "Hibernate", and "Power Off". It has a "run script" option, but that only applies when transitioning between power states -- e.g. I could have it run a script when going from AC to battery, or from battery to low battery, but not when on battery power and idle for 30 minutes. So, is there some way -- either as part of KDE configuration, or as a systemd or sysfs or kernel option -- to override things so that it will try to freeze instead of, or as an alternative to, suspending?

When using "Power Off" action in Gnome if there are some GUI applications with unsaved changes (for example, text editor) there will be label "Some applications are busy or have unsaved work". I am looking for a way to set this "unsaved" status from command line. So I can integrate it into my workflow when I'm using tmux/neovim, to not accidentally power off PC when I have some sessions opened.

Intel Sandy-Bridge family i5 Core CPU, running Linux kernel 3.2 (Debian Squeeze/Wheezy), under heavy computation load, does not react to to cpufreq-set -g powersave (using acpi_cpufreq module). It is 99.9% time running in turbo mode, although it seems to be somehow throttled automatically, as can be seen in kernel messages (dmesg): ... [137547.968129] CPU2: Package temperature/speed normal [137547.968130] CPU0: Package temperature/speed normal [137548.124277] CPU2: Core temperature above threshold, cpu clock throttled (total events = 16455155) [137548.124280] CPU3: Core temperature above threshold, cpu clock throttled (total events = 16455154) [137548.125289] CPU2: Core temperature/speed normal [137548.125291] CPU3: Core temperature/speed normal [137847.287143] CPU2: Package temperature above threshold, cpu clock throttled (total events = 17888019) [137847.287147] CPU3: Package temperature above threshold, cpu clock throttled (total events = 17888017) ... I'd like to turn this CPU to power-saving mode, or choose the frequency, like with good old cpufreq powersave or userpace cpufreq governors. I wonder, what manual throttling method would work on these CPUs..

I just purchased this laptop used and installed Fedora 42 on it. It’s a Dell Latitude 5420 with an i5-1145G7 processor. The laptop does not support S3 sleep, only s2idle. It successfully enters and resumes sleep when the lid is closed, but the battery drains rapidly. I have not done any proper benchmarks but I was at around ~60% battery life last night, and when I opened it this afternoon it was completely dead. After running the S0ix self test tool , I got the following output:

...
Your system supports S0ix substates, but did not achieve the shallowest s0i2.0
    
Here is the S0ix substates status: 
Substate   Residency      
S0i2.0     0              
S0i3.0     0     
...
Below are the deeper S0ix substate required IPs did not show YES:
    pmc0:            USB2PLL_OFF_STS    Required               
    pmc0:            OPIOPLL_OFF_STS    Required               
    pmc0:                CSME_PG_STS    Required               
    pmc0:                xHCI_PG_STS    Required               
    pmc0:                 GBE_PG_STS    Required               
    pmc0:               xHCI0_D3_STS    Required               
    pmc0:          CPU_C10_REQ_STS_0    Required               
    pmc0:    MPHY_Core_DL_REQ_STS_16    Required

Full output here . Unfortunately I have no idea what this means.

Yocto System taking more time to resume from S3 sleep, it should take 2sec, but taking 12sec: Suspend entry: [ 244.086061] PM: suspend entry (deep) Low-level resume complete: [ 246.900251] Suspend exit: [ 247.970167] Display usable (login/dmesg): [ 257.556554] sshd or ACP logs visible Stage Time (sec) Suspend → Low-level resume ~2.81s Suspend → Suspend exit ~3.88s Suspend → Usable system ~13.5s How do I diagnose this and identify the part where it gets stuck for so long?

system hang with G2/G3 NIC card after resuming from S3 suspend. But it works with G1 NIC & ethernet. What is the culprit here xhci_hcd 0000:03:00.3: Controller not ready at resume -19 xhci_hcd 0000:03:00.3: PCI post-resume error -19! xhci_hcd 0000:03:00.3: HC died; cleaning up xhci_hcd 0000:03:00.4: Controller not ready at resume -19 xhci_hcd 0000:03:00.4: PCI post-resume error -19! xhci_hcd 0000:03:00.4: HC died; cleaning up xhci_hcd 0000:03:00.3: PM: dpm_run_callback(): pci_pm_resume returns -19 xhci_hcd 0000:03:00.4: PM: dpm_run_callback(): pci_pm_resume returns -19 xhci_hcd 0000:03:00.3: PM: failed to resume async: error -19 xhci_hcd 0000:03:00.4: PM: failed to resume async: error -19

I'm trying to let logind handle my lid events. So I followed the instructions here: https://docs.xfce.org/xfce/xfce4-power-manager/faq And tried

$ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch
Property "/xfce4-power-manager/logind-handle-lid-switch" does not exist on channel "xfce4-power-manager".

As you can see it says that property does not exist. According to xfce4-about, I'm running version 4.18.

On my machine, i have power savings disable on the BIOS. When I run Ubuntu on this machine, the CPU's are running maximum at 2100 MHz. However, when I'm running CentOS 7, even with the scaling governor set to "performance", the CPU's are not running full at 2100 MHz. cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance grep -i mhz /proc/cpuinfo cpu MHz : 1688.285 cpu MHz : 2058.656 cpu MHz : 1622.988 cpu MHz : 2070.632 My application is a network processing application, so the CPU clock difference is resulting a performance difference. I do not have cpuspeed,powerd, or any other power regulating services running. So my question is, is this expected behavior given the cpupower is set to "perform"? It seems CentOS is override the BIOS setting. When I boot to Ubuntu, it just takes the BIOS settings and all the CPU's are running max.

**Question:** I want to look at parameters under /sys/class/typec, but on my laptop, this doesn't show up. When I load the typec module manually, the directory appears but it is empty. After loading tcpm module, nothing happens. How do I get the /sys/class/typec interface? How can I know if it is even supported? If it isn't, why not -- does my hardware not expose the controls? Are drivers missing? etc. The laptop is a HP ProBook 430 G5 (based on intel 8gen Kaby Lake Refresh core i5). It has one USB-C port capable of USB Power Delivery (alongside DisplayPort and regular USB traffic). I'm on Linux Mint Sylvia, my kernel is 4.15.3 from kernel.ubuntu.com (installed through ukuu tool). This should be recent enough that all the relevant kernel things exist. Why don't I see them? (I also want to learn a little about the TypeC interface, hence why I'm asking this specific question, as opposed to the more task-oriented variant seen below.) --- **Background,** AKA, why am I even doing this, in case this is helpful: HP hardware is notorious for disliking 3rd party USB-C chargers, but this got somewhat better in the 8gen series; it sort of works now. I'm using the following USB-C dock: http://i-tec.cz/?t=3&v=443 When the laptop is on AC power, I can connect the dock and everything works fine. When I disconnect the AC adapter, the laptop _will continue to charge_ over the USB-C connection. Same thing happens when I connect the dock when laptop is turned off. However, if I simply plug in the dock when the laptop is on AC power, it doesn't work at all. No charging, no devices, not even a connect event. Furthermore, the laptop starts making a slight clicking sound. In Windows, this is accompanied by repeated connect/disconnect sounds. In dmesg, I see messages like this:

[10356.375855] xhci_hcd 0000:00:14.0: Cannot set link state.
[10356.375866] usb usb2-port2: cannot disable (err = -32)

(yes, this might be a hardware problem) However, if the problem lies with power delivery (as it seems to be, given the "plug in while on AC" thing), I'd like to try to switch the port to a non-PD mode. Then I could at least get the dock functionality. This seems to be done through USB Type-C Port Manager (tcpm) interface. I don't have that on my laptop. /sys/class/typec doesn't exist initially, shows up empty after inserting typec module.

I got Pi4 4Gb running rasbian (similar to Debian) and Orico 4bay HDD rack connected with USB3. Earlier with same host and one HDD in separate enclosure I was able to power off disk using: sudo udisksctl power-off -b /dev/sda But now, for this four disks enclosure rack I got errors like this: pi@raspberrypi:~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─sda1 8:1 0 931.5G 0 part └─md0 9:0 0 931.4G 0 raid1 /mnt/raid sdb 8:16 0 931.5G 0 disk └─sdb1 8:17 0 931.5G 0 part └─md0 9:0 0 931.4G 0 raid1 /mnt/raid sdc 8:32 0 2.7T 0 disk └─sdc1 8:33 0 2.7T 0 part /mnt/wdred sdd 8:48 0 1.8T 0 disk └─sdd1 8:49 0 1.8T 0 part mmcblk0 179:0 0 14.8G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot └─mmcblk0p2 179:2 0 14.6G 0 part / pi@raspberrypi:~ $ sudo umount /mnt/raid pi@raspberrypi:~ $ sudo umount /mnt/wdred pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sdc Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sda Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sdb Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sdd Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ If I shutdown pi and the turn off this rack with power button on it I see increment of Power-Off_Retract_Count attribute in HDD Smart (so this is not graceful power off, but emergency retract). How can I properly power off drives in this rack?

nvme smart-log /dev/nvme0n1 shows consistently climbing temporature of a KINGSTON SKC3000D4096G NVME SSD drive, even when idle. Without load, it converges to 85-90 degrees Celsium. Laptop is indeed very hot at that and the fan is running all the time. The problem is reproducible when booting in single-user mode. System is Debian running kernel 6.12.12+bpo-amd64 (or 6.1.0-31-amd64 - the same result). However, when booting Linux Mint or Debian **LiveCD** (with similar kernel, e.g. 6.8; actually a USB flash drive, not CD), the drive does **not heat up** when idle, even if something is mounted from it. Only actively reading to it or writing to it makes the temperature climb. It stays hot even when doing echo s2idle > /sys/power/mem_sleep echo mem > /sys/power/sleep , but cools down when doing echo deep > /sys/power/mem_sleep echo mem > /sys/power/sleep How do I debug this? I tried experimenting with applying powertop suggestions, with using nvme_core.default_ps_max_latency_us=0 or (=20). Maybe there is some arcane nvme set-feature command to help? Maybe there is a way to temporarily suspend the device besides full s2ram (like hdparm -y, but for NVMe)? --- nvme get-feature /dev/nvme0 -f 0x0c -H shows a couple of non-zero entries (100 ms, 4). Entries seem to stay the same. --- # Update: partial workaround Based on [this bug report](https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/2064042) , I tried using nobarrier and it indeed stopped the heating (after s2ram cycle). Doing mount -o remount,barrier / immediately starts the power drain.

I am working on an embedded Linux system (kernel-5.10.220). Now I am testing the suspend and resume in this system with a watchdog time as the wakeup source to wake system up from suspend. The watchdog interrupt comes in every 5 seconds, and the script calls sleep 10 to add 10 seconds delay between continous test. And there is NO RTC in system! Here is my testing script.

#!/bin/sh

trap ctrl_c INT

function ctrl_c()
{
    echo "Exiting"
    exit 0
}

count=0
sec=10

while [ true ]
do
    echo ">>>>>>>>>>> Testing suspend $count"
    echo mem > /sys/power/state
    echo ">>>>>>>>>> Testing suspend 0
>>>>>>>>>> Testing suspend 1
>>>>>>>>>> Testing suspend 2
>>>>>>>>>> Testing suspend 3
>>>>>>>>>> Testing suspend 4
>>>>>>>>>> Testing suspend 5
>>>>>>>>>> Testing suspend 6
<<<<<<<<<<< Resumed after suspend

Thu Jan  1 06:33:12 UTC 1970

From the output of date, the script did NOT delay 10 seconds between tests. The real interval of 10 seconds sleeping is about 2 or 3 seconds! So why sleep 10 did NOT sleep for 10 seconds in the suspend and resume testing?

I was going through the Linux power management files, and I am confused about the C and S states. - The C-states are defined in /sys/devices/system/cpux/cpuidle/. From what I understand they are used to put the CPU in different sleep states depending on the level of idleness. - The S-state interface is in /sys/power/state and I can see different sleep states like freeze, standby, mem, etc. If I read their description they are trying to accomplish the same thing that the C-states are trying to do. This brings me to my question: What is the difference between them? And if I want to prevent my system from going into idle, what parameters should I set. I set the disable parameter for the C-state in /sys/devices/system/cpux/cpuidle/ but I could still observe my phone going into the idle state (used systrace for observation).

I recently had my laptop serviced, and the motherboard was replaced. I run a dual boot setup with Fedora Linux and Windows. Before the servicing, the USB-C port supported charging on Linux via Power Delivery. However, afterwards, charging via USB-C PD exhibits some peculiar behaviour: - Works fine on Windows - Works fine when laptop is plugged in while powered off - Does not charge on Linux if laptop boots without USB-C plugged in, charging - Charges fine on Linux if laptop was already plugged in before booting (even charges after plugging out and plugging in) To summarise, I have to have the laptop plugged in via a USB-C charger, if I want the laptop to be able to charge for this boot/session, where it will continue to work even if I plug out the USB-C charger and plug it in another time. Clearly Linux still supports charging via USB-C, but cannot initiate the charging if the conditions above aren't met. The result of cat /sys/class/typec/port0/power_role is [source] sink even when plugged in. USB-C accessories still work with the port. What is going on and how can I rectify this issue? Thank you.

I have a Thermalright Frozen Vision liquid cooler with display for my CPU. On windows it works perfectly with all sensors details due to a dedicated app released from the manufacturer. Unfortunately the company seems to not consider to release the same app for ubuntu, so using this OS the AIO screen remains powered off without chance to activate it via software. The device works with a usb cable header-to-c, and by removing and re-plug manually the usb-c from the AIO, the screen magically starts, showing the wallpaper previously set on windows without sensors data, but only for 10 seconds after which it will shutdown again. Recording events with udevadm that's what happen removing/re-plug the usb-c:

$ udevadm monitor --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [4024.985576] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0 (usb)
UDEV  [4024.986461] unbind   /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4024.987085] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4030.148850] add      /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4030.149910] add      /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0 (usb)
UDEV  [4030.150705] bind     /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0 (usb)
UDEV  [4030.151278] add      /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1 (usb)
UDEV  [4030.172597] add      /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/tty/ttyACM0 (tty)
UDEV  [4030.173432] bind     /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1 (usb)
UDEV  [4030.175570] bind     /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4032.694441] unbind   /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0 (usb)
UDEV  [4032.694523] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/tty/ttyACM0 (tty)
UDEV  [4032.695109] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0 (usb)
UDEV  [4032.695318] unbind   /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1 (usb)
UDEV  [4032.695919] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1 (usb)
UDEV  [4032.696594] unbind   /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4032.697118] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4039.552281] add      /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)
UDEV  [4039.553868] add      /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0 (usb)
UDEV  [4039.556294] bind     /devices/pci0000:00/0000:00:14.0/usb1/1-11 (usb)

The strange thing is that no event are recorded when the screen shuts down. In fact the event list stops with a bind line. Here the usb1/1-11 details:

$ lsusb -v -t | grep -A1 '11:'
    |__ Port 11: Dev 11, If 0, Class=Vendor Specific Class, Driver=, 480M
        ID 0e8d:201c MediaTek Inc.

My goal is to power on the screen only to show the wallpaper. I'm not interested about sensors measurations because simply I hate the black square. That's all. How I can do this? Why the screen shuts down by itself?

I’m having an issue with my laptop battery draining too quickly. I tried optimizing power consumption by installing **auto-cpufreq** using the --install command as per a guide I found. However, I haven’t noticed any difference in battery life—it still drains just as fast, even when I’m just coding in an IDE or browsing in Firefox. First of all, I also tried tlp, but it doesn't help either. - Could the issue be with the battery itself (e.g., wear and tear)? How can I check - What other power optimization methods can I - Could Firefox or my IDE (e.g., VS Code) be causing the rapid drain? How can I check this? - Are there any alternatives to auto-cpufreq that might help? **My Setup:** **OS**: - Debian GNU/Linux 12 bookworm (x86-64) **Inteface**: - Cinnamon Version 5.6.8 **Processor**: - 11th Gen Intel© Core™ i5-1135G7 @ 2.40GHz × 4 I bought my laptop 2 years ago. Results of command: upower -i $(upower -e | grep BAT) | grep -E 'energy-full|capacity'

energy-full:         28.8827 Wh
    energy-full-design:  37.037 Wh
    capacity:            77.9834%

I am trying to use my old notebook to monitor some things, and I really don't need it to run past its lowest frequency, since it will only gather data every few minutes or so and relay it. But the problem is, I don't want it to sleep either. I am using pm-powersave true but after installing it, suddenly the PC sleeps very often and the ping only replied a few seconds after I press the button at the notebook. I've tried with cable and wifi. The OS is Ubuntu Server 23.04, running on an old Compaq Presario with Core Duo processor. Is there a way to prevent this? What is the correct way to keep it at minimum frequency but stays awake?