I appologize. I accidently posted the traffic of regular flash-memory disk. This is the traffic for the HDD:
USB data USB3.0 Device Super Speed Mass Storage - USB Mass Storage Device ID: 1 Function: IRP_MJ_PNP Minor function: PNP_IRP_UNKNOWN (0x18) Status code: 0xC00000BB Status: ERROR ID: 2 Function: IRP_MJ_PNP Minor function: IRP_MN_QUERY_RESOURCE_REQUIREMENTS Status code: 0xC00000BB Status: ERROR ID: 3 Function: IRP_MJ_PNP Minor function: IRP_MN_FILTER_RESOURCE_REQUIREMENTS Status code: 0xC00000BB Status: ERROR ID: 4 Function: IRP_MJ_PNP Minor function: IRP_MN_START_DEVICE Status code: 0x00000000 Status: STATUS_SUCCESS ID: 5 Function: IRP_MJ_PNP Minor function: IRP_MN_QUERY_CAPABILITIES Status code: 0x00000000 Status: STATUS_SUCCESS ID: 6 Function: IRP_MJ_PNP Minor function: IRP_MN_QUERY_PNP_DEVICE_STATE Status code: 0x00000000 Status: STATUS_SUCCESS ID: 7 Function: IRP_MJ_SYSTEM_CONTROL Status code: 0x00000000 Status: STATUS_SUCCESS Ido On Mon, 2013-12-02 at 18:15 +0100, Josua Dietze wrote: [...] > In case there IS a driver required on Windows, you might be able to catch the > initial traffic between this driver and the device once the thing is > re-plugged. In a second step, the initiating command(s) can possibly be > 'replayed' in Linux. This is the usual way usb_modeswitch works. > Note that if a special Windows driver is required for actually ACCESSING the > disk (not just for initialization), then a new Linux driver may be required > as well ... > [...] I don't know if it will help but I tried to capture the USB traffic on Windows station at the time I connected the drive. I got some output but I don't know it's meaning. That what I got by the USB capturing software: USB data SMI Corporation USB DISK - USB Mass Storage Device [...] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/1386280523.9471.9.camel@ihlaptop
