Language Selection

English French German Italian Portuguese Spanish

The New Firmware Manager: Updating firmware across Linux distributions

Filed under
GNU
Linux

Over the past few months, System76 has been developing a simple, easy-to-use tool for updating firmware on Pop!_OS and System76 hardware. Today, we’re excited to announce that you can now check and update firmware through Settings on Pop!_OS, and through the firmware manager GTK application on System76 hardware running other Debian-based distributions.

One of the issues we faced with with firmware management on Linux was the lack of options for graphical frontends to firmware management services like fwupd and system76-firmware. For fwupd, the only solutions available were to distribute either GNOME Software or KDE Discover, which is not viable for Linux distributions which have their own application centers, or frontends to package managers. For system76-firmware, an official GTK application existed, but it only supported updating System76 firmware, when it would be more ideal if it could support updating firmware from both services.

Read more

Also: System76 Unveils Their Firmware Manager Project For Graphically Updating Firmware

System76 Launches A Graphical Firmware Manager Compatible

  • System76 Launches A Graphical Firmware Manager Compatible With LVFS, All Ubuntu And Debian Distros

    It's a logical approach, and as someone focused on usability and elegantly onboarding all new Linux users, I think a graphical interface for updating firmware just makes sense.

    In order to benefit the larger Linux ecosystem, System76 has designed the Firmware Manager to be tookit-agnostic, although any frontend interaction will require Rust. The company also notes that its GTK widget can be implemented into any Ubuntu and Debian-based distributions not using GNOME. Critically, it supports both LVFS updates via fwupd as well as system76-firmware. It's also Wayland-compatible.

    You can view the full project notes and source code here.

    On a related note, if you're interested in why System76 uses its own firmware update service, I covered that earlier this year when the Asus "Shadowhammer" malware attack was making the rounds. Here's the relevant excerpt, detailing the decidedly Blockchain-inspired approach.

System76 announce their own graphical Firmware Manager

  • System76 announce their own graphical Firmware Manager

    System76, the company known for their Linux hardware and the Pop!_OS Linux distribution recently announced their new Firmware Manager.

    Supporting their own Pop!_OS as well as other Debian-based distributions like Ubuntu, their firmware tooling is aimed at easing the update process for users. Developed due to a "lack of options for graphical frontends to firmware management services", since previous tools for LVFS (Linux Vendor Firmware Service) relied on GNOME Software or KDE Discover "which is not viable for Linux distributions which have their own application centers, or frontends to package managers".

    They've created a GTK application for other distributions to use, as well as widget library with it integrated into GNOME Settings. They do say that the core of the framework is "toolkit-agnostic", enabling frontends to be written in any toolkit. System76 said their new Firmware Manager project supports updating from both LVFS and system76-firmware, along with being compatible with Wayland.

System76 Unveils Graphical Firmware Updater for All Debian-Based

  • System76 Unveils Graphical Firmware Updater for All Debian-Based Linux Distros

    American computer manufacturer System76 announced a new, cross-platform graphical utility that promises to make checking and updating your computer's firmware a lot more easier.

    The Firmware Manager project is System76's latest toy for the company's in-house built, Ubuntu-based Pop!_OS Linux distribution, but also compatible with any Debian-based GNU/Linux distro out there. Backed by the fwupd and system76-firmware CLI tools, the Firmware Manager utility will integrate into the GNOME Settings panel for easier firmware updating.

    "One of the issues we faced with firmware management on Linux was the lack of options for graphical frontends to firmware management services like fwupd and system76-firmware," said System76.

System76 Still Aiming To Be The Apple Of The Linux Space

  • System76 Still Aiming To Be The Apple Of The Linux Space With Software & Hardware

    System76 continues doing much more work on software these days as well as expanding their own hardware manufacturing capabilities. This is much more than they did a decade or even several years ago when they were just selling PCs/laptops pre-loaded with Ubuntu. As summed up by System76 founder and CEO, Carl Richell, their end game is much more Apple-esque.

    Following their announcement on Saturday of their new System76 Firmware Manager project, Carl tweeted, "This work continues our transition from a hardware company shipping a distro to a hardware company providing an integrated, holistic hardware and OS product. Still a lot of work ahead of us but manufacturing, open firmware, and Pop!_OS are pulling together."

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Debian: CUPS, LTS and Archival

  • Praise Be CUPS Driverless Printing

    Last Tuesday, I finally got to start updating $work's many desktop computers to Debian Buster. I use Puppet to manage them remotely, so major upgrades basically mean reinstalling machines from scratch and running Puppet. Over the years, the main upgrade hurdle has always been making our very large and very complicated printers work on Debian. Unsurprisingly, the blog posts I have written on that topic are very popular and get me a few 'thank you' emails per month. I'm very happy to say, thanks to CUPS Driverless Printing (CUPS 2.2.2+), all those trials and tribulations are finally over. Printing on Buster just works. Yes yes, even color booklets printed on 11x17 paper folded in 3 stapled in the middle.

  • Freexian’s report about Debian Long Term Support, August 2019

    Like each month, here comes a report about the work of paid contributors to Debian LTS.

  • Louis-Philippe Véronneau: Archiving 20 years of online content

    mailman2 is pretty great. You can get a dump of an email list pretty easily and mailman3's web frontend, the lovely hyperkitty, is well, lovely. Importing a legacy mailman2 mbox went without a hitch thanks to the awesome hyperkitty_import importer. Kudos to the Debian Mailman Team for packaging this in Debian for us. But what about cramming a Yahoo! Group mailing list in hyperkitty? I wouldn't recommend it. After way too many hours spent battling character encoding errors I just decided people that wanted to read obscure emails from 2003 would have to deal with broken accents and shit. But hey, it kinda works! Oh, and yes, archiving a Yahoo! Group with an old borken Perl script wasn't an easy task. Hell, I kept getting blacklisted by Yahoo! for scraping too much data to their liking. I ended up patching together the results of multiple runs over a few weeks to get the full mbox and attachments. By the way, if anyone knows how to tell hyperkitty to stop at a certain year (i.e. not display links for 2019 when the list stopped in 2006), please ping me.

Running The AMD "ABBA" Ryzen 3000 Boost Fix Under Linux With 140 Tests

Last week AMD's AGESA "ABBA" update began shipping with a fix to how the boost clock frequencies are handled in hopes of better achieving the rated boost frequencies for Ryzen 3000 series processors. I've been running some tests of an updated ASUS BIOS with this adjusted boost clock behavior to see how it performs under Linux with a Ryzen 9 3900X processor. The AGESA 1.0.0.3 ABBA update has an improved boost clock frequency algorithm along with changes to the idle state handling. This AGESA update should better position AMD Ryzen 3000 processors with the boost clock behavior expected by users with better hitting the maximum boost frequency and doing so more aggressively. Read more

Stable kernels 5.2.16, 4.19.74, and 4.14.145

  • Linux 5.2.16
    I'm announcing the release of the 5.2.16 kernel. All users of the 5.2 kernel series must upgrade. The updated 5.2.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.2.y and can be browsed at the normal kernel.org git web browser: https://git.kernel.org/?p=linux/kernel/git/stable/linux-s...
  • Linux 4.19.74
  • Linux 4.14.145

Linux Container Technology Explained (Contributed)

State and local governments’ IT departments increasingly rely on DevOps practices and agile development methodologies to improve service delivery and to help maintain a culture of constant collaboration, iteration, and flexibility among all stakeholders and teams. However, when an IT department adopts agile and DevOps practices and methodologies, traditional IT problems still need to be solved. One long-standing problem is “environmental drift,” when the code and configurations for applications and their underlying infrastructure can vary between different environments. State and local IT teams often lack the tools necessary to mitigate the effects of environmental drift, which can hamper collaboration and agility efforts. Read more