Skip to main content
rupy
Up and Coming
February 4, 2015

Linux

So I'm trying to get my DK2 to work on linux.

This is what the oculusd tells me:

OVR::DeviceManagerThread - running (ThreadId=0x7f9484f46700).
OVR::DeviceManager - initialized.
OVR::Linux::HIDDevice - Opened '/dev/hidraw3'
Manufacturer:'Oculus VR, Inc.' Product:'Rift DK2' Serial#:'MSCEM707JHC4KP008100'
[TrackingManager] Sensor added: PrintedSerial=2042AV0357VB UUID=MSCEM707JHC4KP008100


But the driver can't find the HMD:

No Oculus Rift devices found, creating dummy DK1 device..


Did any1 get it to work, and if so is there a tutorial somewhere?

    3 replies

    bullale
    Up and Coming
    February 4, 2015
    I got it to work, but only at the refresh rate of the primary monitor.

    I installed the latest nvidia driver and nvidia-settings.
    In NVidia X settings I set the two displays as part of the same X display (DISPLAY=:0).
    oculusd -d
    OculusWorldDemo
    F9 to full screen it on the rift.
    Press space and see it's running at 60 FPS and it's juddery.

    Note that I tried modifying Nvidia settings to set the DK2 as the device that drives the VSync. This seems to have no effect. I tried setting the DK2 as the main display. This seems to have no effect. I changed the refresh rate of my primary monitor to 144 Hz using xrandr, this led to the OculusWorldDemo running at 144 FPS. At least it wasn't juddery.

    I then ran BlazeRush. It detects the dk2 but doesn't expect it to be rotated. I could have gone back into nvidia settings and rotated the dk2 then gone back to blazerush but I didn't try. I expect it too would have ran at 60 FPS but I'm not sure.

    Note I also tried setting the DK2 as a separate X Display (requires logout,login). In this mode, nothing can detect the DK2, even if I first export DISPLAY=:1. In fact, the OculusWorldDemo segfaults if I first set DISPLAY=:1 and steam refuses to run.

    I think the best way should be with the DK2 as a separate X display, but how to do this is not very well documented.
    rupyAuthor
    Up and Coming
    February 4, 2015
    Yes, I noticed the vSync was locked to the main 60Hz monitor too.

    But my only problem is that the HMD is undetected, I only use the sensor part of the Oculus stack.

    Oh well, I guess OSX might work better...
    "It's like Homeworld in first person." Disable Aero and vSync for a completely simulator sickness free experience with 2xHz FPS. Keep the config utility open for tracking to work.
    thendrix
    New Participant
    February 9, 2015
    Used to you had to run a separate X display, but I can get proper vsync it appears with the new nvidia drivers while still running twinview. I basically sync to the HMD then disable vsync in the application for HMD mode. Did a very short blog post:

    http://mongooseichiban.blogspot.com/2015/01/nvidia-34635-linux-drivers-on-dk2-seem.html?m=1
    Terms & ConditionsAccessibility statement