On Mon, Jul 29, 2013 at 9:05 AM, Pete Batard <p...@akeo.ie> wrote: > On 2013.07.29 00:15, James Ohr wrote: > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] driver(s): HidUsb > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] lower filter > > driver(s): LUsbFilt > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] matched driver > > name against HID API API > > [ 0.029002] [0001271c] libusbx: debug [windows_get_device_list] found > > existing device for session [1A8] (2.4) > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] driver(s): > > usbccgp > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] matched driver > > name against Composite API API > > [ 0.029002] [0001271c] libusbx: debug [windows_get_device_list] found > > existing device for session [B6] (2.8) > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] driver(s): WUDFRd > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] upper filter > > driver(s): libusb0 > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] lower filter > > driver(s): WinUsb > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] matched upper > > filter driver name against libusb0 API > > [ 0.029002] [0001271c] libusbx: debug [windows_get_device_list] found > > existing device for session [3DC] (1.3) > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] driver(s): > > USBSTOR > > [ 0.029002] [0001271c] libusbx: debug [windows_get_device_list] found > > existing device for session [370] (3.6) > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] driver(s): WUDFRd > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] lower filter > > driver(s): WinUsb > > [ 0.029002] [0001271c] libusbx: debug [get_api_type] matched lower > > filter driver name against WinUSB API > > (...) > > > [ 0.036002] [0001271c] libusbx: debug [libusb_claim_interface] > interface 0 > > [ 0.037002] [0001271c] libusbx: debug [get_interface_details_filter] > assigned libusb0 symbolic link \\.\libusb0-0001 > > [ 0.037002] [0001271c] libusbx: error [winusbx_claim_interface] could > not access interface 0: [1] Incorrect function. > > Please don't use the filter drivers. > > You have filter drivers all over the place, and unless you really have a > lot of time on your hand and plan to help patch the Windows backend to > make it work with filter drivers under the various unsympathetic > conditions that are associated with them, I *strongly* suggest that you > remove all these filter drivers, install one of the WinUSB, libusb-win32 > or libusbK drivers (preferably WinUSB), as a regular (i.e. non-filter) > driver, and see how if it works better.
In some of the above cases, most likely the filter drivers are installed as part of the vendor drivers. LUsbFilt : logitech filter driver WinUSB: lower filter driver for UMDF ( WUDFRd). But in the case of libusb-win32 (upper filter), most likely it is installed by the user. -- Xiaofan ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
