BIOS 3.17 has been removed from beta and marked as a full release. It is now available for download here:
If you already installed the beta, you do not need to re-install.
We are happy to release a Beta of BIOS 3.17. This fixes several security issues, and improves battery life when DP/HDMI expansion cards are attached. If no major regressions are found, we will move this from Beta to full release after around a week of Community testing.
In the 3.10 release, some of the SMBIOS/ESRT metadata was encoded using 0x310, which was converted from hex to decimal, and became 3.16. So we had to skip a few versions ahead so that both the hex and decimal versions are both incremented correctly.
Updating via LVFS is available in the testing channel.
You can enable updates from testing by running:
fwupdmgr enable-remote lvfs-testing
Currently LVFS support has regressed due to fwupdmgr defaulting to file based capsule update on newer versions which is not supported in our BIOS.
Please set DisableCapsuleUpdateOnDisk=true in /etc/fwupd/uefi_capsule.conf before applying this update, otherwise the update will fail.
LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.
You can downgrade your firmware by running fwupdmgr downgrade and selecting the version you want to downgrade to. Please note that versions before 3.09 do not have the F3 one time boot file menu if you need to select an alternate bootloader after downgrading.
Instructions for EFI shell update:
- Extract contents of zip folder to a fat32 formatted USB drive.
- Disable secure boot in BIOS.
- Boot your system while pressing F12 and boot from the thumb drive.
- Let startup.nsh run automatically.
- System will reboot, you can unplug the thumb drive.
Warning! Update may cause your system to lose boot entries.
Updating the BIOS firmware will erase NVRAM boot variables, This can cause some alternate bootloaders or operating systems to fail to boot. This may impact users of rEFInd and some Linux distributions. If your system reboots after updating and cannot find a bootable device, you can manually select a boot device by using the one time boot menu by pressing F3 during boot, and manually selecting your EFI boot file. After this you may need to reinstall grub. See Lost GRUB dual boot after updating to BIOS 3.07 - #6 by XADE 41
This should not be an issue for Fedora/Ubuntu unless they are installed alongside a windows partition.
- Add BIOS menu option in advanced tab to enable standalone operation mode. This will modify onboard LED behavior to remove detection items for audio, touchpad, and display checks triggering debug LED behavior.
- Change low battery power LED behavior from red to white.
- Improve battery life when HDMI/DP expansion cards are attached but no display is connected.
- Add support for Capsule on Disk for future updates to improve LVFS compatibility.
- Fix pressing F12 key during boot will system hang when disabled BIOS quiet boot.
- Correct BIOS setup item TPM availability missing word.
- Thunderbolt devices may not be recognized on S4 resume in some cases, but will be detected by replugging the device.
- Touchpad PS2 fallback mode may not work if the user is in an OS that supports the SerialIO driver, and then restarts to an OS that does not support the SerialIO driver, such as trying to reboot into the Windows 11 Installation media. Workaround is to power off the laptop and perform a cold boot into the installer/os to enable PS2 mouse fallback mode if necessary.