Linux Kernel 6.18: The LTS Kernel That Finally Gets It
Linux kernel 6.18 arrives as the 2025 LTS with Snapdragon X1 mainline support, haptic touchpads, and Bcachefs removal. Let’s see what…
Linux kernel 6.18 arrives as the 2025 LTS with Snapdragon X1 mainline support, haptic touchpads, and Bcachefs removal. Let’s see what matters.
One kernel release. Four major laptop platforms. Zero Bcachefs. Linux 6.18 just dropped as the final LTS kernel of 2025, and after two decades of watching kernel releases come and go, this one actually moves the needle for hardware support. But it also reveals something uncomfortable about how kernel governance handles dissent.
Let me break down what matters, what does not, and why the Bcachefs removal is more significant than most headlines suggest.
The Hardware Story Nobody Expected
Here is something I rarely say about kernel releases: the hardware support in 6.18 is genuinely impressive.
Snapdragon X1 Elite laptops from Dell, HP, and Lenovo now have mainline support. If you have been following the ARM laptop saga, you know this is significant. I have watched ARM on desktop fumble for over a decade. Microsoft tried with Surface RT (disaster), Qualcomm tried with Always Connected PCs (battery life great, software support abysmal), and Apple finally cracked it with M1.
Now Linux is catching up on the ARM laptop front. The X1 Elite support means you can actually run a proper Linux distribution on these machines without fighting proprietary blobs at every turn.
Apple M2 Pro, Max, and Ultra device trees also landed. The Asahi Linux team has been doing incredible work here, and seeing their efforts flow into mainline validates years of reverse engineering. This is not just about running Linux on your MacBook (though you can). It is about proving that community-driven hardware support can match or exceed vendor-provided drivers.
If you have been skeptical about ARM laptops for serious work, 6.18 might be the kernel that changes your mind.
Haptic Touchpads: The Feature You Did Not Know You Needed
Modern laptops are shipping with haptic touchpads. No physical click mechanism, just force sensors and actuators that simulate the click. Apple has been doing this for years, and now Windows laptops are following.
Linux was behind. Not anymore.
The 6.18 kernel adds proper haptic touchpad support, which means Force Touch style trackpads will actually work correctly. For those of us who switched from macOS to Linux (guilty as charged after 20 years on Apple hardware), this matters more than you might think. The tactile feedback on these touchpads is genuinely good when properly supported.
Will most users notice? Probably not. But if you are running Linux on a premium laptop with a haptic touchpad, you were stuck with either no feedback or weird workarounds. Now it just works.
I am a human writer who gets motivated to write more with your support! You don’t need to pay. I just need your clap 👏 if you like my story and comment ✍️ if you want to say something. You can follow me on Medium, LinkedIn, Instagram, and X.
The Nouveau GSP Firmware Switch
Here is where things get interesting from an architecture perspective.
Nouveau, the open source NVIDIA driver, now defaults to GSP (GPU System Processor) firmware for supported cards. This is a fundamental shift in how the driver operates.
Previously, Nouveau tried to do everything itself through reverse engineering. With GSP, NVIDIA’s own firmware handles low-level GPU initialization and management. Nouveau essentially becomes a shim that communicates with the GSP.
Why does this matter?
Performance improves significantly. Power management becomes more reliable. Features that were impossible to reverse engineer (like proper reclocking on newer cards) suddenly work because the proprietary firmware handles them.
The open source community resisted using NVIDIA firmware for years. Understandably so. But users need working hardware today, not philosophical victories tomorrow.
The GSP default is a pragmatic compromise. It works. That counts for something.
Tyr: Rust Comes to GPU Drivers
The Tyr Rust GPU driver for ARM Mali GPUs got upstreamed. This is notable for two reasons.
First, it is a Rust driver in the kernel. The Rust-in-kernel debate has been contentious (we will get to Bcachefs in a moment), but Tyr represents the approach working as intended. A new driver, written in Rust, merged without drama.
Second, ARM Mali GPUs are everywhere. Phones, tablets, embedded systems, Chromebooks. Having a proper open source driver upstream means better support for a huge range of devices that previously relied on binary blobs.
The driver is experimental. Do not expect to game on your Mali GPU just yet. But the foundation is there, and the merge process demonstrates that Rust can coexist with C in the kernel without the world ending.
The Bcachefs Removal: Governance Lessons
Now for the uncomfortable part.
Bcachefs was completely removed from the kernel. 117,000 lines of code, gone. If you are not familiar, Bcachefs is (was?) a next-generation filesystem that promised the best of ZFS, Btrfs, and ext4 combined. Copy-on-write, checksumming, compression, caching, and modern design principles.
The removal was not technical. The filesystem works. The issue was governance.
Kent Overstreet, the lead developer, had ongoing conflicts with kernel maintainers over development practices, merge processes, and communication style. These disputes escalated to the point where Linus Torvalds removed the entire subsystem.
Here is what 20+ years of coordinating technology professionals has taught me about this situation:
Technical excellence does not excuse process violations. I have seen brilliant engineers torpedo their own projects by refusing to work within organizational constraints. The code can be perfect, but if you cannot collaborate with the people responsible for merging and maintaining it, your code does not ship.
Bcachefs is a cautionary tale for any developer who thinks their technical contributions exempt them from community standards. They do not. They never have. The kernel is not just a codebase; it is a community with established norms. Violate those norms consistently enough, and the community will protect itself.
Does this mean Bcachefs is dead? Not necessarily. The code exists. Forks can happen. But mainline inclusion requires working with mainline maintainers, and that relationship appears broken.
Btrfs Block Size: The Quiet Revolution
Speaking of filesystems, Btrfs gained experimental support for block sizes greater than page size. This sounds obscure. It matters.
Modern NVMe drives have large internal block sizes. When your filesystem’s block size matches the drive’s capabilities, you get better performance and less write amplification. Until now, Btrfs was limited to page-sized blocks (4KB on most systems), which left performance on the table.
The feature is experimental. Do not use it on production systems yet. But it signals that Btrfs development continues, which matters given the Bcachefs situation. If you wanted a next-generation Linux filesystem, Btrfs just became a safer long-term bet.
LTS Means Something
Kernel 6.18 will receive support through December 2027. That is two years of security patches and bug fixes.
For those of us architecting systems that need to run reliably for extended periods, LTS kernels are the only reasonable choice. You do not want to chase kernel upgrades on production systems. You want stability, security patches, and predictability.
If you are deploying new Linux systems in late 2025 or 2026, target 6.18. The hardware support is excellent, the LTS commitment is solid, and the feature set is mature enough for production use.
The Takeaway
Linux 6.18 is a strong kernel release. Hardware support for ARM laptops finally reaches a usable state. Haptic touchpads work. GPU support improves across multiple vendors. Btrfs evolves.
But the Bcachefs removal reminds us that open source development is as much about people as code. Technical excellence matters. So does collaboration.
After two decades in this industry, I have seen countless technically superior projects fail because their developers could not work within community norms. Do not let that happen to your work.
Have you been tracking the kernel 6.18 changes? Planning to run it on ARM hardware? Share your experiences in the comments.
I am a human writer who gets motivated to write more with your support! You don’t need to pay. I just need your clap 👏 if you like my story and comment ✍️ if you want to say something. You can follow me on Medium, LinkedIn, Instagram, and X.