We’re kicking off 2026 with the release of Ganymede Neo. As you are accustomed to with our Neo releases, this release includes upstream updates and minor changes compared to the Ganymede ISO.
Before I go into the release notes, I just want to remind you of the following.
The changes described over here are affecting new installs, our Calamares installer, and the Live environment on the ISO only. Running systems don’t have to “upgrade” to Ganymede Neo; if you update regularly, your system is fine.
The Ganymede Neo release
This ISO and offline installer ships with:
Calamares 26.01.1.5-1
Firefox 146.0.1-1
Linux 6.18.4.arch1-1
Mesa 1:25.3.3-2
Xorg-server 21.1.21-1 (xorg)
Nvidia-utils 590.48.01-2
And has the following bugfixes:
- The long startup time issue with Calamares has been resolved.
- The package Nemo preview was removed from the default package bundle for Cinnamon and Budgie during installation due to its removal from the Arch repository.
- Starting with this release, the NVIDIA proprietary drivers have been switched to nvidia-open due to the upstream changes to NVIDIA drivers: https://archlinux.org/news. As a result, the proprietary option now only supports Turing GPUs(16xx) and later. Earlier NVIDIA GPUs are still supported using the default boot option, which will use the Nouveau open-source drivers.
These are all the changes Ganymede Neo ships with to ensure a smooth ISO boot and installation. We are currently hard at work with further refinements and additions for Ganymede’s successor, Titan. So keep an eye out for our announcements.
Ganymede Neo is available on our homepage.
What’s llvmpipe initializing with?
Could you give us more info on what you were trying to do?
starting the computer, starting the game, playing the game
That makes sense, llvmpipe is the software rendering backend for Mesa. It uses the IGPU to do 3D tasks when there’s no dedicated graphics card available.
yeah, the point is llvmpipe is the software backend render. for youtube processes, where video material has mp3 data, the video doesn’t transcode hardware encoded since mp3 just software encodes. llvmpipe does the organisation of driver inloads and stuff. and on my nobara 43 installation form the last install, mesa is version 25.3.4 or something, but the software backend over llvmpipe runs llvm 21.1.7. and llvm 21.1.7 over llvmpipe doesn’t read the AI XMX cores i have on my Intel Arc A750 OC i have installed and doesn’t support CSM correctly yet. CSM support comes over software backend llvm 22.2.3 i think. i was just asking which llvm llvmpipe does initialize on the release since i’m thinking to use CSM activated again as it was by February till April 24. llvmpipe did initialize with the llvm version mesa used and that was mesa 24 version. llvmpipe 21.1.7 is technically mesa 21. the llvmpipe software rasterisation did fallback since wayland sudo rust support collided and llvmpipe initializes since about may/june 24 in fallback mode, which doesn’t support AI cores and doesn’t support AI image interpolation systems like xess or dlss well. in february till april 2024 mesa 24 used llvmpipe mesa 24, after april it changed that mesa 24 uses llvmpipe mesa 21 and 20 partially. nobara 43 release january 26 still uses mesa 21 llvmpipe framework as software render backend since wayland, sudo and rust are in collision with x11. linuxmint released a 22.3 version which uses llvmpipe mesa 22 again for the fallback, which mesa 22.3 on llvmpipe does support CSM again which gives fluent and accurate computation in games. that does help, CSM makes the games more fluent on mesa 22.3 as software driver loadin and the fallback of wayland doesn’t go into collisions with the login screen manager bootload with the package manager deciding if the gpu has to be loaded in, since the encryption keys pass to use pacman or apt, but the software backend doesn’t load in the right arithmetics, since CSM support isn’t there and AI cores are not registered, the data misses and the package systems usually behave nebulic. commands disappeare, programs doesn’t install or generate collision errors or don’t find the right packages structures to install and AI interpolation like Xess/FSR or DLSS generate ghost fragments since the AI cores are not initialized and the Raytracing cores doesn’t serve correctly in mesa libwayland.
I think you should address this question to the Mesa team, we just provide the upstream versions without any tinkering nor are we involved with their decision making.
I just could not leave your website prior to suggesting that I extremely enjoyed the usual info an individual
supply on your visitors? Is gonna be again steadily to
investigate cross-check new posts
Hell yeah! When’s the Titan release coming out? :0
There’s no specific date decided,yet. But it will be soon!
Another amazing release, team EndeavourOS!
Happy to see NVidia 590 driver now.
Thnx, Robin. Nice to hear from you again!