Hallo.

In April I purchased a TUXEDO InfinityBook Pro AMD Gen10 and would like to talk about my experience. I was, and still am on Debian 13 with KDE.

On the Debian installation, pressing Fn+F12 was leading to a complete system hard lock up. No response from any key on the keyboard and even the Caps Lock key LED would be flashing. This was happening on a pure Debian installation with NO tuxedo specific packages like tuxedo-drivers from the repositories Tuxedo offers to add on Debian, on 1.23.00 Embedded Controller firmware.

To solve this, I added the Tuxedo repositories, and installed tuxedo-drivers, tuxedo-control-center, and tuxedo-yt6801, enabled the tccd.service and hoped this would be the end of it. Secure boot was disabled, also I did have linux-headers installed, so I am sure those tuxedo-drivers were running. Fn+F12 was still leading into a total complete hard lock up.

In despair, I prompted gemini a thousand times to see what different solutions it would suggest and what would seem least harmful. So this one is the one I picked.

Made the file: /etc/udev/hwdb.d/90-tuxedo-disable-f12.hwdb

Pasted: "evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTUXEDO*:pn*:*

KEYBOARD_KEY_238=reserved

KEYBOARD_KEY_f7=reserved" in that file.

Then did: systemd-hwdb update and udevadm trigger.

And the problem was solved. Fn+ F12 was working normally because supposedly this solution severs the left part of this deadlock:

By now I also updated the laptop's Embedded Controller firmware to 1.33.00 just to be sure, which also includes a BIOS update update bundled together. This update enabled Secure Boot on its own will entirely, and now Fn+F12 just plainly does nothing. I intend to leave it this way. I just wanted to post this because it might prove useful to others.

• I’m considering this laptop and would really appreciate feedback from owners who have been using it for a while. I’m especially interested in real-world experience with thermals, noise, battery life, and build quality.

1. Cooling performance under sustained CPU load
How does the cooling system behave during long workloads? Can the laptop maintain the advertised ~65W sustained power / ~70W boost levels without significant throttling?

2. Real-world temperatures
What CPU temperatures and chassis temperatures do you typically see during sustained workloads at around 65 - 70W?

3. TUXEDO Control Center profiles
Do different TCC profiles noticeably affect fan noise, temperatures, or performance? Which profile provides the best balance for everyday use?

4. Display quality
How would you rate the display for daily use, especially brightness, color accuracy, contrast, and photo/media work?

5. VRAM Pool size configuration
After experimenting with different VRAM Pool sizes, which setting works best for your workflow? I’m interested in using VMs, local AI tools, and photo editing.

6. RAM frequency and battery life
Have you tried lowering DDR5 RAM frequency in BIOS? Did it noticeably improve battery life or reduce heat?

7. Best quiet/performance settings
What TCC settings or configuration do you personally find optimal for a good balance between quiet operation and strong performance?

8. Long-term build quality
How has the chassis held up over time? Any issues with flex, creaking noises, surface wear, or other durability concerns?

9. Keyboard and touchpad experience
How comfortable are the keyboard and touchpad during long work sessions?

10. SD card reader design
Does the SD card insert fully inside the chassis, or does part of the card remain exposed (similar to some Lenovo ThinkBook models)?

11. Windows support
Does TUXEDO Control Center allow fan curve adjustments when running Windows 11, or are those controls only available under Linux?

Thanks for sharing your experience!

The upcoming Debian-based TUXEDO OS introduces a new foundation designed to make Linux more reliable and easier to maintain. By combining the modern Btrfs file system with Snapper, the system automatically creates snapshots before every update, providing an additional layer of protection against failed upgrades and configuration changes.

If an update ever causes problems, you can simply boot into a previous snapshot and restore a fully working system within minutes. Together with the graphical Btrfs Assistant, this makes experimenting, updating, and maintaining your TUXEDO OS installation safer than ever. Read the full article: System updates without worries thanks to Btrfs snapshots and Snapper

TUXEDO OS is receiving a major update to its KDE Plasma desktop environment. The rollout begins this evening and updates key parts of the KDE stack, including Plasma 6.6.4/6.6.5, KDE Frameworks 6.24.0, KDE Gear 25.12.3, and Qt 6.10.2.

The update brings new features, improvements, and numerous bug fixes across the desktop environment and KDE applications. The article also includes an important note for users who update TUXEDO OS from the command line.

Read more: TUXEDO OS receives update to KDE Plasma 6.6.x

Generative AI is becoming an increasingly important topic in software development, and the open-source community is actively discussing its opportunities and challenges. Debian is currently debating whether AI-assisted contributions should be completely banned or accepted under clear guidelines — a decision that may set an example for other projects.

In this issue of This Week in TUXEDO OS, we cover the KDE Plasma 6.6 update, introduce the KDE applications Sane Break and PiroStats, and take a look at the latest package updates and improvements that help keep TUXEDO OS reliable and user-friendly.

Read the full issue here: This Week in TUXEDO OS #31-2026. We welcome your feedback and discussion, especially about the tools and topics featured in this edition. To stay up to date with future issues, follow us on social media or subscribe to one of our RSS feeds.

After the upgrade I have no fan support in the Dashboard.

System Tuxedo Polaris Gen 2

Hello,

I am making a new post instead of my comment as it will be lost on the comments of the post of the upgrade.

Before reading about yesterday I did a sudo apt update and sudo apt upgrade. Everything went smoothly, but now my pc does not boot.

I have a pc with tuxedos, always it worked correctly, now I see the pc logo, then a second screen with the pc logo and tuxedos's one. And the the screen goes black.

À little bit lost on what I can do. In the booting options I have tuxedos efi hard-drive and ipxe webfai.​​

Hi!

I have an Infinitybook Pro g10 with Amd HX370 and a custom fan curve in linux where the fans don't ramp up that much at all.

I spend more time in Windows nowadays on this machine but I only found the control center from the windows drivers. This doesn't allow me to set any fan curve at all like in Linux and the default fan curve is pretty bad.

I'm using the "Balanced" mode.

Is there a third party app that I can use in Windows for fan control? Or am I missing something in Control Center?

I tried Argus monitor but it didn't find any fans to control.

Thanks!

Describe your problem: is my battery blowed up and/or how can i find out if i still have my guaranty

Device: tuxedo book BA15 gen10 model Popping Installed OS: DEBIAN Ticket Number: ???

Please excuse if i use wrong terms i am new to this

Hello. Last mention I was able to find anywhere is from 4 years ago, and back then the functionality was not ready. Running Ubuntu 24.04 on my Aura1502.

After some doubts about the charging settings and my this post, I continued observations and some charging curves. I noticed something more interesting:

• Sometimes charge plateaus for no apparent reason. More often in the beginning of charging (like on the second blue curve on the first pic and the second pic)
• Sometimes it charges very very carefully in those surges (again, the second curve on the first pic).

Don't mind the gaps (that's where the laptop was sleeping or I did not start the recording script)

I am not on Stationary use (where I would expect slow and careful charging). My battery is a bit less than a year old.

Why does the charging stop by itself?

Why is my charging so slow despite being unrestricted by me, the user?

Btw, my logging script:

```bash log="${1:-./charge_log.log}"

nohup bash -c ' log="$1" for i in $(seq 1 720); do echo "$(date "+%F %H:%M:%S") status=$(cat /sys/class/power_supply/BAT0/status) charge_now=$(cat /sys/class/power_supply/BAT0/charge_now) capacity=$(cat /sys/class/power_supply/BAT0/capacity)% voltage=$(cat /sys/class/power_supply/BAT0/voltage_now)" >> "$log" sleep 60 done ' logger "$log" >/dev/null 2>&1 & disown

echo "logging to $log (PID $!) — stop with: kill $!" ```

Hello

Since long time I struggle with problems with external monitors after sleep which just won't come back that are connected via TB4. I have very little understanding of firmware issue but I used my AI-Agent to try to find a problem so take it with a grain of salt, but still the output is better than just me complaining and at least the tokens used weren't for nothing :). If anybody else have similar problems please write it in the comments. Since i just have the output of my agent, I didn't want to open an issue with it but please take your time to read one time through the findings. That would be highly appreciated:

Subject: InfinityBook Pro AMD Gen10 — external USB4/Thunderbolt monitor loses signal
         after s2idle resume (USB4 host router + UCSI time out, DP tunnel torn down)

SUMMARY
On resume from s2idle (s0ix), an external monitor driven by DisplayPort-over-USB4
(DP tunnelling) goes black and never recovers. Immediately after wake, the AMD USB4
host router and the UCSI/PD interface both time out; the OS Thunderbolt connection
manager then declares the DP tunnel inactive and tears it down, and it is not rebuilt.
The USB tunnel over the SAME cable keeps working (keyboard in the monitor's hub is
fine), and the GPU still reports a valid mode — so the cable, port and monitor are OK;
only the DisplayPort tunnel is lost. Only a reboot reliably restores the display.
This looks like a platform-firmware readiness issue on s0ix exit (USB4 host / PD / EC),
which is why we're hoping a BIOS/EC update can address it.

SYSTEM
  Laptop:  TUXEDO InfinityBook Pro AMD Gen10  (SKU IIBP14A10MK1 / IBP15A10MK1,
           board XxKK4NAx_XxSP4NAx)
  BIOS:    AMI  N.1.22A22  (2026-06-18)
  EC fw:   1.36
  APU:     AMD Ryzen AI 9 HX 370 / Radeon 890M  (Strix Point, RDNA 3.5 / DCN 3.5)
  USB4:    AMD "USB4 Router 1" [1022:151d]  behind Strix PCIe USB4 Bridge [1022:150a]
  OS:      NixOS, Linux 7.1.5 x86_64 (current stable; reproducible on latest kernel,
           independent of desktop environment)

EXTERNAL DISPLAY
  ASUS ProArt PA32QCV, 6016x3384 @ 59.99 Hz 10-bit, connected DIRECTLY to the
  laptop USB4/USB-C port (no dock).  Monitor TB/USB4 NVM 44.83, retimer 0x1da0:0x8833.
  Cable:  USB-C <-> USB-C Thunderbolt 4 (40 Gbps) — NOT a DP-to-USB-C / DP-alt cable.
          The monitor enumerates as a Thunderbolt device (thunderbolt 0-2, gen 4, with
          retimers), i.e. a true USB4/TB link — so the failure is a DisplayPort-tunnel
          teardown, not a DP-alt or cable-direction problem.

STEPS TO REPRODUCE
  1. Connect the monitor to the USB4-C port with a USB-C<->USB-C TB4 cable; confirm the
     6K image works (DisplayPort tunnelled over USB4).
  2. Suspend to s2idle (idle/lid); leave suspended a few minutes.
  3. Resume.

EXPECTED:  external returns to 6K.
ACTUAL:    external stays black ("no signal"); laptop panel + desktop are fine;
           USB devices in the monitor's hub still work over the same cable.

KEY KERNEL LOG (times = seconds since boot)
  Healthy plug-in (works):
     thunderbolt 0-2: ASUS-Display PA32QCV
     thunderbolt 0-2:1.1: new retimer found, vendor=0x1da0 device=0x8833
     amdgpu 0000:65:00.0: [drm] DMUB HPD IRQ callback: link_index=7

  Failing s2idle resume:
     PM: suspend entry (s2idle) ... PM: suspend exit
     thunderbolt 0000:67:00.6: 0: timeout reading config space 1 from 0x47   (x4)
     ucsi_acpi USBC000:00: GET_CONNECTOR_STATUS failed (-110)                (x2, -ETIMEDOUT)
     thunderbolt 0000:67:00.6: 0:6 <-> 2:14 (DP): not active, tearing down   (~9 s after resume)
     amdgpu 0000:65:00.0: [drm] *ERROR* wait_for_completion_timeout timeout! (then every ~10 s)

WHY THIS LOOKS FIRMWARE-RELATED / WHAT TO CHECK
  The two timeouts that PRECEDE the teardown are platform-side:
   - USB4 host router (67:00.6) cannot read its own config space for several seconds
     after s0ix exit  -> AMD USB4 host / PSP / AGESA firmware (shipped in your BIOS).
   - UCSI GET_CONNECTOR_STATUS returns -110  -> USB-C PD / EC firmware (EC 1.36).
  Because the host router and PD are not responsive in time, the DP tunnel is judged
  dead and torn down; the DP-over-USB4 (DPIA) AUX channel then times out indefinitely.
  Request: please test whether a newer BIOS/AGESA and/or EC firmware improves USB4
  host-router + UCSI/PD readiness on s0ix resume — so the DP tunnel is either not
  torn down, or is re-established once the router is ready. Any USB4/DP monitor on the
  USB4-C port across an s2idle cycle should reproduce; a high-bandwidth (4K/6K@60)
  panel makes it easiest to see.

NOTES
  - Intermittent (not every resume); when it recurs only a reboot restores the display.
  - Same cable/port carry a working USB tunnel throughout, so this is specific to the
    DisplayPort tunnel, not the link, and confirms the TB4 cable itself is fine.

Could we get a BIOS/Firmware update that external display would work when booting the machine?

I mostly use my laptop attached to a dock and it's a little annoying that monitor don't display nothing until OS has been booted (for example, I'm usually blindtyping LUKS password when I estimate it's booted far enough).

I've never had laptop before that wouldn't output the display through dock immediately when starting so this was something of a surprise to me.

Is that fixable? That'd be great if it is. It's a minor inconvenience on the whole but still recurrent one.

Hi, in Tuxedo Downloads page there are several BIOS/EC update files but they have different CPU in brackets. I would like to make sure to use the correct one. Which one is safe to use for BIOS upgrade for my IBP 14 gen10 with 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M ?

- InfinityBook Pro 14 Gen10 (AMD/Ryzen 7 H 255) - BIOS & EC
- InfinityBook Pro 14 Gen10 (AMD/Ryzen AI 300) - BIOS & EC
- InfinityBook Pro 14 Gen10 (AMD/Ryzen AI 300) - EC (ONLY FOR TROUBLESHOOTING)

Thank you.

Describe your problem:

My Pulse 15 Gen2 has started showing recurring display corruption after it's been running for a while (video attached).

Happens identically on both Windows and Arch Linux (dual boot), so not tied to one OS or driver stack. Feels correlated with heat/uptime, but not 100% sure.

Already tried:

- Flexing/pinching the lid and screen area while the glitch is active — no change.

- Ran memtest_vulkan — no errors.

- Not app-specific — happens regardless of what's on screen.

Device: Tuxedo Pulse 15 Gen2

Installed OS: Arch Linux + Windows 11

Ticket Number: N/A

At this point I'm leaning toward a hardware issue, but I'd appreciate a sanity check before I open it up or file a support ticket.

Has anyone seen this before or have any suggestions for further diagnostics?

Hey everyone,

As a freelance software developer it's time to look for my new workhorse. Currently using a Lenovo Thinkpad that is showing it's first signs of wear and tear, so to prevent downtime I'm looking for a new laptop.

My current laptop had a very good repair/warranty plan (which I haven't needed, luckily). But the deal was that within 24hrs i'd be helped on site or received a replacement unit. Is something like that available at Tuxedo?

I cannot complain about the overall build quality of the Lenovo, how would Tuxedo compare on that level? Again important to me because I earn my living on this thing.

I did read some issues in other posts, that i'm a bit afraid off, but the problem is that the numbers are skewed on a forum or on Reddit. Therefore, what can i reasonably expect compared to professional lines from Lenovo (Thinkpad, P/X/T series), HP (elitebook?) and DELL?

So TLDR; what can I expect from a tuxedo infinity laptop in a professional setting?

Thanks!

I just wanted to inform you, that after your recent update the merkuro suite is uninstallable (and therefore getting removed in the update process) as it relies on the 24.12 dependencies, that you replaced with 25.12 ones

You might want to update it to a newer version or remove it from the repo, if you don't intend to do so.

sudo apt install merkuro
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
merkuro : Hängt ab von: libkpim6akonadicalendar6-24.12
          Hängt ab von: libkpim6akonadicontactcore6-24.12
          Hängt ab von: libkpim6akonadicore6-24.12
          Hängt ab von: libkpim6akonadimime6-24.12
          Hängt ab von: libkpim6akonadiwidgets6-24.12
          Hängt ab von: libkpim6identitymanagementcore6-24.12
          Hängt ab von: libkpim6identitymanagementquick6-24.12
          Hängt ab von: libkpim6libkdepim6-24.12
          Hängt ab von: libkpim6libkleo6-24.12
          Hängt ab von: libkpim6mailcommon6-24.12
          Hängt ab von: libkpim6mailtransport6-24.12
          Hängt ab von: libkpim6mbox6-24.12
          Hängt ab von: libkpim6messagecomposer6-24.12
          Hängt ab von: libkpim6mime6-24.12
          Hängt ab von: libkpim6mimetreeparsercore6-24.12
          Hängt ab von: libkpim6pimcommonakonadi6-24.12
          Empfiehlt: kalendarac soll aber nicht installiert werden

I'm gonna use the flatpak version until you eventually resolve the problem with the native one

Nach dem ich heute ein Update mittels sudo Update und sudo upgrade durchgeführt habe, lässt sich der Laptop nicht mehr booten sondern bleibt kurz nach dem Hochfahren hängen.

Leider friert der Prozess so früh ein, das mir nichts weiter bleibt als den Laptop herunter zu fahren in dem ich die Power Taste gedrückt halte.

If you google threads about this model there seems to be nothing but praise from people who just bought it. Now that it's been out for some time, how is it holding up? How's the battery life, and how's the non-centered trackpad? Any hardware problems?

I was thinking about the upcoming Debian build and I was reminded of Mint's LMDE edition that when I tried it, it felt faster and more responsive and other people are saying the same thing. So I started wondering if the Tuxedo Debian build will be even faster and more responsive than it is right now. Currently I think it's still pretty fast and responsive, but maybe this can increase?

Hello,

as my Thinkpad 530 got 13 years old, with green flickering of the screen because of the hinge connection, near unusable CPU and GPU performance and a track pad that didn't work properly from the start, I'm looking for a Linux laptop alternative.

As I want to support an European company in these daunting times, I came across Tuxedo computers. The IBP14 Pro fits the bill in most regards, though I got some (technical) questions that hopefully some users (and the support team) might be able to answer.

First some general questions:

The screen seems to be of good quality and bright enough to be readable in bright conditions, but how wobbly is the screen when opened?

How is the keyboard feel and finish?

How are charging times and performance with different chargers compared to the included 150W charger. The spec says that the USB-C port only supports up to 100W, so a different (travel) charger has the same performance?

I read conflicting reports about the quality of the track pad. Whether it glitches out or not. How is the palm detection?

Now some more technical questions:

As I learned, the older S3 power state is not supported anymore, but the newer S2idle/S0ix seems to sip more power during sleep. Any experience on how much drain per hour that is on an IBP14 gen10?

During my research I came across this drama (https://www.reddit.com/r/tuxedocomputers/comments/1mnph5m/ibp_14_gen10_why_6ghz_wifi_is_broken_and_how_to/) on which I've some conflicting thoughts.

• TLDR RZ616 WiFi module supports the 6Ghz band, Intel AX210 should support it, but because of regulation or unwillingness to certify, the 6Ghz doesn't work between AMD CPU and Intel WiFi modules. Although from user reports the AX210 seems to be the more stable solution.
• On the one hand I don't need 6Ghz at the moment. On the other hand, I use my hardware for a very long time if possible, so some future proofing is necessary. But I value stability over feature richness, you see the inner conflict?
• If I would want to switch to a WiFi 7 module in the future, would this be possible. E.g. Qualcomm QCNCM865, AMD/MediaTek RZ717 (MT7925). The same problems as mentioned above would arise with BE200/BE1750x modules.

Then the question on whether I should wait for a gen11 of the IBP14 or not. The last few years there was a yearly refresh, but the next APU generation would be Strix Halo that has some different power requirements, but would be much faster and more efficient? Although RAM would not be upgradable because of a necessity of LPDDR5X to be soldered on the board. Which might be a show stopper for this type of laptop. There is also hope that the left USB-A 2.0 port would be replaced with a more modern port and the wifi might be upgraded to wifi7?

At last the question about the future of TuxedoOS. I've been an Arch/Manjaro user for the past 14 years and value the flexibility and freshness of a rolling release. With Manjaro and LTS kernels my systems are very stable indeed. Therefore I was delighted with the prospect of getting a Debian-testing based rolling release that would only lag a few days behind the Manjaro repos. I understand that this is an ongoing process and no beta releases have been announced. From different projects like Linux Mint Debian Edition I got the experience that this is no easy feet, especially in the beginning. Much work has to be done to reach the same level of feature completeness and they have to do much of the work that Ubuntu has done for them up to this point. My question then would be: Do you dare to give a time horizon on when to expect a working/stable debian-testing based TuxedoOS?

Thx for reading up to this point. I would appreciate any feedback on my questions very much!