-
Notifications
You must be signed in to change notification settings - Fork 57
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
AMD Gpu traning not working #19
Comments
@rickytrevor Ah yes you're right. I haven't tried this on AMD. Try changing the brand on line 119 (graph/gpu/mod.rs) to |
I've tried changing it to Brand::Amd and it just panics to "Not supported", I've briefly looked at the Impl for Brand and the implementation for amd's missing in the get_bus_id function
|
Update, I've managed to implement the case for Amd
The problem is that right after starting it crashes because of this error, any clues? Error: GpuError(OclError(Kernel(ArgTypeMismatch { idx: 0, arg_name: "out", ty_name: "float*", ty: ArgType { base_type: Float, cardinality: One, is_ptr: true } }))) |
@rickytrevor I don't have a AMD card so can't debug 😄 Happy to get a PR for AMD support though 😉 |
Hello, I'm trying to run femtoGPT on my rx 6600 under Ubuntu Linux, I've installed the required Rocm OpenCL drivers but, when I run the program using
cargo run --release --features gpu
I get an index out of bounds exception
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', src/graph/gpu/mod.rs:119:22
note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceEdit
This is the log with RUST_BACKTRACE=1
0: rust_begin_unwind
at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/panicking.rs:67:14
2: core::panicking::panic_bounds_check
at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/panicking.rs:162:5
3: femto_gpt::graph::gpu::GpuGraph::new
4: femto_gpt::main
note: Some details are omitted, run with
RUST_BACKTRACE=full
for a verbose backtrace.The text was updated successfully, but these errors were encountered: