2 Replies Latest reply on Feb 4, 2018 1:41 PM by mrucux7

    Libusb - Device detected only in latepass - Possible USB hub driver issue?

    mrucux7

      OS: Windows 7 SP1 64-bit - Tried on both fully updated and fresh install

      MB: MSI B350M PRO-VDH / Bios vA.60

      RAM: 8GB G.Skill

      CPU: Ryzen 5 1600X

      Chipset drivers: v17.40  16/01/18 (the newest ones)

       

      I had an issue getting my RTL-SDR (software defined radio) to work on my new hardware (as above), and so I started digging around the internet trying to find an answer to the problem. On another forum, I found a hint as to where I should investigate, and that this could be a driver issue (for the curious: Trouble getting a generic RTL2832U to work - Page 2 - The RadioReference.com Forums ). Used newest libusb-1.0.21 release and the included examples (listdevs and xusb, to be exact). Logs below:

      C:\Users\testos\Desktop\libusb-1.0.21\examples\bin64>xusb.exe -d
      Using libusb v1.0.21.11156
      
      [timestamp] [threadID] facility level [function call] <message>
      --------------------------------------------------------------------------------
      
      [ 0.000000] [00000a5c] libusb: debug [libusb_init] created default context
      [ 0.000000] [00000a5c] libusb: debug [libusb_init] libusb v1.0.21.11156
      [ 0.000000] [00000a5c] libusb: debug [windows_init] Windows 7 SP1 64-bit
      [ 0.000000] [00000a5c] libusb: debug [setup_cancel_io] Will use CancelIoEx for I
      /O cancellation
      [ 0.000000] [00000a5c] libusb: info [winusbx_init] libusbK DLL is not available,
       will use native WinUSB
      [ 0.000000] [00000a5c] libusb: debug [winusbx_init] initalized sub API libusbK
      [ 0.000000] [00000a5c] libusb: debug [winusbx_init] initalized sub API libusb0
      [ 0.000000] [00000a5c] libusb: debug [winusbx_init] initalized sub API WinUSB
      [ 0.000000] [00000a5c] libusb: debug [windows_init_clock] hires timer available
      (Frequency: 3515693 Hz)
      [ 0.000000] [00000a5c] libusb: debug [windows_init_clock] timer thread will run
      on core #0
      [ 0.000000] [00000a5c] libusb: debug [htab_create] using 1021 entries hash table
      
      [ 0.000000] [00000a5c] libusb: debug [usbi_add_pollfd] add fd 0 events 1
      Opening device 0000:0000...
      [ 0.000000] [00000a5c] libusb: debug [libusb_get_device_list]
      [ 0.000000] [00000a5c] libusb: debug [windows_get_device_list] allocating new de
      vice for session [327]
      [ 0.000000] [00000a5c] libusb: debug [windows_get_device_list] allocating new de
      vice for session [3C3]
      [ 0.000000] [00000a5c] libusb: debug [get_api_type] driver(s): amdhub3
      [ 0.000000] [00000a5c] libusb: debug [windows_get_device_list] allocating new de
      vice for session [264]
      [ 0.000000] [00000a5c] libusb: debug [get_api_type] driver(s): amdhub31
      [ 0.000000] [00000a5c] libusb: debug [windows_get_device_list] allocating new de
      vice for session [1DC]
      [ 0.000000] [00000a5c] libusb: debug [windows_get_device_list] found existing de
      vice for session [1DC] (0.0)
      [ 0.000000] [00000a5c] libusb: debug [init_device] (bus: 2, addr: 1, depth: 0, p
      ort: 0): '\\.\USB#AMDROOT_HUB31#5&392D0FAB&0&0'
      [ 0.015600] [00000a5c] libusb: debug [windows_get_device_list] extra GUID: {253F
      7BD6-49E7-4656-B459-932A4C8B406A}
      [ 0.015600] [00000a5c] libusb: info [windows_get_device_list] The following devi
      ce has no driver: '\\.\USB#VID_0BDA&PID_2838&MI_01#7&38A180A5&0&0001'
      [ 0.015600] [00000a5c] libusb: info [windows_get_device_list] libusb will not be
       able to access it.
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] driver(s): USBSTOR
      [ 0.015600] [00000a5c] libusb: warning [windows_get_device_list] '\\.\USB#VID_07
      81&PID_556B#200601645007C4328390' was only detected in late pass (newly connecte
      d device?) - ignoring
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] driver(s): usbccgp
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] matched driver name against
      Composite API
      [ 0.015600] [00000a5c] libusb: warning [windows_get_device_list] '\\.\USB#VID_0B
      DA&PID_2838#00000001' was only detected in late pass (newly connected device?) -
       ignoring
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] driver(s): HidUsb
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] matched driver name against
      HID API
      [ 0.015600] [00000a5c] libusb: warning [windows_get_device_list] '\\.\USB#VID_1B
      CF&PID_0005#6&292BC060&0&4' was only detected in late pass (newly connected devi
      ce?) - ignoring
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] driver(s): WinUSB
      [ 0.015600] [00000a5c] libusb: debug [get_api_type] matched driver name against
      WinUSB
      [ 0.015600] [00000a5c] libusb: debug [libusb_unref_device] destroy device 1.0
      [ 0.015600] [00000a5c] libusb: debug [libusb_unref_device] destroy device 0.0
      [ 0.015600] [00000a5c] libusb: debug [libusb_get_device_descriptor]
      [ 0.015600] [00000a5c] libusb: debug [libusb_unref_device] destroy device 2.1
      [ 0.015600] [00000a5c] libusb: debug [libusb_unref_device] destroy device 2.0
        Failed.
      [ 0.015600] [00000a5c] libusb: debug [libusb_exit]
      [ 0.015600] [00000a5c] libusb: debug [libusb_exit] destroying default context
      [ 0.015600] [00000a5c] libusb: debug [usbi_remove_pollfd] remove fd 0
      [ 0.015600] [00000640] libusb: debug [windows_clock_gettime_threaded] timer thre
      ad quitting
      
      C:\Users\testos\Desktop\libusb-1.0.21\examples\bin64>listdevs.exe
      1022:43bb (bus 2, device 1)
      

      What caught my attention was the "Device was only detected in late pass" bit and the lack of any devices on the listing (despite having plugged in a couple of flash drives), so I did some more digging around, and came across a libusb mailing list about this exact issue, which pointed to the vendor drivers being the culprit. I have tried the same thing on the newest version of the chipset drivers (16 Jan), on both my usual install and a fresh Windows install, but the result is the same.

      Now, I am not a driver engineer and I might be very wrong on all of this (especially since the mailing list conversation is from 2011, and the other person's post is from 2014 [thanks xkcd!]), however I'm desperate to get this thing running. I'd love if somebody more knowledgeable on the topic replied with their thoughts on this.