-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation Error #396
Comments
Hi @TimDouglas2! I have opened an issue with |
Hello @TimDouglas2! I just merged #424 which uses a new version of our CUDA backend driver which should support version 11.5. Can you please run
And then try to run the model again? |
@TimDouglas2 tagging to let you know I am closing this. |
These commands seem to have fixed my "undefined reference to 'hgemm_' build error |
happened when i entered:
cargo run --release --features cuda -- -i --token-source none --isq Q4K plain -m microsoft/Phi-3-mini-4k-instruct -a phi3
error: failed to run custom build command for
cudarc v0.11.4
Caused by:
process didn't exit successfully:
/root/mistral.rs/target/release/build/cudarc-7276cb883fd7b801/build-script-build
(exit status: 101)--- stdout
cargo:rerun-if-changed=build.rs
cargo:rerun-if-env-changed=CUDA_ROOT
cargo:rerun-if-env-changed=CUDA_PATH
cargo:rerun-if-env-changed=CUDA_TOOLKIT_ROOT_DIR
--- stderr
thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cudarc-0.11.4/build.rs:73:14:
Unsupported cuda toolkit version:
11.5
. Please raise a github issue.note: run with
RUST_BACKTRACE=1
environment variable to display a backtracewarning: build failed, waiting for other jobs to finish...
root@Glarbsttentenford:~/mistral.rs#
The text was updated successfully, but these errors were encountered: