Skip to content

Garuda hardware profiles

The Garuda hardware profiles are meta packages that pull in the graphics drivers and the driver settings for a system. They are built from one split package, garuda-hardware-profiles (pkgbuilds/garuda-hardware-profiles, version 2.0.1 release 3). Together with Garuda Hardware Tool, they replace MHWD. The changelog 260819 marks the change with Remove garuda-settings-manager, mhwd. Replace with garuda-hardware-tool and garuda-hardware-profiles.

Garuda Hardware Tool picks the profiles that fit your hardware and installs them. Its page covers the detection rules and the options. This page covers the packages themselves.

PackageDescription in the PKGBUILDBuilds on
garuda-hardware-profile-standardGaruda Linux hardware profile with opensource driversNothing. It is the base of all others.
garuda-hardware-profile-standard-x11Garuda Linux hardware profile with opensource x11 driversgaruda-hardware-profile-standard
garuda-hardware-profile-vmGaruda Linux hardware profile for virtual machinesgaruda-hardware-profile-standard
garuda-hardware-profile-nvidiaGaruda Linux hardware profile with nvidia driversgaruda-hardware-profile-standard
garuda-hardware-profile-nvidia-580xxGaruda Linux hardware profile with nvidia 580xx driversgaruda-hardware-profile-standard

garuda-hardware-profile-standard installs the open source Mesa, Intel and AMD user space drivers with their 32-bit versions.

FieldPackages
Dependsvulkan-intel, vulkan-radeon, intel-media-driver, libva-intel-driver, libva-mesa-driver, vulkan-mesa-layers, vulkan-swrast, lib32-vulkan-intel, lib32-vulkan-radeon, lib32-libva-intel-driver, lib32-libva-mesa-driver, lib32-vulkan-mesa-layers
Optionalopencl-mesa, lib32-opencl-mesa, intel-compute-runtime
Providesvulkan-driver, lib32-vulkan-driver
Replaceszdummy-vlkdrv

It installs no config files.

garuda-hardware-profile-standard-x11 adds the Xorg drivers for AMD and NVIDIA cards on top of the standard profile.

FieldPackages
Dependsgaruda-hardware-profile-standard, xf86-video-ati, xf86-video-amdgpu, xf86-video-nouveau
Providesgaruda-video-linux-config
Replacesgaruda-video-linux-config

The PKGBUILD comment says it replaces the MHWD package since we can not be sure what the user has installed.

garuda-hardware-profile-vm installs the guest tools for VirtualBox, VMware, SPICE and QEMU.

FieldPackages
Dependsgaruda-hardware-profile-standard, xf86-video-fbdev, virtualbox-guest-utils, open-vm-tools, xf86-input-vmmouse, spice-vdagent, qemu-guest-agent, gtkmm3
Replacesgaruda-virtualmachine-guest-config
FileContent
/usr/lib/systemd/system/garuda-virtualmachine-guest-config.targetWants vboxservice.service, vboxclient.service, vmtoolsd.service, spice-vdagentd.socket and qemu-guest-agent.service. Wanted by multi-user.target.
/usr/lib/systemd/system/garuda-virtualbox-live.serviceRuns chmod 666 /dev/vboxuser so that the user side guest additions work (clipboard, drag and drop). Runs only when /dev/vboxuser exists.

The install script enables garuda-virtualmachine-guest-config.target on install and disables it on removal. Upgrades from versions older than 1.1.1-3 enable it too. Both units are also linked into ght-live.target.wants. See Live session.

The two NVIDIA profiles install the same config files and differ only in the driver branch.

Fieldgaruda-hardware-profile-nvidiagaruda-hardware-profile-nvidia-580xx
Drivernvidia-open-dkms>=590nvidia-580xx-dkms
Dependsgaruda-hardware-profile-standard, egl-wayland, nvidia-utils>=590, opencl-nvidia>=590, lib32-nvidia-utils>=590, lib32-opencl-nvidia>=590, nvidia-primegaruda-hardware-profile-standard, egl-wayland, nvidia-580xx-utils, opencl-nvidia-580xx, lib32-nvidia-580xx-utils, lib32-opencl-nvidia-580xx, nvidia-prime
Providesgaruda-nvidia-config, GARUDA-HARDWARE-PROFILE-NVIDIAGARUDA-HARDWARE-PROFILE-NVIDIA
ConflictsGARUDA-HARDWARE-PROFILE-NVIDIAGARUDA-HARDWARE-PROFILE-NVIDIA
Replacesgaruda-nvidia-config, garuda-nvidia-prime-config, garuda-hardware-profile-nvidia-primegaruda-hardware-profile-nvidia-closed, garuda-hardware-profile-nvidia-prime-closed

Both profiles provide and conflict with GARUDA-HARDWARE-PROFILE-NVIDIA. Only one of them can be installed at a time. nvidia-settings is not part of either profile. The changelog lists Remove nvidia-settings from requirements.

Installed pathSource fileContent
/usr/lib/modules-load.d/garuda-nvidia.confnvidia-modules-load.confLoads the nvidia-drm module at boot.
/usr/lib/modprobe.d/garuda-nvidia.confnvidia-modprobe.confoptions nvidia-drm modeset=1 and options nvidia-drm fbdev=1
/usr/lib/modprobe.d/garuda-nvidia-prime-powersaving.confgaruda-nvidia-prime-powersaving.confoptions nvidia "NVreg_DynamicPowerManagement=0x02"
/usr/lib/udev/rules.d/90-nvidia-prime-powermanagement.rules90-nvidia-prime-powermanagement.rulesRuntime power management for NVIDIA cards. See below.
/usr/lib/systemd/system/garuda-nvidia-live.servicegaruda-nvidia-live.serviceRuns modprobe nvidia_drm && modprobe nvidia-uvm. Linked into ght-live.target.wants.

The udev rules match PCI devices with vendor 0x10de (NVIDIA) and class 0x030000 (VGA) or 0x030200 (3D controller).

Eventpower/control set toComment in the rules file
bind or addautoEnable runtime PM for NVIDIA VGA/3D controller devices
unbindonDisable runtime PM for NVIDIA VGA/3D controller devices

See Switching between integrated and dedicated graphics for running programs on the NVIDIA card.

On the live ISO, ght-live.service runs Garuda Hardware Tool before the user session starts. It then starts ght-live.target. The profiles link their live units into ght-live.target.wants, so the target starts them.

ProfileUnits started by ght-live.target
NVIDIA profilesgaruda-nvidia-live.service
VM profilegaruda-virtualmachine-guest-config.target, garuda-virtualbox-live.service

The changelog entry for this reads Load nvidia modules and virtualmachine services automatically when in live session. The live script logs to /var/log/ght-live.log.

The replaces arrays above define how pacman moves an older system to the new profiles.

Old packageNew package
zdummy-vlkdrvgaruda-hardware-profile-standard
garuda-video-linux-configgaruda-hardware-profile-standard-x11
garuda-virtualmachine-guest-configgaruda-hardware-profile-vm
garuda-nvidia-config, garuda-nvidia-prime-config, garuda-hardware-profile-nvidia-primegaruda-hardware-profile-nvidia
garuda-hardware-profile-nvidia-closed, garuda-hardware-profile-nvidia-prime-closedgaruda-hardware-profile-nvidia-580xx

The -closed profiles map to the 580xx profile, not to the current NVIDIA profile. garuda-update also removes garuda-hardware-profile-nvidia-prime-closed on its own and marks garuda-hardware-profile-nvidia-closed as explicitly installed first. The changelog entry reads Remove garuda-hardware-profile-nvidia-prime-closed automatically to allow for smooth update.

No profile replaces the old 470xx NVIDIA packages. The MHWD packages themselves are replaced by garuda-hardware-tool. Its page lists them.