Skip to main content
antoche
New Participant
October 29, 2014

Linux + DK1 + sdk 0.4.3 = no device attached

Spec: Ubuntu 14.04, intel core i5 with integrated GPU (H67ITX-C-E/H67ITX-C-E), latest Intel graphics drivers.

SDK 0.2.3 works fine, but with 0.4.3 the config utility says there is no device attached. When trying to toggle legacy app support, I see this in the console:

Error: [SysDlg] Service and driver legacy mode are out of sync: Failed to fix it.


Oculus world demo seems to be opening a window for a microsecond then exits with status 1. Log:
X Error of failed request:  GLXBadDrawable
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  29 (X_GLXGetDrawableAttributes)
  Serial number of failed request:  80
  Current serial number in output stream:  80


(tried the fix at viewtopic.php?f=20&t=16268#p213055, didn't help).

oculusd log:

OVR::DeviceManagerThread - running (ThreadId=0x7f7f67988700).
OVR::DeviceManager - initialized.
OVR::Linux::HIDDevice - Opened '/dev/hidraw0'
                    Manufacturer:'Oculus VR, Inc.'  Product:'Tracker DK'  Serial#:'M1EGG3PGPM39'
Error: {ERR-011} [SensorImpl] Magnetometer calibration not found!
[TrackingManager] Sensor added: PrintedSerial=M1EGG3PGPM39 UUID=
[TrackingManager] Display added: UUID=SerialRD
     Driver=0

    5 replies

    antocheAuthor
    New Participant
    October 29, 2014
    Also tried sdk 0.3.2. The ConfigUtility works, as well as the config demo scene (albeit some issues including errors in the shader code and GLSL 1.50 not supported). But the Oculus World Demo just shows be a black unresponsive window (no warnings or error).

    The piece of bad shader code:

    EyeRotation[0] = mix ( EyeRotationStart[0], EyeRotationEnd[0], Color.a );


    (should be mix(...).xyz).

    So only 0.2.3 works for me. :(
    rjoyce
    Participant
    October 30, 2014
    I'm guessing you don't have a DK2?

    I did not try very hard, but I briefly unplugged my DK2 and fired back up the old DK1 to see if my application still worked with it after the upgrade to 0.4.3, but it could never find it, ovrHmd_Create() would just fail. I didn't have time to see if there is something obvious I'm missing, but its certainly possible that there is a bug that causes DK1 not to work with linux 0.4.3, as it is after all, an experimental beta :?
    mungewell
    Up and Coming
    October 31, 2014
    Would love some confirmation whether DK1 will work with 0.4.3 on Linux. My own experience (with non Oculus hardware) is that it doesn't see it, in app or config tool.

    A console log from 'oculusd' would be helpful to compare.
    Thanks,
    Simon.
    antocheAuthor
    New Participant
    November 3, 2014
    Indeed, I don't have a DK2. Happy to test one if it's send my way. :p
    In the meantime, it would be good to know what's wrong and what's the ETA for a fix.
    anmlr
    New Participant
    November 6, 2014
    I'm getting the same stuff happen to me, DK1 on Ubuntu 14.04, GTX 680

      * I can see my desktop through the DK1.
      * No Device Attached in config utility
      * No tracking in demos
      * Have tried different USB ports, both USB2 and USB3 which other devices work in


    Starting oculusd seems sensible:
    ./oculusd
    OVR::DeviceManagerThread - running (ThreadId=0x7f7cdcceb700).
    OVR::DeviceManager - initialized.
    OVR::Linux::HIDDevice - Opened '/dev/hidraw1'
                        Manufacturer:'Oculus VR, Inc.'  Product:'Tracker DK'  Serial#:'GA9EH3RGQCI8'
    [TrackingManager] Sensor added: PrintedSerial=GA9EH3RGQCI8 UUID=
    [TrackingManager] Display added: UUID=SerialRD
         Driver=0


    Attempting to enable the DK1 legacy mode in the config utility gives the same error as you
    Error: [SysDlg] Service and driver legacy mode are out of sync: Failed to fix it.


    Fiddling with cables gives sensible messages in oculusd - I will include them for completion.

    Removing HDMI:
    [TrackingManager] Display removed: UUID=SerialRD
         Driver=0

    Plugging HDMI back in:
    [TrackingManager] Display added: UUID=SerialRD
         Driver=0


    Removing USB:
    OVR::Linux::HIDDevice - HID Device Closed '/dev/hidraw1'
    OVR::SensorDevice - Closed '/dev/hidraw1'
    OVR::Linux::HIDDevice - HIDShutdown '/dev/hidraw1'

    Plugging USB back in:
    OVR::Linux::HIDDevice - Opened '/dev/hidraw1'
                        Manufacturer:'Oculus VR, Inc.'  Product:'Tracker DK'  Serial#:'GA9EH3RGQCI8'
    [TrackingManager] Sensor added: PrintedSerial=GA9EH3RGQCI8 UUID=


    Pressing the power button on the Rift has no effect on messages
    Wrenching the power cable out gives the same result as removal of the USB
    Terms & ConditionsAccessibility statement