Debian 13 Trixie environments release notes: Difference between revisions
(Created page with "{{Portal|User}} __TOC__ There is some significant evolutions since previous debian11 environments. <span id="common-componants-changes-debian"></span> = Common componants changes (Debian) = {| class="wikitable" |- ! Componant ! style="text-align: center;"| Debian 11 Bullseye ! style="text-align: center;"| Debian 13 Trixie |- | Linux kernel | style="text-align: center;"| 5.10 | style="text-align: center;"| 6.12 |- | GCC | style="text-align: center;"| 10.2 | style="tex...") |
No edit summary |
||
| Line 51: | Line 51: | ||
|} | |} | ||
For more informations, see [https://www.debian.org/releases/trixie/release-notes/whats-new.en.html#desktops-and-well-known-packages debian.org Release Notes] | For more informations, see [https://www.debian.org/releases/trixie/release-notes/whats-new.en.html#desktops-and-well-known-packages debian.org Release Notes]. | ||
<span id="environments-specific-changes"></span> | <span id="environments-specific-changes"></span> | ||
= Environments specific changes = | = Environments specific changes = | ||
Available in debian13-big and debian13-std (default) environments | Available in debian13-big and debian13-std (default) environments : | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 104: | Line 104: | ||
|} | |} | ||
⚠ Note some “old” Nvidia GPU clusters use a new environment named debian'''nvlegacy'''13-big and debian'''nvlegacy'''13-std (default). The only change in this environment flavor is that the proprietary nvidia module kernel is used, instead of the more recent opensource one, as it is mandatory for Nvidia GPU Compute Capability < 7.5 | ⚠ Note some “old” Nvidia GPU clusters use a new environment named debian'''nvlegacy'''13-big and debian'''nvlegacy'''13-std (default). The only change in this environment flavor is that the proprietary nvidia module kernel is used, instead of the more recent opensource one, as it is mandatory for Nvidia GPU Compute Capability < 7.5 . | ||
Some other useful informations: | For more informations, see [https://developer.nvidia.com/blog/nvidia-transitions-fully-towards-open-source-gpu-kernel-modules/ this Nvidia explanation]. | ||
Some other useful informations: | |||
* [https://gitlab.inria.fr/grid5000/environments-recipes/-/blob/master/steps/data/setup/puppet/modules/env/manifests/common/software_versions.pp Kameleon environment recipe - software versions] | |||
* [https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/user-kernel-space-compat-matrix.html User and AMD GPU Driver (amdgpu) support matrix] | |||
<span id="modules-evolution"></span> | <span id="modules-evolution"></span> | ||
| Line 113: | Line 118: | ||
The default provided modules are no more build with [https://spack.readthedocs.io Spack], but with [https://codeberg.org/guix-science/guix-modules GUIX] | The default provided modules are no more build with [https://spack.readthedocs.io Spack], but with [https://codeberg.org/guix-science/guix-modules GUIX] | ||
For more informations, see | For more informations, see | ||
* [https://www.grid5000.fr/w/News#Upcoming_changes_to_modules ''Upcoming changes to modules'' news] | |||
* [https://www.grid5000.fr/w/Modules ''Modules'' wiki page]. | |||
'''TODO''' | |||
Note ARM64 CPU architecture modules are not available for now. We are [https://gitlab.inria.fr/moyens-de-calcul/environnement-logiciel/-/work_items/9 working on it]. | |||
<span id="nvidia-cuda-and-amd-rocm"></span> | <span id="nvidia-cuda-and-amd-rocm"></span> | ||
| Line 122: | Line 132: | ||
Only Nvidia and amdgpu drivers (kernel modules) are provided in big and default environments. Tools like CUDA and ROCm have to be loaded with module commands. | Only Nvidia and amdgpu drivers (kernel modules) are provided in big and default environments. Tools like CUDA and ROCm have to be loaded with module commands. | ||
<span id="cuda"></span> | <span id="cuda-module"></span> | ||
=== CUDA === | === CUDA module === | ||
An example if environment debian13 : <code>module load cuda-toolkit nvidia-driver-libs</code> (default is currently ''cuda-toolkit/13'') | An example if environment debian13 : <code>module load cuda-toolkit nvidia-driver-libs</code> (default is currently ''cuda-toolkit/13''). | ||
An example if environment debiannvlegacy13 : <code>module load cuda-toolkit/12 nvidia-driver-libs</code> | An example if environment debiannvlegacy13 : <code>module load cuda-toolkit/12 nvidia-driver-libs</code> | ||
| Line 154: | Line 164: | ||
For more informations on CUDA GPU Compute Capability, see [https://developer.nvidia.com/cuda/gpus/legacy Nvidia documentation]. | For more informations on CUDA GPU Compute Capability, see [https://developer.nvidia.com/cuda/gpus/legacy Nvidia documentation]. | ||
<span id="rocm"></span> | <span id="rocm-module"></span> | ||
=== ROCm === | === ROCm module === | ||
'''TODO''' | '''TODO''' | ||
ROCm module has some others modules dependancies. <code>module load rocm-hip-runtime hipblas hipblas-common rocblas rocm-toolchain gcc-toolchain</code> To make it easier to use, a ''rocm-abaca'' meta module to load has been defined : <code>module load rocm-abaca</code> | ROCm module has some others modules dependancies. <code>module load rocm-hip-runtime hipblas hipblas-common rocblas rocm-toolchain gcc-toolchain</code> | ||
To make it easier to use, a ''rocm-abaca'' meta module to load has been defined : <code>module load rocm-abaca</code> | |||
<span id="tools-changes"></span> | <span id="tools-changes"></span> | ||
| Line 167: | Line 179: | ||
== DHCP client and IPv6 == | == DHCP client and IPv6 == | ||
ISC DHCP tools (client and server) are deprecated. See [https://www.isc.org/dhcp/ ISC Note]. The client has been replaced by '''dhcpcd'''. So the commonly used <code>dhclient <interface_name></code> is no more available, and is be replaced by <code>dhcpcd <interface_name></code>. | ISC DHCP tools (client and server) are deprecated. See [https://www.isc.org/dhcp/ ISC Note]. | ||
The client has been replaced by '''dhcpcd'''. So the commonly used <code>dhclient <interface_name></code> is no more available, and is be replaced by <code>dhcpcd <interface_name></code>. | |||
Node network interface will have '''both IPv4 and IPv6 addresses''' by default. | Node network interface will have '''both IPv4 and IPv6 addresses''' by default. | ||
| Line 179: | Line 193: | ||
== CPU frequency scaling == | == CPU frequency scaling == | ||
cpufrequtils has been replaced by '''linux-cpupower''' (introduced with kernel 3.1). See the [https://manpages.debian.org/trixie/linux-cpupower/cpupower.1.en.html cpupower manpage] for more informations. | cpufrequtils has been replaced by '''linux-cpupower''' (introduced with kernel 3.1). | ||
See the [https://manpages.debian.org/trixie/linux-cpupower/cpupower.1.en.html cpupower manpage] for more informations. | |||
<span id="open-mpi"></span> | <span id="open-mpi"></span> | ||
Revision as of 10:40, 19 August 2026
There is some significant evolutions since previous debian11 environments.
Common componants changes (Debian)
| Componant | Debian 11 Bullseye | Debian 13 Trixie |
|---|---|---|
| Linux kernel | 5.10 | 6.12 |
| GCC | 10.2 | 14.2 |
| LLVM/Clang toolchain | 11 | 19 |
| Perl | 5.32 | 5.40 |
| Python | 3.9 | 3.13 |
| Ruby | 2.7 | 3.3 |
| OpenJDK | 17 | 25 |
| Qemu | 5.2 | 10.0 |
| Open MPI | 4.1 | 5.0 |
For more informations, see debian.org Release Notes.
Environments specific changes
Available in debian13-big and debian13-std (default) environments :
| x86_64 (AMD64) componants | debian11 envs | debian13 envs |
|---|---|---|
| Nvidia drivers | 535.x | 580.x |
| Nvidia CUDA | 11.2.x | via modules |
| AMD drivers (amdgpu) | 6.3.x | 30.x |
| AMD ROCm | 6.3.x | via modules |
| Singularity | 4.1.2 | N/A |
| Apptainer (Singularity replacement) | N/A | 1.4.5 |
| aarch64 (ARM64) componants | debian11 env | debian13 env |
|---|---|---|
| Nvidia drivers | N/A | 580.x |
| Nvidia CUDA | N/A | N/A |
⚠ Note some “old” Nvidia GPU clusters use a new environment named debiannvlegacy13-big and debiannvlegacy13-std (default). The only change in this environment flavor is that the proprietary nvidia module kernel is used, instead of the more recent opensource one, as it is mandatory for Nvidia GPU Compute Capability < 7.5 .
For more informations, see this Nvidia explanation.
Some other useful informations:
Modules evolution
The default provided modules are no more build with Spack, but with GUIX
For more informations, see
TODO
Note ARM64 CPU architecture modules are not available for now. We are working on it.
Nvidia CUDA and AMD ROCm
Only Nvidia and amdgpu drivers (kernel modules) are provided in big and default environments. Tools like CUDA and ROCm have to be loaded with module commands.
CUDA module
An example if environment debian13 : module load cuda-toolkit nvidia-driver-libs (default is currently cuda-toolkit/13).
An example if environment debiannvlegacy13 : module load cuda-toolkit/12 nvidia-driver-libs
Compatibility matrix:
| environment | Nvidia kernel module | Nvidia GPU compute capability | CUDA 12.9 | CUDA 13 |
|---|---|---|---|---|
| debiannvlegacy13 | proprietary (legacy) | < 7.5 | OK | KO |
| debian13 | open | ≥ 7.5 | OK | OK |
For more informations on CUDA GPU Compute Capability, see Nvidia documentation.
ROCm module
TODO
ROCm module has some others modules dependancies. module load rocm-hip-runtime hipblas hipblas-common rocblas rocm-toolchain gcc-toolchain
To make it easier to use, a rocm-abaca meta module to load has been defined : module load rocm-abaca
Tools changes
DHCP client and IPv6
ISC DHCP tools (client and server) are deprecated. See ISC Note.
The client has been replaced by dhcpcd. So the commonly used dhclient <interface_name> is no more available, and is be replaced by dhcpcd <interface_name>.
Node network interface will have both IPv4 and IPv6 addresses by default.
Network Time Protocol (NTP) client
For system time synchronizaton, ntpsec and ntpsec-ntpdate are used instead of no more available ntp et ntpdate tools packages.
CPU frequency scaling
cpufrequtils has been replaced by linux-cpupower (introduced with kernel 3.1).
See the cpupower manpage for more informations.
Open MPI
Debian11|12 disable many providers by default. We restore UCX and Fabric while keeping openib disabled to avoid useless warnings
TODO Bug 17590: debian 13 - Choix de configuration Open MPI
PMem
Debian ipmctl package, a utility for configuring and managing Intel® Optane™ Persistent Memory modules is not compatible with python 3.13 provided by Debian 13 repository.
So the Troll cluster in Grenoble featuring PMEM remains on debian11 environnement by default.
Singularity to Apptainer
Apptainer is available in replacement of Singularity.