#Lsusb device id tty how to
#Lsusb device id tty driver
#Lsusb device id tty iso

#Lsusb device id tty iso

To do this, we can run: $ dmesg | tail sd 7: 0: 0: 0: Attached scsi generic sg3 type 0 sd 7: 0: 0: 0: 15806464 512-byte logical blocks: ( 8.09 GB / 7.54 GiB) sd 7: 0: 0: 0: Write Protect is off sd 7: 0: 0: 0: Mode Sense: 00 00 00 00 sd 7: 0: 0: 0: Asking for cache data failed sd 7: 0: 0: 0: Assuming drive cache: write through sdc: sdc1 sdc2 sd 7 : 0: 0: 0: Attached SCSI removable disk ISO 9660 Extensions: Microsoft Joliet Level Extensions: RRIP_1991A To carry out this task we will need to know which device we are going to reconnect. If we want to venture, we can also enter / sys / bus / usb and look at everything there is, we will see a lot of information, but fortunately the above commands classify all this information. $ udevadm info -query = path -name = / dev / sdX -attribute-walk

#Lsusb device id tty driver

For example, if we connect a USB hard drive, for us to be able to see how the device is used, we need a SCSI driver (for being / dev / sdX), we also need a USB storage driver, which works through the USB port, which belongs to a hub, which is plugged into a PCI port, among other intermediate systems. Other very useful commands are usb devices, hwinfo, or, for example, if we have the path of a device (inside / dev /), we can ask the system for all possible information about it and the subsystems it has to go through.

4GB Pen Drive MaxPower 480mA Bus 001 Device 003: ID 04f2: b424 Chicony Electronics Co., Ltd MaxPower 500mA Bus 001 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub MaxPower 0mA Hub MaxPower 100mA Bus 001 Device 010: ID 125f: c93a A-DATA Technology Co., Ltd. Unifying Receiver MaxPower 98mA Bus 001 Device 005: ID 1a40: 0101 Terminus Technology Inc. MaxPower 100mA Bus 001 Device 007: ID 046d: c52b Logitech, Inc. If we want much more information, we can use lsusb -v (the output is very large), we could also, for example, know the maximum power that is delivered to the device, in the following way: $ lsusb -v 2> / dev / null | egrep '^ Bus | MaxPower' Bus 002 Device 001: ID 1d6b: 0003 Linux Foundation 3.0 root hub MaxPower 0mA Bus 001 Device 006: ID 8087: 0a2a Intel Corp. If we want more information, we can use the -t modifier that will show us an output in the form of a tree with information about the modules: $ lsusb -t /: Bus 02.Port 1: Dev 1, Class = root_hub, Driver = xhci_hcd / 8p, 5000M /: Bus 01.Port 1: Dev 1, Class = root_hub, Driver = xhci_hcd / 16p, 480M | _ Port 4: Dev 3, If 0, Class = Video, Driver = uvcvideo, 480M | _ Port 4: Dev 3, If 1, Class = Video, Driver = uvcvideo, 480M | _ Port 5: Dev 10, If 0, Class = Mass Storage, Driver = usb-storage, 480M | _ Port 6: Dev 5, If 0, Class = Hub, Driver = hub / 4p, 12M | _ Port 4: Dev 7, If 0, Class = Human Interface Device, Driver = usbhid, 12M | _ Port 4: Dev 7, If 1, Class = Human Interface Device, Driver = usbhid, 12M | _ Port 4: Dev 7, If 2, Class = Human Interface Device, Driver = usbhid, 12M | _ Port 9: Dev 6, If 0, Class = Wireless, Driver = btusb, 12M | _ Port 9: Dev 6, If 1, Class = Wireless, Driver = btusb, 12M 4GB Pen Drive Bus 001 Device 003: ID 04f2: b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b : 0002 Linux Foundation 2.0 root hub Hub Bus 001 Device 010: ID 125f: c93a A-DATA Technology Co., Ltd. Unifying Receiver Bus 001 Device 005: ID 1a40 : 0101 Terminus Technology Inc. Bus 001 Device 007: ID 046d: c52b Logitech, Inc. $ lsusb Bus 002 Device 001: ID 1d6b: 0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087: 0a2a Intel Corp. I put examples of what I get on my computer right now, but maybe it is very different from what you get:

For this, we can use lsusb, which will list the connected devices right now.

#Lsusb device id tty how to

Hiding and showing the deviceД«efore we start, let's see how to get information about USB devices connected to the system. Your fingerprint reader has a really high device number. Over time, are those addresses counting up? 1-1.3, 1-1.4. Why would someone design a laptop where the WiFi is on an internal USB?Д®dit: You show an excerpt from your error outputs. Edit: On second thought, I don't think you can without loosing your Bluetooth. It may be possible to inhibit that controller to stop the spam.

There is something wrong on bus 1-1.ДЄre all of the internal peripherals working? There may be something built in on one that bus that is misbehaving.Дo all of your external buses work? Where do those devices map? This does not solve the problem, but it let's you see what you are doing.Д®dit: BTW, this is likely a hardware issue. Now you won't see the errors that are being logged to the primary console (console 1). The easy workaround is to switch to console 2.