-
Notifications
You must be signed in to change notification settings - Fork 45
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
Installation path could not be located (111) #4
Comments
I also get the following in dmesg:
|
Same error reported on my machine at startup I am using the exact drivers specified in the readme
Like the readme says you may need to pin this higher than the |
Thanks for the response, perhaps it is a driver issue then. As I said in the OP I'm running Arch Linux which is already on a later version of the driver and there isn't an LTS package for 375.27.10 that I can see. I can try searching for the older release, installing it may be as simple as changing the PKGBUILD but as this is my work machine I'm wary of trying to hack together nvidia driver installs. Perhaps you could try upgrading to the latest (378.13-1/2) nvidia driver and seeing if the headset still displays content? I'm not aware of it being available in an easy to install (.deb) format yet however. |
My bad, missed that in your description, for some reason I just assume everyone is on *buntu. I haven't messed much with Nvidia drivers on Arch (only ran on a ThinkPad), but could you just run the |
I have the same error, but additionally the room setup crashes with the message The easiest way should be by using the linked PPA debian/ubuntu package and a PKGBUILD to create an AUR package (unfortunately AUR does not have a package for the developer driver). I'll see how far I'll come without X11 failing :D. If everything works I'll publish a Gist of the PKGBUILD. |
NVIDIA cards require version 375.27.10 of the NVIDIA Developer Beta Driver. Not 378.13. |
@kkriehl Thanks for your insight, and good luck on the PKGBUILD creation. I'll do my own testing once I get home today. @johnv-valve As @connerbrooks receives the same 111 error with the correct Nvidia driver perhaps we should keep this issue open? |
@connerbrooks issue is different as his SteamVR works fine. If you want to create a new issue for the spurious message (I think it might just be a first run thing) then do that. |
@johnv-valve I'll create a new issue if I still receive the error after installing the new driver, unless @connerbrooks wants to go ahead and do it if he's still getting the same issue. |
Subscribing to this thread for that PKGBUILD @kkriehl. It would be good if you posted it on the official archlinux aur as well. |
@hcorion @kkriehl I've created a thread on the SteamVR Linux forums with current PKGBUILD progress: https://steamcommunity.com/app/250820/discussions/5/133257959063392200/ |
When you have it working, please send a pull request for README.MD in this repo with instructions. |
@johnv-valve Will do once it goes live. |
@johnv-valve PR added. No longer receiving the Edit: Nevermind, still getting the error. Room setup does launch successfully however, which is a huge plus :) |
Your system information
Please describe your issue in as much detail as possible:
When starting SteamVR the compositor shows up correctly and displays full what the headset should be seeing (controllers can be seen as tracked through this window) however the headset display does not turn on.
Shortly after the SteamVR Compositor window appears, the error message "SteamVR failed to initialized (typo btw) for unknown reasons. (Error: Config path could not be located (111))" shows up. The indicator light on the side of the headset is green, but its display is off.
Room setup will crash immediately after launching.
I've tried running with the Steam runtime with nvidia (378.13-2) and nvidia-beta (378.13-1) drivers, but both give the same issue.
Log during error.
My setup consists of two 1440p monitors over DVI with the headset running over HDMI. I have a Nvidia GTX 970.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: