weird issue running stardust
trying to screw with stardust stuff on our newly fixed up old gaming laptop since it's decently powerful, and for some reason stardust just..outputs
and then dies when running it. building from source and running with
cargo run yields the process from that ending with a seg fault. everything else seems to work fine, just not stardust. system info is in attached hyfetch screenshot.
48 Replies
that's really weird
i've never seen that
stardust works better on our hp emmc laptop that cant even do alvr than this 2018 gaming laptop
@Nova have you seen this before?
i could get stardust working better by running it in a remote x session with turbovnc on our pc with a 2080 that refuses to output than this
..somehow
i just wanna try stuff out now that we have a stable machine that isnt our steam deck with bad ram
is there any way to get anything to give like..debug output?
i wonder if it's related to multigpu, but i feel like someone would have caught that by now
yeah idk
that's my only guess
the other screen is literally just plugged in for me to test having that running exclusively to see
it def isnt multigpu since i disabled keyboard screen and the hdmi port is wired up to the 1060
it still fails
so... which version of stardust is this?
tried latest release as well as building from source
both fail
this is definitely a stereokit issue
i have nothing else that even can segfault in stardust
:p
huh
that's what i was thinking too lol
everything else is rust
any chance you could pop it open in a debugger and see where it segfaults on a debug build?
you will have to walk me through this
the most we can do with technical stuff is writing cc lua and ts stuff to go with it as a backend
ok, so build the thing with cargo then do
gdb ./target/debug/stardust-xr-server
or lldb in place of gdb
then type runohh huh
i cant see anything fatally wrong here
it just..runs
and then dies
try
cargo run -- -fworks fine
it shows a window and everything?
yep
steamvr is broken
maybe it is multigpu
it would be jank but i could blacklist i915
did this in a previous install on this machine, its slightly funky but it works
well, it's possible (after all, stereokit does just pick
/dev/dri/renderD128)oh, then that's gotta be it
alright, lemme try
then that's my bad lol
idk how to do better on that part
i use gdm to open an egl context from the card
i'd assume the igpu is getting loaded by the kernel
i915 driver and that nvidia is loaded much later and so the igpu is card0 and renderD128
multigpu like this for a project like this is a MASSIVE edge caseyea, i get why people want it though
yeah
in our case, this machine is our only fully working system
as an example
damn did i actually call it xD
yeah
wasn't expecting to be right
eh, i was expecting multigpu to be the issue
at least its intel+nvidia and not amd+amd
alright, booting back up now
it was the only thing that looked unusual in your setup based on hyfetch
wish me luck
good luck!
i think i screwed myself over
maybe
either that or long boot
nope, long boot. plymouth showed
oh
huh
last i checked
nvidia-prime should work with stardust btw
if i remember correctlyright
im dumb
no clue tbh
i tried stardust on a multigpu system like once
oh wait this is prob why games run so..okay
fast but not as fast as a 1060 should do
to get this screenshot: https://stardustxr.org/img/carousel/multipleclients.png
wait im gonna try a bit of a stupid thing
installing
vulkan-intelfor the record, stardust uses opengl
since stereokit does
ah, right
using
prime-run just gets me flatscreenmaybe it just doesn't work with steamvr
https://discord.gg/wskGgzac
ask them about wivrn
that might work better