Zed refuses to use GPU (Nvidia) WSL 2 #33802
Replies: 21 comments
-
|
I have also started having this same exact issue on my arch Linux install. Probably NVIDIA causing more issues. |
Beta Was this translation helpful? Give feedback.
-
|
does regular zed even work in wsl 2? |
Beta Was this translation helpful? Give feedback.
-
No, which is what I said in my issue as well. I tried both regular and preview and neither worked. |
Beta Was this translation helpful? Give feedback.
-
|
In WSL, I was able to get past the error popup with |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem , zed dont use nvidia gpu in wsl2 , even though I unset wayland ; |
Beta Was this translation helpful? Give feedback.
-
|
I think I've been down the rabbit hole... TLDR; it's not a direct issue with Zed but with Blade the Vulkan library used by Zed which require a Vulkan extension called VK_EXT_inline_uniform_block like OP mentionned in the former post. Zed is not using your nvidia GPU under WSL2 because the Mesa/Dozen Vulkan implementation which is a passthrough to Direct3D12 lack of VK_EXT_inline_uniform_block extension. This command show the issue: And now it makes more sense. When looking at Blade, the Vulkan library used by Zed, it's written:
I'm now looking at Dozen which was merged two years ago in Mesa if and when the missing VK_EXT_inline_uniform_block will be implemented. I'll let you know if I find something new. 😅 |
Beta Was this translation helpful? Give feedback.
-
Thank you seriously for all this. |
Beta Was this translation helpful? Give feedback.
-
|
If it helps, I'm also getting the emulation in zed on WSL2 with a working Radeon 7900XT. zed does work but it doesn't matter which GPU I try to select, it always uses emulation: command:
result:
|
Beta Was this translation helpful? Give feedback.
-
|
microsoft/wslg#40 sudo add-apt-repository ppa:kisak/kisak-mesa That brind d3d deveice to WSL 2 as mesa. |
Beta Was this translation helpful? Give feedback.
-
|
@brys0 You seem to have already tried running zed with wayland display. However, could you please try manually switching to nvidia, before running with wayland display? And then try running zed with |
Beta Was this translation helpful? Give feedback.
-
|
Hi, unfortunately switching to nvidia with prime-select doesn't work currently on wsl 2 it seems. brys0@brys:/mnt/c/Users/bryso$ sudo prime-select nvidia
Error: no integrated GPU detected. |
Beta Was this translation helpful? Give feedback.
-
Hi @apestel, I see similar issue with my integrated GPU: |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. Zed is only using λ ~/ MESA_VK_DEVICE_SELECT=list zed --foreground
MESA-INTEL: warning: cannot initialize blitter engine
selectable devices:
GPU 0: 8086:7d55 "Intel(R) Arc(tm) Graphics (MTL)" integrated GPU 0000:00:02.0
GPU 1: 10005:0 "llvmpipe (LLVM 15.0.7, 256 bits)" CPU 0000:00:00.0
Fwiw: the last time my integrated GPU was used is The only think I can think of changing was my build from Ghostty, which required Zig, gtk4, and a few other things. EDIT: Zed version info: |
Beta Was this translation helpful? Give feedback.
-
|
Just to make things clear: it's not your device, nor your system or your libraries. Under WSL2, we depend on a Vulkan driver which translates GPU API calls to Direct3D (DirectX 12). You can try to implement this feature in Dozen (Mesa Vulkan to Direct3D Driver). It's out of my knowledge and current capabilities (Person willing to achieve this challenge need to have a good understanding of both Vulkan and Direct3D). In the meantime, you can build Zed from source. It works well natively under Windows. I hope it makes things clearer. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thanks. Yeah, I'm using Zed also via Windows (scoop install versions/zed-nightly), but was exactly looking for the "remote" feature and that's why I gave a try on WSL. |
Beta Was this translation helpful? Give feedback.
-
|
@apestel - thanks for the explanation but can you help us understand why that inline_uniform_block call is strictly required in zed? Why do apps like google-chrome and vscode run fine in wsl2? it's not like their gpu performance is bad or anything either. |
Beta Was this translation helpful? Give feedback.
-
|
The Zed developers have selected the Blade GPU library to handle the bulk of the rendering workload. This library relies on certain Vulkan features for optimal performance, such as VK_EXT_inline_uniform_block. In contrast, other applications use different GPU rendering implementations and may not require the same Vulkan feature set. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like a... strong choice if this means WSL can't possibly work then, eh? |
Beta Was this translation helpful? Give feedback.
-
They built blade specifically for rendering in zed. I don't think it'd be a very worthwhile change to create a different renderer |
Beta Was this translation helpful? Give feedback.
-
|
can we have some fallback plan if VK_EXT_inline_uniform_block is only for "optimal performance"? fallback to a normal gpu solution could still be better than fallback to cpu simulation. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Check for existing issues
Describe the bug / provide steps to reproduce it
wsl -v
Tried the regular ver. of zed as well
zed --version
Attempting to run zed results in it using the llvmpipe software renderer and not my dedicated gpu.
To attempt and resolve this I have tried the following
vkcube
This works, gpu is dedicated correctly and used in the application.
nvidia-smi
vulkaninfo (truncated)
MESA_VK_DEVICE_SELECT=list zed --foreground
Things I've tried:
Running zed with
DRI_PRIME=1Running zed with
MESA_VK_DEVICE_SELECT=10de:1e81(my gpu id)Running zed with
MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1(Running zed with this causes the application not to display at all, the logs are similar as well)Running zed with
VK_ICD_FILENAMES=nvidia_icd.jsonRunning zed with
WAYLAND_DISPLAY=''Additional steps I've tried:
Restarting computer
Restarting WSL
Reinstalling Ubuntu WSL from scratch
Installing CUDA drivers on Windows and Linux
Reinstalling mesa on Linux
Logs:
Environment
Processor Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 32.0 GB
Device ID 0F91E45C-0632-495F-9E08-DC08052333DE
Product ID 00330-80000-00000-AA933
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
GPU Settings
neofetch
If applicable, add mockups / screenshots to help explain present your vision of the feature
If applicable, attach your Zed.log file to this issue.
Zed.log
2024-07-26T13:13:18.418476216-05:00 [INFO] ========== starting zed ========== 2024-07-26T13:13:18.427655516-05:00 [INFO] Compositor detection: _NET_WM_CM_S?=false, _NET_WM_CM_OWNER=false, _NET_SUPPORTING_WM_CHECK=true 2024-07-26T13:13:18.427801716-05:00 [INFO] x11: compositor present: true, gtk_frame_extents_supported: false 2024-07-26T13:13:18.438767016-05:00 [INFO] Opening main db 2024-07-26T13:13:18.440276416-05:00 [INFO] Using git binary path: None 2024-07-26T13:13:18.471715916-05:00 [INFO] extensions updated. loading 1, reloading 0, unloading 0 2024-07-26T13:13:18.472276016-05:00 [INFO] set environment variables from shell:/bin/bash, path:/home/brys0/.local/bin:/home/brys0/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/ImageMagick-7.1.1-Q16-HDRI:/mnt/c/Program Files/Common Files/Oracle/Java/javapath:/mnt/c/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.2/bin:/mnt/c/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.2/libnvvp:/mnt/c/Program Files/Java/jdk-17/bin:/mnt/c/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/bin:/mnt/c/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/libnvvp:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files/dotnet/:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Program Files/GitHub CLI/:/mnt/c/Program Files (x86)/FAHClient:/mnt/c/Strawberry/c/bin:/mnt/c/Strawberry/perl/site/bin:/mnt/c/Strawberry/perl/bin:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Users/bryso/.gpg/bin:/mnt/c/Users/bryso/AppData/Local/pnpm:/mnt/d/v/.bin:/mnt/l/v/.bin:/mnt/c/Users/bryso/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/JetBrains/IntelliJ IDEA/bin:/mnt/c/Users/bryso/go/bin:/mnt/c/adb:/mnt/c/Program Files/LLVM/bin:/mnt/c/Program Files/Docker/Docker/resources/bin:/mnt/c/Program Files/FileDrop:/mnt/c/Program Files/NVIDIA Corporation/Nsight Compute 2023.2.0/:/mnt/c/Users/bryso/AppData/Roaming/nvm:/mnt/c/Program Files/nodejs:/mnt/c/Program Files/Go/bin:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/NVIDIA Corporation/NVIDIA App/NvDLISR:/mnt/c/Program Files/PowerShell/7/:/mnt/c/Program Files/Cloudflare/Cloudflare WARP/:/mnt/c/Program Files/Tailscale/:/mnt/c/Users/bryso/.cargo/bin:/mnt/c/Users/bryso/AppData/Local/Programs/Python/Python38/Scripts/:/mnt/c/Users/bryso/AppData/Local/Programs/Python/Python38/:/mnt/c/Users/bryso/AppData/Local/pnpm:/mnt/d/v:/mnt/l/v/L:/v:/mnt/c/Users/bryso/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/JetBrains/IntelliJ IDEA/bin:/mnt/c/Users/bryso/go/bin:/mnt/c/Users/bryso/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/Users/bryso/AppData/Roaming/npm:/mnt/c/mingw64/bin:/mnt/c/Users/bryso/AppData/Local/JetBrains/Toolbox/scripts:/mnt/c/Users/bryso/AppData/Roaming/nvm:/mnt/c/Program Files/nodejs:/mnt/c/Users/bryso/go/bin:/mnt/c/Users/bryso/bin:/mnt/c/Program Files/qemu:/mnt/c/Users/bryso/AppData/Local/Android/Sdk/cmdline-tools/latest/bin:/mnt/c/Users/bryso/.dotnet/tools:/mnt/l/UnLockCatch/tools/vcruntime:/mnt/c/Users/bryso/.bun/bin:/mnt/c/Users/bryso/AppData/Local/GitHubDesktop/bin:/mnt/c/Users/bryso/AppData/Local/Packages/PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0/LocalCache/local-packages/Python310/Scripts:/mnt/c/Program Files (x86)/Nmap:/mnt/c/cygwin64/bin:/mnt/c/Users/bryso/AppData/Local/atom-ng/bin:/snap/bin 2024-07-26T13:13:18.472719816-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.472907316-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.472934116-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.571051016-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.572132616-05:00 [INFO] activate is not implemented on Linux, ignoring the call 2024-07-26T13:13:18.572268616-05:00 [INFO] Opening main db 2024-07-26T13:13:18.573790116-05:00 [INFO] Using Visual { id: 73, colormap: 0, depth: 32 } 2024-07-26T13:13:18.573831716-05:00 [INFO] Creating colormap 6291459 2024-07-26T13:13:18.634600316-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.634656516-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.634679516-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.634700416-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.634722116-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.712598616-05:00 [INFO] Enabling color space support 2024-07-26T13:13:18.905278916-05:00 [WARN] Rejected for device extension "VK_EXT_inline_uniform_block" not supported 2024-07-26T13:13:18.906456416-05:00 [INFO] Adapter "llvmpipe (LLVM 15.0.7, 256 bits)" 2024-07-26T13:13:18.906482516-05:00 [INFO] Ray tracing is supported 2024-07-26T13:13:18.915122116-05:00 [INFO] Using surface present mode MAILBOX 2024-07-26T13:13:18.916431816-05:00 [WARN] Unable to forbid exclusive full screen 2024-07-26T13:13:18.918517316-05:00 [INFO] Creating a descriptor pool for at most 16 sets 2024-07-26T13:13:18.918544316-05:00 [INFO] Creating a descriptor pool for at most 16 sets 2024-07-26T13:13:18.918564316-05:00 [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: Ignored } 2024-07-26T13:13:18.937097416-05:00 [INFO] Refreshing at 6948 micros 2024-07-26T13:13:18.937243016-05:00 [INFO] x11: no compositor present, falling back to server-side window decorations 2024-07-26T13:13:18.937959116-05:00 [INFO] Using GPU: GPUSpecs { is_software_emulated: true, device_name: "llvmpipe (LLVM 15.0.7, 256 bits)", driver_name: "llvmpipe", driver_info: "Mesa 24.1.4 - kisak-mesa PPA (LLVM 15.0.7)" } 2024-07-26T13:13:18.979880716-05:00 [ERROR] DBus error zbus error I/O error: No such file or directory (os error 2) 2024-07-26T13:13:18.980698116-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.980846316-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.981251116-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:18.981620916-05:00 [INFO] Node runtime install_if_needed 2024-07-26T13:13:18.982596016-05:00 [INFO] Opening main db 2024-07-26T13:13:19.008659616-05:00 [INFO] Initializing default prettier with plugins {} 2024-07-26T13:13:19.010129216-05:00 [ERROR] no worktrees when constructing ProjectLspAdapterDelegate 2024-07-26T13:13:19.032219516-05:00 [WARN] request completed with error: failed to connect to the server 2024-07-26T13:13:19.103651916-05:00 [INFO] starting language server. binary path: "/home/brys0/.local/share/zed/node/node-v22.5.1-linux-x64/bin/node", working directory: "/", args: ["/home/brys0/.local/share/zed/copilot/copilot-v0.5.0/dist/agent.js", "--stdio"] 2024-07-26T13:13:19.523031715-05:00 [INFO] Language server with id 0 sent unhandled notification LogMessage: { "level": 0, "message": "[DEBUG] [agent] [2024-07-26T18:13:19.519Z] Agent service starting", "metadataStr": "[DEBUG] [agent] [2024-07-26T18:13:19.519Z]", "extra": [ "Agent service starting" ] } 2024-07-26T13:13:19.524996815-05:00 [INFO] Language server with id 0 sent unhandled notification client/registerCapability: { "registrations": [ { "id": "5e9e6f7b-45ed-44b5-82ad-3ca36ad10476", "method": "workspace/didChangeWorkspaceFolders", "registerOptions": {} } ] } 2024-07-26T13:13:19.579037315-05:00 [INFO] Language server with id 0 sent unhandled notification LogMessage: { "level": 0, "message": "[DEBUG] [agent] [2024-07-26T18:13:19.542Z] Telemetry initialized", "metadataStr": "[DEBUG] [agent] [2024-07-26T18:13:19.542Z]", "extra": [ "Telemetry initialized" ] } 2024-07-26T13:13:20.859572514-05:00 [ERROR] Failed to open with dbus: ZBus Error: I/O error: No such file or directory (os error 2)Here are the logs just running with WAYLAND_DISPLAY='''
Zed.log
Zed_MESA_VK_DEVICE_SELECT&DRI_PRIME.log, Unsupported GPU, but window is displayed
There are no logs at all when MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 is set. No logs are created in .local/share/zed/logs/Zed.log
Logs in console are the following:
With
VK_ICD_FILENAMES=nvidia_icd.jsonas well logs return an error fromblade_graphics::hal::initBeta Was this translation helpful? Give feedback.
All reactions