Bug 2443028

Summary: Enable intel-lpmd by default
Product: [Fedora] Fedora Reporter: Neal Gompa <ngompa13>
Component: fedora-releaseAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 44CC: alciregi, awilliam, fedoraproject, kevin, lruzicka, mboddu, pbrobinson, samyak.jn11, sgallagh, thrcka, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard: AcceptedFreezeException
Fixed In Version: fedora-release-44-0.15 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-03-06 06:00:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2362358    

Description Neal Gompa 2026-02-26 15:36:26 UTC
The intel-lpmd service needs to be enabled by default for current generation Intel laptops to have meaningfully decent power management.

Reproducible: Always

Reference: https://forge.fedoraproject.org/workstation/tickets/issues/493

Comment 1 Fedora Blocker Bugs Application 2026-02-26 15:37:15 UTC
Proposed as a Freeze Exception for 44-beta by Fedora user ngompa using the blocker tracking app because:

 This is required to ensure intel-lpmd is enabled by default on Workstation and KDE images.

Comment 2 Fedora Update System 2026-02-26 15:39:46 UTC
FEDORA-2026-38b0efc7ab (fedora-release-44-0.12) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-38b0efc7ab

Comment 3 Stephen Gallagher 2026-02-26 15:48:37 UTC
Note the above comment is incorrect due to a miss-click on my part; the actual version being submitted as an update is fedora-release-44-0.15

Comment 4 Fedora Update System 2026-02-27 01:36:36 UTC
FEDORA-2026-38b0efc7ab has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-38b0efc7ab`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-38b0efc7ab

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Adam Williamson 2026-02-27 02:10:30 UTC
+3 in https://pagure.io/fedora-qa/blocker-review/issue/2058 , marking accepted FE.

Comment 6 Lukas Ruzicka 2026-03-05 13:01:08 UTC
mvasicek@fedora:~$ sudo systemctl status intel_lpmd.service 
○ intel_lpmd.service - Intel Linux Energy Optimizer (lpmd) Service
     Loaded: loaded (/usr/lib/systemd/system/intel_lpmd.service; enabled; prese>
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
  Condition: start condition unmet at Thu 2026-03-05 13:42:00 CET; 5min ago
             └─ ConditionVirtualization=no was not met
       Docs: man:intel_lpmd(8)

bře 05 13:42:00 fedora systemd[1]: intel_lpmd.service - Intel Linux Energy Opti>
mvasicek@fedora:~$ 

intel_lpmd.service is enabled by default on RC1.2, however it is not started. As the report says it has to be "enabled", I think we can verify this.

Comment 7 Stephen Gallagher 2026-03-06 01:13:06 UTC
(In reply to Lukas Ruzicka from comment #6)
> mvasicek@fedora:~$ sudo systemctl status intel_lpmd.service 
> ○ intel_lpmd.service - Intel Linux Energy Optimizer (lpmd) Service
>      Loaded: loaded (/usr/lib/systemd/system/intel_lpmd.service; enabled;
> prese>
>     Drop-In: /usr/lib/systemd/system/service.d
>              └─10-timeout-abort.conf
>      Active: inactive (dead)
>   Condition: start condition unmet at Thu 2026-03-05 13:42:00 CET; 5min ago
>              └─ ConditionVirtualization=no was not met
>        Docs: man:intel_lpmd(8)
> 
> bře 05 13:42:00 fedora systemd[1]: intel_lpmd.service - Intel Linux Energy
> Opti>
> mvasicek@fedora:~$ 
> 
> intel_lpmd.service is enabled by default on RC1.2, however it is not
> started. As the report says it has to be "enabled", I think we can verify
> this.

Notice that it wasn't started because "ConditionVirtualization=no was not met". In other words, this service is only useful on non-virtualized (bare metal) systems. Please verify that it starts correctly on a physical system, if possible.

Comment 8 Fedora Update System 2026-03-06 06:00:09 UTC
FEDORA-2026-38b0efc7ab (fedora-release-44-0.15) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.