Calling All Ally X20 Owners — Support Arrives on Our Testing Branch, Acer Predator Atlas Makes its Debut Too!

Bazzite
1

I’m absolutely loving my X20! Between the larger screen compared to the Xbox Ally X, the OLED display, and HDR support, I’m really happy I picked it up. It also just feels better to hold than the Legion Go 2!

We’ve already ironed out most of the major kinks, but there are still a few smaller issues we could use your help tracking down. If you’re interested in pitching in, Ally X20 support is now available on our testing branch!

What’s Going Well?

  • Display: Full support, including VRR and HDR
  • TDP Control: Working, though custom TDP still needs some investigation
  • Back Buttons: Fully mappable
  • Sleep/Wake: Working well in our testing
    • It’s difficult to cover every sleep/wake edge case, so please capture logs if you encounter any issues.

What Still Needs Work?

  • RGB Lighting
    • Support is expected with upcoming drivers from the OGC.
  • Fan Control
    • Like our other devices, fan control will eventually be handled through OGUI plugins.
    • In the meantime, Decky plugins such as Panel de Control may offer a workaround.

Acer Predator Atlas 8 Enablement Begins

After some hard work by some of our maintainers and friends at the OGC the ACER Predator is receiving some of its first commits.

  • Initial button mapping is available allowing it to he used for games.
  • Hold the Guide (top left button next to the screen) to access the left side menu.
  • QAM/Predator (top right button next to the screen) tap functionality had been added so you can access the right side menu.
  • Holding QAM will open the OpenGamepadUI overlay once it is enabled for this device
  • Drivers will be needed upstream to enable tap functionality, and that work is already underway.
  • M1 and M2 does not work yet
  • Gyroscope does not work in linux

How to Jump In

1. Pin Your Current Working Deployment

Before rebasing to testing, we strongly recommend pinning your current deployment:

sudo ostree admin pin 0

This preserves your working deployment and gives you a reliable fallback if something goes wrong.

If you later return to Bazzite’s stable channel and want to remove the pin, first identify the deployment index:

rpm-ostree status -v

Then unpin the appropriate deployment:

sudo ostree admin pin --unpin <deployment-number>

Note: Pinning preserves a deployment, but doesn’t automatically switch you back to it. Keep your fallback pinned until you’ve confirmed your new deployment works correctly.

2. Rebase to Testing or Unstable

You can switch channels through the Bazzite Portal app or use the terminal:

Testing:

brh rebase testing

Unstable:

brh rebase unstable

3. Help Us Keep Testing Organized

GitHub is our source of truth for tracking and resolving issues. To make sure reports are actionable and don’t get lost:

  • Threads in testing-help must have an associated GitHub issue.
  • Capture logs using ujust logs-this-boot and attach them to your GitHub issue.
  • Include relevant information such as your Bazzite image, hardware specifications, steps to reproduce, and rpm-ostree status -v output.
  • Threads without an associated GitHub issue will be removed to keep the forum organized.
  • If you’re unable to create an issue yourself, don’t worry! We’ll work with you to get one filed.

The more hardware and real-world scenarios we can validate, the better Bazzite gets for everyone. Your testing helps us catch issues we might never encounter on our own hardware.

Thanks to everyone who’s helping us make this release better!

2 Likes