ValveSoftware / SteamVR-for-Linux

Issue tracker for the Linux port of SteamVR
934 stars 45 forks source link

Error code 306 #133

Closed Zamundaaa closed 6 years ago

Zamundaaa commented 6 years ago

Your system information

Please describe your issue in as much detail as possible:

It seems like #122 is now fixed, but the fix comes with an error that's very much worse: Connect Failed A key component of SteamVR isn't working properly. Error code 306 I think the fix is responsible for the error because of this in the log of the VRCompositor: Fri Sep 21 2018 13:19:36.271449 - Found bad mirror window settings: Fri Sep 21 2018 13:19:36.271462 - Creating CHmdWindowSDL! and the display mirror button is greyed out.

Steps for reproducing this issue:

  1. Start SteamVR beta
  2. be unable to play because of the error stopping the compositor from starting
Zamundaaa commented 6 years ago

I tested the latest Beta in Manjaro and it's working there. Must be something about Ubuntu or my system

Zamundaaa commented 6 years ago

It's now not putting the compositor on the Vive but just showing it as a borderless window but that could just be my fault as I tampered with the steam folder. But no crashes anymore in Ubuntu!

anon2828226 commented 6 years ago

How do you get no more crashes in Ubuntu? I still have the same issue.

Zamundaaa commented 6 years ago

I just downloaded the latest SteamVR beta and it worked, I don't know any fix other than that

Zamundaaa commented 6 years ago

I see that you wrote your vulkan install may have not worked. Why do you think so?

anon2828226 commented 6 years ago

My graphics card is the R9 390. Supposedly, Kernal 4.15 does not address it according to how the libvulcan needs it. The R9 300 series in general is not well supported on linux. I may try moving to kernal 14.18 or something see if that works. I don't really know if my card is the issue but this is what I am taking into consideration at the moment otherwise I am totally lost.

Zamundaaa commented 6 years ago

Is your system using radeon or amdgpu? I'd try to blacklist the one you're not using currently and look if it changes something. And I'd also try the latest (stable) kernel using ukuu, perhaps it could help

anon2828226 commented 6 years ago

When I install amdgpu (for R9 390 on ubuntu 18.04 from the AMD website) the system crashes on startup after a restart or shutdown and must be removed to allow ubuntu to boot. It also causes programs like steam to break/crash. This is probably also why Vulkan doesn't work. I have not tried black listing, but I don't see how that would help given that amdgpu doesn't even install correctly. People say on ubuntu 18.10 (having kernal 4.18) amdgpu and vulkan work like a charm. I might try upgrading to kernal 4.16 or hopefully 4.18 inside 18.04 possibly. Thank you for all your advise. I hate booting into windows just to do VR.

kisak-valve commented 6 years ago

Hello @jackleson, mesa/radv needs amdgpu to work. If you're feeling adventurous, you could give https://launchpad.net/~kisak/+archive/ubuntu/steamvr a try.

Zamundaaa commented 6 years ago

@jackleson You shouldn't install the proprietary amdgpu-pro driver from the website. amdgpu is already included in the kernel, so installed by default, but it may not be used. To ensure your system's using amdgpu you have to blacklist radeon (if that gives you a black screen or something on login you'll have to use the terminal to change it back again. Or use a live install to do it And installing a newer kernel is really fast&easy with ukuu, so just try it

anon2828226 commented 6 years ago

I didn't do "amdgpu-pro". I used the "amdgpu" install in terminal and just to see if I could get any helpful error messages. (I don't get any error messages it just doesn't work) I'll try the blacklist now

anon2828226 commented 6 years ago

moved to Kernal 4.18.11 everything fine. I did the blacklist on radeon now my monitors are unrecognized and are only operating in mirror mode with weird graphical glitches during startup. ran lsmod to confirm radeon didn't show up only amdgpu. nothing changed Steamvr and Vulkan do not work. Going back now. Worth a try. Think I am just screwed here.

anon2828226 commented 6 years ago

actually when I ran "sudo update-initramfs -u" after editing blacklist.conf I get:

update-initramfs: Generating /boot/initrd.img-4.18.11-041811-generic W: Possible missing firmware /lib/firmware/amdgpu/vegam_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vegam_smc.bin for module amdgpu

I don't have a vega or vega 10 card mine is hawaii pro or whatever. proly doesn't matter.

Bonus, during the install of vulkan, dxvk, or anything like that I always get:

The following packages have unmet dependencies: libwayland-egl1-mesa : Conflicts: libwayland-egl1 libwayland-egl1-mesa:i386 : Conflicts: libwayland-egl1 E: Broken packages

Zamundaaa commented 6 years ago

You shouldn't have to install amdgpu nor do I remember a download for it on the AMD website... Whatever Those possible missing firmware things pop up for me most times, too. Doesn't really matter. Are you running Ubuntu on Wayland? If so, you could try it on X. And of course you should try to reinstall libwayland-egl1 if you haven't already