What is TUXEDO Tomte? Architecture and Functionality explained - TUXEDO Computers

When Linux is installed on a notebook or PC, users initially receive only the standard configuration provided by their chosen distribution. To ensure that all of a computer’s hardware components function optimally, however, additional driver packages or specific configuration adjustments are often required – going well beyond what a standard installation can typically provide out of the box.

This is exactly where our TUXEDO Tomte comes in. The name is derived from the Swedish term for a house spirit or elf, making it a fitting description for our own small software assistant. It automates the necessary hardware customizations for your TUXEDO system and has already gone through several technical iterations during its development.

With Tomte 3, the tool has undergone a fundamental redesign. Unlike the previous generation, Tomte is no longer closely tied to a specific distribution. Instead, the current version uses a modular, package-based architecture. This makes it possible to provide hardware-specific customizations consistently across different Linux distributions.

From the Beginnings to Tomte 3

The first generation of TUXEDO Tomte emerged from a collection of scripts that could automatically install drivers and other customizations on TUXEDO devices. With Tomte 2, this evolved into a comprehensive configuration service that was primarily tailored to Ubuntu LTS systems.

As the number of supported Linux distributions grew, this approach increasingly reached its limits. Hardware-specific customizations had to be maintained in multiple places for different distributions. This not only increased development and maintenance efforts, but also made consistent installation and testing procedures more difficult.

At the end of 2025, TUXEDO therefore introduced a new Tomte architecture for the first time with TUXEDO Tomte Light. The deliberately lightweight tool decoupled hardware detection from the actual customizations and relied largely on packages provided by the respective distribution.

Tomte Light was subsequently used for Debian installations as well as in WebFAI, among other applications. The codebase tested in this process ultimately formed the foundation for TUXEDO Tomte 3. Tomte Light was therefore an intermediate step on the way to the third generation of Tomte. With Tomte 3, the new architecture is also being used in TUXEDO OS and Ubuntu 24.04.

Efficient Detection and Automatic Installation

Tomte’s basic task sounds simple: The tool determines which hardware is installed in the computer and uses this information to decide which customizations are required. To do this, Tomte collects information about PCI and USB devices as well as the mainboard, among other things. It compares the collected data with rules stored in YAML files. These rules can take into account specific PCI or USB IDs, for example, or the number of graphics processors present.

The applicable rules produce a list of the required packages. Tomte initially works with distribution-independent package names. Another mapping then translates these into the specific package names used by the distribution, based on the information in /etc/os-release. For installation, Tomte then uses the system’s native package manager. This means that hardware customizations are installed using the same mechanisms as other software on the respective distribution.

Board Meta-Packages and Specific Fix Packages

A key element of the new architecture is the separation between board meta-packages and the actual fix packages. A board meta-package describes a specific device or hardware platform and defines which customizations are required for that model.

The meta-package does not contain the optimizations itself. Instead, it defines the required fix packages as dependencies or recommendations. These fix packages then perform the actual configuration, for example by setting kernel parameters, modifying the initramfs, or providing required services and configuration files.

This separation offers a decisive advantage: The device description is no longer directly tied to the implementation of a fix. If a customization is updated or support for a distribution is extended, the entire device handling in Tomte does not have to be modified. Furthermore, a separate board meta-package is not necessarily required for every model if the regular fix packages already cover all requirements.

Cross-Distribution Compatibility and Flexibility

The new architecture makes it possible to use the same detection and configuration logic across different distributions. Tomte abstracts the package manager being used and can map the detected packages to the appropriate package names for the system.

WebFAI also benefits from this approach. The package-based architecture enables reproducible installations in which WebFAI and an already installed system can use the same hardware rules and packages. This also allows more consistent testing procedures to be used for quality assurance.

TUXEDO OS and Ubuntu 24.04 were automatically switched to Tomte 3 through a regular system update. Debian, Fedora, and openSUSE Tumbleweed were already using the new codebase introduced with Tomte Light and essentially switched to the new name with Tomte 3. Ubuntu 22.04, on the other hand, remains with TUXEDO Tomte 2.

Optimized Integration of NVIDIA Graphics Drivers

Tomte Light initially focused exclusively on the package-based installation of fixes and did not yet include specific logic for systems with NVIDIA or hybrid graphics. Tomte 3 now closes this gap. The tool works closely with the revamped nvidia-driver-assistant to automatically detect NVIDIA hardware and perform the necessary customizations without manual intervention.

The actual NVIDIA-specific logic remains encapsulated within the nvidia-driver-assistant. Within this interaction, Tomte takes care of central detection and orchestration. This allows NVIDIA systems to be seamlessly integrated into Tomte 3’s automated installation and configuration processes, significantly simplifying the handling of complex graphics configurations.

Unobtrusive Background Processes in Everyday Use

TUXEDO Tomte is now designed so that users do not need to interact with the tool during normal operation. It runs automatically in the background and keeps track of completed installations. This prevents the same actions from being performed every time the program runs. The configuration therefore remains largely invisible.

For maintenance and diagnostic purposes, however, Tomte 3 provides a deliberately streamlined command-line interface. An overview of the available options can be displayed with:

tuxedo-tomte --help

This provides a quick way to check which functions are available for manual diagnostics or maintenance. Previously completed installations can be processed again using the --reset option:

tuxedo-tomte --reset

This resets Tomte’s stored installation flags. As a result, the corresponding packages or rules are evaluated again during the next regular run. If the run should not wait until it is triggered automatically at a later point, it can be started immediately with --force:

tuxedo-tomte --force

This option also resets the stored installation flags and then immediately starts a new Tomte run. The deliberately limited number of options is intentional: Unlike Tomte 2, the current generation is not intended to be an extensive interactive administration tool.

Instead, Tomte handles system configuration as automatically and reproducibly as possible through the designated packages. The few manual intervention options are therefore primarily intended for maintenance and diagnostic purposes. During normal operation, the little system assistant remains where it belongs: quietly working in the background.

Traceable GRUB Configuration Changes

When switching to Tomte 3, adjustments to the GRUB configuration may also be required. Tomte does not automatically overwrite existing settings without documenting the changes in a way that remains understandable to the user. During the one-time migration, the existing CMDLINE line in /etc/default/grub is commented out.

If any of the values it contains differ from the default configuration, Tomte additionally records an appropriate note. The tool then adds the optimized configuration for the system as a new line. This keeps individual changes traceable in the configuration file and allows them to be reviewed if necessary.

Conclusion: Tomte 3 as an Efficient System Assistant

The transition from Tomte 2 to Tomte 3 is more than a conventional version upgrade. The new architecture moves a significant part of the hardware customizations out of the configuration tool itself and into clearly defined, modular packages.

This allows Tomte itself to remain comparatively small. Its primary tasks are to detect the hardware, evaluate the corresponding rules, and ensure that the required packages are installed through the package manager of the distribution in use.

For users, ideally, little changes as a result: Tomte continues to do its work automatically in the background. The new architecture, however, makes it easier for TUXEDO to provide, test, and maintain hardware customizations consistently across multiple Linux distributions.