bugzilla-daemon@xxxxxxxxxxxxxxxxxxx schrieb:
--- Comment #1 from Greg Kroah-Hartman <greg@xxxxxxxxx> 2009-05-21 15:35:39 ---
Please post this request on the linux-usb@xxxxxxxxxxxxxxx mailing list,
so it can be properly discussed.
OK. Here I am (again). I'll just repeat the text from the bugzilla
entry.
------------------------
The entry for vendor=0x05c6 and product=0x1000 in "unusual_devs.h"
is specific for only one maker. There are several other devices
which share these IDs (used by a Qualcomm chipset for storage device
mode) but need a different handling to switch their mode to "modem".
I received a report recently that one device ("Anydata ADU-510L")
could not be switched by the userspace tool "usb_modeswitch" when
used with 2.6.30rc5, compared to 2.6.27. In the latter, dmesg shows
there are problems with the storage device at plugin time,
presumably caused from the "option_ms_init" function, but afterwards
the storage device is bound correctly. This fails in 2.6.30rc5 with
the error:
"usb-storage: probe of 6-2:1.0 failed with error -5".
Consequently, the storage device is not initialized correctly and
the userspace switching tool stops working. Logs are provided in the
forum entry URL.
[edit]
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=739#739
[/edit]
I presently know about three different modem devices (or families)
that show vendor=0x05c6 and product=0x1000 (all storage class):
- Older "Option" 3G modems
- AnyData 3G modems
- Samsung SGH-Z810
They need three different switching commands which may interfere if
used in a sequence.
Conclusion
----------
I see two possible solutions:
- Usb-storage has a module option "option_zero_cd". Set the default
to be "2" (Allow CD-Rom) instead of "1" (Force Modem)
- Remove entry from "unusual_devs.h" entirely
--------------------------
Josh
--
Man is the only creature on earth enabled to take a
warm meal while flying! Loriot
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
