River Cam and Clare Bridge from Garret Hostel Bridge
River Cam and Clare Bridge from Garret Hostel Bridge by Christopher Hilton is licensed under CC-BY-SA 2.0

[UEFI-BIOS(add.!TODO)] Switching to UEFI Mode: Step-by-Step Let Me Guide You for Firmware Updates

#RAW! running this and got an error:

<blockquote class="mastodon-embed" data-embed-url="https://mastodon.social/@kevinmarville/114716156291405643/embed" style="background: #FCF8FF; border-radius: 8px; border: 1px solid #C9C4DA; margin: 0; max-width: 540px; min-width: 270px; overflow: hidden; padding: 0;"> <a href="https://mastodon.social/@kevinmarville/114716156291405643" target="_blank" style="align-items: center; color: #1C1A25; display: flex; flex-direction: column; font-family: system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Oxygen, Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', Roboto, sans-serif; font-size: 14px; justify-content: center; letter-spacing: 0.25px; line-height: 20px; padding: 24px; text-decoration: none;"> <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="32" height="32" viewBox="0 0 79 75"><path d="M63 45.3v-20c0-4.1-1-7.3-3.2-9.7-2.1-2.4-5-3.7-8.5-3.7-4.1 0-7.2 1.6-9.3 4.7l-2 3.3-2-3.3c-2-3.1-5.1-4.7-9.2-4.7-3.5 0-6.4 1.3-8.6 3.7-2.1 2.4-3.1 5.6-3.1 9.7v20h8V25.9c0-4.1 1.7-6.2 5.2-6.2 3.8 0 5.8 2.5 5.8 7.4V37.7H44V27.1c0-4.9 1.9-7.4 5.8-7.4 3.5 0 5.2 2.1 5.2 6.2V45.3h8ZM74.7 16.6c.6 6 .1 15.7.1 17.3 0 .5-.1 4.8-.1 5.3-.7 11.5-8 16-15.6 17.5-.1 0-.2 0-.3 0-4.9 1-10 1.2-14.9 1.4-1.2 0-2.4 0-3.6 0-4.8 0-9.7-.6-14.4-1.7-.1 0-.1 0-.1 0s-.1 0-.1 0 0 .1 0 .1 0 0 0 0c.1 1.6.4 3.1 1 4.5.6 1.7 2.9 5.7 11.4 5.7 5 0 9.9-.6 14.8-1.7 0 0 0 0 0 0 .1 0 .1 0 .1 0 0 .1 0 .1 0 .1.1 0 .1 0 .1.1v5.6s0 .1-.1.1c0 0 0 0 0 .1-1.6 1.1-3.7 1.7-5.6 2.3-.8.3-1.6.5-2.4.7-7.5 1.7-15.4 1.3-22.7-1.2-6.8-2.4-13.8-8.2-15.5-15.2-.9-3.8-1.6-7.6-1.9-11.5-.6-5.8-.6-11.7-.8-17.5C3.9 24.5 4 20 4.9 16 6.7 7.9 14.1 2.2 22.3 1c1.4-.2 4.1-1 16.5-1h.1C51.4 0 56.7.8 58.1 1c8.4 1.2 15.5 7.5 16.6 15.6Z" fill="currentColor"/></svg> <div style="color: #787588; margin-top: 16px;">Post by @kevinmarville@mastodon.social</div> <div style="font-weight: 500;">View on Mastodon</div> </a> </blockquote> <script data-allowed-prefixes="https://mastodon.social/" async src="https://mastodon.social/embed.js"></script>

#RAW! Then I should read the documentation:

https://github.com/fwupd

#RAW! Finally did:

Understanding the Warning

The warning message you’re seeing indicates that your system is running in legacy BIOS mode or UEFI BIOS in “CSM compatibility mode,” which prevents fwupd from updating UEFI firmware. This is because UEFI runtime functions are not available in these modes, and fwupd relies on these functions to schedule and apply firmware updates.

The warning message:

WARNING: UEFI firmware can not be updated in legacy BIOS mode

is telling you that your system is not in UEFI mode, and therefore, firmware updates for UEFI-based devices cannot be applied.

Options to Resolve the Issue

  1. Switch to UEFI Mode:
    If you want to update your UEFI firmware, you will need to switch your system from legacy BIOS mode to UEFI mode. This involves changing the boot mode in your system’s BIOS/UEFI settings. Here are the general steps:
  • Enter BIOS/UEFI Setup:
    Restart your computer and enter the BIOS/UEFI setup menu. This is usually done by pressing a specific key during startup (common keys include F2, Del, Esc, or F10).
  • Change Boot Mode:
    Look for an option related to boot mode, such as “Boot Mode,” “UEFI/Legacy Boot,” or “CSM.” Change this setting to “UEFI Only” or disable “CSM” (Compatibility Support Module).
  • Save and Exit:
    Save the changes and exit the BIOS/UEFI setup. Your computer will reboot.
  • Reinstall Operating System (if necessary):
    If you switch from legacy BIOS to UEFI mode, you may need to reinstall your operating system. UEFI mode requires an EFI System Partition (ESP), which is typically not created by Linux installers when installed in legacy mode.
  1. Disable the Warning:
    If you do not need to update UEFI firmware and want to disable this warning, you can add the following line to /etc/fwupd/fwupd.conf or /etc/fwupd/daemon.conf (depending on your fwupd version):
   DisabledPlugins=test;invalid;bios
  • Edit the Configuration File:
    Open the configuration file in a text editor with superuser privileges: sudo nano /etc/fwupd/fwupd.conf
  • Add the Line:
    Add the line DisabledPlugins=test;invalid;bios to the file.
  • Save and Exit:
    Save the file and exit the text editor.
  1. Recompile fwupd Without UEFI Support:
    If you prefer not to change your system’s boot mode and do not need UEFI firmware updates, you can recompile fwupd without UEFI support. This involves recompiling the fwupd package with the plugin_uefi=false option. This is a more advanced option and should be done with caution.

Summary

  • Switch to UEFI Mode: If you need to update UEFI firmware, switch your system to UEFI mode.
  • Disable the Warning: If you do not need UEFI firmware updates, add DisabledPlugins=test;invalid;bios to the fwupd configuration file.
  • Recompile fwupd: As a last resort, recompile fwupd without UEFI support.

Additional Information

  • fwupd Documentation: For more detailed information, refer to the fwupd documentation.
  • UEFI vs. Legacy BIOS: Understand the differences between UEFI and legacy BIOS modes and the implications for your system.

If you decide to switch to UEFI mode, ensure you have backups of your data and understand the process, as it may require reinstalling your operating system.


Discover more from Kevin Marville Insights

Subscribe to get the latest posts sent to your email.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)