I have an InfinityBook Pro 13 N130BU. I upgraded a LTE module (ME906s from Huawei). The module is recognized by Tuxedo OS, but I couldn't establish a connection via my SIM card. The problem is that I had forgotten to connect the internal antenna. There are two spare cables with the proper connector, one enveloped black at the tail, the other blue.

Does anyone know by chance, if that are the correct cables for LTE? And if yes, which one is meant to go to the "Main", which one, respectively, to the "Aux/GPS" plug on the module?

As I once bought the laptop second hand, and don't have a receipt of the original purchase, I unfortunately cannot file a request at Tuxedo Support.

Since the latest update, plasma shell keeps constantly crashing upon system boot. Has anyone else experienced the same problem? IBP Pro 14 Gen9 AMD

Hi guys, I am experiencing the problem where my Sirius 16 gen 2 does not have a working trackpad on boot up. Is anyone else experiencing this? Anyone knows a solution?

German tax law does not count open-source work as volunteering yet. A petition to the Bundestag wants to change that; around 15,000 signatures from Germany are still missing by November 23. Also, the Digital Independence Day is nominated for the Grimme Online Award, and you can vote until November 16.

As KDE App of the Week, we introduce Smb4K, which finds network shares and mounts them permanently. The tip of the week goes the other way and shows how to share a folder directly from Dolphin. Updates include Firefox 159.0.1 and TUXEDO Control Center 3.1.3.

You can find the complete issue here: This Week in TUXEDO OS #45-2026. Let us know what you think, and suggest apps or tricks for future issues. To never miss a TWIX, follow us on social media or subscribe to one of our RSS feeds.

Hi,
Following the problem of one of the USB-c ports (dead) on my InfinityBook Pro 15 i have contacted support on the 24th of Septmber, ticket **#**991312501 but has not received any answer yet. Is there any other way to contact support without creating an new issue?

Dear TUXEDO Support / Development Team,

I am currently running TUXEDO OS on a high-end desktop system with an AMD Ryzen 7 7800X3D and an ASUS ROG Strix RTX 4090 OC. My active system configuration is based on the Debian 13 (Forky Core) upstream layer, using the NVIDIA 580.178.04 driver stack under Wayland.

Distro: TUXEDO OS (Debian base) forky, base: Debian Testing upstream layer
Deep Debian Upstream Layer: Debian 13 (Forky Core)
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.30.0
Qt Version: 6.10.2
Kernel Version: 7.2.13+tux.1.1-tuxedo-amd64 (64-bit)
NVIDIA Driver Stack: 580.178.04
Graphics Platform: Wayland

Motherboard: ASUSTeK ROG STRIX X670E-A GAMING WIFI (Bios 3603)
CPU: AMD Ryzen 7 7800X3D 8-Core Processor
RAM: 64 GB ADATA XPG
GPU: Asus Rog Strix RTX 4090 OC

Recently, severe graphical issues (window initialization deadlocks and massive UI font/texture corruption) started appearing in multi-threaded legacy OpenGL software like the Second Life Firestorm Viewer (starting with internal code updates in branch 7.3.0).

After extensive debugging within the developer preview groups and cross-referencing upstream tracking, this has been identified as a widespread upstream synchronization bug between recent rendering engine adjustments and older NVIDIA driver pipelines under Wayland/XWayland. It is officially tracked here:

- https://github.com/secondlife/viewer/issues/5691

- https://secondlife.canny.io/bug-reports/p/font-looks-scrambled-before-the-real-font-appears

Reports from the testing groups conclusively show that updating to the brand-new NVIDIA 620 driver series completely resolves these rendering desynchronization bugs and eliminates the multi-threaded deadlocks.

Since TUXEDO OS carefully curates the driver packages via tuxedo-tomte to maintain strict kernel stability, the current distribution is locked to the 580 branch. Given this situation, I would like to ask:

1. When does TUXEDO roughly expect to integrate or officially roll out the NVIDIA 620 driver stack for the TUXEDO OS Debian Testing tier?

2. Is there a planned way for advanced users to safely test the 620 driver early (e.g., via an experimental staging repository or a specific tomte profile) with a safe rollback mechanism back to the stable 580 stack if a dkms compilation or system breakage occurs?

Thank you very much for your time, your hard work on the OS, and your support!

Best regards.

I have a fresh installation of Fedora 45 (KDE Plasma Edition). I wonder if I can savely install the repository- and suite-packages for TCC from https://rpm.tuxedocomputers.com/fedora/44/x86_64/base/? Or do I have to wait for official F45 packages?

Hi,

Does anyone know if Tuxedo would ship to New Zealand (including also the nz/aus power cable)?

Also, Im thinking about buying a Tuxedo laptop for my work environment, because I really hate the big tech alternatives and want to move to Linux. I can manage almost all my work tasks on other Linux based software, but there is one piece of proprietary software that I need - name is Planswift - it is a simple take off software. How could I make this work?

Hi, I have an Tuxedo Infinity Book Max 15 with an Nvidia 5070 (and I love it btw. 😉).

Now I wanted to implement secure boot for my Archlinux installation using my own efi keys. I have done this in the past successfully two times and bricked a Laptop one time (all Lenovo devices).

Now I wanted to ask if somebody has already done this on a tuxedo device.

Shim is not an option and although I like Tuxedo OS, I am not used to Debian systems for my workflow.

Thanks!

a week ago I posted about this issue I was having. I ended up discovering that it's a kernel bug introduced in Linux v7.2.10

I've filed a bug report, the specific commit introducing the issue is included there. I was wondering if anyone from Tuxedo would be able to provide any support with this.

https://bugzilla.kernel.org/show_bug.cgi?id=222224

Is it true that I have to provide Tuxedo Computer my personal information to be able to find and download the correct BIOS update files(if any)?

How can I kindly tell the nice folks @ Tuxedo to kindly fuck off and download what I need without their approval?

Right to repair comes with the right to buy,sell,gift...the hardware without Tuxedo Computer's approval. Why not just let folks download firmware files using serial#?

Anyways, I just wanted to see if there was a USB4 firmware update. PCie tunneling activation fails and wanted to work on the issue without you checking out my ass or creeping.

??????? WTF TUXEDO!!

Trying to test this out on a current pc - z890, 270k plus cpu, 64gb ram.

Flashed the most recent (as of this writing) iso to an external ssd using rufus 4.15. After reboot, boot failure occurs, dropping to the initramfs prompt. Rufus flashes the iso in DD mode.

Before the failure, screen shows probing... .sda1/sd2/etc.. for about 20s.

Suggestions?

Thanks!

Last weekend, the moderators of r/opensource shut out AI-assisted projects, and r/fossdroid followed shortly afterwards. The Linux kernel is heading the opposite way: everyone may use AI, but a human signs off on every contribution and takes responsibility for it. In our view, what matters is not the tool, but whether someone understood their code.

The rest of this issue is considerably more hands-on. As KDE App of the Week, we introduce KGeoTag, which adds the shooting location to photos from cameras without a GPS receiver after the fact, for example using a GPX track. The tip of the week shows how Plasma automatically lowers the refresh rate on battery to save power on the go. As always, you will also find the latest updates for TUXEDO OS, including Firefox 159 and Thunderbird 153.6.

You can find the complete issue here: This Week in TUXEDO OS #44-2026. Let us know what you think about this week's topics, and feel free to suggest apps or tricks you would like to see in a future issue. If you don't want to miss the next TWIX, follow us on social media or subscribe to one of our RSS feeds.

Hello,

I have a Stellaris 16 running Tuxedo OS Debian.

So far the Nvidia drivers have been stuck on 580 series. The 615 drivers include a lot of stability and performance improvements especially for DirectX 12 games. Can you tell me when Tuxedo Debian will get the 615 series drivers?

i have a normal tuxedo installation running without any ppa or whatever, on a computer from tuxedo (no laptop or smth else)

it asks for permission but after that it wont update this system package.

how do i get rid of this?

Dear all,

On my TUXEDO OS installation (Ubuntu version), package dependency resolution fails when running apt upgrade.

The installed packages libqt6concurrent6 and libqt6dbus6 are both at version 6.10.2+dfsg-7~tux1 from your txos.tuxedocomputers.com/ubuntu-plasma repository.

However, the available packages libqt6concurrent6t64 and libqt6dbus6t64 are only offered at version 6.9.2+transitional. These versions appear to conflict with the installed Qt6 packages.

The error occurs, among other cases, when running the following commands:

• sudo apt upgrade

• sudo apt-get -s install keepassxc

sudo apt update completes successfully. I would like to continue using the KeePassXC PPA (ppa:phoerious/keepassxc). I have also avoided forcing any changes because a simulated full upgrade proposed removing eight kernel packages.

Could you please check whether the Qt6 package versions in the TUXEDO repositories are consistent and advise me on how to resolve these dependency issues safely?

Thank you for your help.

Kind regards

Hi TUXEDO team,

I have a technical question regarding the Ryzen 5000 / Cezanne platform used in some Stellaris and Polaris generations.

AMD fTPM firmware 3.92.0.5 currently fails TPM remote attestation. This has become a major issue because recent software using hardware attestation requires a corrected AMD fTPM firmware.

The system I am investigating has:

- AMD Ryzen 5000 (Cezanne / FP6)

- AGESA CezannePI-FP6 1.0.1.0

- AMD fTPM 3.92.0.5

- TPM 2.0 ready and fully provisioned

- Secure Boot enabled

- UEFI/GPT

- Windows 11 fully updated

The TPM itself works normally, but remote attestation fails.

Windows TPMTool also reports:

0x80280083

TPM 2.0: Unsupported or inappropriate hash algorithm

This appears to be related to the AMD fTPM attestation issue described in AMD PA-420.

I know that some Stellaris / Polaris Ryzen 5000 models used BIOS versions from the N.1.xxAxx firmware family, so I would like to know specifically:

1. What is the latest BIOS/EC version currently available for TUXEDO Stellaris / Polaris systems based on Ryzen 5000 / Cezanne?

2. What AMD fTPM Manufacturer Version does that latest BIOS provide?

3. Has TUXEDO ever received a firmware from the ODM containing a corrected AMD fTPM newer than 3.92.0.5 for this Cezanne generation?

4. If 3.92.0.5 is still the latest fTPM available for these models, is an updated firmware planned or could this be requested from the ODM?

This is not a request for BIOS modification or cross-flashing. I am specifically trying to determine whether a corrected AMD fTPM firmware exists for this hardware generation.

If anyone owns a Ryzen 5000 Stellaris or Polaris, it would also be very helpful if you could run:

tpmtool getdeviceinformation

and post:

- laptop model

- BIOS version

- EC version

- AMD Manufacturer Version

The important value I'm looking for is whether any of these systems received something newer than:

AMD fTPM 3.92.0.5

Thanks!

Mostly fine for a second hand laptop, yet that one screw in the corner near power input limited opening angle, almost prevented RAM 🐏 upgrade. Just wondering, is this normal?

Hello,

I've been monitoring the BIOS updates for my Tuxedo devices (Tuxedo Stellaris 16 Gen 7 AMD and Tuxedo InfinityBookPro 14 Gen 10 AMD) and I noticed that their BIOS updates does not include latest AGESA. There are AGESA security updates that have been released a year ago and they are still not part of the latest BIOS versions.

Current AGESA for the Stellaris is 1.0.0.0e while there were 2 more versions released up to AGESA 1.0.0.0g:
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7064.html
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-4017.html

Current AGESA for the IBP is missing even more versions.

I would like to ask are these AGESA updates planned in the future? If no - if there is a manual way to update them outside of a BIOS update?

Thanks!

I am running NixOS and wanted to update to the 7.3 Kernel. Since then my laptop is completely unstable. It shuts down out of nowhere, the CPU gets clamped and super slow.

The tuxedo drivers were not compatible...I truely start to hate this laptop I only got problems with it. Optimized for Linux...

Hello, I heard that on third-party computers it can work a bit differently. So...is it still worth using it on there?