RIM devices don't work in mass storage mode when the default kernel max_sectors, 240, is used. The USB device is repeatedly reset when I/O is attempted to or from it. I found that adding this rule to udev solves the problem: SUBSYSTEM=="block", BUS=="usb", KERNEL=="sd*", ATTRS{idVendor}=="0fca", RUN+="/bin/sh -c 'echo 128 > /sys/block/%k/device/max_sectors'" I got the idea for this from http://www.thinktek.ca/articles/article3.php, although I added the ATTRS{idVendor} check to make the rule only apply to RIM devices.
why does udev need to do that? seems to be a workaround for a thing that should happen in the kernel the first place. quoting the article: In the syslog file I would see repeated "reset high speed USB device using ehci_hcd and address #" messages. Upon further investigation I learnt that this may be due to the setting for the maximum amount of data that will be transferred to or from the device in a single command, as set in /sys/block/sdb/device/max_sectors once the device is connected. The default setting is 240, which equates to 120KB. This value works for most devices, but the Bold doesn't like it. I changed it to 128 (aka 64KB) using "echo 128 > /sys/block/sdb/device/max_sectors", which is the default for Windows, and hey presto! It worked!
Does the kernel know about hardware-specific device settings like this? If so, then I suppose it would be reasonable for this to be handled by the kernel. I can't say I care *who* does it, just as long as *somebody* does so my BlackBerry's filesystem doesn't keep getting corrupted ;-).
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
May I suggest a _general_ rule to set _all_ devices to a max_sectors of 128? This affects a lot of various devices that have only been tested under Windows.. For more information: http://www.linux-usb.org/FAQ.html#i5
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.