Lsusb command

On Ubuntu, you may (for one reason or another) wish to view information about all USB devices connected to the system. Unfortunately, Ubuntu doesn’t come with an official GUI USB tool that users can use to view this information efficiently.Thankfully, there are many command-line utilities that users can take advantage of to view USB device information. In this guide, we’ll go over each of these tools, how they work, and how to use them.The number one way an Ubuntu user can view all connected USB devices is with the lsusb command. This command literally means “list USB,” and it does exactly that — it lists all of your USB devices, their IDs, names, etc.To get started, open up a terminal window on the Ubuntu desktop. To open up a terminal window on Ubuntu, press Ctrl + Alt + T on the keyboard. Or, search for “Terminal” in the app menu and launch it that way.With the terminal window open and ready to use, execute the lsusb command in the terminal window. Once you enter it, it will print out detailed information about the USB devices connected to the system.lsusbIn the lsusb output, you’ll see “Bus,” followed by numbers, “Device,” more numbers, “ID,” some hex code (that’s your device’s ID code), and the name of the device. To locate any USB device, find the name at the end.If you’d like to save this output to a text file for later reading, research, or easier viewing via your favorite text editor, pipe the output to a file using the > command-line modifier. lsusb > ~/my-usb-devices.txtAt any time, you can view the “my-usb-devices.txt” file in the terminal with the cat command below.cat ~/my-usb-devices.txtOr, open up the text file in your home folder using your favorite text editor.Ubuntu list USB devices – DmesgAnother way

O o /---o /---/---oo---/ \---\---o o \---o oCymeList system USB buses and devices. A modern cross-platform lsusb that attempts to maintain compatibility with, but also add new features. Profiles system USB buses and the devices on those buses, including full device descriptors.As a developer of embedded devices, I use a USB list tool on a frequent basis and developed this to cater to what I believe are the short comings of lsusb: verbose dump is mostly too verbose, tree doesn't contain useful data on the whole, it barely works on non-Linux platforms and modern terminals support features that make glancing through the data easier.The project started as a quick replacement for the barely working lsusb script and a Rust project to keep me up to date! Like most fun projects, it quickly experienced feature creep as I developed it into a cross-platform replacement for lsusb. It started as a macOS system_profiler parser, evolved to include a 'libusb' based profiler for reading full device descriptors and now defaults to a pure Rust profiler using nusb.It's not perfect as it started out as a Rust refresher but I had a lot of fun developing it and hope others will find it useful and can contribute. Reading around the lsusb source code, USB-IF and general USB information was also a good knowledge builder.The name comes from the technical term for the type of blossom on a Apple tree: cyme - it is Apple related and also looks like a USB device tree 😃🌸.FeaturesCompatible with lsusb using --lsusb argument. Supports all arguments including --verbose output - fully parsed device descriptors! Output is identical for use with no args (list), tree (excluding drivers on non-Linux) and should match for verbose (perhaps formatting differences).Default build is a native Rust profiler using nusb.Filters like lsusb but that also work when printing --tree. Adds --filter-name, --filter-serial, --filter-class and option to hide empty --hide-buses/--hide-hubs.Improved --tree mode; shows device, configurations, interfaces and endpoints as tree depending on level of --verbose.Controllable display --blocks for device, bus --bus-blocks, configurations --config-blocks, interfaces --interface-blocks and endpoints --endpoint-blocks. Use --more to see more by default.Modern terminal features with coloured output, utf-8 characters and icon look-up based device data. Can be turned off and customised. See --encoding (glyphs [default], utf8 and ascii), which can keep icons/tree within a certain encoding, --color (auto [default], always and never) and --icon (auto [default], always and never). Auto --icon will

Libusb-1.0-0-dev or one's package manager of choice.Was the default feature before 2.0.0 for gathering verbose information. It is the profiler used by lsusb but there should be no difference in output between the two, since cyme uses control messages to gather the same information. If one wishes to use 'libusb', use --no-default-features and --feature=libusb or --feature=ffi for udevlib too.Note'libusb' does not profile buses on non-Linux systems (since it relies on root_hubs). On these platforms, cyme will generate generic bus information.macOS system_profilerUses the macOS system_profiler SPUSBDataType command to profile devices.Was the default feature before 2.0.0 for macOS systems to provide the base information; 'libusb' was used to open devices for verbose information. It is not used anymore if using the default native profiler but can be forced with --system-profiler - the native profiler uses the same IOKit backend but is much faster as it is not deserializing JSON. It also always captures bus numbers where system_profiler does not.TipIf wishing to use only macOS system_profiler and not obtain more verbose information, remove default features with cargo install --no-default-features cyme. There is not much to be gained by this considering that the default native profiler uses the same IOKit as a backend, can open devices to read descriptors (verbose mode) and is much faster.UsageUse cyme --help for basic usage or man ./doc/cyme.1. There are also autocompletions in './doc'.ExamplesTree tree.json# Then import the JSON file to view the system USB tree as it was when exported. All cyme args can be used with this static import as if it was profiled data.cyme --from-json tree.json"># List all USB devices and buses in a tree format with default display blockscyme --tree# As above but with configurations toocyme --tree --verbose# And with interfaces and endpoints - each verbose level goes futher down the USB descriptor tree. Using short arg here.cyme --tree -vvv# List all USB devices and buses in a tree format with more display blocks, all verbose levels and headings to show what is being displayedcyme --tree --more --headings# Export the tree to a JSON file - --json works with all optionscyme --tree --verbose --json > tree.json# Then import the JSON file to view the system USB tree as it was when exported. All cyme args can be used with this static import as if it was profiled data.cyme --from-json tree.jsonlsusb# List all USB devices and buses like 'lsusb'cyme --lsusb# lsusb verbose device dump including all