Mounting the Rio MP3 Player as USB Storage Device?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Apparently, that user had success in using his Rio as an USB Storage Device, and so was able to simply transfer files as though it were a normal hard drive.
I'm running SuSE 10.0 with the default 2.6.13-15 kernel. I have not been able to use the Rio as a USB storage device. In fact, no block exists at /dev/sdx, except for my hard drive at /dev/sda. Running lsusb, however, does show that the kernel does detect the USB device, but does not associate it with a node.
Nov 10 13:54:09 linux kernel: usb 3-1: USB disconnect, address 10
Nov 10 13:54:19 linux kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 11
dmesg This is after plugging and unplugging the device several times.
usb 3-1: new full speed USB device using uhci_hcd and address 9
usb 3-1: USB disconnect, address 9
usb 3-1: new full speed USB device using uhci_hcd and address 10
usb 3-1: USB disconnect, address 10
usb 3-1: new full speed USB device using uhci_hcd and address 11
usb 3-1: USB disconnect, address 11
usb 3-1: new full speed USB device using uhci_hcd and address 12
I don't compile my kernels anymore, but I used to under Slackware. I read somewhere that it might have to do with multi LUN, but my USB card reader works fine in SuSE out of box. I used to compile multi LUN support to get my USB card reader to work, so I don't think it's that.
Note that the umask is the inverse of the permissions you want to give it. a umask=000 actually gives permissions of octal 777.
I should mention that I am using Linux SLAMD64 12.0 (a 64 bit distro based on Slackware ) and
I use the UDEV device names in the fstab so the device is mounted in the same place every time no matter what is plugged in on power up.
I forgot--you mentioned recompiling the kernel for multi-LUN support. I had to do that too.
The reason for doing that under any kernel, is to rescan the scsi bus for devices that have more than one LUN on the same device.
1. a Sansa E280 mp3 player has main memory as one LUN and the micro SD card in it as a different LUN but is seen as 1 scsi device. So you need to have multi-LUN support for a device like that, otherwise your computer stops looking for LUNs after it finds the first one on the device.
2. Not all 6-in-1 card readers are made the same. Some are made with type card as one LUN, and some are made with 2 or 3 different LUNs for different cards that can be inserted in the device. An example is the card reader built into my Dell 24" monitor--it uses 2 LUNS.
What happened to me when I did not have multi-LUN support compiled in was I would boot up with no card in the 6-in-1, then use a Compact flash card. When done, unmount it and take it out. Then if I inserted a memory stick into the 6-in-1, it would not find the memory stick at all. If I rebooted with no card in, then put a memory stick in, it would mount and read it. if after that I put a CF card in, and tried to mount it, it wouldn't read it. It would only use the first _type_ device inserted in the 6-in-1 reader after boot up.
To fix that problem, I did 2 steps:
1. recompile the kernel with multi-LUN support.
2. between inserting different cards, run a script that I had attached to an icon on my panel forcing a rescan of the LUNs. There may be better ways of doing this, and if so, I'm willing to learn.
Here is the simple script in case someone else reading this wants to do it:
for x in `ls ?-* -d `
echo "found: "$x
echo -n $x > /sys/bus/usb/drivers/usb-storage/unbind
echo -n $x > /sys/bus/usb/drivers/usb-storage/bind
Had I realized that all 6-in-1 card readers are not made the same, I might have just bought a different one and ignored the one in the side of the dell monitor (grin), but I didn't know that at the time I was trying to solve this. They don't say on the box what kind they are, so I still don't know how I would be able to tell what kind I was buying in a store...
Anyway, I just wanted to say some reasons to need multi-LUN support, and what the problem of not having that compiled in might look like.
I agree with you that that is probably not the problem with getting whatever rio you have mounted as a USB mass storage device.