Fedora 36 Workstation Setup Guide

🔗Fedora 36 Setup

The recommended flavour of Linux by asus-linux.org is Fedora, for its ease of use for new users, friendly community, and good support for the latest hardware. This guide is written for Fedora 36.

This guide does not cover the choices of running Windows and Linux, or only Linux on your device, and their respective partitioning requirements.

For additional information not covered by this guide, see the installation instructions: Official Fedora install guide

For simple USB stick flashing: Fedora Media Writer


🔗Backup Propietary eSupport Drivers Folder

Stock installations of Windows on ASUS laptops include propietary drivers that cannot be sourced directly from the ASUS website or the MyASUS utility. Before removing the Windows partition or recovery partition these drivers should be backed up. If you ever decide to dual boot or run Windows in a VM, you will need a copy of the drivers for your specific model.

The folders can be found in C:\eSupport

Make sure to backup this folder before performing any destructive operations on your Windows partition!

🔗Disable Secure Boot

To make sure Nvidia drivers and the necessary support modules work without issues, Secure Boot must be disabled in the UEFI.

  1. Press DEL repeatedly during boot to enter UEFI setup screen
  2. Press F7 for advanced mode
  3. Security → Secure Boot Control → Disable
  4. Save and exit

🔗Use the Laptop Screen

Due to display signal routing on Asus ROG laptops, and the setup process dealing with multiple graphics devices, having external screens connected during setup may result in unpredictable behavior. Please follow this guide with all external displays disconnected.


  1. Download Fedora 36 Workstation ISO file from the official Fedora website and write it to a USB stick.
  2. If you have difficulties starting the live environment from USB, in the Fedora boot menu select: Troubleshooting → Start Fedora in basic graphics mode
  3. Follow the steps of the installer, and remove the USB stick when you reboot
  4. After rebooting, the installer will present a series of dialog boxes to configure wireless networking, privacy, third party repositories, cloud services, and finally a local user account. Ensure that third party repositories are enabled, so that the proprietary NVIDIA drivers can be installed (covered later in this guide).


🔗Update the System

System update should be done after setting up the repos and copr.

🔗Using the Terminal

This guide requires typing terminal commands. To type them, start the Terminal application, which opens a window that has a command prompt.

To open the Terminal, simply press the Windows/Meta key to bring up the Activities view, and start typing "term" in the search box. Click on the search result.

Terminal in search bar

Commands that have sudo in front are administrator commands, and may require you to type in your password.

🔗Edit Default Package Repositories

First, edit the package repositories to exclude kernel updates from Fedora. Starting from 5.17.x, the required patches have been merged into upstream and step 1 is no longer required; asusctl uses a copr to get updates:

1. Edit the package repos:

  1. Add the copr for asusctl
    sudo dnf copr enable lukenukem/asus-linux

🔗Do Update

  1. Open Software store

  2. Navigate to Updates tab

  3. Click the Refresh-button in the top left corner

  4. Download all available updates

    Software Updates

  5. After the updates have been downloaded, click the "Restart & Update" button

    Software Updates

  6. When the updates have been installed, reboot your computer

NOTE: Upon restart the device is still possibly running in software rendering mode, symptoms:

  • Laggy desktop
  • Black screen after reboot
  • Suspend on lid close not working
  • Screen brightness control not working
  • Multi-touch gestures not working This will all be addressed in the later steps.

🔗Install Nvidia Graphics Drivers

The next step is to install the drivers for the Nvidia GPU.

  1. If you didn't enable third-party repositories during the initial install wizard, you can use the following command to enable the RPM Fusion repositories required to install the Nvidia drivers:

    sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
  2. Input the following terminal commands:

    sudo dnf update -y
    sudo dnf install kernel-devel
    sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-power
  3. Enable Nvidia power services:

    sudo systemctl enable nvidia-hibernate.service nvidia-suspend.service nvidia-resume.service

🔗Update System Boot Configuration

  1. In Terminal, launch the text editor to edit the system boot options.

    sudo gedit /etc/default/grub

    Edit the file to look like below. Note that if disk encryption was enabled during installation, there will be additional configuration text in the GRUB_CMDLINE_LINUX line that must be preserved.

    GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
    GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=0 rhgb quiet"

    There are usually only two modifications to make:

    1. Change the value of nvidia-drm.modeset=1 to nvidia-drm.modeset=0. This change is needed to allow switching between graphics devices without needing a reboot but will prevent external display working.
    2. Fedora installer may create duplicates of rd.driver.blacklist=nouveau, modprobe.blacklist=nouveau, and nvidia-drm.modeset=1. These duplicates can be safely deleted.

    Optionally, if the install guide has been deviated from, the same line of text that contains the previous changes may also contain a standalone word nomodeset. This must be removed or graphics acceleration is disabled.

    Save the file and close the editor.

  2. Update grub:

    The edits made to the grub file need to be updated to the system. This is just a single terminal command.

    sudo grub2-mkconfig -o /etc/grub2.cfg
  3. Reboot


nvidia-drm.modeset=0 may prevent use of the dGPU connected display output if you have one. It might also prevent some screen mode changes. If things are not behaving as you would expect then set this to 1 - this does mean that supergfx will require you to reboot to change gpu modes however.

🔗Install asusctl

The final section is to install asusctl and its supporting software. This enables controls for the Asus ROG hardware on the laptop.

  1. Install asusctl

    sudo dnf install asusctl supergfxctl
    sudo dnf update --refresh
    sudo systemctl enable supergfxd.service
  2. Reboot

    After the reboot, you should have a fully functional Fedora laptop, with ROG hardware features enabled.

Please note that asusctl/supergfxctl is under continuous development, and will improve in capability over time.

🔗Optional Steps

🔗Enabling Secure Boot

With Fedora 36 and above, it has become super easy to auto sign kernel modules and enable secure boot. To enable auto signing follow these steps:

  1. Install the required tools
sudo dnf install kmodtool akmods mokutil openssl
  1. Initiate the key enrollment

NOTE: This step requires a password, it doesn't need to be fancy. You'll just need it once during the enrollment.

sudo mokutil --import /etc/pki/akmods/certs/public_key.der
  1. Reboot to enroll the key. When you reboot, the MOK Manager will appear, just hit "Enroll MOK" and enter the password set in step 2. After that is completed choose "Continue boot".

  2. Rebuild the kernel module. The key has successfully enrolled but our kernel modules that have been built before are still unsigned, to sign them, they need to be rebuilt again, below the process is explained for NVIDIA kernel module.

sudo dnf remove kmod-nvidia #Remove the previously built module
sudo dnf reinstall akmod-nvidia
sudo akmods --force #Rebuild the NVIDIA Module

From now on the NVIDIA kernel module will be automatically signed when there is a kernel update or driver update.

  1. Enable Secure Boot from BIOS.

🔗Keyboard Backlight

If the keyboard backlight does not work automatically, set a mode in asusctl:

asusctl led-mode static

🔗RGB Backlights

If an RGB capable laptop has no led modes available, then the /etc/asusd/asusd-ledmodes.toml file needs adjusting:

cat /sys/class/dmi/id/product_family # provides the prod_family var,
cat /sys/class/dmi/id/board_name # provides name to be added to board_names.

Edit the configuration file and add the needed values:

sudo gedit /etc/asusd/asusd-ledmodes.toml

Save the file and close the text editor.

🔗Switching from Nvidia GPU to AMD Integrated

If the laptop has booted in Nvidia mode, switching to AMD integrated graphics and the Wayland desktop requires a reboot. To fix this so the switch only requires a logout/login, change the following:

sudo gedit /lib/udev/rules.d/61-gdm.rules

Edit the following lines of text to have a hash in the front, as in the example. This will disable the settings.

# ATTR{parameters/modeset}!="Y", GOTO="gdm_disable_wayland"

Save the file and close the editor.

Reboot to enable the change.

🔗Hide an Unnecessary Boot Message

When booting the computer in integrated mode, a message displays "Nvidia kernel module not found. Falling back to Nouveau." This is harmless and normal for asusctl integrated mode, but may feel distracting. To disable the message, input this terminal command:

sudo systemctl mask nvidia-fallback.service

🔗Desktop Wigdets

A desktop widget to operate some aspects of asusctl and supergfxctl: GNOME Shell extension asusctl-gex

🔗Known Limitations

🔗Nvidia GPU suspend issue on 2020 models of Zephyrus G14 and G15

Be aware that the Nvidia GPU on the 2020 models of G14 and G15 has an issue concerning power draw. In general, the GPU fails to enter a low-power state even when idle, and this causes unnecessary power draw and heat generation. This issue has been addressed in the 2021 models. Things have improved for the 2020 models with Wayland and the 470 driver (read below).

🔗Nvidia Graphics on Wayland Desktop

The default Gnome desktop in Fedora 34 and newer uses a new protocol called Wayland. Since the 470 Nvidia driver version it is possible to run Wayland desktop on Nvidia GPUs. This is a major update to the capability and utility of Nvidia graphics on ROG laptops, but because this is a new development, there are still lingering issues.

  1. Exclusive Nvidia mode does not work Currently the asusctl Nvidia mode which runs everything exclusively on the more powerful GPU does not work. This is due to a remaining issue on the 470 driver related to technology called Reverse-PRIME, a method of passing graphics rendered by the Nvidia GPU back to the AMD integrated graphics.

  2. USB-C DisplayPort output does not work on Wayland Another Reverse-PRIME issue is that if you need to use an external display with the DisplayPort connection (via USB-C or a dock), it only works on the X.org desktop. This issue does not affect all ROG laptop models, but depends on their internal signal routing.

  3. Compute vs. hybrid on Zephyrus G14 and G15 Currently the best way to take advantage of Nvidia graphics on Wayland desktop is to use asusctl integrated graphics mode, and enable compute if you wish to run applications using the Nvidia GPU. In compute mode, the Nvidia GPU automatically suspends even on 2020 models when it has no active processes, reducing power consumption. On these laptops, compute mode can also be disabled manually without requiring a logout/login.

    Hybrid mode is also operational on Wayland, and there are early reports of a slight performance benefit. On 2020 G14 and G15 the hybrid mode suffers from the GPU suspend issue, increasing power consumption and heat output when idle.

    Both modes currently offer the same functionality despite their naming because Wayland does not respect X.org settings.

  4. Disabling compute If asusctl fails to disable compute, there are likely active processes still using the Nvidia device. Check for these with nvidia-smi and lsof /dev/nvidia* commands.

  5. Resuming from suspend Applications that were running on the Nvidia GPU may have all-black windows after resuming from sleep. No workaround for this issue exists yet. Enabling Nvidia suspend/resume/hibernate services does not address the matter.

For older Nvidia drivers (pre-470) whenever Nvidia graphics are enabled, in either standalone or hybrid mode, using the X.org desktop is necessary.

To select the correct desktop environment, click on the gear icon in the bottom right corner of the login screen. Select "Gnome" with asusctl in integrated graphics mode to run Wayland, or "Gnome on Xorg" when Nvidia graphics are enabled in hybrid or exclusive mode.

Has this guide helped you setting your machine?

If this site helps you and you want to contribute we welcome you to help with development, search for issues, join the discord, and add to this website.

You can also donate

Your support on Pateron or Paypal helps us buy ASUS devices for development to support new features and drivers.
Patreon button image or PayPal button image