-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[linux] Vulkan ERROR_INITIALIZATION_FAILED #8168
Comments
same issue on OS: Arch Linux x86_64 |
I encountered a similar error while building on WSL: OS: Debian GNU/Linux 12 (bookworm) on Windows 10 x86_64 Log:
The crashing was fixed when I installed
|
I encountered a similar error while building on WSL: OS: Ubuntu 22.04.4 LTS Output after 1st compiling
|
This hasn't worked for me, I have troubleshot X11 in a thousand different ways, anyone know a workaround or specific cause? PopOS 22.04 |
Same here with
OS: Ubuntu 20.04.6 LTS x86_64 Edit: I only have the EOF errors now
|
The minimal json file is {}
|
@Godskull, @AA1999 Zed crashed immediately with the same errors. I run archlinux with 6.6.18-1 kernel, AMD Ryzen 7 PRO 6850U CPU and AMD ATI Radeon 680M GPU. However, after installing Try to install I think |
i installed vulkan-devel i have nvidia card so i ran
and the editor was open and when i used mangohud to check the fps then the fps where fluctuating from 3 fps to 60 fps with a average frametime of 1400ms , going as high as 2600ms , in short the editor was unusable |
same issue.
arning: zed@0.126.0: Info: using '6fcd57ac53cd73adb717532c1f76b132a998e8c8' hash for ZED_COMMIT_SHA env var |
I already have vulkan-devel installed, but isn't vulkan-amdgpu-pro for AMD GPUs? Mine is NVIDIA I did install vulkan-devel again anyway (just to be sure) but the error is the same:
Output of
|
@AA1999 according to archwiki, you also need a 1- Intel: Install the drivers and see if it changes anything, in my case Zed does not crash after installing the drivers. But it's still generating the errors you are getting. |
|
For everybody having
|
with the added changes, i get this on arch wayland
thread 'main' panicked at crates/gpui/src/platform/linux/x11/client.rs:52:10: |
tried it on x11, it at least opened with errors, tried fixing one of them and it did not start again even after reverting the change (adding some json file) so switched back to wayland and it does work to an extent, it opens but its unusable, no extensions, sign in doesnt work, and saving files or closing windows doesnt work [skullcmd@linuxtechi zed]$ sudo cargo run --release |
I can run said command however I still get the same error
https://pastebin.com/SHh5BB9V |
Did you test |
Yeah it was ran at the same mode. Lemme try vkcube-wayland too
|
This sounds to me like |
@aohanhongzhi could you also do the following please:
@flukejones what do you make of this case? |
Ancient versions of Ubuntu (20.04 is ridiculous) are not ideal and will be missing all sorts of improvements and features for the drivers, graphics stacks, firmware etc etc. It's unlikely to have all the vulkan features/extensions required. Either specify a minimum Ubuntu version such as only the last release (24.04), or support only Fedora (and possibly Arch). Fedora at least keeps pace with development of the underlying critical parts (kernel, drivers, firmware). Ubuntu is not a nice distro to try and support when everything else is moving rapidly except that distro and I wish folks would stop recommending it. (which is based on years of supporting ASUS ROG laptops with software and kernel driver work). Sorry if this is more like a rant and not helpful - I get far too many people on my discord installing 2 year old distros on 6 month old hardware and wondering why things don't work. The same thing applies to development eventually. Windows and Mac at least offer a stable foundation, but we don't have that luxury on Linux thanks to fragmentation caused by distros moving at different speeds to upstream. As for the actual issue, the logs just above... I see that vkcube sleected the Nvidia device. While Zed will select Intel (whcih is what we want, don't need 15w+ extra from dgpu).
We would need to force vkcube to run on intel with the above, and check the present modes. That might hint at something. And grab Does blade support opengl use with Zed? That might be a good fallback for these older hardware/distro scenarios. I've not kept up with the levels of vulkan support through the Linux ecosystem. For the original post issue, I'm not sure. The rest of the issue seems to have a common theme:
These are supposed to support Vulkan 1.2 from what i can tell. So maybe outdated drivers? So I don't think I can help further sorry. |
so I need to install vkcube-wayland? |
@flukejones thank you for the info!
That's very unlikely. Blade checks for the features it enables, and it has good error reporting in the log.
The basics are in place - you can compile and run Zed on top of OpenGLES-3.1. But there is a few bugs (or just missing pieces) in the GLES backend of Blade that need to be resolved before Zed becomes usable on this path. I do see it as a good fallback for platforms not supporting Vulkan. @aohanhongzhi vkcube --gpu_number 0 |
Hi I encountered the same issue on openSUSE and solved it by installing proprietary drivers Should something be added to the instructions for Linux to install proprietary drivers if you use an NVIDIA gpu? |
I solved this by installing |
In all seriousness y'all will be better served by moving to newer distros. At least Ubuntu 24.04, if not Fedora 40. |
@aohanhongzhi ok, that's something. So Vulkan is just plain broken on adapter 0 for you. The only reason some stuff works is because it decides to choose the discreet GPU and avoids the adapter 0, which must be Intel. We currently have a small workaround in place to handle some of those broken platforms (and it is a platform bug), and we need to extend it slightly to support yours. |
If you have an NVIDIA GPU and installed arch with the |
Installing this fix my issue vulkan-radeon |
What would be the appropriate package for NVIDIA?
After uninstalling
|
Never mind, I am having the error again |
On EndeavourOS with KDE Plasma and Wayland. Installing |
Installing |
I've found a process with zed, killed him and launched again. It helped for me. Env: ArchLinux, Wayland, Sway |
I've been experiencing a similar issue in a mode old hardware (new one is working fine). Env: Artix Linux, zed 0.164.2, nvidia Someone in the thread said that vulkan 1.2 drivers are the minimum, which my GTX 760 supports. However, in the docs... It says that 1.3 is the minimum. When things changed? |
We basically require this list of extensions (which hasn't changed since the start): vk::EXT_INLINE_UNIFORM_BLOCK_NAME,
vk::KHR_TIMELINE_SEMAPHORE_NAME,
vk::KHR_DESCRIPTOR_UPDATE_TEMPLATE_NAME,
vk::KHR_DYNAMIC_RENDERING_NAME, |
I am using Manjaro and I installed Zed using official script. Version is 0.165.4. Changed |
@AA1999 Also, could you please share your log file? The link you have pasted does not work . To make sure you have vulkan driver installed, Also please try In case everything is configured properly, both the commands should open up a window with a rotating cube on the display. Can you also please try manually switching to your NVIDIA gpu? Then: |
Check for existing issues
Describe the bug / provide steps to reproduce it
After following the instructions for building zed on linux, I run
cargo run --release
and the resulting error:Steps to reproduce:
git submodule update --init --recursive
rustup target add wasm32-wasi
cargo run --release
Environment
OS: Arch Linux x86_64
Kernel: 6.7.5-arch1-1
DE: KDE Plasma 5.27.10
WM: KWin (Wayland)
CPU: Intel(R) Core(TM) i7-7700HQ (8) @ 3.80 GHz
GPU 1: NVIDIA GeForce GTX 1050 Ti Mobile
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.If you only need the most recent lines, you can run the
zed: open log
command palette action to see the last 1000.https://paste.ofcode.org/7WyGRWWXTSSnjWRvEtxCVb
The text was updated successfully, but these errors were encountered: