From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}} {{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/change...")
 
No edit summary
Line 48: Line 48:


== Detailed Description ==
== Detailed Description ==
It is always a good practice to have the bootloaders updated as much as possible, at least in order to keep our systems not booting known bad bootloaders/software.
It is always a good practice to have the bootloaders updated as much as possible, at least in order to keep our systems not booting known bad bootloaders/software.  
Knowing when firmware update can be applied on a system, would avoid us having to handle the follow issues already detected:
 
Note that we are not updating the bootloader or the firmware here, we're just refreshing the firmware metadata to let users know where an update is available. We can not automatically update firmwares as this might involve reboots or need manual user action.
Knowing when firmware update can be applied on a system, would help/avoid us having to handle the follow issues already detected:
* [https://github.com/coreos/fedora-coreos-tracker/issues/1452 bootloaders denylisted in newer UEFI dbx]
* [https://github.com/coreos/fedora-coreos-tracker/issues/1452 bootloaders denylisted in newer UEFI dbx]
* [https://github.com/coreos/fedora-coreos-tracker/issues/1441 bootloader versions don't boot new aarch64 6.2+ kernels]
* [https://github.com/coreos/fedora-coreos-tracker/issues/1441 bootloader versions don't boot new aarch64 6.2+ kernels]
Note that we are not updating the bootloader or the firmware here, we're just refreshing the firmware metadata to let users know where an update is available.
 


== Feedback ==
== Feedback ==

Revision as of 17:20, 10 July 2023

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Guidance
For details on how to fill out this form, see the documentation.
Report issues
To report an issue with this template, file an issue in the pgm_docs repo.


Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

fwupd-refresh systemd service unit & timer are designed to regularly refresh the fwupd metadata and update the MOTD when new firmware updates can be applied on a system. We want to enable the fwupd-refresh.timer by default on IoT, CoreOS & Server editions so that users get reminded about firmware updates.

On desktops, firmware updates are generally coordinated by graphical applications such as GNOME Software or Plasma Discover so we will not enable it on those editions.

Owner

Current status

  • Targeted release: Fedora Linux 39
  • Last updated: 2023-07-10
  • [<will be assigned by the Wrangler> devel thread]
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

It is always a good practice to have the bootloaders updated as much as possible, at least in order to keep our systems not booting known bad bootloaders/software.

Note that we are not updating the bootloader or the firmware here, we're just refreshing the firmware metadata to let users know where an update is available. We can not automatically update firmwares as this might involve reboots or need manual user action.

Knowing when firmware update can be applied on a system, would help/avoid us having to handle the follow issues already detected:


Feedback

None so far.

Benefit to Fedora

Knowing when firmware updates can be applied on a system would make systems more reliable.

Scope

  • Proposal owners: Do the change required to enable fwupd-refresh.timer by default
  • Other developers: N/A
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Community Initiatives: N/A

Upgrade/compatibility impact

No impact, it is just a refresh to check about new firmware updates. It will be enabled for existing and new systems.

How To Test

Install a system on hardware that has an old firmware and check if you get a notification about a new firmware update on login in the MOTD.

User Experience

User will still have to manually update their firmware.

Dependencies

There are no dependencies

Contingency Plan

  • Contingency mechanism: Continue to ship things the way we ship them today
  • Contingency deadline: N/A
  • Blocks release? N/A

Documentation

N/A (not a System Wide Change)

Release Notes