Add migration to backfill Mesa Vulkan drivers for pre-vulkan.sh installs#6199
Open
sridhar-3009 wants to merge 1 commit into
Open
Add migration to backfill Mesa Vulkan drivers for pre-vulkan.sh installs#6199sridhar-3009 wants to merge 1 commit into
sridhar-3009 wants to merge 1 commit into
Conversation
install/config/hardware/vulkan.sh was added on 2026-02-20 but ships no corresponding migration, so systems installed before that date never received their Mesa Vulkan ICD. On Intel+NVIDIA Optimus laptops this left only the NVIDIA Vulkan device present, causing cross-presentation stalls in mpv (Vulkan path) and similar GPU-selection bugs. Add a migration that replays the same GPU detection and `omarchy-pkg-add` calls as vulkan.sh. `omarchy-pkg-add` is idempotent, so systems that already received the driver (installed after 2026-02-20) are unaffected. Fixes basecamp#6089.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a migration to backfill Mesa Vulkan ICD packages on systems installed before install/config/hardware/vulkan.sh existed, ensuring Vulkan devices are correctly available for Intel/AMD/Asahi GPUs on older installs.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
Changes:
- Add a new migration that detects GPU vendors via
lspciand installs the corresponding Mesa Vulkan package(s) usingomarchy-pkg-add.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| PACKAGES=() | ||
|
|
||
| for vendor in "${!VULKAN_DRIVERS[@]}"; do | ||
| if lspci | grep -iE "(VGA|Display).*$vendor" > /dev/null; then |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
install/config/hardware/vulkan.shwas added on 2026-02-20 but ships nocorresponding migration. Systems installed before that date never received
their Mesa Vulkan ICD. On Intel+NVIDIA Optimus laptops the effect is
concrete: only the NVIDIA Vulkan device is present, causing cross-presentation
stalls in mpv (Vulkan path) and similar GPU-selection bugs.
Reported in #6089.
Fix
Add a migration that replays the same GPU vendor detection and
omarchy-pkg-addcalls asvulkan.sh.omarchy-pkg-addis idempotent,so systems that already received the driver (installed after 2026-02-20, or
on NVIDIA-only machines) are unaffected.
No changes to install scripts or existing behaviour.