S50 S35S S30S and S10

Spoon
2002-11-26
2003-01-02
  • Spoon

    Spoon - 2002-11-26

    I have heard that protocal for these is identical as with Rio 800 & Rio 600, all that is needed is for new device IDs to be recognized.

     
    • Nathan Hjelm

      Nathan Hjelm - 2002-12-01

      Cool! Then all I need are the product ids. Anyone know what they are?

       
    • Ken Collins

      Ken Collins - 2002-12-10

      One of the users on rioworld was a developer on the S series. He might be able to help out:

      http://www.rioworld.org/yabbse/index.php?board=1;action=viewprofile;user=phrenzy

       
    • Ken Collins

      Ken Collins - 2002-12-10

      This is what he had to say about the driver:

      "A linux developer could make a Rio 800 linux driver work with the S series in a short amount of time.  It won't work right out of the box though."

       
    • Carmine F. Greco

      S35 is vendor 0x045a and product 0x5007.  I tried patching the rioutil code from raceme.org/rioutil (is that the same as this project?) but had some trouble.  The message from the driver was:
      <pre>
      rio500.c: probe_rio: device node registration failed
      </pre>
      I didn't try anything after that.  Someone more familiar with the code will probably have better luck than me.  All I did was add the vend/prod to the rio500.c and rio500_usb.h to see if the driver would spit out a message that it recognized the device.  (My first attempt at hacking Linux code)

       
      • Nathan Hjelm

        Nathan Hjelm - 2002-12-16

        Ohh, ignore that. That is just devfs failing (which im assuming you dont have?).

        Anyway, the latest version is in cvs. Give it a try.

         
    • Nathan Hjelm

      Nathan Hjelm - 2002-12-16

      I'll add it and upload to cvs. (rioutil/linux_driver)

       
    • Carmine F. Greco

      Bad news.  It didn't just work :(

      Here's the output from rio_stat followed by the modules error messages.
      -----------------------------------------------------
      [root@carmine root]# rio_stat
      Your Rio500 has firmware revision 0.00
      Card 0 reports 0 Mb free (0 bytes) out of 0 Mb (0 bytes).
      Command 0x57 returned:
      first_free_block = 0x00000000
      sl = 0x00000000
      -------------------------------------------------------------
        N   offset  num songs       Folder Name
      -------------------------------------------------------------

      ----------------------------------------------------

      hub.c: USB new device connect on bus2/1/2, assigned device number 14
      rio500.c: USB Rio S35 found at address 14
      rio500.c: Device assigned minor 0
      rio500.c: open_rio: rio opened.
      usb-uhci.c: interrupt, status 2, frame# 971
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 993
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1094
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1128
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1153
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1183
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1214
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1243
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1274
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1304
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1333
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1363
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1393
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1423
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1453
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1484
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1514
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1544
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1573
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1603
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1634
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1663
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1693
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1723
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1753
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1783
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1814
      rio500.c: Error executing ioctrl. code = -32
      usb-uhci.c: interrupt, status 2, frame# 1843
      rio500.c: Error executing ioctrl. code = -32
      rio500.c: close_rio: rio closed.
      ------------------------------------------------

       
    • Nathan Hjelm

      Nathan Hjelm - 2002-12-19

      DO NOT use the rio500 software. It uses a completly different protocol! Use rioutil instead.

       
    • Nathan Hjelm

      Nathan Hjelm - 2003-01-02

      For those of you trying to use rioutil with an S-Series try downloading from CVS and let me know of any successes/failures.

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks