Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Omarchy Steam installation and vulkan-driver provides dependencies leads to incorrect graphics configuration for iMac 2015 [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Reported by cometaj2 · filed Aug 30, 2025Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
mesa radv and amdvlk are incompatible drivers for [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] and lead to vulkan failure.
This is observed by installing vulkan-tools and running vulkaninfo which yields vulkan instance errors. The is also observed in the form of steam games making use of vulkan failing to start altogether.
I'm not sure what the fix would look like in context since the /bin/omarchy-install-steam blanket installs all the vulkan-driver (yay -Ss vulkan-driver) provides that steam claims to depend on. Maybe a post installation step if/as needed to properly configure graphic cards, or a more tailored installation depending on what the hardware on the system is? Or perhaps this belongs closer to the baseline Omarchy OS installation proper (I think that this is probably the right answer to make best use of the hardware on the Hyprland desktop)?
The issue is also described here (https://bbs.archlinux.org/viewtopic.php?id=299630) and the amdvlk removal and kernel module parameter setting fix works on my iMac 2015 with the above mentioned Graphics card.
Here's a bit of logic post installation to cleanup after omarchy-install-steam and the provides assumption.
https://github.com/cometaj2/config/blob/master/omarchy/mac/install.sh#L106
GRAPHICS=$(lspci -d ::03xx)
case "$GRAPHICS" in
'[AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]')
echo "Found: $GRAPHICS"
echo "Cleaning up after steam..."
yes | yay -Rns lib32-amdvlk 2>/dev/null
yes | yay -Rns amdvlk 2>/dev/null
yes | yay -S --needed lib32-vulkan-radeon
yes | yay -S --needed vulkan-radeon
yes | yay -S --needed mesa-utils
yes | yay -S --needed vulkan-tools
echo "hint: vulkaninfo"
echo "hint: vkcube"
echo "hint: glxgears"
sudo cp ./etc/modprobe.d/amdgpu.conf /etc/modprobe.d/amdgpu.conf
sudo cp ./etc/modprobe.d/radeon.conf /etc/modprobe.d/radeon.conf
sudo mkinitcpio -P
echo "hint: reboot!"
;;
*)
echo "Ignoring: $GRAPHICS"
;;
esac
amdgpu.conf:
options amdgpu si_support=1
options amdgpu cik_support=0
radeon.conf:
options amdgpu si_support=0
options amdgpu cik_support=0
After removing the amdvlk drivers, updating the kernel, and rebooting, the vulkaninfo command yields success and steam games that make use of vulkan function properly.
View raw text
mesa radv and amdvlk are incompatible drivers for [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] and lead to vulkan failure.
This is observed by installing vulkan-tools and running vulkaninfo which yields vulkan instance errors. The is also observed in the form of steam games making use of vulkan failing to start altogether.
I'm not sure what the fix would look like in context since the /bin/omarchy-install-steam blanket installs all the vulkan-driver (yay -Ss vulkan-driver) provides that steam claims to depend on. Maybe a post installation step if/as needed to properly configure graphic cards, or a more tailored installation depending on what the hardware on the system is? Or perhaps this belongs closer to the baseline Omarchy OS installation proper (I think that this is probably the right answer to make best use of the hardware on the Hyprland desktop)?
The issue is also described here (https://bbs.archlinux.org/viewtopic.php?id=299630) and the amdvlk removal and kernel module parameter setting fix works on my iMac 2015 with the above mentioned Graphics card.
Here's a bit of logic post installation to cleanup after omarchy-install-steam and the provides assumption.
https://github.com/cometaj2/config/blob/master/omarchy/mac/install.sh#L106
GRAPHICS=$(lspci -d ::03xx)
case "$GRAPHICS" in
*'[AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]'*)
echo "Found: $GRAPHICS"
echo "Cleaning up after steam..."
yes | yay -Rns lib32-amdvlk 2>/dev/null
yes | yay -Rns amdvlk 2>/dev/null
yes | yay -S --needed lib32-vulkan-radeon
yes | yay -S --needed vulkan-radeon
yes | yay -S --needed mesa-utils
yes | yay -S --needed vulkan-tools
echo "hint: vulkaninfo"
echo "hint: vkcube"
echo "hint: glxgears"
sudo cp ./etc/modprobe.d/amdgpu.conf /etc/modprobe.d/amdgpu.conf
sudo cp ./etc/modprobe.d/radeon.conf /etc/modprobe.d/radeon.conf
sudo mkinitcpio -P
echo "hint: reboot!"
;;
*)
echo "Ignoring: $GRAPHICS"
;;
esac
amdgpu.conf:
options amdgpu si_support=1
options amdgpu cik_support=0
radeon.conf:
options amdgpu si_support=0
options amdgpu cik_support=0
After removing the amdvlk drivers, updating the kernel, and rebooting, the vulkaninfo command yields success and steam games that make use of vulkan function properly.Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.