System76 Oryx Pro

All necessary packages can be found in the AUR. It is recommended to install everything in the list below.

Modules

• system76-dkms^AUR
• system76-io-dkms^AUR

Daemons

• (needed for System76 switchable graphics)
• (seems to be needed for things like audio to work right)

Other

• system76-firmware^AUR (required if you want to update your BIOS)
• (required if you want to know when there is a BIOS update available)
• (if you want to change your keyboard's backlight color)

(There are also "-git" versions of many of these packages, if you wish to stay bleeding edge.)

Once you have installed the above, you will need to tell your computer to use them.

Enable the following services: (source)

• system76-firmware-daemon

To make sure all drivers are being loaded correctly, run ; this will automatically add necessary rules to , and execute .

To enable switchable graphics, run once; and then put prime-run before every application you want to start with your dGPU. Note that this will only work for applications that use GLVND. (source)

To verify whether switchable graphics is working, run and . These commands should succeed and have different vendors. If the latter command fails, go to #prime-run not working. (Note that you can limit the output to just the relevant information by appending to the aforementioned commands.)

You can control the brightness and color of your keyboard's LEDs. To do so, simply run sys76-kb set -b $B -c $C, with being how bright you want the keyboard (on a scale of 0-255) and being a 6-digit color hex (eg, "ffffff"). Since the keyboard's LEDs are controlled from the commandline, it is possible to script patterns and light shows.

Note that these settings are not maintained across boots; so you will need to reapply them on startup.

To check your current BIOS version and whether there is a new version available, run as root. Keep in-mind that this is a GTK application, so you need to be running X or Wayland for it to run. (It has no CLI -- it does not even respond to .)

To update your system to the latest firmware on the next boot, run system76-firmware-cli schedule.

The oryp7, as with all System76 computers, comes with a fan curve designed to minimize noise. By default, your fans will only reach 100% at 90°C; but by the time you have reached that temperature, the CPU is already throttling hard. By setting a custom fan curve that reaches 100% at 70°C, you can easily avoid such unnecessary throttling. However, in order to customize the fan curve, you have to compile and flash the EC to your BIOS (There is an open issue to add runtime-configurable fan curves here.). Make sure to not set your lowest fan speed below around 25% on the oryp7, as doing so can cause rattling (see #163). Some people will be able to use values as low as 20%; others may need to go up to 30% or higher. There is an open pull request with settings optimized for the oryp7 here. Note that even with this better curve, your computer will still run hot. You will need to repaste the oryp6/7 if you intend to use the CPU for long periods of time.

Another thing you can try is undervolting. However, due to Plundervolt, undervolting has been disabled in the firmware. There is an issue on GitHub requesting a toggle for this mitigation.

does not currently support runtime configuration of fan speeds, so  and  will not work. There is an open feature request for this, though.

In the meantime, a custom fan curve can be configured by those willing to compile their BIOS manually. Quoth one of the devs: "The fan speed is controlled by the fan curve in the firmware: system76/ec@16778e4/src/board/system76/oryp7/board.mk. You can change the fan curve by changing the values in that file before you build firmware-open." You do not actually have to build , though -- you can simply build and flash the ec itself. The command to flash is make BOARD=system76/oryp7 flash_internal.

Set your keyboard brightness to 100%. There is a known issue with the firmware on oryp6/oryp7 when the brightness is less than 100%.

Try creating and adding the following to it: (source)

Change the fields above to match the first field in the output of this command: (you can omit leading zeroes). You will need to restart your X server for this to take effect.

If you find (normally after an update & restart) that launching X (via or otherwise) does not work, you may confirm that the device is installed and working by doing the following:

Confirm the error in . The kernel module should successfully load. You may also confirm the error with dmesg or .

Check whether both integrated and discrete graphics cards are available:

# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] (rev a1)

If you do not see the second entry (or some similar NVIDIA card), make sure the card has been turned on by (use to explore options):

# system76-power graphics 

Check whether the discrete NVIDIA graphics card is powered on using :

# system76-power graphics power

To power the discrete NVIDIA graphics card on, supply "on" as an argument (i.e. ). After doing so and querying again, you should see:

# system76-power graphics power
on (discrete)

Once the card is powered on, it should show up in the output of , and be detectable by Xorg, given that the appropriate NVIDIA driver is installed.

If using the new (replacement) EFI mount point /efi, ensure you have the mount present in . You may find the appropriate device to mount by using a combination of lsblk and fdisk -l.

# fdisk -l # List disks (one device will be designated as "EFI System")
# lsblk    # List devices and mount points, you should see the EFI system device, and confirm whether it is mounted/unmounted
# mount device /efi
#
# genfstab -U / # (optional) print fstab configuration for inclusion/merging into /etc/fstab

After doing the above, it might be a good idea to schedule a firmware update:

# system76-firmware-cli schedule

After scheduling a firmware update, ensure that GRUB is set to use the EFI partition like so:

# grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=grub
# cp /boot/grub/grub.cfg /boot/grub/grub.cfg.bak
# grub-mkconfig -o /boot/grub/grub.cfg

Restart to trigger the firmware update.

If you have anything plugged-into the HDMI port on the back, this is why. Unplug your HDMI cord, boot the computer, and plug it back in after X starts. This issue only happens when the Nvidia card is used for display, either in or mode; so if you do not want Nvidia to do your graphics anyway, switching to or will fix this problem. If you actually do want to use your Nvidia card, though, there is currently no known fix; but watching Linus swear at Nvidia may prove therapeutic.

The oryp7 has a Realtek ethernet chip whose in-tree Linux driver is (as of Linux v5.15) guaranteed to fail link autonegotiation. You can work around this issue by manually setting your onboard ethernet's link negotiation to 'ignore' or '100mbps' (How you do so depends on your computer's network manager.); however, both options mean that your Internet speed will be capped at 100mbps. In order to get your ethernet port to work at speeds above that, you will need to install Realtek's out-of-tree driver, with , r8168-lts, or (Although r8168 is out-of-tree, it is still open-source and GPL-licensed.). Once installed, you need to blacklist the default r8169 driver: .