FAQ: TUXEDO InfinityBook Pro 14 – Gen10 (AMD) - TUXEDO Computers

Welcome to the FAQ collection of TUXEDO Computers! Here you will find answers to the most frequently asked questions about the new TUXEDO InfinityBook Pro 14 – Gen10 – AMD.

Why do some Fn key combinations not work?

On this model, the keyboard does not support full N-Key Rollover. Due to the physical design of the key matrix, certain multi-key combinations cannot be registered simultaneously.

The key matrix is designed so that common combinations (e.g. Ctrl+Alt+Del) work without any issues. However, there are exceptions. These include combinations such as Fn+Tux+Up/Down. In this case, the Fn key is used to convert Up/Down into Page Up/Page Down, but it also acts as an independent key press within the matrix. This can lead to input conflicts.

Unfortunately, there is no technical solution for this behavior. The limitation is hardware-based and cannot be resolved via firmware or driver updates. Alternative keyboard variants for this model are also not available.

What is the alternative in KDE?

In KDE Plasma, window management typically uses Page Up/Page Down key combinations, for example to maximize or minimize windows. Other desktop environments such as GNOME or Windows use Tux+Up/Down directly instead.

In TUXEDO OS, Tux+Up/Down is used by default to snap windows to the upper or lower half of the screen. If a window has previously been placed on the left or right half of the screen using Tux+Left/Right, it can be further arranged into the corresponding screen quadrants using Tux+Up/Down.

If these functions are used less frequently in daily work and you prefer to maximize or minimize windows instead, the keyboard shortcuts can be adjusted accordingly:

1. Open System Settings.
2. Navigate to Keyboard » Shortcuts » Window Management.
3. Adjust the following actions:

• Maximize Window » [Meta]+[Up]
• Minimize Window » [Meta]+[Down]

This allows you to reliably use the desired functions even without the Fn key. Further information about keyboard shortcuts in KDE Plasma can be found in the official documentation.

Recommended Kernel Version

For optimal operation of the notebook, a current kernel should be used. When running a custom distribution, we recommend version 6.17 or newer, as many of our adjustments have already been incorporated into the standard kernel. The necessary quirk fixes are automatically applied through the WebFAI installation of TUXEDO OS or our optimized Ubuntu. On other distributions, a current kernel ensures maximum stability and full functionality.

Known issues with other distributions or kernel versions

• Internal keyboard no longer works after waking up from standby

Affects only devices with AMD CPUs. The fix has already been submitted upstream and has been included in the mainline kernel since version 6.17. If you are using a distribution other than TUXEDO OS or a system not set up via our WebFAI, please ensure that you have a sufficiently recent kernel installed. On systems with older kernels, the kernel parameters i8042.nomux i8042.reset i8042.noloop i8042.nopnp may help.

• Graphical artifacts, e.g. when scrolling within the user interface (such as in the terminal)
• CPU remains permanently in low power mode regardless of workload

Why doesn’t my device with an AMD processor support 6 GHz Wi-Fi (Wi-Fi 6E)?

When combining an AMD processor with an Intel Wi-Fi module, the 6 GHz band is currently not supported. Intel does not enable this frequency range for its Wi-Fi modules when used with AMD CPUs. As a result, no corresponding certification from Intel and the Wi-Fi Alliance can be obtained. Technically, 6 GHz Wi-Fi would be possible on AMD systems using Mediatek Wi-Fi modules, but these come with their own limitations and issues.

Driver for Motorcomm YT6801 LAN chipset (with AMD)

The Motorcomm YT6801 LAN chipset installed in the device requires a driver that is already integrated into TUXEDO OS but is often missing in other distributions. You can add the driver to Fedora and Ubuntu using the following packages. Please note that Secure Boot must be disabled in the BIOS/UEFI for the driver to load successfully.

• tuxedo-yt6801_1.0.28–1_all.deb
• tuxedo-yt6801–1.0.28–1.noarch.rpm