From Gentoo Wiki
< USB(Redirected from USB/HOWTO)
Jump to: navigation, search
The information in this article is probably outdated as of May 15th, 2015. You can help the Gentoo Wiki by verifying and updating this article.
This article has some todo items:
  • Update article with informations about USB 3.0.

This USB guide helps users setup and configure various USB devices on Gentoo systems.


What is USB?

USB stands for Universal Serial Bus which is an external interface standard that enables communication between computers and various peripherals. Some of the most commonly used USB devices are keyboards, mice, pen drives, digital cameras, external CD and DVD writers, printers, MP3 players, smart phones, and biometric devices.

There are currently three versions of USB in use, USB 2.0, USB 3.0, and USB 3.1. Since USB has always been backward compatible with previous versions, USB 2.0 is backwards compatible with USB 1.1. Likewise USB 3.0 and 3.1 can work with versions 2.0 and 1.1. The latest USB devices are typically USB 3.0 compatible, although some motherboards still include USB 2.0. USB 2.0 supports a maximum data transmission speed of 480 Mbit/s or 60 MB/s, 3.0 can transfer at a rate of 5.0 Gbit/s or 625 MB/s[1], and 3.1 tops out at a whopping 10.0 Gbit/s or 1.25 GB/s. Another advantage with USB is that the devices are all hot-pluggable, which means the system does not need a restart in order for the devices that have been plugged in to work.

A technical perspective

Before the exact configuration options in the kernel, it would be apt to look at USB in a little more detail. For readers in a hurry or want to skip this section, please go to the kernel configuration section.

A USB system has a host controller, hubs, a root hub amongst others and can support up to 127 USB devices including the hubs. The host controller is nothing but the hardware interface between the USB device and the operating system. There are a couple of HCIs (Host Controller Interfaces) in use today. They are the OHCI (Open HCI) by Compaq, UHCI (Universal HCI) and EHCI (Enhanced HCI) which are both from Intel, and xHCI (eXtensible Host Controller Interface). The OHCI/UHCI are the two industry standard USB 1.1 interfaces whereas EHCI is for USB 2.0 and xHCI is compatible with all of the previously mentioned interfaces including USB 3.0.[2]

The hardware vendor provides an interface for the programmer that allows the system to interact with the hardware and this is called the HCD or Host Controller Device. It is through this HCD that the device interacts with the system software. The following diagram should make things easier to comprehend.

# Software consists of other components as well like the device driver, but for the sake of simplicity, they are not shown
    + ----  Hardware  ----   + ----  Software  ---- +
    |                        |                      |
    | [USB Dev] -+-> {EHCI} -+--->  ( EHCD )        |
    |            |           |                      |  User
    |            `-> {UHCI} -+--->  ( UHCD )        |
    |                        |                      |
    + ----  Hardware  ----   + ----  Software  ---- +

A USB device can either use a custom driver or use one already present in the system and this is based on the concept of a device class. This means that if a device belongs to a certain class, then other devices belonging to the same class can make use of the same device driver. Some of these classes are the USB HID (Human Interface Devices) class which covers input devices like keyboards and mice, the USB Mass Storage devices class which covers devices like pen drives, digital cameras, audio players etc and the USB CDC (Communication Devices Class) which essentially covers USB modems and similar devices.

What is on the machine?

It is very simple to find out whether the machine in question has USB support. The lspci command (comes with the sys-apps/pciutils package) is perfect for this purpose.

Example for a USB 1.1 compliant system (note the UHCI in the output):

user $/usr/sbin/lspci -v | grep USB
0000:00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])

A system that is USB 2.0 compliant, note the EHCI and UHCI:

user $/usr/sbin/lspci -v | grep USB
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01) (prog-if 00 [UHCI])
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01) (prog-if 00 [UHCI])
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01) (prog-if 00 [UHCI])
00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 01) (prog-if 20 [EHCI])

So using the lspci command it is easy to determine if the system supports USB 2.0, or 3.0. This is useful for the section to come so that corresponding options can be correctly set in the kernel.

Kernel configuration

Getting the kernel

First emerge the kernel sources of your choice. Here we'll use sys-kernel/gentoo-sources. For more information on the various kernel sources available on Portage, please look up the Gentoo Linux Kernel Guide.

root #emerge --ask gentoo-sources

Now, lets get on with the task of configuring the kernel.

root #cd /usr/src/linux
root #make menuconfig
The above example assumes that /usr/src/linux symlink points to the kernel sources you want to use. Please ensure the same before proceeding.

Config options for the kernel

Now we will look at some of the options we will have to enable in the kernel to ensure proper USB support for our devices.

Examples in this document will show configuration options for basic USB support as well as those needed commonly, for example a USB mass storage device (most cameras and USB pen drives). If you have a specific USB device that needs to be configured, please look up your device's manual or search online to see if that device has support built-in into the kernel or custom drivers that you can use. Please note that for the sake of ease, all examples have the options compiled into the kernel. If you would like to have a modular kernel, ensure that you note down the various modules and adjust your config files accordingly.
KERNEL make menuconfig options
Device Drivers  --->
  SCSI device support  --->
## (Although SCSI will be enabled automatically when selecting USB Mass Storage,
we need to enable disk support.)
---   SCSI support type (disk, tape, CD-ROM)
<*>   SCSI disk support
## (Then move back a level and go into USB support)
USB support  --->
## (This is the root hub and is required for USB support.
If you'd like to compile this as a module, it will be called usbcore.)
<*> Support for Host-side USB
## (Select at least one of the HCDs. If you are unsure, picking all is fine.)
--- USB Host Controller Drivers
<*> EHCI HCD (USB 2.0) support
< > OHCI HCD support
<*> UHCI HCD (most Intel and VIA) support
## (Moving a little further down, we come to CDC and mass storage.)
< > USB Modem (CDC ACM) support
<*> USB Printer support
<*> USB Mass Storage support
## (If you have a USB Network Card like the RTL8150, you'll need this)
USB Network Adapters  --->
    <*> USB RTL8150 based ethernet device support (EXPERIMENTAL)
## (If you have a serial to USB converter like the Prolific 2303, you'll need this)
USB Serial Converter support  --->
    <*> USB Serial Converter support
    <*> USB Prolific 2303 Single Port Serial Driver (NEW)

If you have a USB keyboard, mouse, joystick, or any other input device, you need to enable HID support. Go back one level to "Device drivers" and enable HID support as shown:

KERNEL Enabling HID support
Device Drivers --->
  [*] HID Devices  --->
    <*>   USB Human Interface Device (full HID) support

Now that your options are set, you can (re)compile the kernel and USB support should be functional once you reboot into the new kernel.

Seeing USB at work

dmesg is a friend!

In this section, we'll see how the system responds to various USB devices. We'll start by plugging in a 512 MB removable USB drive. Any similar mass storage device can be used for this test. For this experiment dmesg will be the primary utility used to see what is happening and how the system responds to plugged devices.

dmesg will generally give a lot of output up front before coming to the relevant info, as it reads the kernel ring buffer that has all the boot up messages as well. The output in the following examples have only the relevant portion(s) and extra spaces in between to enable better readability. If needed please use dmesg | more or dmesg | less to see the output better in your system.

Plug in USB drive into available USB port and then...

root #dmesg | less
## (The device is picked up as a USB 1.1 and allocated an address. Also says what HCD it is using.)
usb 1-1: new full speed USB device using uhci_hcd and address 2
## (SCSI emulation automatically kicks in)
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
## (Now the device information including model number is retrieved)
usb-storage: waiting for device to settle before scanning
  Vendor: JetFlash  Model: TS512MJF2A        Rev: 1.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
SCSI device sdb: 1003600 512-byte hdwr sectors (514 MB)
## (The write-protect sense is EXPERIMENTAL code in the later kernels)
sdb: Write Protect is off
sdb: Mode Sense: 0b 00 00 08
sdb: assuming drive cache: write through
SCSI device sdb: 1003600 512-byte hdwr sectors (514 MB)
/dev/scsi/host0/bus0/target0/lun0: p1
Attached scsi removable disk sdb at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
usb-storage: device scan complete
## (At this point, the device is generally accessible by mounting /dev/sdb1)
## (When the device is disconnected, the system acknowledges the same)
usb 1-1: USB disconnect, address 2

How would a USB mouse show up in case you had one? It will show up as an HID device.

root #dmesg | grep USB
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usb 1-1: new low speed USB device using address 2
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:07.2-1

Mounting a USB mass storage device

See the removable media article.

Once the device is connected and mounted, you can access it like a normal hard disk. Usual operations like cp, mv, rm, etc work fine. You could also create a filesystem on the USB stick/format it.

Digital cameras can be accessed the same way as USB flash drives. Cameras these days usually have two modes to transfer pictures; USB mass storage and PTP (Picture Transfer Protocol). When the camera is set to USB mass storage mode the procedure is exactly the same as that of accessing a USB flash drive. Please note that this may NOT work in all cases and with all digital cameras that have USB support.

Userspace USB

Another nifty command you can use to see the status of your USB ports is lsusb. This is part of sys-apps/usbutils and is also covered in the next chapter.

Nifty tools

So far we've seen how much support exists on the kernel and system side for USB on Linux. Now take a peek into what kind of support is provided by Gentoo for USB in the userspace.

One of the most useful tools around is lsusb. This lists all the USB devices connected to the system. Installing it is a breeze:

root #emerge --ask sys-apps/usbutils

Once installed, run lsusb to get simple info on the USB devices attached to the machine.

user $lsusb
## (This is the 512 MB USB flash drive from Transcend)
Bus 001 Device 003: ID 0c76:0005 JMTek, LLC. USBdisk
## (This is the Optical Mouse)
Bus 001 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse
## (This is the root hub)
Bus 001 Device 001: ID 0000:0000

For those who love to see lots of information run lsusb with the -v option. Another good option is that lsusb dumps the current physical USB hierarchy as a tree and thus makes it easier to understand the exact device map. The command is lsusb -t. For example:

user $lsusb -t
Bus#  1
`-Dev#   1 Vendor 0x0000 Product 0x0000
  |-Dev#   2 Vendor 0x046d Product 0xc00e
  `-Dev#   3 Vendor 0x0c76 Product 0x0005

You can easily correlate the outputs of lsusb and lsusb -t, which helps debugging as well as understanding how USB works.

See also

External resources

The following documents are highly technical but truly interesting:


This article is based on a document formerly found on our main website
The following people have contributed to the original document: Shyam Mani
They are listed here as the Wiki history does not provide for any attribution. If you edit the Wiki article, please do not add yourself here; your contributions are recorded on the history page.