On 2015-03-24 17:20, Oliver Neukum wrote:
On Mon, 2015-03-23 at 21:11 +0200, Sami Farin wrote:
I tried reverting f46ad73ac696 in 4.0.0-rc5, did not help. Have to
reboot first into 3.18.9.
This happens:
[ 2765.268081] usb 2-1.4.4: USB disconnect, device number 16
[ 2777.209388] usb 2-1.4.4: new high-speed USB device number 17 using
ehci-pci
[ 2777.303172] usb 2-1.4.4: New USB device found, idVendor=12d1,
idProduct=157d
[ 2777.303174] usb 2-1.4.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 2777.303176] usb 2-1.4.4: Product: HUAWEI_MOBILE
[ 2777.303177] usb 2-1.4.4: Manufacturer: HUAWEI_MOBILE
[ 2777.303178] usb 2-1.4.4: SerialNumber: 0123456789ABCDEF
[ 2777.325198] usb-storage 2-1.4.4:1.0: USB Mass Storage device
detected
[ 2777.325282] scsi host37: usb-storage 2-1.4.4:1.0
[ 2777.903039] usb 2-1.4.4: usbfs: interface 0 claimed by usb-storage
while 'usb_modeswitch' sets config #2
This fails. It comes from proc_setconfig(). It suggests that a change
in storage causes this. To verify, could you blacklist usb-storage
in a test with 4.0?
Regards
Oliver
12d1:157d has 2 configurations, config #1 being the virtual cd-rom
containing windows drivers and config #2 containing cdc_mbim interfaces.
cdc_mbim is the primary protocol for this Win8 approved dongle but it
can be switched via a bulkmsg into an "old Win" compatibility mode which
usually is cdc_ether.
usb_modeswitch will check if the cdc_mbim driver is present in the
system when it finds a dongle which has cdc_mbim attributes on its
interfaces.
If the driver is found then the port will be set to config #2 which is
the required config number for cdc_mbim.
If no driver is found then the bulk msg will be sent for switching the
dongle into compatibility mode where it also will have a different usb id.
--
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
