The terminal cannot find the runner
Run pwd and ls version/v8/scripts/cks-v8-run. If the file is missing, return to the cloned repository and check out the version containing the v8 runner. If the error names a missing Python package or compiler, revisit setup and look for the first failed installation step.
The weights never arrive
Compare the complete model identifier, including its filename, with the first-run command. A repository name alone does not select this GGUF file. Check connectivity and free space with df -h . "$HOME". Downloading the weights and compiling the model are separate stages.
There are compiler messages but no answer yet
On the first run, expect output from the C compiler. If the process is still running, let it finish. If it exits, run echo $? immediately in the same shell. A nonzero result means the command failed. Copy the first error and the final lines together so someone can see which stage stopped.
What to include when asking for help
Record the exact command, model filename, Linux version, CPU model and checkout revision from git rev-parse --short HEAD. Include the final output with private prompts and paths removed. If a run completes but gives a surprising answer, include a short public prompt that shows the same behavior.