-
Notifications
You must be signed in to change notification settings - Fork 35
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
crashes on startup for PRIME enabled hardware thats configured to use the onboard nvidia not the intel #88
Comments
Based on the Discord discussion, even |
Setup 1: Setup 2: In this 'Setup 2'... Zed and the blade 'bunnymark' example both work great, no issue here... but thats not how most people with a PRIME setup and nvidia hardware are gonna be using it Summary: |
$ uname -a $ cat /etc/lsb-release $ nvidia-smi
|
note to say that updating the nvidia driver to 550 didn't magically make it work, but did change a few things ( like the number of reported devices in 'vulkaninfo' output is now 4 for me ( one intel, two nvidia, and the mesa driver ) , and vkcube now seems to run no matter which of the 4 devices I choose ... |
vkcube without explicity choosing a device , chooses the nvidia hardware.... let me see... The ordering of the GPU's output by these two vulkan commands is different ... vulkaninfo reports GPU0 as Intel, and vkcuke when specifying a GPU reports that 'GPU0' is the nvidia.. so their "get a list of vulcan deivces" code is using a different ordering/numbering/indexing ...?
is that important? |
Yes, we want to do what
Please post the exact error |
command: blade]$ RUST_LOG=blade_graphics=debug RUST_BACKTRACE=1 cargo run --example bunnymark > buzz.550.bunnymark.validation2.error.txt 2>&1 output:
|
pretty sure it's https://gitlab.freedesktop.org/mesa/mesa/-/issues/4688 |
What is the exact situation here? Is it:
I had a similar issue with WGPU, gfx-rs/wgpu#4110, solved by checking the mesa version and if less than 21.2 it is disabled. (I wrote and maintain https://gitlab.com/asus-linux/supergfxctl/, so I have a fairly decent understanding of the hardware level but not so much actual use) |
@davidbuzz I need to knwo more info about this. I noticed:
This to me implies that you are using xorg-dgpu mode. Something that is pretty much a hack and not necessary these days. As a result of this I think some incorrect assumptions have been made. Can you please verify for me that under a wayland session blade works perfectly fine without the blocking commit? Given that the Linux world is likely going to be defaulting to Wayland by the end of the year if not by this quarter the resulting knee-capping of everyone because of this one unique and not very well supported use-case isn't justified. |
@flukejones ... its a nice Dell laptop with both Intel graphics and Nvidia Graphics. Its an integration that at the hardware is called 'Nvidia Optimus' and the software/switcher/etc is called 'Nvidia Prime'. [Google both those for more] The nvidia card being more powerful, amd this laptop always being on power, and it doing some pretty busy stuff, i keep the nvidia active and in-use all the time by running the 2nd of those commands , and just leavong it like that. |
Right. So xorg configured to use nvidia as primary is the entire cause of the issue you had. Any work around needs to check just that one thing, not chop everything off at the knees for everybody else. I suggest you give KDE 6 Wayland a try if you can, it works very very well on hybrid setups |
@flukejones thanks for your input!
So it would not make sense to try to port your wgpu PR here. Or at least, it wouldn't help this issue in particular.
Any idea how to detect this specifically (i.e. without chopping everything off at the knees)? |
Lets keep new discussion on the linked issue :) |
... seems to specifically choose the incorrect (intel) video card even tho 'prime-select query' output says 'nvidia'
temporary workaround, switch-around your prime configuration to use the worse 'intel" video card, reboot, and then it won't crash.
run: sudo prime-select intel
reboot
Edit: vulkaninfo
The text was updated successfully, but these errors were encountered: