Hardware & Firmware

Documents the PowerShell cmdlet that returns True or False for whether Secure Boot is on. It needs an elevated prompt and prints 'Cmdlet not supported on this platform' on legacy BIOS machines.

Dell's guide to checking and updating BIOS. Firmware flashing carries risk: stay on AC power, suspend BitLocker, remove BIOS and drive passwords first, and use Dell's BIOS Recovery if an update fails.

Three ways to clear CMOS: the CLR_CMOS button, shorting the CLRTC pins, or removing the battery. Clearing erases BIOS settings and password; always power off and unplug first.

Intel's jumper and battery methods for resetting BIOS settings on boards with boxed desktop processors. Move the jumper from pins 1-2 to 2-3 (or remove the battery) for 1 to 5 minutes. Check your board manual first.

Introduces LVFS, where hardware vendors publish firmware, and fwupd, the daemon that installs it via clients such as fwupdmgr and GNOME Software. Firmware updates carry risk, so keep power connected.

Memtest86+ boots from USB and tests RAM more thoroughly than BIOS checks. Windows uses an installer, Linux and macOS write the image to the raw device (dd or balenaEtcher); on a Secure Boot violation add its CA or temporarily disable Secure Boot. Writing an image erases the USB drive.

The Rufus FAQ covers UEFI:NTFS and Secure Boot, and Windows 11 media options such as bypassing TPM requirements. Read the Secure Boot and certificate sections before changing firmware settings.

Explains what SMART attributes are (raw, normalised, worst, threshold), the difference between pre-fail and old-age types, and why raw values need vendor documentation. Includes a sample smartctl output.

Walkthrough of smartctl on Ubuntu: installing smartmontools, checking health, viewing attributes, and running short and long self-tests.

Explains what a TPM is and how keys are sealed to it (for example for BitLocker), plus anti-hammering lockout behaviour. Useful background before clearing a TPM or changing firmware.

Install Ventoy once on a USB drive, then copy as many ISO files as you like to it and pick one from the boot menu. Installation erases the drive, so back it up first.

How to recover an Apple silicon or T2 Mac with corrupted firmware by using DFU mode from a second Mac and choosing Revive (keeps data) before Restore (erases). Needs a data-capable USB-C cable and macOS 14+ on the host.

Explains that firmware checks the signature of each piece of boot software, and notes that the Secure Boot certificates issued in 2011 begin expiring in June 2026, so updates should be applied.

Explains UEFI Secure Boot on Debian: Microsoft-signed shim, Machine Owner Keys enrolled via mokutil --import and confirmed at boot, and how to disable validation. Changing Secure Boot affects boot security; keep recovery media handy.

Describes Secure Boot with Ventoy: the first boot shows a MOK manager to enroll a key, some machines need the Microsoft 3rd Party UEFI CA allowed, and otherwise Secure Boot must be turned off. Steps are shown mostly as an animation.