On Tue, Mar 24, 2015 at 18:02:51 +0700, Lars Melin wrote: > On 2015-03-24 17:20, Oliver Neukum wrote: ... > >>[ 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. 4.0.0-rc5+ does not switch to "old Win" mode even if I blacklist usb_storage, have to reboot to 3.18.9. Why? [57023.245141] usb 5-1: USB disconnect, device number 3 [57036.756071] usb 5-1: new high-speed USB device number 4 using xhci_hcd [57036.926823] usb 5-1: New USB device found, idVendor=12d1, idProduct=157d [57036.926827] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [57036.926828] usb 5-1: Product: HUAWEI_MOBILE [57036.926829] usb 5-1: Manufacturer: HUAWEI_MOBILE [57036.926831] usb 5-1: SerialNumber: 0123456789ABCDEF > 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. -- Do what you love because life is too short for anything else. -- 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
