Description of problem: Power profile is always in Power Saver, cannot click on performance, can click on Balanced but it does not activate this mode and switch back to Power Saver Version-Release number of selected component (if applicable): 0.12-2.fc37 How reproducible: All the time for maybe 3-4 days now (we're January 26) Steps to Reproduce: 1. Turn on computer 2. It always starts/stays in Power Saver 3. Cannot switch to other modes Actual results: Stays in Power Saver Expected results: Use Performance or balance as it makes my laptop super slow Additional info: > journalctl -b 0 -g power Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [PXP] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [PUBS] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [BTPR] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [PXP] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [MRST] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [DRST] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [PXP] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [V0PR] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [V1PR] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [V2PR] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [WRST] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [TBT0] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [TBT1] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [D3C] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [PIN] Jan 26 15:53:32 romeo kernel: ACPI: PM: Power Resource [PINP] Jan 26 15:53:32 romeo kernel: Low-power S0 idle used by default for system suspend Jan 26 15:53:32 romeo kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 Jan 26 15:53:32 romeo kernel: ACPI: button: Power Button [PWRB] Jan 26 15:53:32 romeo kernel: usb: port power management may be unreliable Jan 26 15:53:38 romeo systemd[1]: Starting power-profiles-daemon.service - Power Profiles daemon... Jan 26 15:53:38 romeo systemd[1]: Starting upower.service - Daemon for power management... Jan 26 15:53:38 romeo systemd-logind[881]: Watching system buttons on /dev/input/event2 (Power Button) Jan 26 15:53:38 romeo audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=power-profiles-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re> Jan 26 15:53:38 romeo systemd[1]: Started power-profiles-daemon.service - Power Profiles daemon. Jan 26 15:53:38 romeo boltd[956]: power: state located at: /run/boltd/power Jan 26 15:53:38 romeo boltd[956]: power: force power support: no Jan 26 15:53:38 romeo audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 26 15:53:38 romeo systemd[1]: Started upower.service - Daemon for power management. Jan 26 15:53:42 romeo kernel: wlp0s20f3: Limiting TX power to 23 (23 - 0) dBm as advertised by 04:42:1a:a2:fb:64 Jan 26 15:53:47 romeo /usr/libexec/gdm-wayland-session[1229]: dbus-daemon[1229]: [session uid=42 pid=1229] Activating service name='org.gnome.ScreenSaver' requested by ':1.23' (uid=42 pid=1396 comm="/usr/libexec/gsd-power" label="s> Jan 26 15:53:56 romeo systemd[1687]: Starting org.gnome.SettingsDaemon.Power.service - GNOME power management service... Jan 26 15:53:56 romeo systemd[1687]: Started org.gnome.SettingsDaemon.Power.service - GNOME power management service. Jan 26 15:53:56 romeo systemd[1687]: Reached target org.gnome.SettingsDaemon.Power.target - GNOME power management target.
I ran into this, too. The solution seemed to be booting the system with an older kernel. I have the problem with 6.1.7-200.fc37 I do not have the problem with 6.1.6-200.fc37 Hope this helps. Additional info: # lshw -short /W path Device Class Description =========================================================== system 21AKCTO1WW (LENOVO_MT_21AK_BU_Th /0 bus 21AKCTO1WW /0/1 memory 32GiB System Memory /0/1/0 memory 16GiB SODIMM DDR4 Synchronous 32 /0/1/1 memory [empty] /0/1/2 memory [empty] /0/1/3 memory [empty] /0/1/4 memory 16GiB SODIMM DDR4 Synchronous 32 /0/1/5 memory [empty] /0/1/6 memory [empty] /0/1/7 memory [empty] /0/12 memory 192KiB L1 cache /0/13 memory 128KiB L1 cache /0/14 memory 5MiB L2 cache /0/15 memory 18MiB L3 cache /0/16 memory 256KiB L1 cache /0/17 memory 512KiB L1 cache /0/18 memory 4MiB L2 cache /0/19 memory 18MiB L3 cache /0/1a processor 12th Gen Intel(R) Core(TM) i7-12 /0/1b memory 128KiB BIOS /0/100 bridge Intel Corporation /0/100/2 /dev/fb0 display Alder Lake-P Integrated Graphics /0/100/4 generic Alder Lake Innovation Platform F /0/100/6 bridge 12th Gen Core Processor PCI Expr /0/100/6/0 /dev/nvme0 storage SAMSUNG MZVL41T0HBLB-00BL7 /0/100/6/0/0 hwmon3 disk NVMe disk /0/100/6/0/2 /dev/ng0n1 disk NVMe disk /0/100/6/0/1 /dev/nvme0n1 disk 1024GB NVMe disk /0/100/6/0/1/1 volume 259MiB Windows FAT volume /0/100/6/0/1/2 /dev/nvme0n1p2 volume 15MiB reserved partition /0/100/6/0/1/3 /dev/nvme0n1p3 volume 15EiB Windows FAT volume /0/100/6/0/1/4 /dev/nvme0n1p4 volume 1999MiB Windows NTFS volume /0/100/6/0/1/5 /dev/nvme0n1p5 volume 1GiB EXT4 volume /0/100/6/0/1/6 /dev/nvme0n1p6 volume 780GiB EFI partition /0/100/7 bridge Alder Lake-P Thunderbolt 4 PCI E /0/100/7.2 bridge Alder Lake-P Thunderbolt 4 PCI E /0/100/a generic Platform Monitoring Technology /0/100/d bus Alder Lake-P Thunderbolt 4 USB C /0/100/d/0 usb1 bus xHCI Host Controller /0/100/d/1 usb2 bus xHCI Host Controller /0/100/d/1/1 multimedia Logitech StreamCam /0/100/d.2 bus Alder Lake-P Thunderbolt 4 NHI # /0/100/d.3 bus Alder Lake-P Thunderbolt 4 NHI # /0/100/14 bus Alder Lake PCH USB 3.2 xHCI Host /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/0/4 multimedia Integrated RGB Camera /0/100/14/0/6 bus 4-Port USB 2.0 Hub /0/100/14/0/6/1 input AKKO 3068BT /0/100/14/0/6/2 input USB Receiver /0/100/14/0/6/3 input LG Monitor Controls /0/100/14/0/a communication Bluetooth wireless interface /0/100/14/1 usb4 bus xHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3 wlp0s20f3 network Alder Lake-P PCH CNVi WiFi /0/100/15 bus Alder Lake PCH Serial IO I2C Con /0/100/15.1 bus Alder Lake PCH Serial IO I2C Con /0/100/16 communication Alder Lake PCH HECI Controller /0/100/1f bridge Alder Lake PCH eSPI Controller /0/100/1f.3 multimedia Alder Lake PCH-P High Definition /0/100/1f.4 bus Alder Lake PCH-P SMBus Host Cont /0/100/1f.5 bus Alder Lake-P PCH SPI Controller /0/100/1f.6 enp0s31f6 network Ethernet Connection (16) I219-V /0/0 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/3 generic PnP device LEN0071 /0/4 generic PnP device LEN030b /0/5 system PnP device PNP0c02 /0/6 system PnP device PNP0c02 /0/7 system PnP device PNP0c02 /0/8 system PnP device PNP0c02 /0/9 system PnP device PNP0c01 /1 power 5B10W51864
I can confirm that, seems to be a regression in a kernel, I've upgraded my Lenovo P1 gen2 yesterday from 6.1.6-200.fc37 to 6.1.8-200.fc37 and experience the same problem.
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2163301
I am having this problem as well. ThinkPad X1 Yoga Gen 6 Power mode options have become limited with upgraded kernel versions. In kernel 6.1.8, both balanced and performance options are not available for selection. Only Power Saver is available and selected by default. In kernel 6.1.7 only performance is not available for selection. Balanced and Power Saver are available and can be switched to either. In kernel 6.1.6 all three power modes are available and can be switched to without restriction.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.