<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Linux on KnightLi Blog</title>
        <link>https://www.knightli.com/en/categories/linux/</link>
        <description>Recent content in Linux on KnightLi Blog</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en</language>
        <lastBuildDate>Sun, 26 Apr 2026 19:35:57 +0800</lastBuildDate><atom:link href="https://www.knightli.com/en/categories/linux/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Ubuntu 26.04 LTS GPU and Hardware Updates: CUDA, ROCm, DPC&#43;&#43;, and More Platform Changes</title>
        <link>https://www.knightli.com/en/2026/04/26/ubuntu-26-04-lts-gpu-hardware-ai-updates/</link>
        <pubDate>Sun, 26 Apr 2026 19:35:57 +0800</pubDate>
        
        <guid>https://www.knightli.com/en/2026/04/26/ubuntu-26-04-lts-gpu-hardware-ai-updates/</guid>
        <description>&lt;p&gt;If the previous article worked as a desktop-focused overview of &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt;, this one is better read as its hardware and compute-side follow-up. In this &lt;code&gt;26.04&lt;/code&gt; cycle, Ubuntu pushed a number of AI, GPU computing, and platform compatibility changes into the main archive or formal support scope.&lt;/p&gt;
&lt;p&gt;The short version is this: the most important part of this round is not just desktop and kernel upgrades, but that &lt;strong&gt;Ubuntu is bringing Intel, NVIDIA, and AMD GPU computing stacks into the distribution in a more systematic way&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id=&#34;1-intel-dpc-and-related-components-are-now-in-ubuntu-archive&#34;&gt;1. Intel DPC++ and related components are now in Ubuntu Archive
&lt;/h2&gt;&lt;p&gt;Starting with &lt;code&gt;26.04&lt;/code&gt;, Intel&amp;rsquo;s open-source &lt;code&gt;oneAPI DPC++&lt;/code&gt; compiler is available directly from Ubuntu Archive for building &lt;code&gt;SYCL&lt;/code&gt; code. Its runtime also includes adapters for Intel GPUs.&lt;/p&gt;
&lt;p&gt;Two related components are also now available from Ubuntu repositories:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;oneDPL&lt;/code&gt;, the DPC++ library, which provides higher-productivity developer APIs&lt;/li&gt;
&lt;li&gt;&lt;code&gt;oneDNN&lt;/code&gt;, built with &lt;code&gt;dpclang-6&lt;/code&gt;, which can run on Intel GPUs&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That means if you are already working with &lt;code&gt;SYCL&lt;/code&gt;, heterogeneous computing, or AI workloads on Intel GPUs, Ubuntu now offers a more direct path instead of forcing you to maintain a separate external stack for everything.&lt;/p&gt;
&lt;p&gt;Ubuntu also calls out one practical requirement: users need to be in the &lt;code&gt;render&lt;/code&gt; group to actually use these Intel GPU-related capabilities.&lt;/p&gt;
&lt;h2 id=&#34;2-the-nvidia-cuda-toolkit-can-now-be-installed-directly-with-apt&#34;&gt;2. The NVIDIA CUDA toolkit can now be installed directly with &lt;code&gt;apt&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;For many developers and operators, this may be one of the most immediately useful changes in the notes.&lt;/p&gt;
&lt;p&gt;Starting with &lt;code&gt;26.04&lt;/code&gt;, the &lt;code&gt;NVIDIA CUDA toolkit&lt;/code&gt; can now be installed directly from Ubuntu Archive:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo apt install cuda-toolkit
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;The value here is bigger than just saving a few setup steps.&lt;/p&gt;
&lt;p&gt;For developers shipping software on Ubuntu, this new model means they can simply declare a dependency on the &lt;code&gt;CUDA runtime&lt;/code&gt;, while Ubuntu manages installation and compatibility at the distribution level. That makes CUDA feel more like a native system capability on Ubuntu, rather than an extra software layer that always has to be maintained separately.&lt;/p&gt;
&lt;h2 id=&#34;3-amd-rocm-710-is-now-in-universe&#34;&gt;3. AMD ROCm 7.1.0 is now in Universe
&lt;/h2&gt;&lt;p&gt;On the AMD side, Ubuntu Universe now includes &lt;code&gt;ROCm 7.1.0&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;These libraries mainly provide:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;backend infrastructure for AI training and inference on AMD GPUs&lt;/li&gt;
&lt;li&gt;software foundations for machine learning and high performance computing&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Canonical also notes that ROCm-related components are continuously tested in its CI/CD pipeline. Beyond &lt;code&gt;autopkgtests&lt;/code&gt;, that includes several user-space applications such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;llama.cpp&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;pytorch&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Blender&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Lemonade Server&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That detail matters, because it shows Ubuntu is not just dropping packages into the archive. It is validating ROCm as a maintainable software stack.&lt;/p&gt;
&lt;h2 id=&#34;4-the-bigger-story-is-that-all-three-gpu-ecosystems-are-landing&#34;&gt;4. The bigger story is that all three GPU ecosystems are landing
&lt;/h2&gt;&lt;p&gt;It becomes easier to see the direction of &lt;code&gt;26.04&lt;/code&gt; when &lt;code&gt;DPC++&lt;/code&gt;, &lt;code&gt;CUDA&lt;/code&gt;, and &lt;code&gt;ROCm&lt;/code&gt; are viewed together:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Intel: bringing &lt;code&gt;SYCL&lt;/code&gt; / &lt;code&gt;oneAPI&lt;/code&gt; components into official repositories&lt;/li&gt;
&lt;li&gt;NVIDIA: giving the &lt;code&gt;CUDA toolkit&lt;/code&gt; a distribution-managed installation path&lt;/li&gt;
&lt;li&gt;AMD: shipping &lt;code&gt;ROCm 7.1.0&lt;/code&gt; in Universe with ongoing testing&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you work with these kinds of workloads on Ubuntu, this release will probably feel more relevant:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;local LLM inference&lt;/li&gt;
&lt;li&gt;GPU-accelerated training or fine-tuning&lt;/li&gt;
&lt;li&gt;Blender, scientific computing, and HPC&lt;/li&gt;
&lt;li&gt;development environments that need to move across different GPU platforms&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In other words, Ubuntu is no longer just &amp;ldquo;a system where you can install a GPU driver.&amp;rdquo; It is starting to carry a fuller &lt;strong&gt;user-space software stack for AI and GPU computing&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id=&#34;5-nvidia-dynamic-boost-is-enabled-by-default&#34;&gt;5. NVIDIA Dynamic Boost is enabled by default
&lt;/h2&gt;&lt;p&gt;Since &lt;code&gt;25.04&lt;/code&gt;, &lt;code&gt;Dynamic Boost&lt;/code&gt; has been enabled by default on supported NVIDIA laptops.&lt;/p&gt;
&lt;p&gt;The idea is straightforward: depending on system load, power can be shifted dynamically between the CPU and GPU. In gaming scenarios, that usually means giving more power to the GPU when needed to extract more performance.&lt;/p&gt;
&lt;p&gt;It only applies under two conditions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the laptop is connected to AC power&lt;/li&gt;
&lt;li&gt;the GPU load is high enough&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It does not engage while the system is running on battery.&lt;/p&gt;
&lt;h2 id=&#34;6-support-for-new-intel-integrated-and-discrete-gpus-keeps-moving-forward&#34;&gt;6. Support for new Intel integrated and discrete GPUs keeps moving forward
&lt;/h2&gt;&lt;p&gt;Ubuntu also continues expanding support for new Intel GPUs, including:&lt;/p&gt;
&lt;p&gt;Integrated:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Intel Core Ultra Xe2&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Intel Core Ultra Xe3&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Discrete:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Intel Arc 5 B570&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Intel Arc 5 B580&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Intel Arc Pro B50&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Intel Arc Pro B60&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Intel Arc Pro B65&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Intel Arc Pro B70&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Ubuntu also highlights several features already available around these devices:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;improved GPU and CPU ray tracing performance through Intel Embree, benefiting applications such as &lt;code&gt;Blender 4.2+&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;hardware video encoding for &lt;code&gt;AVC&lt;/code&gt;, &lt;code&gt;JPEG&lt;/code&gt;, &lt;code&gt;HEVC&lt;/code&gt;, and &lt;code&gt;AV1&lt;/code&gt; on &amp;ldquo;Battlemage&amp;rdquo; devices&lt;/li&gt;
&lt;li&gt;a new &lt;code&gt;CCS&lt;/code&gt; optimization in Intel Compute Runtime&lt;/li&gt;
&lt;li&gt;enabled debugging support for Intel Xe GPUs&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you are watching follow-up releases, &lt;code&gt;25.10&lt;/code&gt; also continues to bring in more capabilities, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;initial support for Intel&amp;rsquo;s next-generation client platform codenamed &lt;code&gt;Panther Lake&lt;/code&gt; through &lt;code&gt;Linux kernel 6.17&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;improved IOMMU, PCIe subsystem, and multi-GPU support&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Mesa 25.2.3&lt;/code&gt; enabling &lt;code&gt;VK_KHR_shader_bfloat16&lt;/code&gt; for Battlemage and Panther Lake&lt;/li&gt;
&lt;li&gt;&lt;code&gt;intel-media-driver 25.3.0&lt;/code&gt; adding Panther Lake decode support and &lt;code&gt;VP9&lt;/code&gt; encoding&lt;/li&gt;
&lt;li&gt;&lt;code&gt;intel-compute-runtime 25.31&lt;/code&gt; adjusting the Level Zero &lt;code&gt;USM&lt;/code&gt; pool and local device memory event allocation behavior&lt;/li&gt;
&lt;li&gt;&lt;code&gt;level-zero 1.24&lt;/code&gt; and &lt;code&gt;level-zero-raytracing 1.1.0&lt;/code&gt; bringing broader spec and RTAS extension support&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;7-suspend-and-resume-is-more-stable-on-nvidia-desktops-too&#34;&gt;7. Suspend and resume is more stable on Nvidia desktops too
&lt;/h2&gt;&lt;p&gt;Starting with &lt;code&gt;25.10&lt;/code&gt;, Ubuntu enables suspend-resume support in the proprietary &lt;code&gt;Nvidia&lt;/code&gt; driver to reduce corruption and freezing when waking a desktop system.&lt;/p&gt;
&lt;p&gt;This is not the most visible kind of change, but it matters a lot in everyday use, especially on desktops that stay on for long periods and frequently suspend and resume.&lt;/p&gt;
&lt;h2 id=&#34;8-arm-raspberry-pi-risc-v-and-ibm-z-also-get-harder-platform-level-changes&#34;&gt;8. ARM, Raspberry Pi, RISC-V, and IBM Z also get harder platform-level changes
&lt;/h2&gt;&lt;p&gt;Beyond the GPU software stack, the release notes also include several platform-level changes worth calling out separately.&lt;/p&gt;
&lt;h3 id=&#34;arm64-desktop-platforms&#34;&gt;ARM64 desktop platforms
&lt;/h3&gt;&lt;p&gt;Starting with &lt;code&gt;25.10&lt;/code&gt;, the &lt;code&gt;ARM64&lt;/code&gt; &lt;code&gt;linux-generic&lt;/code&gt; kernel provides broader desktop compatibility for ARM64 desktop platforms that boot through &lt;code&gt;UEFI&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&#34;a-new-raspberry-pi-boot-layout&#34;&gt;A new Raspberry Pi boot layout
&lt;/h3&gt;&lt;p&gt;One change introduced in &lt;code&gt;25.10&lt;/code&gt; and refined in &lt;code&gt;26.04&lt;/code&gt; is a new boot partition layout for Raspberry Pi systems.&lt;/p&gt;
&lt;p&gt;Its goal is to improve boot reliability: newly written boot assets are first &amp;ldquo;tested&amp;rdquo; before they are committed as the new &amp;ldquo;known good&amp;rdquo; set.&lt;/p&gt;
&lt;p&gt;The firmware date requirements are the part most users will want to remember:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Pi 3 / 3+ / CM3+ / Zero 2W&lt;/code&gt;: no additional action required, the boot firmware is in the image itself&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Pi 4 / 400 / CM4&lt;/code&gt;: boot firmware must be dated no earlier than &lt;code&gt;2022-11-25&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Pi 5 / 500 / CM5&lt;/code&gt;: boot firmware must be dated no earlier than &lt;code&gt;2025-02-11&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can check it with:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo rpi-eeprom-update
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;If the firmware is too old and you are using &lt;code&gt;Ubuntu 24.04 LTS&lt;/code&gt; or newer, you can update it like this:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;span class=&#34;lnt&#34;&gt;2
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo rpi-eeprom-update -a
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo reboot
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;h3 id=&#34;raspberry-pi-desktop-images-now-use-desktop-minimal&#34;&gt;Raspberry Pi desktop images now use desktop-minimal
&lt;/h3&gt;&lt;p&gt;Since &lt;code&gt;25.10&lt;/code&gt;, Ubuntu Desktop images for Raspberry Pi are based on &lt;code&gt;desktop-minimal&lt;/code&gt; rather than the full &lt;code&gt;desktop&lt;/code&gt; seed.&lt;/p&gt;
&lt;p&gt;Ubuntu gives a very concrete benefit here: the default app set is smaller, saving about &lt;code&gt;777MB&lt;/code&gt; on the uncompressed image and on installed systems.&lt;/p&gt;
&lt;p&gt;If you want to remove that default app set in bulk after upgrading, you can use:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo apt purge ubuntu-desktop --autoremove
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;If you want to keep some of those applications, just mark them as manually installed with &lt;code&gt;apt&lt;/code&gt; first.&lt;/p&gt;
&lt;h3 id=&#34;swap-on-raspberry-pi-is-now-handled-by-cloud-init&#34;&gt;Swap on Raspberry Pi is now handled by cloud-init
&lt;/h3&gt;&lt;p&gt;Since &lt;code&gt;25.10&lt;/code&gt;, swap file creation on Raspberry Pi desktop images is handled by &lt;code&gt;cloud-init&lt;/code&gt;.&lt;br&gt;
If you want to customize swap size before first boot, you can edit &lt;code&gt;user-data&lt;/code&gt; on the boot partition directly.&lt;/p&gt;
&lt;h3 id=&#34;risc-v-requirements-have-moved-up&#34;&gt;RISC-V requirements have moved up
&lt;/h3&gt;&lt;p&gt;Starting with &lt;code&gt;25.10&lt;/code&gt;, the &lt;code&gt;RISC-V&lt;/code&gt; build of &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt; requires hardware that implements the &lt;code&gt;RVA23S64 ISA profile&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Systems that do not meet that requirement can no longer run &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt;. If you still have boards based on earlier &lt;code&gt;RVA20&lt;/code&gt; processor cores, you need to stay on the support line provided by &lt;code&gt;Ubuntu 24.04 LTS&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;According to Ubuntu, as of &lt;code&gt;April 2026&lt;/code&gt;, there is still no real &lt;code&gt;RVA23S64&lt;/code&gt; hardware available. So the only currently supported platform is effectively a &lt;code&gt;QEMU&lt;/code&gt; virtualized environment configured with &lt;code&gt;-cpu rva23s64&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&#34;ibm-z-now-requires-z15-at-minimum&#34;&gt;IBM Z now requires z15 at minimum
&lt;/h3&gt;&lt;p&gt;Starting with &lt;code&gt;26.04&lt;/code&gt;, the minimum requirement for the &lt;code&gt;s390x&lt;/code&gt; architecture has moved up to &lt;code&gt;z15&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;That means:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;z14&lt;/code&gt; / &lt;code&gt;LinuxONE II&lt;/code&gt; and older systems can no longer install &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;z15&lt;/code&gt; / &lt;code&gt;LinuxONE III&lt;/code&gt; and newer systems should see better performance&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;9-who-should-read-this-first&#34;&gt;9. Who should read this first
&lt;/h2&gt;&lt;p&gt;This article is more useful than the desktop overview if you fall into any of these cases:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;you use Ubuntu for &lt;code&gt;CUDA&lt;/code&gt;, &lt;code&gt;ROCm&lt;/code&gt;, &lt;code&gt;SYCL&lt;/code&gt;, or local AI inference&lt;/li&gt;
&lt;li&gt;you do development or compute work on Intel, NVIDIA, or AMD GPUs&lt;/li&gt;
&lt;li&gt;you maintain Raspberry Pi, ARM64, RISC-V, IBM Z, or other non-standard x86 platforms&lt;/li&gt;
&lt;li&gt;you are especially sensitive to repository availability, driver behavior, runtimes, and platform requirements after an upgrade&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;10-one-line-takeaway&#34;&gt;10. One-line takeaway
&lt;/h2&gt;&lt;p&gt;The key point of &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt; on the hardware and AI stack side is not that one GPU vendor got a standout upgrade. It is that &lt;strong&gt;Intel&amp;rsquo;s DPC++, NVIDIA&amp;rsquo;s CUDA, and AMD&amp;rsquo;s ROCm are all entering the Ubuntu ecosystem in a more official, in-repository, and maintainable way&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If you used to think of Ubuntu as &amp;ldquo;the system first, then I assemble the GPU environment myself,&amp;rdquo; &lt;code&gt;26.04&lt;/code&gt; starts to look more like a distribution that is willing to actively carry AI and heterogeneous computing workloads.&lt;/p&gt;
</description>
        </item>
        <item>
        <title>Ubuntu 26.04 LTS Released: Major Desktop Updates with GNOME 50 and Linux 7.0</title>
        <link>https://www.knightli.com/en/2026/04/26/ubuntu-26-04-lts-release-notes/</link>
        <pubDate>Sun, 26 Apr 2026 16:10:25 +0800</pubDate>
        
        <guid>https://www.knightli.com/en/2026/04/26/ubuntu-26-04-lts-release-notes/</guid>
        <description>&lt;p&gt;&lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt; was released on &lt;strong&gt;April 23, 2026&lt;/strong&gt;, under the codename &lt;code&gt;Resolute Raccoon&lt;/code&gt;. This is the new long-term support release, with standard support through &lt;strong&gt;April 2031&lt;/strong&gt;. If you use &lt;code&gt;Ubuntu Pro&lt;/code&gt;, security maintenance can be extended to &lt;strong&gt;10 years&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If you are upgrading from &lt;code&gt;Ubuntu 24.04 LTS&lt;/code&gt;, this is more than a routine release. It also folds in the major changes introduced across &lt;code&gt;24.10&lt;/code&gt;, &lt;code&gt;25.04&lt;/code&gt;, and &lt;code&gt;25.10&lt;/code&gt;. So this article works best as a quick guide to what is worth checking before you upgrade.&lt;/p&gt;
&lt;p&gt;If you only want the biggest takeaways from this release, remember these four points first:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;GNOME 50&lt;/code&gt; has landed in an LTS release, bringing clearer improvements to desktop experience and display support&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Linux kernel 7.0&lt;/code&gt; becomes the new baseline, refreshing both hardware support and the long-term maintenance base&lt;/li&gt;
&lt;li&gt;Ubuntu Desktop has now fully moved to &lt;code&gt;Wayland&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The default app set has been refreshed across the board, with major updates to &lt;code&gt;Firefox&lt;/code&gt;, &lt;code&gt;LibreOffice&lt;/code&gt;, &lt;code&gt;Thunderbird&lt;/code&gt;, and &lt;code&gt;GIMP&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;1-start-with-the-key-updates&#34;&gt;1. Start with the key updates
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt; is a long-term support release with standard support through &lt;code&gt;2031-04&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The desktop environment has been updated to &lt;code&gt;GNOME 50&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The generic kernel has moved to &lt;code&gt;Linux kernel 7.0&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu Desktop now provides only a &lt;code&gt;Wayland&lt;/code&gt; session&lt;/li&gt;
&lt;li&gt;Older versions cannot jump directly to &lt;code&gt;26.04&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you are still on &lt;code&gt;Ubuntu 22.04 LTS&lt;/code&gt; or &lt;code&gt;25.04&lt;/code&gt;, the official recommendation is to upgrade to &lt;code&gt;Ubuntu 24.04 LTS&lt;/code&gt; or &lt;code&gt;25.10&lt;/code&gt; first, then continue to &lt;code&gt;26.04 LTS&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&#34;2-biggest-change-1-gnome-50-is-now-in-lts&#34;&gt;2. Biggest change #1: GNOME 50 is now in LTS
&lt;/h2&gt;&lt;p&gt;The most visible desktop-side change this time is that &lt;code&gt;GNOME 50&lt;/code&gt; has finally entered an LTS release. For most users, the value is not one flashy standalone feature, but a smoother desktop experience overall:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Better usability on small screens and narrow windows&lt;/li&gt;
&lt;li&gt;Notifications can be grouped by app&lt;/li&gt;
&lt;li&gt;Continued improvements to HDR, VRR, and fractional scaling&lt;/li&gt;
&lt;li&gt;Better smoothness and stability in remote desktop, Wayland, and NVIDIA-related scenarios&lt;/li&gt;
&lt;li&gt;Stronger accessibility support, including clear updates to the &lt;code&gt;Orca&lt;/code&gt; screen reader&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Ubuntu has also added a few practical changes of its own:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;GNOME Shell global search can directly find available &lt;code&gt;snap&lt;/code&gt; apps&lt;/li&gt;
&lt;li&gt;Web searches can also be triggered directly from search&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;Yaru&lt;/code&gt; theme continues moving closer to upstream GNOME styling&lt;/li&gt;
&lt;li&gt;Permissions, file access, and drag-and-drop behavior for &lt;code&gt;snap&lt;/code&gt; apps feel more natural on the desktop&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you mainly use the desktop edition, the real point of this LTS is not a dramatic visual overhaul. It is that many small frictions from the past have been polished away together.&lt;/p&gt;
&lt;h2 id=&#34;3-biggest-change-2-the-default-apps-got-a-broad-refresh&#34;&gt;3. Biggest change #2: the default apps got a broad refresh
&lt;/h2&gt;&lt;p&gt;Compared with &lt;code&gt;24.04 LTS&lt;/code&gt;, the built-in app set in &lt;code&gt;26.04 LTS&lt;/code&gt; has been updated in a big way:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Firefox&lt;/code&gt; moves to &lt;code&gt;150&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;LibreOffice&lt;/code&gt; goes from &lt;code&gt;24.2&lt;/code&gt; to &lt;code&gt;25.8&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Thunderbird&lt;/code&gt; moves to &lt;code&gt;140&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;GIMP&lt;/code&gt; jumps from &lt;code&gt;2.10&lt;/code&gt; to &lt;code&gt;3.2&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are also several replacements that matter in day-to-day use:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The PDF viewer is now &lt;code&gt;Papers&lt;/code&gt;, replacing &lt;code&gt;Evince&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The image viewer is now &lt;code&gt;Loupe&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The terminal is now &lt;code&gt;Ptyxis&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The system monitor is now &lt;code&gt;Resources&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The default video player is now &lt;code&gt;Showtime&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The direction behind these changes is clear: Ubuntu is leaning more fully into a new generation of GNOME applications built on &lt;code&gt;GTK4&lt;/code&gt;, &lt;code&gt;libadwaita&lt;/code&gt;, and in some cases Rust-based rewrites.&lt;/p&gt;
&lt;h2 id=&#34;4-biggest-change-3-wayland-is-now-the-only-desktop-session&#34;&gt;4. Biggest change #3: Wayland is now the only desktop session
&lt;/h2&gt;&lt;p&gt;This is the most important change for many long-time users.&lt;/p&gt;
&lt;p&gt;The shift that started in &lt;code&gt;25.10&lt;/code&gt; is now fully settled in &lt;code&gt;26.04 LTS&lt;/code&gt;: Ubuntu Desktop runs only on the &lt;code&gt;Wayland&lt;/code&gt; backend, because &lt;code&gt;GNOME Shell&lt;/code&gt; can no longer run as an &lt;code&gt;X.org&lt;/code&gt; session.&lt;/p&gt;
&lt;p&gt;That does not mean old applications suddenly stop working. The official notes make it clear that &lt;code&gt;X.org&lt;/code&gt; applications can still run through the &lt;code&gt;XWayland&lt;/code&gt; compatibility layer. But if your workflow still depends on older graphics drivers, certain remote desktop methods, screen recording tools, or input method details, this is still something you should verify before upgrading.&lt;/p&gt;
&lt;h2 id=&#34;5-biggest-change-4-linux-kernel-70-and-the-lower-stack-move-forward-together&#34;&gt;5. Biggest change #4: Linux kernel 7.0 and the lower stack move forward together
&lt;/h2&gt;&lt;p&gt;The GA generic stack in &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt; moves from &lt;code&gt;Linux 6.8&lt;/code&gt; to &lt;code&gt;Linux 7.0&lt;/code&gt;, and the HWE stack is also unified on &lt;code&gt;7.0&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Among the lower-level changes highlighted by Ubuntu, the most relevant ones for general users and operators are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Crash dump is enabled by default on both desktop and server&lt;/li&gt;
&lt;li&gt;&lt;code&gt;sched_ext&lt;/code&gt; introduces a new scheduler extension model that lets developers implement scheduling policies with eBPF&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;linux-lowlatency&lt;/code&gt; binary package is being retired, replaced by &lt;code&gt;linux-generic&lt;/code&gt; plus the user-space &lt;code&gt;lowlatency-kernel&lt;/code&gt; package for low-latency tuning&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;amd64v3&lt;/code&gt; architecture variant is available as an option, but still opt-in by default&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If your machine is relatively new, &lt;code&gt;amd64v3&lt;/code&gt; is worth keeping an eye on. The official notes give this enablement method:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;span class=&#34;lnt&#34;&gt;2
&lt;/span&gt;&lt;span class=&#34;lnt&#34;&gt;3
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;echo&lt;/span&gt; &lt;span class=&#34;s1&#34;&gt;&amp;#39;APT::Architecture-Variants &amp;#34;amd64v3&amp;#34;;&amp;#39;&lt;/span&gt; &lt;span class=&#34;p&#34;&gt;|&lt;/span&gt; sudo tee /etc/apt/apt.conf.d/99enable-amd64v3
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo apt update
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo apt upgrade
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;That said, it is not enabled automatically. Ubuntu is still prioritizing compatibility first.&lt;/p&gt;
&lt;h2 id=&#34;6-hardware-requirements-and-install-baseline&#34;&gt;6. Hardware requirements and install baseline
&lt;/h2&gt;&lt;p&gt;The official recommended baseline for Ubuntu Desktop 26.04 LTS is:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;code&gt;2 GHz&lt;/code&gt; dual-core processor or better&lt;/li&gt;
&lt;li&gt;At least &lt;code&gt;6 GB RAM&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;At least &lt;code&gt;25 GB&lt;/code&gt; of available storage&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If your machine is on the lighter side, the official recommendation is to consider Ubuntu flavors such as &lt;code&gt;Xubuntu&lt;/code&gt; or &lt;code&gt;Lubuntu&lt;/code&gt;.&lt;br&gt;
The server edition has a lower floor. The documentation notes it can start from &lt;code&gt;1.5 GB RAM&lt;/code&gt; and &lt;code&gt;4 GB&lt;/code&gt; of storage, though the real requirement still depends on your workload.&lt;/p&gt;
&lt;h2 id=&#34;7-who-should-prioritize-upgrading&#34;&gt;7. Who should prioritize upgrading
&lt;/h2&gt;&lt;p&gt;If you are already on &lt;code&gt;24.04 LTS&lt;/code&gt; and want the following, &lt;code&gt;26.04 LTS&lt;/code&gt; is worth a close look:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A full-generation desktop stack refresh instead of minor patching&lt;/li&gt;
&lt;li&gt;More mature &lt;code&gt;Wayland&lt;/code&gt; and display support&lt;/li&gt;
&lt;li&gt;A more up-to-date default application set&lt;/li&gt;
&lt;li&gt;A newer kernel with a longer support runway&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But if you still depend heavily on older &lt;code&gt;X11&lt;/code&gt; workflows, special drivers, or custom desktop extensions, or if your production environment is extremely conservative about changes, it is still best to do a compatibility pass before upgrading.&lt;/p&gt;
&lt;h2 id=&#34;8-one-line-summary&#34;&gt;8. One-line summary
&lt;/h2&gt;&lt;p&gt;The value of &lt;code&gt;Ubuntu 26.04 LTS&lt;/code&gt; is not one especially flashy headline feature. It is that Ubuntu has rolled two years of desktop, kernel, application, and compatibility progress into a new LTS baseline all at once.&lt;/p&gt;
&lt;p&gt;If you want the shortest possible judgment, it is this: &lt;strong&gt;this is an Ubuntu LTS release that feels broadly newer and more stable as a whole, rather than one built around a single standout feature.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&#34;related-links&#34;&gt;Related links
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Official release notes: &lt;code&gt;https://documentation.ubuntu.com/release-notes/26.04/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Summary for LTS users: &lt;code&gt;https://documentation.ubuntu.com/release-notes/26.04/summary-for-lts-users/&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
        </item>
        
    </channel>
</rss>
