So I am working on an install script for a program that needs the device id from lsusb in its configuration so I was thinking of doing the following: $usblist=(lsusb) #put the list into a array for each line. #use the array to give the user a selection list usinging whiptail. #from that line strip out the device id and vender id from the selected line. The line looks as follows: Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial So I want only the 9 characters after "ID{space}"

I am working on an embedded Linux system (kernel-5.10.200), and I met one problem about USB disk detection. I did 2 tests as follows. 1. Inserted the USB disk before boot system up. 2. Inserted the USB disk after system booted up (hot-plug). In both tests, after system booted up, I manually configured the USB port from device mode to host mode, then check how fast the /dev/sda is created. I found in the 1st case, it took about 17 seconds for /dev/sda to be created. In the 2nd case, it took about 2 seconds for /dev/sda to be created. I could NOT figure out the reason of the big difference in time of /dev/sda creation. So I enabled usbmon in kernel, and I got following extra output for the 1st case (after the port is switched to host mode).

811c4480 7790082 C Ii:1:001:1 0:2048 1 = 02
811c4480 7790128 S Ii:1:001:1 -150:2048 4 
8220bd00 14390474 S Bi:1:002:1 -150 36 
81ea5000 14391634 S Bi:1:002:1 -150 13 
8220b080 14391891 S Bi:1:002:1 -150 18 
81ea5000 14392510 S Bi:1:002:1 -150 13 
8220b580 14392852 S Bi:1:002:1 -150 8 
8220b580 14393375 S Bi:1:002:1 -150 192 
8220b580 14393878 S Bi:1:002:1 -150 192 
81ea5000 14430666 S Bi:1:002:1 -150 13 
81ea5000 14431019 S Bi:1:002:1 -150 13 
82399780 14431374 S Bi:1:002:1 -150 8 
82399780 14431764 S Bi:1:002:1 -150 192 
82399780 14432277 S Bi:1:002:1 -150 192 
81ea5000 14432714 S Bi:1:002:1 -150 13 
82399600 14433138 S Bi:1:002:1 -150 4096 
81ea5000 14434594 S Bi:1:002:1 -150 13 
81ea5000 14435507 S Bi:1:002:1 -150 13 
81ea5000 14435827 S Bi:1:002:1 -150 13 
8238be80 14436174 S Bi:1:002:1 -150 8 
8238be80 14436646 S Bi:1:002:1 -150 192 
8238be80 14437036 S Bi:1:002:1 -150 192 <
8238be80 14437076 C Bi:1:002:1 -140 12 = 0b000008 0003e311 00000800
81ea5000 14437139 S Bi:1:002:1 -150 13 <
81ea5000 14437171 C Bi:1:002:1 0 13 = 55534253 14000000 00000000 00
811c4480 96790040 C Ii:1:001:1 0:2048 1 = 02
811c4480 96790071 S Ii:1:001:1 -150:2048 4 <
8235d100 96790167 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
8235d100 96790193 C Ci:1:001:0 0 4 = 00000300
8235d100 96790206 S Co:1:001:0 s 23 01 0010 0001 0000 0
8235d100 96790216 C Co:1:001:0 0 0
8235d100 96790223 S Co:1:001:0 s 23 01 0011 0001 0000 0
8235d100 96790230 C Co:1:001:0 0 0
831bd000 96901033 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
831bd000 96901147 C Ci:1:001:0 0 4 = 00000000
81ea5580 96950067 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
81ea5580 96950099 C Ci:1:001:0 0 4 = 00000000
81ea5580 97000044 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
81ea5580 97000071 C Ci:1:001:0 0 4 = 00000000
81ea5580 97050044 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
81ea5580 97050071 C Ci:1:001:0 0 4 = 00000000
81ea5580 97100039 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
81ea5580 97100065 C Ci:1:001:0 0 4 = 00000000
81ea5580 97100083 S Co:1:001:0 s 23 03 0008 0001 0000 0
81ea5580 97100098 C Co:1:001:0 0 0

I don't know how to intepret above outputs, and where should I focus on to solve the 17 seconds of /dev/sda creation. The system is using mdev to manage devices' lifecycle.

##### Examples lsusb -v returns entries like the undermentioned: ~~~YAML Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 9 Hub bDeviceSubClass 0 [unknown] bDeviceProtocol 2 TT per port bMaxPacketSize0 64 idVendor 0x05e3 Genesys Logic, Inc. idProduct 0x0610 Hub bcdDevice 34.04 iManufacturer 1 GenesysLogic iProduct 2 USB2.1 Hub iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0029 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 [unknown] bInterfaceProtocol 1 Single TT iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 [unknown] bInterfaceProtocol 2 TT per port iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x0049 bNumDeviceCaps 5 Couldn't get device capability descriptors can't get hub descriptor, LIBUSB_ERROR_TIMEOUT (Resource temporarily unavailable) cannot read device status, Resource temporarily unavailable (11) ~~~ usb-devices returns: ~~~YAML T: Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=10000 MxCh= 1 D: Ver= 3.10 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=06.13 S: Manufacturer=Linux 6.13.9-200.fc41.x86_64 xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=0000:c3:00.4 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256m ~~~ Neither of these appear to inform me of which (physical) connector type the port is. I've grep -E'd for -c and type, etcetera, and manually scoured the output with my eyes.

On linux systems, the lsusb command produces a concise listing of connected USB devices. $ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 2ce3:9563 Generic EMV Smartcard Reader Bus 001 Device 007: ID 174f:181f Syntek Integrated Camera Bus 001 Device 010: ID 8087:0033 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Is there a similar command for bluetooth devices? **Update: reposnse to @totoaussi** Thanks for pointing me at hciconfig It doesn't provide any info on individual devices, and indicates that it's looking at USB devices, not bluetooth. Nothing in hciconfig --help indicates any command that does anything about bluetooth. **Update: reposnse to @telcoM** Thanks for pointing me at bluetoothctl. Syntax is not quite what you indicate. bluetoothctl devices Paired and bluetoothctl devices Connected are not recognized commands. Perhaps you meant bluetoothctl paired-devices? bluetoothctl devices does perform as you described: $ bluetoothctl devices Device D6:EB:4B:54:DF:54 MX Master 3S Device D7:D9:8D:73:F6:95 MX MCHNCL $ bluetoothctl paired-devices Device D6:EB:4B:54:DF:54 MX Master 3S Device D7:D9:8D:73:F6:95 MX MCHNCL I suppose you could infer by running bluetoothctl devices and bluetoothctl paired-devices which devices were connected but not paired, which in my case above is none. **But perhaps I should explain my purpose in going down this path.** I'd like to remap some keys on the MX Mechanical keyboard which lacks PrtSc and SysRq keys. I'm looking at the following idea https://www.reddit.com/r/logitech/comments/13neatr/comment/jsplvbk/ and trying to adapt it to a bluetooth setup. With that purpose in mind, please note that the bluetoothctl information is much less than what lsusb provides, no vendor codes or model codes.

Any help would be deeeeeeply appreciated. I've dealt with this for 3-4 years now and I'm finally wanting to fix this once and for all. **System info:** - Device: Lenovo Thinkpad E14 Gen 2 - Linux Kernel: 6.13 - Current OS: NixOS - Past OS's used: Ubuntu, Debian, Arch, Kali & openSUSE. - (Windows 10/11 seems to be the only OS that works with my USB ports.) **Issue:** Like the title states, all my USB ports are non-functional across multiple Linux distributions. The issues I've encountered are as follows. 1. No power delivery to devices 2. No device recognition in the system 3. No response when plugging in/unplugging devices (other than a USB or keyboard light turns on for a split second, then off) **System Logs:** Here are some of the outputs I get when I run dmesg & lsusb. (After I've plugged in and unplugged a USB/USB device). lsusb output:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:c123 Realtek Semiconductor Corp. Bluetooth Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

dmesg output:

[ 1724.098991] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1724.547011] amdgpu 0000:04:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
[ 1724.614838] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 1724.623063] amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 1724.623065] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[ 1724.623068] amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
[ 1724.623369] amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
[ 1724.623790] amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
[ 1724.625244] [drm] kiq ring mec 2 pipe 1 q 0
[ 1724.628977] [drm] DMUB hardware initialized: version=0x0101002B
[ 1724.632546] amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 1724.632549] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 1724.632550] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 1724.632552] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 1724.632553] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 1724.632554] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 1724.632555] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 1724.632556] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 1724.632557] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 1724.632559] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 1724.632560] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[ 1724.632562] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[ 1724.632563] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[ 1724.632564] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[ 1724.632565] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[ 1724.639212] OOM killer enabled.
[ 1724.639214] Restarting tasks ... 
[ 1724.639750] pci_bus 0000:01: Allocating resources
[ 1724.639763] pcieport 0000:00:02.1: bridge window [io  0x1000-0x0fff] to [bus 01] add_size 1000
[ 1724.639772] pcieport 0000:00:02.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000 add_align 100000
[ 1724.639784] pci_bus 0000:02: Allocating resources
[ 1724.639790] pcieport 0000:00:02.2: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000 add_align 100000
[ 1724.639800] pci_bus 0000:03: Allocating resources
[ 1724.639818] pcieport 0000:00:02.1: bridge window [mem 0x430200000-0x4303fffff 64bit pref]: assigned
[ 1724.639823] pcieport 0000:00:02.2: bridge window [mem 0x430400000-0x4305fffff 64bit pref]: assigned
[ 1724.639832] pcieport 0000:00:02.1: bridge window [io  0x4000-0x4fff]: assigned
[ 1724.640081] pci_bus 0000:04: Allocating resources
[ 1724.640218] done.
[ 1724.640242] random: crng reseeded on system resumption
[ 1724.642680] PM: suspend exit
[ 1724.645235] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822
[ 1724.646861] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 1724.646871] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 1724.646960] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[ 1724.646985] Bluetooth: hci0: RTL: cfg_sz 6, total sz 37346
[ 1724.692451] Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
[ 1724.844497] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1724.972239] Bluetooth: hci0: RTL: fw version 0xaed66dcb
[ 1725.073443] Bluetooth: MGMT ver 1.23
[ 1729.587480] wlp3s0: authenticate with ac:2a:a1:a5:f4:8c (local address=f8:89:d2:59:ff:83)
[ 1729.647555] wlp3s0: send auth to ac:2a:a1:a5:f4:8c (try 1/3)
[ 1729.650936] wlp3s0: authenticated
[ 1729.651402] wlp3s0: associate with ac:2a:a1:a5:f4:8c (try 1/3)
[ 1729.674019] wlp3s0: RX AssocResp from ac:2a:a1:a5:f4:8c (capab=0x1101 status=0 aid=5)
[ 1729.674466] wlp3s0: associated
[ 1729.744202] wlp3s0: Limiting TX power to 13 dBm as advertised by ac:2a:a1:a5:f4:8c

I recently purchased a Coolgear USB-32COM-RM 32 Port RS-232 USB-to-Serial Adapter connected to a Thinkpad T490s running Mint 21.3. Some lsusb output:

# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f2:b681 Chicony Electronics Co., Ltd ThinkPad T490 Webcam
Bus 001 Device 118: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 117: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 116: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 115: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 114: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 113: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 109: ID 2109:8887 VIA Labs, Inc. 40AN
Bus 001 Device 108: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
Bus 001 Device 112: ID 17ef:3083 Lenovo ThinkPad Thunderbolt 3 Dock USB Audio
Bus 001 Device 110: ID 17ef:3081 Lenovo USB2.0 HUB
Bus 001 Device 107: ID 17ef:3080 Lenovo USB2.0 Hub             
Bus 001 Device 106: ID 17ef:3080 Lenovo USB2.0 Hub             
Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 2: Dev 106, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 1: Dev 107, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 110, If 0, Class=Hub, Driver=hub/2p, 480M
                |__ Port 2: Dev 112, If 2, Class=Audio, Driver=snd-usb-audio, 12M
                |__ Port 2: Dev 112, If 0, Class=Audio, Driver=snd-usb-audio, 12M
                |__ Port 2: Dev 112, If 3, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 2: Dev 112, If 1, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 4: Dev 108, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 5: Dev 109, If 0, Class=, Driver=, 480M
    |__ Port 4: Dev 113, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 114, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 3: Dev 117, If 2, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 3: Dev 117, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 3: Dev 117, If 3, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 3: Dev 117, If 1, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 1: Dev 115, If 3, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 1: Dev 115, If 1, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 1: Dev 115, If 2, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 1: Dev 115, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 4: Dev 118, If 3, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 4: Dev 118, If 1, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 4: Dev 118, If 2, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 4: Dev 118, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 2: Dev 116, If 2, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 2: Dev 116, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 2: Dev 116, If 3, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 2: Dev 116, If 1, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
    |__ Port 8: Dev 2, If 3, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 2, If 2, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

Even though this is a 32-port device, I only see 16 /dev/ttyUSB devices:

# ls -ld /dev/ttyUSB*
crw-rw---- 1 root dialout 188,  0 Dec 12 23:02 /dev/ttyUSB0
crw-rw---- 1 root dialout 188,  1 Dec 12 23:02 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 10 Dec 12 23:02 /dev/ttyUSB10
crw-rw---- 1 root dialout 188, 11 Dec 12 23:02 /dev/ttyUSB11
crw-rw---- 1 root dialout 188, 12 Dec 12 23:02 /dev/ttyUSB12
crw-rw---- 1 root dialout 188, 13 Dec 12 23:02 /dev/ttyUSB13
crw-rw---- 1 root dialout 188, 14 Dec 12 23:02 /dev/ttyUSB14
crw-rw---- 1 root dialout 188, 15 Dec 12 23:02 /dev/ttyUSB15
crw-rw---- 1 root dialout 188,  2 Dec 12 23:02 /dev/ttyUSB2
crw-rw---- 1 root dialout 188,  3 Dec 12 23:02 /dev/ttyUSB3
crw-rw---- 1 root dialout 188,  4 Dec 12 23:02 /dev/ttyUSB4
crw-rw---- 1 root dialout 188,  5 Dec 12 23:02 /dev/ttyUSB5
crw-rw---- 1 root dialout 188,  6 Dec 12 23:02 /dev/ttyUSB6
crw-rw---- 1 root dialout 188,  7 Dec 12 23:02 /dev/ttyUSB7
crw-rw---- 1 root dialout 188,  8 Dec 12 23:02 /dev/ttyUSB8
crw-rw---- 1 root dialout 188,  9 Dec 12 23:02 /dev/ttyUSB9

Why do I only see 16 of the 32 ports? Update: I removed the case. Looks like the bottom 16 ports are working but not the top 16. I swapped one of the cables from a lower board to the top board and the front lights appeared on the top board rather than the lower board so I might just need to replace the cable. These look like USB cables but the connectors are different. The writing on the cable is "AWM 2725 80C 30V VW-1 E237114 USB(28AWGX1P+28AWGX2C) CABLETECH TECHNOLOGY". Anyone know where I can purchase these USB cables. I reached out to Coolgear as well and am waiting to hear back.

How to programmatically get a system timestamp when a USB HID message was received? My understanding is that the USB controller should raise an interrupt flag and when the kernel processes the interrupt there should be an accessible system time. But I don't see this option in any of the USB tutorials.

I have connected an onboard hub to my microprocessor. The onboard hub is USB2514B and the microprocessor is a STM32MP1. I can specify the the connection to the onboard hub by using OHCI (Open Host Controller Interface), but then I will get the error messages. usb 1-1.4: device descriptor read/64, error -62 usb 1-1-port4: unable to enumerate USB device This means that OHCI (USB 1.1) cannot communicate with USB2514B, which requires USB 2.0 specification. But if I connect my onboard hub by using EHCI (Enhanced Host Controller Interface), which is USB 2.0. Then in Linux I will not get any errors about any device description. My lsusb looks like this: >> lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub **Question:** Does this mean that this 1d6b:0002 is the USB2514B hub, or does it mean that it's the internal USB of the processor? I'm looking for a way to confirm if I have connection to my USB2514B or if lsusb only shows my internal USB connection from the processor. NOTE: This onboard USB hub does not require any external communication interfaces such as SMDbus, I2C or other. Only plain USB connection + linux device tree configuration. &usbh_ehci{ status = "okay"; /* USER CODE BEGIN usbh_ehci */ phys = ; #address-cells = ; #size-cells = ; /* onboard HUB */ hub@1 { compatible = "usb424,2514"; reg = ; vdd-supply = ; }; /* USER CODE END usbh_ehci */ }; &usbh_ohci{ status = "disabled"; }; Useful sources: * https://wiki.st.com/stm32mpu/wiki/USB_overview * https://wiki.st.com/stm32mpu/wiki/USBH_device_tree_configuration

I'm using a Raspberry Pi4 device. We plug a USB HUB connected to 2 USB devices (a Fluigent pressure controller and a FTDI-based home made board controller). After booting, I run lsusb, it lists many devices (hubs, mouse, keyboard...). Then I plug my USB HUB. Now when I run lsusb, it only lists a single device "Linux foundation 2.0 root hub", all other devices disappeared. If I run sudo lsusb, the devices are all visible. What can lead to this? Non-root users should have access to USB enumeration. **Note:** I originally hit the problem by deploying some C++ code using library libusbp and got "libudev error -13" reported by libusbp. Then I found out that using sudo works and saw that lsusb reproduces the problem outside my progrem. Maybe this -13 error code can help.

So I am having a strange problem. Short story is, I have a Lenovo monitor P32P-30 which has a USB to Ethernet adapter, so I connect my laptop (Yoga 71i 12700h) to this monitor via thunderbolt port, my laptop does NOT list the wired network in lsusb, as if it does not exist. Long story: 1. I had it working with Deepin 20.9 with kernel 6.1.x (don't remember exact number). It just worked, nothing special. 2. What happened was, I installed the new deepin release, it comes with 2 kernels, 6.6.x and 6.9.x, I tried both, same result, see below. 3. All other ports on the monitor works. It has USB ports, I conntected a USB externet HDD on the monitor, Canon printer etc, they all showed up in lsusb except the realtek ethernet port. 4. Removed all devices connected to the USB on the monitor, still doesn't work. Tried to replug in, unplug and replug 1 million times, same result. 5. Tried dmesg -w then plug it in, no error message 5 using xhci_hcd 6. To rule out the adapter itself, plugged the monitor to a Macbook pro, the realtek ethernet adapter showed up and connected to internet instantly. 7. Installed deepin v23 with kernel 6.9.x on a Beelink SER7 mini box, and the adapter showed up immedidately and connected instantly. 8. Reinstalled Deepin 23 on this Yoga 7i 12700H again, still doesn't show up, as if it did not exist. So what could be the issue? Thanks Update: seems the problem is Deepin's support of thunderbolt 4. Added kernel param pcie_ports=compat, now ip a displays the adapter, but state is DOWN. Seems thundbolt is not working: Here is lspci -v:

2e:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) (prog-if 00 [Normal decode])
        Subsystem: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020]
        !!! Unknown header type 7f
        I/O behind bridge: 00005000-00008fff [size=16K] [32-bit]
        Memory behind bridge: 52000000-5e1fffff [size=194M] [32-bit]
        Prefetchable memory behind bridge: 0000006130000000-000000614bffffff [size=448M] [64-bit]

2f:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) (prog-if 00 [Normal decode])
        Subsystem: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020]
        !!! Unknown header type 7f

2f:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) (prog-if 00 [Normal decode])
        Subsystem: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020]
        !!! Unknown header type 7f
        I/O behind bridge: 00005000-00005fff [size=4K] [32-bit]
        Memory behind bridge: 52000000-55efffff [size=63M] [32-bit]
        Prefetchable memory behind bridge: 0000006130000000-00000061394fffff [size=149M] [64-bit]

2f:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) (prog-if 00 [Normal decode])
        Subsystem: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020]
        !!! Unknown header type 7f
        I/O behind bridge: 00006000-00006fff [size=4K] [32-bit]
        Memory behind bridge: 55f00000-59dfffff [size=63M] [32-bit]
        Prefetchable memory behind bridge: 0000006139500000-00000061429fffff [size=149M] [64-bit]

2f:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) (prog-if 00 [Normal decode])
        Subsystem: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020]
        !!! Unknown header type 7f
        I/O behind bridge: 00007000-00007fff [size=4K] [32-bit]
        Memory behind bridge: 59e00000-5dcfffff [size=63M] [32-bit]
        Prefetchable memory behind bridge: 0000006142a00000-000000614befffff [size=149M] [64-bit]

2f:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) (prog-if 00 [Normal decode])
        Subsystem: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020]
        !!! Unknown header type 7f
        Memory behind bridge: 5dd00000-5dffffff [size=3M] [32-bit]

56:00.0 Ethernet controller: Intel Corporation Ethernet Controller (2) I225-LMvP (rev 03)
        Subsystem: Lenovo Ethernet Controller (2) I225-LMvP
        !!! Unknown header type 7f
        Memory at 5dd00000 (32-bit, non-prefetchable) [size=1M]
        Memory at 5df00000 (32-bit, non-prefetchable) [size=16K]
        Expansion ROM at 5de00000 [disabled] [size=1M]
        Kernel driver in use: igc
        Kernel modules: igc

So how fix that?

I have a brand new framework 16 laptop and was wandering if i could route a certain usb controller to a VM for use with a music software only available under Windows (So a Linux host system and a Windows VM is the setup i want, no dual-boot), I checked with

to see if there where more than 1 usb controllers and I got this output :

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/5p, 480M
    |__ Port 001: Dev 002, If 0, Class=Billboard, Driver=[none], 12M
    |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 002: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 006, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 006, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 006, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 004: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 008, If 0, Class=Vendor Specific Class, Driver=[none], 12M
        |__ Port 002: Dev 009, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 009, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 009, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 009, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 005: Dev 007, If 0, Class=Wireless, Driver=btusb, 480M
    |__ Port 005: Dev 007, If 1, Class=Wireless, Driver=btusb, 480M
    |__ Port 005: Dev 007, If 2, Class=Wireless, Driver=[none], 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/3p, 10000M
        |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M

I checked with a usb stick every port and it appears only on bus 1 and 2, not the others. I admit I don't have that much knowledge on how Linux deal with usb but I want to know if those usb controllers can be accessed and if so, can be pass-through to a VM PS : I'm using EndeavorOS Galileo-Neo with GNOME.

If I find a serial number in /var/log/dmesg e.g SerialNumber: xxxxxxxxxxxxxx. How can I find the device and the path to this device? Do I need to enable the kernel module usb-storage? What will that do for me and how do I make it persistent? I've tried to use lsusb but the storage device doesn't seem to appear. I can however see it in dmesg without any errors. I need to find the USB storage device and make a file system on it.

I have several Lenovo machines with varying numbers of physical USB ports. I need to programmatically identify the number of physical USB ports on each machine. The operating system installed is Linux. These USB ports may be either empty or connected to USB devices. Even a suggestion of an approach to take to resolve this would be really helpful.

I want to find out what gnome-disk is doing, how to do the same on the command line and how to undo whatever gnome-disk does. (It can not undo all it does itself.) I have already experimented a little and found out the following: the USB memory thumb drive ("stick") I played with has at least 3 "state levels" to toggle, 2 of them can be switched with gnome-drive's buttons "eject" (on and off) and "power off" (only off). From highest level to lowest, I discovered: 1. eject * gnome-drive's eject button * drive does not disappear, neither from gnome-drive, nor elsewhere * command line: eject /dev/sdb * can not be undone with gnome-drive * undo with: eject --trayclose /dev/sdb * kernel messages (journalctl -k) * eject * sdb: detected capacity change from 30253056 to 0 * uneject * sd 4:0:0:0: [sdb] 30253056 512-byte logical blocks: (15.5 GB/14.4 GiB) * sdb: detected capacity change from 0 to 30253056 * sdb: [partition details of my drive] 2. (un)bind * did not find equivalent in gnome-drive * command line: echo 3-6 > /sys/bus/usb/drivers/usb/unbind * device disappears in gnome-drive entirely * no kernel messages * lsusb -t still sees the device, but does not show class ("Mass Storage") or driver ("usb-storage") any more * /sys/bus/usb/drivers/usb/3-6 directory gone * undo with echo 3-6 > /sys/bus/usb/drivers/usb/bind * this provokes kernel messages * usb-storage 3-6:1.0: USB Mass Storage device detected * scsi host4: usb-storage 3-6:1.0 * scsi 4:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 6 * sd 4:0:0:0: Attached scsi generic sg2 type 0 * sd 4:0:0:0: [sdb] 30253056 512-byte logical blocks: (15.5 GB/14.4 GiB) * sd 4:0:0:0: [sdb] Write Protect is off * sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 00 * sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA * sdb: [partition details of my drive...] * sd 4:0:0:0: [sdb] Attached SCSI removable disk 3. power off * gnome-drive's power off button * device disappears on everything, like physically unplugged * indistinguishable from real unplugging * kernel message: * usb 3-6: USB disconnect, device number 10 * **How to power off via the command line?** * **How to power back on without real re-plugging?** --- For completeness: re-plugging the stick assigns a new device number (11), bus and port stay the same (3-6) and these kernel messages are show: usb 3-6: new high-speed USB device number 11 using xhci_hcd usb 3-6: New USB device found, idVendor=0930, idProduct=6545, bcdDevi> usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-6: Product: TransMemory usb 3-6: Manufacturer: TOSHIBA usb 3-6: SerialNumber: C03FD5F7713EE2B1B000821E [plus all kernel messages as quoted under (re-)bind above]

I have this USB Drive that i'm trying to fix,. When I plug it, dmesg shows the following : [83630.997986] usb 1-10: new high-speed USB device number 12 using xhci_hcd [83631.146553] usb 1-10: New USB device found, idVendor=ffff, idProduct=1201, bcdDevice= 0.00 [83631.146557] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [83631.147917] usb-storage 1-10:1.0: USB Mass Storage device detected [83631.148272] scsi host4: usb-storage 1-10:1.0 [83632.166402] scsi 4:0:0:0: Direct-Access NAND USB2DISK 0.00 PQ: 0 ANSI: 4 [83632.166579] sd 4:0:0:0: Attached scsi generic sg1 type 0 [83632.210532] sd 4:0:0:0: [sdb] Attached SCSI removable disk and a sudo lsusb give that (Bus 001 Device 012 is the USB Drive) : Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b0e:0312 GN Netcom Jabra EVOLVE 30 II Bus 001 Device 011: ID 04f2:0112 Chicony Electronics Co., Ltd KU-8933 Keyboard with PS/2 Mouse port Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 008: ID 8087:0026 Intel Corp. Bus 001 Device 006: ID 413c:4503 Dell Computer Corp. Dell Universal Receiver Bus 001 Device 012: ID ffff:1201 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub This is the result of a lsblk :

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0         7:0    0     4K  1 loop /snap/bare/5
loop1         7:1    0 142,2M  1 loop /snap/chromium/2082
loop2         7:2    0 255,6M  1 loop /snap/gnome-3-34-1804/36
loop3         7:3    0    47M  1 loop /snap/snapd/16292
loop4         7:4    0    48M  1 loop /snap/snapd/16778
loop5         7:5    0 346,3M  1 loop /snap/gnome-3-38-2004/115
loop6         7:6    0  63,2M  1 loop /snap/core20/1623
loop7         7:7    0  45,9M  1 loop /snap/snap-store/592
loop8         7:8    0  55,6M  1 loop /snap/core18/2560
loop9         7:9    0  91,7M  1 loop /snap/gtk-common-themes/1535
loop10        7:10   0 400,8M  1 loop /snap/gnome-3-38-2004/112
loop11        7:11   0  81,3M  1 loop /snap/gtk-common-themes/1534
loop12        7:12   0   219M  1 loop /snap/gnome-3-34-1804/77
loop14        7:14   0    62M  1 loop /snap/core20/1611
loop15        7:15   0  54,2M  1 loop /snap/snap-store/558
loop16        7:16   0 142,2M  1 loop /snap/chromium/2076
loop17        7:17   0  55,6M  1 loop /snap/core18/2566
sda           8:0    0   2,7T  0 disk 
└─sda1        8:1    0   2,7T  0 part 
nvme0n1     259:0    0   477G  0 disk 
├─nvme0n1p1 259:2    0   512M  0 part /boot/efi
└─nvme0n1p2 259:3    0 476,4G  0 part /
nvme1n1     259:1    0   477G  0 disk 
└─nvme1n1p1 259:4    0   477G  0 part

Does this mean that the Drive is dead and I shouldn't expect any recovery on the data that was stocked in it ? Or is there any way to make it happens ? Thanks in advance

I've bought this Lenovo laptop https://www.lenovo.com/gb/en/p/laptops/legion-laptops/legion-slim-series-laptops/lenovo-legion-slim-7-gen-8-(16-inch-amd)/len101g0029#tech_specs that is supposed to support USB 4.0. However the lsusb -t return this output:

$ lsusb -t
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/5p, 480M
    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
    |__ Port 3: Dev 3, If 2, Class=Application Specific Interface, Driver=, 480M
    |__ Port 3: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 3: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 4: Dev 4, If 1, Class=Wireless, Driver=btusb, 480M
    |__ Port 4: Dev 4, If 2, Class=Wireless, Driver=, 480M
    |__ Port 4: Dev 4, If 0, Class=Wireless, Driver=btusb, 480M
    |__ Port 5: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M

I can't see any speed rate more than 10000M. In my other laptop with Thunderbolt 4, I can see 20000M. I use PopOS

$ uname -a
Linux pop-os 6.5.4-76060504-generic

The Linux kernel 6.5.4 should detect the USB4 isn't it? Did I miss something? Did Lenovo install wrong hardware ports on my laptop? Should I return this laptop?

I'm trying to power on/off an USB drive using bind/unbind command following this post , can someone please point me to the right direction where to find tutorial/explanation on bind/unbind usb drive (found some posts but very old and commands are deprecated and I'm not that knowledgeable about linux to understand everything in man)? what I can't figure out is how to find the bus-port number in this sample echo command
echo '1-2.2:1.0' > /sys/bus/usb/drivers/r8712u/bind # switch on in my case, I think I have to change the driver to usb-storage, so the command would be echo '?-?.?:?.?' > /sys/bus/usb/drivers/usb-storage/bind # switch on which command should I use to find the bus-port?

I have a motherboard with [Intel H97 chipset](https://www.intel.com/content/www/us/en/products/sku/82010/intel-h97-chipset/specifications.html) . The chipset supports maximum of eight USB 2.0 ports and maximum of six USB 3.0 ports. According to motherboard manual, it has two USB 2.0 ports and four USB 3.0 ports on the I/O panel and rest of the USB ports are available via connectors on the motherboard. Now regardless if I connect the USB devices to USB 2.0 or 3.0 ports on the rear I/O panel or to USB headers on the motherboard, then the devices always appear under root hub of bus #2. Example where Mass Storage type of device is connected to one of the USB ports on the motherboard I/O panel:

# lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
    |__ Port 1: Dev 18, If 0, Class=Communications, Driver=cdc_ether, 480M
    |__ Port 1: Dev 18, If 1, Class=CDC Data, Driver=cdc_ether, 480M
    |__ Port 1: Dev 18, If 2, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 12: Dev 27, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
#

However, what are the buses #1, #3 and #4? For bus #4 there seems to be a single Linux Foundation 3.0 root hub type of device connected:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

For buses #3 and #1 there seems to be a 8-port(8p in the output of lsusb -t) Intel USB 2.0 hub(8087:8001) and 6-port Intel USB 3.0(8087:8009) hub connected:

Bus 003 Device 002: ID 8087:8001 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I don't know if this is a coincidence, but the number of ports in Intel hub in bus #3 and in Intel hub in bus #1 add up to 14. This aligns with the chipset documentation and with the number of ports seen in the output of lsusb -t for bus #2.

I am trying to connect a MicroSemi FlashPro 4 to my Linux system. When I plug it in, dmesg shows: [13728.408610] usb 11-1: New USB device found, idVendor=1514, idProduct=2006, bcdDevice= 0.00 [13728.408617] usb 11-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 The device/programmer doesn't turn on. But lsusb adds this when it's plugged in: Bus 011 Device 016: ID 1514:2006 Actel I looked up the idVendor and idProduct and they match MicroSemi (formerly known as Actel) and my device. However I don't understand why the second line of dmesg gives values of 0 for fields that it apparently just read the line before. What actually is going on behind the scenes between the two output lines? And do values of 0 mean it didn't find a driver?

I have a 500GB WD My Passport Hard Drive And it doesn't show up on my computer, Which is running arch linux. i've tried searching for solutions, however most of them are only if the drive dosen't show up in lsusb. My drive shows up in lsusb but nowhere else. here is the output of some commands: lsusb:

Bus 002 Device 011: ID 1058:0730 Western Digital Technologies, Inc. My Passport Essential (WDBACY) #My Drive
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 0408:2010 Quanta Computer, Inc. Chromebook HD Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ls /dev:

acpi_thermal_rel  disk/        gpiochip2     mem           net/    rtc0      tty11  tty22  tty33  tty44  tty55  tty9    ttyS19  ttyS3    urandom      vcsa1  vcsu6
autofs            dma_heap/    gpiochip3     mmcblk1       null    shm/      tty12  tty23  tty34  tty45  tty56  ttyS0   ttyS2   ttyS30   userfaultfd  vcsa2  vfio/
block/            dri/         hpet          mmcblk1boot0  nvram   snapshot  tty13  tty24  tty35  tty46  tty57  ttyS1   ttyS20  ttyS31   userio       vcsa3  vga_arbiter
btrfs-control     drm_dp_aux0  hugepages/    mmcblk1boot1  port    snd/      tty14  tty25  tty36  tty47  tty58  ttyS10  ttyS21  ttyS4    v4l/         vcsa4  vhci
bus/              drm_dp_aux1  hwrng         mmcblk1p1     ppp     stderr@   tty15  tty26  tty37  tty48  tty59  ttyS11  ttyS22  ttyS5    vcs          vcsa5  vhost-net
char/             drm_dp_aux2  input/        mmcblk1p2     psaux   stdin@    tty16  tty27  tty38  tty49  tty6   ttyS12  ttyS23  ttyS6    vcs1         vcsa6  vhost-vsock
console           fb0          kmsg          mmcblk1rpmb   ptmx    stdout@   tty17  tty28  tty39  tty5   tty60  ttyS13  ttyS24  ttyS7    vcs2         vcsu   video0
core@             fd@          kvm           mqueue/       ptp0    tpm0      tty18  tty29  tty4   tty50  tty61  ttyS14  ttyS25  ttyS8    vcs3         vcsu1  video1
cpu/              full         log@          mtd0          pts/    tty       tty19  tty3   tty40  tty51  tty62  ttyS15  ttyS26  ttyS9    vcs4         vcsu2  watchdog
cpu_dma_latency   fuse         loop-control  mtd0ro        random  tty0      tty2   tty30  tty41  tty52  tty63  ttyS16  ttyS27  udmabuf  vcs5         vcsu3  watchdog0
cros_ec           gpiochip0    mapper/       mtd1          rfkill  tty1      tty20  tty31  tty42  tty53  tty7   ttyS17  ttyS28  uhid     vcs6         vcsu4  zero
cuse              gpiochip1    media0        mtd1ro        rtc@    tty10     tty21  tty32  tty43  tty54  tty8   ttyS18  ttyS29  uinput   vcsa         vcsu5  zram0

I've tried different ports and cables but nothing works ------------------- **Edit 1** Output of lsusb -t and dmesg as requested by @JaromandaX lsusb -t:

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 2: Dev 12, If 0, Class=Mass Storage, Driver=, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
    |__ Port 4: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 4: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 5: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 5: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

dmesg:

[14304.192151] usb 2-2: new SuperSpeed USB device number 12 using xhci_hcd
[14304.208994] usb 2-2: LPM exit latency is zeroed, disabling LPM.
[14304.209819] usb 2-2: New USB device found, idVendor=1058, idProduct=0730, bcdDevice=10.12
[14304.209853] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[14304.209870] usb 2-2: Product: My Passport 0730
[14304.209885] usb 2-2: Manufacturer: Western Digital
[14304.209897] usb 2-2: SerialNumber: 57584A314142303832313830