The RioS10 is the only usb device connected. Here is /proc/bus/usb/devices:
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI-alt Root Hub S: SerialNumber=ef80 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=045a ProdID=5005 Rev= 0.00 S: Manufacturer=SONICblue Inc. S: Product=Rio S10 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms I thought the same, that if the class is ff then it would need a proprietary device driver. Does the 2nd D line D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 mean that it uses the class 00 driver? I am confused by the last I line where it shows the class number as ff. later--, jon On Mon, 1 Dec 2003 21:24:22 -0800 "Randy.Dunlap" <[EMAIL PROTECTED]> wrote: > On Mon, 1 Dec 2003 23:58:35 -0500 Jon Rafkind <[EMAIL PROTECTED]> > wrote: > > | Hello, > | I am fairly new to the usb devices, but I have looked all over > | the > | internet and have come up empty handed. I recently bought the > | SonicBlue RioS10 and am trying to get it to work under linux. I see > | that it registers with the usb module in dmesg and also information > | is printed in /proc/bus/usb/devices about it. I never seem to get > | /dev/sda1, however. So far I have concluded that a seperate drives > | is needed as usb-storage doesnt seem to work. I downloaded the > | rio500 from sourceforge, but that looks for a /dev/usb/rio500 device > | specifically. Does anyone know if there is support for this device > | or if the rio500 could be hacked to work with the rioS10? > > Please post the contents of /proc/bus/usb/devices when the device is > connected so that we can see its device descriptors. That should > enable us to determine what kind of interface it is and what kind > of driver is required. If the device and interface Class (Cls) fields > are 0xff, that means vendor-specific or proprietary, i.e., the device > doesn't use a USB class interface, so it will need a vendor-specific > driver. > > -- > ~Randy > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users