Fwupd 2.0.17 Released with Support for Lexar and Maxio NVMe SSDs – 9to5Linux

Fwupd 2.0.17 Released with Support for Lexar and Maxio NVMe SSDs – 9to5Linux

Share this article:


Fwupd 2.0.17 Released with Support for Lexar and Maxio NVMe SSDs – 9to5Linux

Fwupd 2.0.17 has been released today as the seventeenth maintenance update to the fwupd 2.0 series of this open-source Linux firmware update utility, adding support for more devices, new features, and bug fixes.

The fwupd 2.0.17 release adds support for updating the firmware on more hardware, including the ASUS CX9406 touch controller, Framework Copilot keyboard, Primax Ryder 2 mouse, Lexar and Maxio NVMe SSDs, Huddly C1, as well as Genesys GL352530 and GL352360.

This release adds the following features:

  • Add support for client-side phased update deployment
  • Add support for post-quantum signatures
  • Allow clearing the cache dirirectory
  • Allow fwupdtpmevlog to dump the raw eventlog data
  • Build a NVMe GUID derived from the serial number
  • Make fwupdtool extract work with deeply nested images
  • Parse VSS and FTW variable stores from EFI volumes
  • Reintroduce the FreeBSD CI target
  • Support very old versions of UDisks

This release fixes the following bugs:

  • Add ‘fwupdmgr hwids’ by exposing another daemon property
  • Add offline hashes for the Microsoft 20250902 dbx
  • Add the Framework-specific KEK and db hashes
  • Allow updating IFD BIOS region via parent MTD
  • Avoid showing reinstall prompts for composite devices
  • Clean up the fwupdtool lock file in all cases
  • Correctly match the correct historical composite component
  • Do not allow PK or KEK updates when system has a test key installed
  • Do not allow reinstalling when using ONLY_VERSION_UPGRADE
  • Do not require AC power to run the installed tests
  • Do not scan EFI volumes when constructing MTD BIOS devices
  • Ensure REGION is always set for MTD IFD children
  • Ensure SCSI instance IDs are valid ASCII values
  • Fix a critical warning when parsing invalid Jabra firmware
  • Fix an Ilitek parsing crash found when fuzzing
  • Fix an inotify race when refreshing metadata
  • Fix a pending-activation problem with Dell docking stations
  • Fix a potential hang when creating a chunk array with aligned sizes
  • Fix MTD emulation recording for PCI-backed devices
  • Fix the device order when the parent specifies install-parent-first
  • Fix the FLMSTR layout when reading IFD partitions
  • Fix the thunderbolt controller rushing to finalize before onlining retimers
  • Fix writing Intel GPU OptionROM data and OptionROM code
  • Flush stale events to make the Logitech Rallybar more reliable
  • Ignore all the Intel GPU MTD devices
  • Ignore errors when writing the last page of Dell dock firmware
  • Make an error message more specific
  • Modify the Dell dock needs-activation flag after updates are installed
  • Only add one devlink device for each PCI card
  • Parse the FMAP SBOM area as uSWID when required
  • Relax the USI dock DMC child device checks for new firmware
  • Revert back to the flashrom deprecated API as the new API is unusable
  • Rewrite the fwupdmgr manpage to be more useful
  • Use higher delay when update status for Logitech peripheral devices

Check out the release notes on the project’s GitHub page for more details about the changes included in fwupd 2.0.17, which you can download as a source tarball from the same location. Of course, it is recommended that you install fwupd from the stable software repositories of your GNU/Linux distribution.

Image credits: Fwupd project

Developing story…

LXQt 2.3 Desktop-Umgebung mit neuen Funktionen und Erweiterungen veröffentlicht – 9to5Linux

Related

Share the Post:

Related Posts