Install a Mainline Linux Kernel Before Your Distro Ships It

Linux 7.3 lands with x86 platform driver work aimed at AMD Zen 6 hardware and RGB LED controls for Ryzen AI Halo handhelds and mini-PCs. It also carries a stack of laptop fixes touching webcams, fingerprint readers, and battery reporting across multiple vendors.

If your laptop has been fighting the kernel all year, that fix might already be merged, months before Ubuntu, Fedora, or Arch package it by default. Waiting for your distro's release cycle means waiting for a problem that's already solved upstream.

Here's how to grab a mainline kernel now, test it safely, and back out cleanly if it breaks something.

Step 1: Confirm You Actually Need Mainline

Before adding a new repository, check what your distro already ships. Run uname -r and compare it against the kernel.org mainline changelog for 7.3. If the laptop fix or Zen 6 platform patch you want landed in an earlier point release, your existing kernel-backports package might already cover it.

Mainline testing makes sense in three cases: you own very new AMD hardware and need Zen 6 platform enablement before your distro's next major kernel bump, you're on a Ryzen AI Halo device and want the new LED driver controls working now, or you're chasing a specific laptop regression fix that a Phoronix article or kernel mailing list thread confirms is merged. If none of those apply, stick with your stable kernel.

Step 2: Install Mainline Builds on Ubuntu

Canonical's kernel team maintains the Ubuntu Kernel PPA for exactly this purpose: testing upstream kernels before they ship. It's the simplest path available to Ubuntu users.

1. Visit kernel.ubuntu.com/mainline and find the 7.3 build matching your architecture.
2. Download the generic, headers, and modules .deb files for your CPU type (amd64 in almost all cases).
3. Install with sudo dpkg -i *.deb from the download directory.
4. Reboot and select the new kernel from the GRUB advanced options menu if it doesn't boot by default.

This method skips DKMS entirely for stock kernel testing, which makes it the safest option. You're installing a self-contained kernel package, not rebuilding modules against your current one.

Step 3: Install Mainline Builds on Fedora

Fedora's route runs through COPR, the community package repository system. The kwizart and various kernel-vanilla COPR repos track mainline releases closely, often within a day or two of an -rc tag.

Enable the repo with sudo dnf copr enable kwizart/kernel-vanilla (check COPR's search for the current active repo name, since maintainers occasionally rename or rotate these), then run sudo dnf update kernel* to pull the 7.3 build. Fedora's dnf registers it as a separate boot entry, so your existing kernel stays intact. This pairs well with fix rtl8723bs wi-fi not working on linux: full guide explained.

Fedora also ships akmods for module rebuilding, which matters if you run Nvidia's proprietary driver or other out-of-tree modules. More on that risk below.

Step 4: Install Mainline Builds on Arch

Arch users have it easiest and hardest at the same time. The linux-mainline AUR package tracks upstream release candidates and stable tags, and a normal AUR helper like yay -S linux-mainline gets you a 7.3 build fast.

The catch is that Arch's rolling model means you're stacking a bleeding-edge kernel on top of a bleeding-edge everything else. Pin your current working kernel in your bootloader before installing the new one, and don't run pacman -Syu immediately after switching kernels. Isolate variables so you know what caused any new instability. This pairs well with go deeper on freebsd 14.5-rc1: upgrade now or wait for ga?.

Step 5: Understand the DKMS Risk Before You Reboot

Dynamic Kernel Module Support (DKMS) rebuilds out-of-tree drivers — Nvidia's proprietary driver, ZFS, VirtualBox host modules, some Wi-Fi drivers — against whatever kernel you're running. Mainline kernels change internal APIs between versions, sometimes significantly, and DKMS builds against 7.3 can fail silently or produce a module that loads but behaves incorrectly.

Check dkms status after installing a mainline kernel and before rebooting into it if possible. If a module shows as failed rather than installed, you have two choices: fix it by checking the vendor's driver repo for a patched version, or accept that the feature will be missing until you roll back or the driver catches up. Nvidia driver users especially should expect a lag of days to weeks between a new mainline kernel and a compatible proprietary driver build.

ZFS is the other common casualty. If you run ZFS on root or for critical storage, don't test mainline kernels on that machine until you've confirmed OpenZFS supports the target kernel version. Test on a spare machine or VM first.

Step 6: Boot Into the New Kernel and Verify the Fix

Reboot, select the 7.3 kernel from your bootloader menu, and confirm you're running it with uname -r. Then verify the specific thing you came for.

Also read: context: why linux kernel cve counts are skyrocketing in 2025

For Ryzen AI Halo LED support, check ls /sys/class/leds/ for new device entries and test control through your usual RGB tool or a simple echo write to the brightness file. For laptop-specific fixes, whether it's a touchpad, webcam, or battery reporting issue, run through the exact use case that was broken and confirm it behaves normally now. For Zen 6 platform prep, there's less to visually verify unless you own the hardware, since much of this is enablement code that pays off once retail systems ship.

Check dmesg | grep -i error and journalctl -b -p err for anything new and alarming. New kernels sometimes introduce noisy but harmless warnings alongside real regressions, so read the context rather than panicking at the first red line.

Step 7: Roll Back Cleanly if Something Breaks

This is why you never remove your working kernel first. On Ubuntu and Fedora, reboot and pick your previous kernel from the GRUB menu, then remove the mainline packages with sudo dpkg -r or sudo dnf remove kernel-<version> once you've confirmed you're back on stable. On Arch, edit your bootloader entry or run grub-mkconfig again after uninstalling linux-mainline so GRUB regenerates without the broken entry.

If the machine won't boot into the new kernel at all, most bootloaders default to showing an advanced or previous-versions submenu automatically. That's your out. Keep at least one known-good kernel installed at all times during any testing window, and don't clear old kernel packages until you're confident the new one is stable for your daily workflow.

What to Expect Next

Running mainline for a few weeks gives you an early read on whether Linux 7.3's laptop and AMD platform work actually helps your hardware. It also puts you in a position to report bugs upstream while they're still fixable, before the general release.

Once your distro's stable kernel catches up, usually within one to two release cycles, you can drop back to the supported package and let your distro's maintainers carry the update burden again.