Tuxedo has its own kernel with fixes. It is installed automatically with tuxedo-tomte. It is working fine.
Kernel 7 has "higher" version number and it overwrite the tuxedo 6.17 kernel.
I was wondering when there will be tuxedo version of Kernel 7.x that will be installed automatically as kernel 6.17 before?
P.S. I'm using Ubuntu 24.04.4
The TuxedoControlCenter allow for creating a custom fan curve. Basically at a given temperature you can set a fan spinning in percent. This is perfect. I was just wondering which temperature is taken for trigger - CPU or GPU? I'm wondering because recently I started using GPU-only workloads so the CPU stays relatively cool. So If I stress only the GPU will this also trigger the fans?
TL;DR:
Hey everyone,
I’ve been tuning my Tuxedo Stellaris Gen 7 (Ryzen 9 9955HX3D) over the past year and stumbled across a few interesting quirks regarding memory behavior, latency, and thermal management. Thought I’d share my findings here in case anyone else wants to squeeze extra efficiency or performance out of their machine.
Initially, I overclocked my RAM to 6200 MT/s (up from stock 5600 MT/s). It was stable, but I noticed a side effect:
While 1.2V is technically acceptable, I prefer lower voltages for long-term health and heat management, so I reverted back to stock 5600 MT/s. Cinebench/Geekbench tests showed only a 1–3% difference between 5600 and 6200 MT/s anyway—nothing noticeable in real-world use.
However, latency testing revealed something strange:
Why? The CPU firmware dynamically downclocks the RAM to 3200 MT/s during any memory traffic under ~10 GB/s to save power, which spikes latency. When you overclock RAM, the system disables this power-saving state and forces max frequency constantly.
The Workaround:
I found a way to lock the RAM at maximum stock speed (5600 MT/s) without manually overclocking or pushing SoC voltages to 1.2V: Plug in a USB-C dummy display adapter (or external monitor) and set internal monitor refresh rate at 240Hz.
Once the iGPU has to handle higher refresh rate + display buffers for a second display (even a ~1080p dummy plug), the CPU firmware crosses a memory traffic threshold and locks the RAM to its max stock frequency (5600 MT/s), even under light loads.
The idle power consumption is increased a little mainly because SoC voltage is ~0.95V (which is the stock SoC at that frequency anyway).
Under heavy stock workloads, CPU temperatures hit 95°C in winter and 98°C in summer (using -10 undervolt). While within operating spec, I don't like running high heat on long renders or compiles.
Here is how I manage it depending on the task:
| Workload Type | Profile / Settings | Power Limits | Max Temp | Perf Impact |
|---|---|---|---|---|
| Short Bursts | Stock Tuxedo Profile | CPU: 162W / GPU: 175W | 95°C–98°C (Brief) | 100% |
| Sustained (1-2+ hrs) | Custom Profile | CPU: 100W / GPU: 140W | <80°C (often <70°C) | ~5% drop |
Dropping the sustained power limits slightly yields a massive 15–20°C drop in thermals for a barely noticeable 5% hit in render times.
If you have the 3D V-Cache version of the 9955HX, use `taskset` to pin your browser to the 3D V-Cache CCD. Chromium browsers love the massive L3 cache and you keep the non-3D CCD free for raw frequency-bound background tasks.
Great device! I'm really happy that it works as it is! The option to control memory clock (fixed vs dynamic frequency based on number of displays) is AMAZING and the massive temp drop for a fraction of performance is outstanding.
Hope this helps anyone tweaking their Zen 5 HX3D laptops! Feel free to ask if you want exact setup details.
Describe your problem:
I use my laptop either only on the built-in monitor, or on the built-in monitor plus 1 or 2 external monitors connected via USB-C. In other words, all monitors are intentionally connected to the iGPU.
How the problem started:
For the first six months after purchasing the laptop, I experienced screen freezes. While working normally, the system would suddenly freeze. The mouse wouldn't move. I waited a bit, but nothing happened, and the only option was to perform a hard reset. I couldn't find a solution at the time. Over time, I noticed that the kernel was actually still running, as audio continued to work. I then tried stopping the system by pressing the power button once to confirm shutdown, and the laptop shut down normally, but after a very long wait. This led me to believe that the issue was related to video driver. I later noticed that it mainly (if not exclusively) occurred when using Chrome-based applications.
I attempted to gather more information from logs, but they were empty, and I couldn't find anything useful.
How the problem evolved:
I tried various kernel flags, but none provided a solution. Then, an LLM model suggested increasing the dedicated memory allocated to the iGPU. I did this, changing it from 512 MB to 2048 MB. I don't know whether this was due to the increased memory allocation or to updated drivers over the past few months, but the problem changed.
The screen still freezes, but if I wait a few seconds, I notice that the mouse can move temporarily, then it freezes again, and so on. So now I have a short window of time to react.
Attempt 1:
I tried moving the mouse across all three monitors, and most often, one of them was frozen while I was able see mouse moving only on other 2 monitors. Almost always, it was the built-in monitor.
Attempt 2:
I tried switching input languages using "Meta + Space". The input language indicator appeared in the center of the screen and didn't disappear. After that, the system froze severely, and I couldn't even open a terminal.
Attempt 3:
In the 3-4 seconds between the freezes I closed all Chrome-based applications (VSCode, Brave, Slack), and things seemed to work fine—as long as I didn't launch any Chrome-based application or try switching the input language with "Meta + Space". All these actions caused the system to hang again. Later, I realized that GNOME was essentially dead in this situation.
Attempt 4:
I opened a terminal after the freeze and managed to restart the laptop. I waited a long time (5+ minutes), and it eventually restarted. During the restart, the log shown in the attached image appeared. Before restarting, I also tried checking the logs, which were full of "flip timeout" or "a process hangs GPU for too long" (or similar) messages.
Attempt 5:
By complete chance, I opened a website—https://podium.global/ (not advertising it; I don't even know what it's for). The entire site relies on WebGL. I opened the site on an external monitor, clicked around the site for a few seconds, and... it froze severely. This happened only when Slack was running on the laptop's built-in monitor. After searching for this issue, it became clear that Chrome doesn't play well with the amdgpu driver and Wayland (https://issuetracker.google.com/issues/519633677 and https://issuetracker.google.com/issues/406187731). The suggested solution was to add "--ozone-platform=x11" to all Chrome-based applications. After doing so, I no longer had issues with WebGL applications, but the overall system freezes persisted.
That's as far as I've gotten in troubleshooting the issue. I'm curious whether anyone else has experienced a similar problem and whether they managed to resolve it.
This issue occurs only with the Radeon 610M integrated graphics card. I also have an IBP Gen 10 with 890M, and I don't experience any such issues with that.
Device: Stellaris Gen 7 AMD Installed OS: Ubuntu 24.04.4 Ticket Number: N/A