fix(installer): CPU backend wrongly overridden to nvidia when capability profile loaded#596
Merged
Lightheartdevs merged 1 commit intoLight-Heart-Labs:mainfrom Mar 24, 2026
Conversation
…ity profile loaded When CAP_LLM_BACKEND=cpu, the case statement fell through to default and set GPU_BACKEND=nvidia. This caused misleading preflight warning 'NVIDIA backend selected but no NVIDIA GPU VRAM was detected' on CPU-only Linux machines. Add explicit cpu and apple cases so the correct backend is preserved.
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
2 participants
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.
On CPU-only Linux machines, when the capability profile loads with CAP_LLM_BACKEND=cpu,
the case statement in 02-detection.sh didn't handle cpu or apple — they fell through
to the default and set GPU_BACKEND=nvidia.
This caused:
Fix: Add explicit cpu and apple cases so the correct backend is preserved.