openSUSE Tumbleweed Setup Guide

A friendly setup guide for openSUSE on ASUS laptops

openSUSE Tumbleweed

OpenSUSE Tumbleweed is a rolling release distribution and should be chosen over openSUSE Leap. Tumbleweed gives users access to the latest software packages and updates, providing better compatibility with ASUS laptops than Leap. However, users with newer laptop models may run into issue. Please see the Considerations section for more details.

All updates to the official repos are incorporated into snapshots and tested with openQA prior to release. This means that Tumbleweed is slightly behind a bleeding-edge distro, such as Arch, but that all updates to the official repos are thoroughly tested.

KDE Plasma is the flagship openSUSE Tumbleweed Desktop Environment. The installer also supports GNOME, Xfce, and many others (including Window Managers).


Users coming from other distributions may run into issues when using Tumbleweed due its default settings. This guide attempts to point out some of these within the relevant sections. A few general items that a user should be aware of before trying openSUSE are:

  1. Custom kernels are difficult with openSUSE. This means the rog/asus-kernel is not supported. Newer laptops will need to wait until any required patches are merged from the rog/asus-kernel into the upstream kernel.
  2. The package manager is zypper, which is RPM-based and relatively similar to Fedora's dnf. The Arch wiki provides a helpful table comparing common package manager commands.
  3. zypper should be used to install packages instead of YaST, KDE Discover, or GNOME Software. These GUI tools may still be useful for flatpaks and searching, but do not use them to install other packages.
  4. Occasional mirror issues, while rare, do exist. Workarounds are required to continue updating the system and installing packages.
  5. Package updates in Tumbleweed are performed through zypper dup (dist-upgrade), not zypper up (update). For more information, see the openSUSE wiki.
  6. OpenSUSE is not as widely used as Fedora or Arch, so some software may not be available. Flatpaks, the Open Build Service, and third-party repositories help alleviate this issue. Note that only official packages are tested as part of the Tumbleweed openQA testing.
  7. OpenSUSE uses the concept of patterns, which include base and recommended software packages. These patterns may result in packages being re-installed, even if you specifically removed them. More information is available on the openSUSE user documentation project.
  8. OpenSUSE community websites may provide "one-click installers", which can cause more trouble than they're worth. Avoid using these.
  9. OpenSUSE provides excellent support for the btrfs file system, and supports automatic bootable btrfs snapshots out of the box.
  10. OpenSUSE provides the YaST GUI tool for system management. YaST is polarizing, but may be helpful for new users to get a better idea of the system configuration. Many operations should still be performed via the terminal instead.


Prior to installation of openSUSE Tumbleweed, follow the instructions in the Preparations section of the Fedora Guide. The list below gives a summary of the important subsections to review.

  1. Proprietary eSupport Drivers Folder - Backing up the proprietary ASUS drivers.
  2. Disable Secure Boot - Disabling secure boot for compatibility with the proprietary Nvidia drivers.
  3. Use the Laptop Screen - Background on installation problems that may arise due to external screens.


Installation Media

The openSUSE Tumbleweed website contains all of the installation images. The offline image is much larger than the network image, but allows installing all packages included without an internet connection. All of the packages will be dated to when the offline image was created. The net installer will pull the latest packages from the openSUSE repositories. It is possible to do this in the offline installer by connecting to the internet and enabling the internet repositories.

Live images also exist on the openSUSE Tumbleweed website. These are located under the Alternative Downloads link on the page. These Live images are similar to what users are used to with other distributions. Live images should be safe for most users. However, the openSUSE Tumbleweed website and openSUSE User Documentation Project warn that issues may occur when installing with a Live image. Please review these warnings on the associated links prior to continuing.

Installing openSUSE Tumbleweed

  1. Download the chosen ISO file from the openSUSE Tumbleweed website and write it to a USB stick. The network and Live ISOs requires a fast internet connection due to the number of downloads.

    Note: Ventoy has known issues and is not considered supported by openSUSE. It can be used, but manual intervention is required after installation.

  2. The online repositories can be enabled with the offline ISO to pull the latest packages. The network ISO does this automatically.

  3. Follow the steps of the installer, choosing a partitioning scheme and Desktop Environment.

  4. The final Summary page allows disabling Secure Boot, if it will not be used, and allows customizing the Software that will be installed.

  5. The system will automatically reboot after installation.

  6. At the grub menu after reboot, press the the E key to modify the boot parameters. Nvidia users should add modprobe.blacklist=nouveau to the Kernel command line arguments to ensure the Nouveau drivers do not cause issues.

    Note: If Ventoy was used, the Kernel command line arguments may contain rdinit=/vtoy/vtoy. This MUST be removed as it will prevent the system from booting. Include this change in the step below.

  7. Once the system boots, log in and make any necessary changes to the GRUB_CMDLINE_LINUX_DEFAULT parameter in /etc/default/grub.

  8. Regenerate grub to prevent repeating the previous steps on every boot.

    sudo grub2-mkconfig -o /boot/grub2/grub.cfg


Notes on Btrfs Snapshots

It is helpful to take snapshots throughout the setup process if using the btrfs filesystem. Pre and post snapshots are automatically taken when installing and updating packages. The "openSUSE-style" snapshots allow booting into the last-known working state through the grub menu. The system will boot into a read-only filesystem based on the chosen snapshot, which the user can explore to ensure the system is working. The system can be restored to the snapshot using the command snapper rollback. More information is available on the openSUSE user documentation project.

Remove the Installer ISO Repository

The openSUSE installer automatically adds a repo entry for the installation media. This feature is more geared toward offline or enterprise systems, not personal devices. Removing the repository will ensure that updates will not fail if the installation media is not found. Command line is the preferred method of removal, but the YaST GUI can be used.

  1. List the currently active repositories:

    sudo zypper lr -d
  2. From the outputs, identify the repo number that corresponds to the installation media. The offline image will likely have DVD in the title. The network image should include a date in the title.

  3. Disable the repo, replacing # with the number identified from the previous steps:

    sudo zypper mr -d -F #
  4. Remove the repo, replacing # with the number identified from the previous steps:

    sudo zypper rr #
  5. Force a refresh of the repositories:

    sudo zypper ref -f

Update the System

  1. Refresh the repositories:

    sudo zypper ref
  2. Update the system via dist-upgrade (dup):

    sudo zypper dup

Adding the wheel group

By default, openSUSE does not automatically add the user to the wheel group. This prevents asusctl and ROG Control Center accessing DBus when run with user privileges. The resulting error messages are similar to Error: org.freedesktop.DBus.Error.AccessDenied. Additionally, the default setup requires the root password when a user runs sudo. This may cause confusion if the user is coming from other distributions. The openSUSE wiki has a guide for setting up sudo behavior in a way that users may be more familiar with.

  1. Open the terminal and switch to the root user:

  2. The wheel group should present by default, but can be verified with:

    grep ^wheel /etc/group
  3. If the wheel group is somehow not present, add it:

    groupadd wheel
  4. Add a user to the wheel group, replacing USERNAME with the desired user:

    usermod -aG wheel USERNAME
  5. Optionally, verify the user was added to the wheel group, replacing USERNAME with the desired user:

  6. Log out or restart for the changes to apply.

Third Party Repositories

The official openSUSE repositories have many restrictions due to strict copyright and IP laws. Third party repositories contain additional packages that are not or cannot be included in the openSUSE OSS and non-OSS repos. Using dependencies from multiple repositories may result in instability and issues. To avoid this, it is recommended to change the vendor for packages to the third party repositories being used. The openSUSE wiki has a guide for setting up commonly used third party repos. Note that only the official repos are included in the openQA testing, so it will not catch any issues related to the additional packages.

All repos use priorities (higher number = lower priority). The official repos are added with the priority of 99 (default). Adding third party repos with a lower number results in packages being installed from them, if available.

Install Nvidia Graphics Drivers

A guide to installing the proprietary Nvidia drivers can be found on the openSUSE wiki. Verify the numbering scheme for the Nvidia card using the instructions on the wiki. The instructions below show how to install the G06 version, for newer devices.

  1. Open the file /etc/zypp/zypp.conf.

  2. Ensure the following line is not commented out:

    multiversion = provides:multiversion(kernel)
  3. Add the Nvidia repo with auto-refresh and a non-default priority (e.g., 90):

    sudo zypper ar --priority 90 --refresh NVIDIA
  4. Install the nvidia-driver-G06-kmp-default package, which should result in all needed packages being installed:

    sudo zypper in nvidia-driver-G06-kmp-default
  5. Search for G06 to verify the additional packages (e.g., nvidia-glG06) were installed:

    zypper se G06
  6. If matching G06 Nvidia packages do not have an i or i+ next to them, install them.

  7. Note that the driver installation process may take 10+ minutes.

  8. After installation, one can verify the driver version:

    sudo modinfo -F version nvidia
  9. Reboot the system.

Update System Boot Configuration for Nvidia

  1. The Nvidia driver installation should handle adding the required Kernel command line arguments.

  2. If issues are encountered, try adding the following to GRUB_CMDLINE_LINUX in /etc/default/grub:

    modprobe.blacklist=nouveau rd.driver.blacklist=nouveau nvidia-drm.modeset=1
  3. After the modifications, regenerate grub with:

    sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Asus-Linux Software

Adding the Repository

The repository for the asus-linux software is hosted on the Open Build Service. As a third party repo, it needs to be added prior to installation. To add the repo with a priority of 50 (as an example), auto-refresh, and asus-linux as the alias:

zypper ar --priority 50 --refresh asus-linux

Asusctl - custom fan profiles, anime, led control etc.

  1. The tlp software is known to conflict with power-profiles-daemon and should be removed. It is installed with the default openSUSE installer settings.

    sudo zypper rm tlp
  2. Next, install asusctl:

    sudo zypper in asusctl
  3. Ensure that power-profiles-daemon is enabled and running:

    sudo systemctl enable --now power-profiles-daemon.service
  4. Either restart the system, or run the following command to immediately begin using asusctl:

    sudo systemctl start asusd
  5. Note that due to the difficulty of custom kernel support on openSUSE Tumbleweed, features for the newest laptop models may not always work.

Supergfxctl - graphics switching

Supergfxctl allows for graphics switching and managing the laptop's iGPU/dGPU. OpenSUSE may install suse-prime, which conflicts with supergfxctl. They should not be installed simultaneously. Supergfxctl is recommended over suse-prime in the vast majority of cases.

  1. Remove suse-prime prior to installing supergfxctl:

    sudo zypper rm suse-prime
  2. Install supergfxctl:

    sudo zypper in supergfxctl
  3. Enable and start the supergfxd service:

    sudo systemctl enable --now supergfxd

ROG Control Center

The optional ROG Control Center GUI tool can be installed to assist with control of asusctl and supergfxctl settings.

sudo zypper in asusctl-rog-gui

GUI Main Window

GUI Fan Curve

Optional Steps

Enabling ZRAM

Unlike Fedora, zram is not enabled by default. The zram-generator package can be installed to set up and use zram instead of traditional swap. The Arch wiki's guide on zram can be used as a reference. The steps below set up zram using the Fedora 37 default configuration and one additional option:

  1. Ensure zswap is disabled to avoid conflicts with zram. The process can be found on the Arch wiki.

  2. Install zram-generator to handle zram creation:

    sudo zypper in zram-generator
  3. Create a zram configuration file at one of zram-generator's expected locations, such as /usr/lib/systemd/zram-generator.conf

  4. Edit the newly created configuration file.

  5. Fedora 37 Default: add the following to the configuration file:

    zram-size = min(ram, 8192)
  6. Optionally, the compression-algorithm parameter can be added to specify compression algorithm used by zram. The default value is lzo-rle on openSUSE Tumbleweed, which is set if this parameter is not present.

    compression-algorithm = zstd
  7. Reboot the system.

  8. Verify zram was added by using the zramctl or swapon commands. A zram0 item should be present.

Open Build Service

The Open Build Service (OBS) is a service that supports community-maintained packages, such as asusctl. The openSUSE wiki has instructions on how to add some popular repos from the build service, such as the latest Wine (based on Wine-HQ), games, and more.

With the exception of home:luke_nukem, a common recommendation is to avoid home repos in the OBS. These repos can cause issues unless you know know or trust the maintainer.

The OBS Package Installer (opi) is a helpful tool that allows users to search the OBS and other vendors (e.g., Packman) for specific packages. It can be used to identify what packages are available on the OBS or elsewhere, along with getting links to review them. Opi prompts the user based on matching package names and build locations it finds (there are usually multiple). The chosen repo will be automatically added by opi when installing packages.


Packman is one of the most commonly used third party repositories for openSUSE. It contains a large set of additional packages like codecs, Discord, OBS Studio, and Steam. Follow the guide on the openSUSE wiki to add the Packman repo. Be sure to follow the zypper dup step to ensure that any existing packages (from the official repos) are updated to pull from Packman. This will help prevent dependency issues. Each future zypper dup will then pull update the packages from Packman instead.

The opi tool can be used to install multimedia codecs directly from Packman. This is an alternative to running the zypper commands manually. Adding the Packman repo prior to opi codecs may result in the Packman repo being added twice. This occurs if the alias used is not what opi expects (e.g., "packman" versus "Packman"). If this happens, one repo can be deleted through the method to remove the installation ISO repository (earlier in this guide).


Flatpaks also solve some of the issues with the lack of software available in the openSUSE repositories. They also provide the benefits of containerized applications. Flatpak may be automatically installed with the default installation settings, but the Flathub repo may need to be added. More information is available on the openSUSE user documentation project.

Legal Matters

ASUS and ROG Trademark is either a US registered trademark or trademark of ASUSTeK Computer Inc. in the United States and/or other countries.

Reference to any ASUS products, services, processes, or other information and/or use of ASUS Trademarks does not constitute or imply endorsement, sponsorship, or recommendation thereof by ASUS.

The use of ROG and ASUS trademarks within this website and associated tools and libraries is only to provide a recognisable identifier to users to enable them to associate that these tools will work with ASUS ROG laptops.

Privacy Policy

We use Matomo

Matomo is an open source web analytics platform. A web analytics platform is used by a website owner in order to measure, collect, analyse and report visitor data for purposes of understanding and optimizing their website.

Purpose of the processing

Matomo is used to get an idea how our website is used by our users so we can optimize things further so that the user may find the most relevant information more quickly.

Data Matomo is processing

  • User IP address
  • Optional User ID
  • Date and time of the request
  • Title of the page being viewed
  • URL of the page being viewed
  • Referrer URL
  • Screen resolution being used
  • Time in local user’s timezone
  • Files that were clicked and downloaded
  • Links to an outside domain that were clicked
  • Page generation time
  • User location: country, region, city, approximate latitude and longitude
  • Main Language of the browser being used
  • User Agent of the browser being used

Pick up the one you are using:

  • Cookies
  • IP address
  • User ID
  • Custom Dimensions
  • Custom Variables
  • Location of the user

And also:

  • Date and time
  • Title of the page being viewed
  • URL of the page being viewed
  • URL of the page that was viewed prior to the current page
  • Screen resolution
  • Time in local timezone
  • Files that were clicked and downloaded
  • Link clicks to an outside domain
  • Pages generation time
  • Country, region, city
  • Main Language of the browser
  • User Agent of the browser

This list can be completed with additional features such as:

  • Form interactions
  • Media interactions
  • A/B Tests

The processing of personal data with Matomo is based on legitimate interests

If you wish us to not process any personal data with Matomo, you can opt-out from it at any time. There will be no consequences at all regarding the use of our website.

You can withdraw at any time your consent by clicking here

The right to lodge a complaint with a supervisory authority

If you think that the way we process your personal data with Matomo analytics is infringing the law, you have the right to lodge a complaint with a supervisory authority.

We are not doing any profiling.