Torvalds releases Linux 7.1 with i486 removal, Steam Deck audio fix, NTFS rewrite

Linus Torvalds released Linux 7.1 Sunday after a final week of driver, networking, sound, tracing, and small subsystem fixes.

Torvalds said the last release candidate carried no major surprises, though his travel schedule may affect the Linux 7.2 merge window. Developers can pull the source from the official kernel Git tree. Most users should wait for Fedora, Arch, Debian, Ubuntu, or another distribution to package, test, and ship the kernel.

Platform update

Linux 7.1 removes i486 support, ending mainline support for Intel's 486 line more than three decades after Intel introduced the chip. That change gives x86 maintainers less compatibility code to carry through scheduler, locking, memory, and boot paths.

The release also includes a Steam Deck audio fix. Valve's handheld runs SteamOS on Linux, so kernel sound fixes can reach users through SteamOS updates after Valve tests and packages them.

The NTFS work matters for anyone who moves drives between Windows and Linux. Linux users have leaned on NTFS-3G in user space or the in-kernel NTFS3 driver for read and write support. Linux 7.1 brings a reworked NTFS path that aims to improve maintainability and performance inside the kernel.

Developer impact

Distribution maintainers get the first hard job. They need to decide how fast to pull 7.1 into rolling, testing, and stable channels. Arch users may see it before Ubuntu LTS users. Enterprise distributions will take more time because kernel updates affect graphics stacks, secure boot signing, storage, virtualization, and vendor driver support.

The i486 removal affects retro systems, lab builds, and niche embedded deployments. Developers who still target 486-class hardware should pin an older supported kernel branch, audit toolchains, and avoid assuming mainline x86 will keep that floor. Pentium-class and newer systems remain the practical baseline for modern Linux distributions.

Steam Deck users should treat the audio fix as a platform update rather than a manual kernel project. If you maintain a handheld-focused Linux image, test speaker output, headphone routing, suspend and resume, Bluetooth audio, and game audio under Proton. Sound regressions often sit at the edge between kernel drivers, PipeWire, ALSA user space, and device firmware.

The NTFS changes carry the broadest cross-platform impact. Developers who dual-boot Windows and Linux, run Linux workstations in Windows-heavy shops, or support external drives for customers should test common cases: large file copies, sparse files, permissions, hibernated Windows volumes, removable media, and recovery after surprise disconnects.

Migration

Kernel builders can fetch 7.1 from kernel.org or the Torvalds Git repository. Use your distribution's config as a base, then review storage, sound, GPU, and filesystem options before you build.

Developers with production machines should wait for distribution packages. Kernel releases need downstream testing against initramfs generation, bootloader hooks, DKMS modules, NVIDIA drivers, ZFS, secure boot, and firmware packages. A clean upstream build can still break a daily workstation if one of those pieces expects a distribution patch.

For NTFS, test before you trust a shared disk. Mount a copy of a Windows volume, run file create, rename, delete, copy, and checksum tests, then check the disk from Windows. Teams that ship appliances or recovery tools should keep NTFS-3G in fallback plans until their test matrix covers Linux 7.1.

For old x86 hardware, freeze the kernel line before you upgrade user space. Document the last working kernel, compiler, libc, and bootloader versions. If the machine has a real job, treat it as a legacy platform with pinned packages.

Linux 7.1 gives distribution maintainers useful cleanup and fixes. Users get the release after their maintainers test it against real hardware, which remains the right path for a kernel that touches CPU support, storage, and audio.