Nitrus

Help
2006-11-12
2013-04-23
  • Jesse Raleigh
    Jesse Raleigh
    2006-11-12

    Just wondering what the status is with the Rio Nitrus. The homepage hasn't been updated in 5 years or so, and there doesn't seem to be much activity in these forums. I installed the rioutils in the 6.06 ubuntu repositories to see if there had been any improvements, and it's still not working. Is it worth the effort to compile the latest version or does the Nitrus just not work at all?

    - Jesse

     
    • Nathan Hjelm
      Nathan Hjelm
      2006-11-13

      Rio Nitrus *should* work as it works under darwin. I can't be sure because I have not been able to test the device with linux as the usb connector on my Nitrus fell apart. Can you elaborate on what exactly is not working? Perhaps send me some output from "rioutil -eee -i"? Your help would be appreciated as it will be some time before I find time to fix my Nitrus.

      -Nathan

       
    • jaeger
      jaeger
      2007-02-14

      It's not working for me either (Ubuntu 6.10).  Using rioutil 1.5.0 and libusb 0.1.12.

      Output from `rioutil -eee -i` is:

      Attempting to open Rio and retrieve song list.... open_rio: creating new rio instance. device: 0x00000000
      open_rio: setting usb driver verbosity level to 3
      usb_set_debug: Setting debugging level to 3 (on)
      usb_os_init: Found USB VFS at /dev/bus/usb
      usb_os_find_busses: Skipping non bus directory devices
      usb_os_find_busses: Found 005
      usb_os_find_busses: Found 004
      usb_os_find_busses: Found 003
      usb_os_find_busses: Found 002
      usb_os_find_busses: Found 001
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 008 on 005
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 007 on 005
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 006 on 005
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 001 on 005
      error obtaining child information: Operation not permitted
      error obtaining child information: Operation not permitted
      error obtaining child information: Operation not permitted
      error obtaining child information: Operation not permitted
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 001 on 004
      error obtaining child information: Operation not permitted
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 002 on 003
      skipped 1 class/vendor specific interface descriptors
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 001 on 003
      error obtaining child information: Operation not permitted
      error obtaining child information: Operation not permitted
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 001 on 002
      error obtaining child information: Operation not permitted
      usb_os_find_devices: couldn't get connect info
      usb_os_find_devices: Found 001 on 001
      error obtaining child information: Operation not permitted
      USB Device: idVendor = 00008088, idProduct = 0000a014
      USB Device: idVendor = 0000045a, idProduct = 00005220
      Error -2: open_rio: could not open a Rio device
      failed!
      Reason: No such file or directory.
      librioutil tried to use method: libusb

       
      • Nathan Hjelm
        Nathan Hjelm
        2007-02-15

        Are the device permissions correct or are you running rioutil as root? The error suggests that rioutil can not write to the device.

        Please respond to me via my sourceforge email address. If you are willing to do some testing I need some help to getting Nitrus working under linux-x86. My Nitrus bit the dust awhile back (usb connector is broken) so I have not been able to fix it on my own.

        thanks,
        -Nathan

         
    • snostorm
      snostorm
      2009-07-28

      I have this working for a nitrus on my arch 64 release, so I may be able to help