Open darrell-roberts opened 1 month ago
bbb651
commented
1 month ago It's due to ring not supporting arm windows pre-0.17, I narrowed down to a dependency on an old version of async-tungstenite, upgrading it (see #17380) should resolve this (but there're probably other blockers).
darrell-roberts
commented
1 month ago It's due to
ringnot supporting arm windows pre-0.17, I narrowed down to a dependency on an old version ofasync-tungstenite, upgrading it (see #17380) should resolve this (but there're probably other blockers).
Thanks. I updated that along with rustls to 0.23 (which required making some changes to crates/client/src/client.rs). I now get the runtime error reported here: https://github.com/zed-industries/zed/issues/17374
frankniujc
commented
2 weeks ago It turns out that the x64 windows zed and arm64 ubuntu (running in wsl) also won't launch.
frankniujc
commented
1 week ago For version 0.162.3, zed can be compiled directly without any issue with ring. However, I still can't launch zed on arm64 windows (Qualcomm X Elite). Here's the error message.
PS C:\Users\frank\Desktop\zed\target\debug> .\zed.exe
[2024-11-20T23:54:17-05:00 ERROR fs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-11-20T23:54:18-05:00 ERROR fs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-11-20T23:54:18-05:00 ERROR fs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-11-20T23:54:18-05:00 ERROR fs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-11-20T23:54:18-05:00 ERROR blade_graphics::hal::init] No composite alpha flag for transparency: OPAQUE
[2024-11-20T23:54:19-05:00 ERROR zed::reliability] {
"thread": "main",
"payload": "called `Result::unwrap()` on an `Err` value: ([0x0], ERROR_UNKNOWN)",
"location_data": {
"file": "C:\\Users\\frank\\.cargo\\git\\checkouts\\blade-b2bcd1de1cf7ab6a\\e142a3a\\blade-graphics\\src\\vulkan\\pipeline.rs",
"line": 546
},
"backtrace": [
"backtrace::backtrace::dbghelp64::trace",
"backtrace::backtrace::trace_unsynchronized<backtrace::capture::impl$4::create::closure_env$0>",
"backtrace::backtrace::trace<backtrace::capture::impl$4::create::closure_env$0>",
"backtrace::capture::Backtrace::create",
"backtrace::capture::Backtrace::new",
"zed::reliability::init_panic_hook::closure$0",
"alloc::boxed::impl$50::call",
"std::panicking::rust_panic_with_hook",
"std::panicking::begin_panic_handler::closure$0",
"std::sys::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure_env$0,never$>"
],
"app_version": "0.162.3",
"release_channel": "Zed",
"os_name": "Windows",
"os_version": "10.0.26100",
"architecture": "aarch64",
"panicked_on": 1732164859317,
"system_id": "7023e526-e0ae-428a-9251-4ca39ebae4d0",
"installation_id": "a3ad595a-3a9d-4df1-be3f-9bcd3eebe914",
"session_id": "eb4fa707-5621-4fde-8ec1-c1ed4a7ad41b"
}It seems that the issue is Blade currently does not support Qualcomm X Elite GPUs. A comment from June 2024 mentioned the lack of a Vulkan SDK for ARM64 Windows as a limitation. However, that’s no longer the case---there is now a Vulkan SDK available for ARM64 Windows. https://vulkan.lunarg.com/sdk/home#windows.
I’ve tried installing the Vulkan SDK and runtime, but this doesn’t resolve the issue. I’m still encountering the following error:
called `Result::unwrap()` on an `Err` value: ([0x0], ERROR_UNKNOWN)This leads me to believe that the issue lies with X Elite GPUs and Adreno GPUs not being added to the supported hardware list in Blade. Now that Vulkan has ARM64 support, could these GPUs be added to the compatibility list so we can enable Blade to work with Qualcomm chips?
I have an update with my previous comment, I can get linux zed running in WSL when running in X11 mode.
Check for existing issues
Describe the bug / provide steps to reproduce it
Cloned the repo and setup the required build toolchains for windows.
Cargo build fails on external build for ring. What is interesting is it is building ring 0.16 when the dep has been upgraded to 0.17 for windows ARM support https://github.com/zed-industries/zed/pull/11689.
Looking at
cargo treeit looks like all ring deps are 0.17 except for one which is for rustls v20.9.tree.txt
cargo buildoutput:Environment
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log