Managing Kernel And Firmware Updates In elementary OS
Kernel and firmware updates are among the most important maintenance tasks on an elementary OS computer. They can improve hardware compatibility, close security weaknesses, fix suspend and Wi-Fi problems, and add support for newer processors, graphics devices, docking stations, and webcams. They also deserve a little care because a kernel is part of the operating system’s foundation, while firmware runs inside the hardware itself.
For most users, elementary OS presents updates through AppCenter in a straightforward way. Behind that simple interface are Ubuntu packages, Linux kernel images, hardware enablement components, and firmware services. Knowing how these parts fit together makes it easier to decide when to install an update, how to check what changed, and what to do if a restart exposes a problem.
What Kernel And Firmware Updates Actually Do
The Linux kernel controls communication between elementary OS and the computer’s hardware. It handles memory, processes, storage, networking, USB devices, graphics, power management, and much more. A kernel update may therefore resolve a fault that appears unrelated to software, such as a laptop refusing to wake from sleep or a Bluetooth adapter disconnecting after a few minutes.
Kernel updates normally install a new version beside the existing one rather than immediately deleting it. At startup, the bootloader can retain older kernels as fallback choices. This is useful when a new release causes trouble with a particular graphics driver, wireless chipset, or external monitor. Once the newer kernel has started successfully, the older version can usually remain until routine package maintenance removes obsolete files.
Firmware is different. It is low-level code stored in a device such as a laptop’s embedded controller, SSD, Thunderbolt controller, Wi-Fi adapter, or UEFI system firmware. Linux can deliver some of these updates through fwupd, which uses the Linux Vendor Firmware Service, commonly known as LVFS. Other updates may still require a manufacturer utility, a bootable file, or a setting in the UEFI setup screen.
Preparing Before Installing Updates
Start by saving current work and connecting a laptop to reliable mains power. A firmware interruption can leave a device unusable, so a nearly empty battery is a poor starting point. It is also sensible to disconnect unnecessary USB accessories, especially storage devices and unusual hubs, while updating a laptop’s system firmware.
Keep a recent backup of documents, photos, browser data, and configuration files. A kernel update rarely damages personal data, but a failed storage operation, interrupted power event, or pre-existing disk problem can turn an ordinary update into a recovery job. For a desktop used for work in Brisbane or Perth, an external backup drive is useful; for a notebook carried between home and the office, a synchronised copy of important files provides an extra layer of protection.
Check that there is adequate free space in the root filesystem and in the EFI System Partition. Several kernels can occupy a few hundred megabytes or more, and a crowded EFI partition can prevent a bootloader update from completing. The graphical storage tools or the following command can show available space:
df -h
Before proceeding, close virtual machines, games, audio production software, and anything performing a long-running transfer over the NBN. Updates usually work while other applications are open, but a quiet system reduces the chance of losing unsaved work or interrupting a package process.
Using AppCenter For Ordinary System Updates
Open AppCenter and look for the available operating system updates. elementary OS separates operating system updates from many third-party applications, so the list may include kernel packages, security patches, drivers, libraries, and desktop components. Read the update details when they are available, then allow the process to finish without forcing the application to close.
A restart is often required after a kernel update. The new kernel is loaded during boot, not while the current session is running. If AppCenter reports that a restart is needed, choose a convenient time, save everything, and reboot normally. A system update that appears to have “done nothing” may simply be waiting for this restart.
The graphical route is the best default for beginners because it handles package dependencies and presents a familiar workflow. It is also appropriate for a family computer or a machine used by someone who prefers not to manage packages from a terminal. Users in Australia should remember that large updates can consume a noticeable amount of data on a mobile hotspot, even though ordinary fixed-line NBN plans commonly include generous or unlimited data.
When AppCenter reports an error, do not repeatedly click the update button. Note the package name and message, restart if the system requests it, and inspect the package state from Terminal. A half-completed package transaction is usually easier to repair before another large update is attempted.
Checking Kernel Packages From Terminal
Terminal provides a clearer view of what is installed and what is waiting. To refresh package information and install available updates, use:
sudo apt update
sudo apt full-upgrade
The first command downloads current package lists. The second can install, upgrade, or remove packages when required to complete a consistent update. Read the proposed changes before accepting them, particularly if the command wants to remove a package associated with a custom driver or desktop component.
You can see the running kernel with:
uname -r
This shows the kernel currently in use, not every kernel installed on the computer. To list installed kernel image packages, try:
dpkg -l 'linux-image*' | grep '^ii'
After installing a new kernel, reboot and run uname -r again. The version should reflect the new boot choice. If the machine behaves badly afterwards, restart and hold the appropriate key during boot to display the GRUB menu, then select an older kernel under the advanced options. The exact key timing varies by hardware and boot configuration, and Secure Boot can affect which entries are available.
Avoid manually deleting a kernel that is currently running. Automated package cleanup is safer because it can preserve the active kernel and a fallback version. Third-party modules built with DKMS, including some proprietary graphics and virtualisation drivers, may need to rebuild for each new kernel. A successful package installation followed by a black screen or missing Wi-Fi can therefore point to a module compatibility issue rather than a failed kernel download.
Managing Firmware With fwupd
First check whether the firmware service is installed and available:
fwupdmgr get-devices
This lists compatible devices and their current firmware versions. To refresh firmware metadata, run:
fwupdmgr refresh
Then look for available releases:
fwupdmgr get-updates
If an update is offered, the normal installation command is:
sudo fwupdmgr update
The computer may reboot into a vendor-provided update screen before returning to elementary OS. Do not power it off simply because the screen looks different from the usual desktop. Some devices take several minutes, display a progress bar, and restart more than once.
Support varies by manufacturer and model. Business laptops from vendors with LVFS participation often provide good coverage, while a recently released consumer machine may show no firmware at all. A missing update does not automatically mean the system is broken. It may mean that the manufacturer has not published a Linux-compatible package, the device is already current, or the update must be applied through UEFI.
For firmware that is not available through fwupd, read the hardware vendor’s instructions carefully. Do not apply a file intended for a similar model. This matters with laptops sold across the Australian market, where a retailer may use a slightly different regional model number from the one shown in an overseas support article. Record the exact model and current firmware version before downloading anything.
Handling Graphics, Wi-Fi, And Special Hardware
Kernel and firmware changes are most noticeable on hardware with complex drivers. Graphics cards, Wi-Fi adapters, Bluetooth chips, fingerprint readers, USB-C docks, and modern power-management controllers can depend on several layers at once. A kernel update may provide a new driver while a separate linux-firmware package supplies the device’s binary firmware.
If Wi-Fi disappears after an update, first test whether the adapter appears at all:
lspci -k
For USB Wi-Fi or Bluetooth hardware, use:
lsusb
These commands do not repair anything, but they help distinguish a missing device, an unloaded driver, and a network configuration problem. Keeping a wired Ethernet cable or a compatible USB adapter nearby is practical for a desktop in regional New South Wales or a home office where wireless troubleshooting would otherwise interrupt work.
Graphics problems deserve particular caution. Proprietary NVIDIA drivers, external GPUs, and hybrid graphics laptops can rely on kernel modules that must match the running kernel. Before a major system update, note the current driver configuration and ensure you know how to reach a text console if the graphical session fails. On a supported machine, the previous kernel may restore the desktop while a driver package is rebuilt or replaced.
Power management can also be affected by firmware. A laptop that loses battery unusually quickly, runs hot while suspended, or fails to wake may benefit from a BIOS or embedded-controller update, but those symptoms can also result from a changed kernel setting or a background process. Check one change at a time rather than applying several unofficial fixes together.
Accessibility devices and input methods should receive the same attention as other hardware. If a kernel or firmware update affects a touchscreen, keyboard, or input device, elementary OS’s accessibility tools can provide a temporary workaround; the guide to on-screen keyboard features explains relevant options for users who need alternative input.
Verifying The System After A Reboot
After restarting, test the functions that matter in daily use: Wi-Fi, Bluetooth, audio, suspend, external displays, camera access, printing, and USB storage. A quick check immediately after an update is more useful than discovering a fault during a video call or while travelling. If the machine is used for remote work from Adelaide or Hobart, confirm that VPN software and any smart-card or security-key hardware still operate.
Check the current kernel and recent boot messages with:
uname -r
journalctl -b -p warning
The journal command may show warnings that are harmless or unrelated. Look for repeated messages associated with a device you know is failing rather than treating every warning as evidence of damage. Firmware history can be reviewed with:
fwupdmgr get-history
If the new kernel causes a problem, select the older kernel from the boot menu and report the exact kernel version, hardware model, and relevant error. Avoid mixing a rollback with several driver downloads, registry-like tweak tools, or random commands copied from search results. Clear information makes community support much more effective.
Keep the working fallback until the updated system has survived normal use for a few days. Once the computer has passed several boots and sleep cycles, routine package maintenance can remove obsolete kernels when appropriate. Firmware generally does not offer the same easy rollback path, which is why checking the model, power supply, and vendor instructions before installation is so important.
A dependable update routine is simple: back up personal files, install operating-system updates through AppCenter or trusted APT commands, inspect firmware through fwupdmgr, reboot when requested, and test essential hardware. Kernel packages provide a recoverable path through older boot entries, while firmware updates require greater care because they change the device itself.
The key point to remember is that a successful update is more than a completed download: elementary OS should restart into the intended kernel, recognise the hardware, and continue doing the jobs you rely on.
