Thomas Schäfer <tschaefer@xxxxxxxxxxx> writes: > Am Montag, 7. Oktober 2013, 16:04:49 schrieben Sie: > >> Have you verified that the latest version of usb-modeswitch doesn't fix >> this issue? I think I've seen reports that it does, but it would be >> good if you could test that out and verify it. > > May be it is intention. Under win8 it does not change its ID. > Do we make the same break as MS does. (cdc --> mbim?) Yes, that's correct. usb_modeswitch will prefer MBIM by default if the cdc_mbim driver exists and the device supports MBIM. But you can change the this, per device if you like. Just set NoMBIMCheck=1 in the usb_modeswitch device config. For example, create a /etc/usb_modeswitch.d/12d1:1f16 file with something like this (I haven't checked the exact config for your device, but you get the idea): TargetVendor=0x12d1 TargetProductList="1f16" NoMBIMCheck=1 MessageContent="55534243123456780000000000000011062000000100000000000000000000" > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 2 Communications > bInterfaceSubClass 14 > bInterfaceProtocol 0 > iInterface 0 > CDC Header: > bcdCDC 1.10 > UNRECOGNIZED CDC: 0c 24 1b 00 01 00 04 10 14 dc 05 20 Yup, that's MBIM. If you use a newer lsusb, you'll get the MBIM descriptor decoded too. > modprobe cdc_mbim > echo "12d1 1f16" > /sys/bus/usb/drivers_mbim/new_id > > has had no effect. Well, it shouldn't have any effect. The driver should already be autoloaded based on the class. Is it not? Does the probe fail? Relevant parts of dmesg would be interesting... And preferably with some debugging too, if the probing really fails. Bjørn -- 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
