Skip Navigation Links | |
Exit Print View | |
![]() |
System Administration Guide: Devices and File Systems Oracle Solaris 10 8/11 Information Library |
1. Managing Removable Media (Overview)
2. Managing Removable Media (Tasks)
3. Accessing Removable Media (Tasks)
4. Writing CDs and DVDs (Tasks)
5. Managing Devices (Overview/Tasks)
6. Dynamically Configuring Devices (Tasks)
7. Using USB Devices (Overview)
Managing USB Devices in the Oracle Solaris OS (Roadmap)
Using USB Mass Storage Devices (Task Map)
Using USB Mass Storage Devices
Using Non-Compliant USB Mass Storage Devices
How to Use a Non-Complaint USB Mass Storage Device
Hot-Plugging USB Mass Storage Devices
How to Add a USB Mass Storage Device Without vold Running
How to Remove a USB Mass Storage Device Without vold Running
Preparing to Use a USB Mass Storage Device With vold Running
How to Display USB Device Information
How to Create a File System on a USB Mass Storage Device
How to Create a File System on a USB Mass Storage Device Without vold Running
How to Mount or Unmount a USB Mass Storage Device Without vold Running
Troubleshooting Tips for USB Mass Storage Devices
Disabling Specific USB Drivers
How to Disable Specific USB Drivers
How to Remove Unused USB Device Links
Using USB Audio Devices (Task Map)
Hot-Plugging Multiple USB Audio Devices
How to Identify Your System's Primary Audio Device
How to Change the Primary USB Audio Device
Troubleshooting USB Audio Device Problems
Key Points of Audio Device Ownership
Hot-Plugging USB Devices With the cfgadm Command (Task Map)
Hot-Plugging USB Devices With the cfgadm Command
How to Display USB Bus Information (cfgadm)
How to Unconfigure a USB Device
How to Logically Disconnect a USB Device
How to Logically Connect a USB Device
How to Logically Disconnect a USB Device Subtree
How to Change the Default Configuration of a Multi-Configuration USB Device
9. Using InfiniBand Devices (Overview/Tasks)
11. Administering Disks (Tasks)
12. SPARC: Setting Up Disks (Tasks)
13. x86: Setting Up Disks (Tasks)
14. Configuring Oracle Solaris iSCSI Targets and Initiators (Tasks)
15. The format Utility (Reference)
16. Managing File Systems (Overview)
17. Creating and Mounting File Systems (Tasks)
18. Using The CacheFS File System (Tasks)
19. Configuring Additional Swap Space (Tasks)
20. Checking UFS File System Consistency (Tasks)
21. UFS File System (Reference)
22. Backing Up and Restoring UFS File Systems (Overview)
23. Backing Up UFS Files and File Systems (Tasks)
24. Using UFS Snapshots (Tasks)
25. Restoring UFS Files and File Systems (Tasks)
26. UFS Backup and Restore Commands (Reference)
27. Copying Files and File Systems (Tasks)
|
You can add and remove a USB device from a running system without using the cfgadm command. However, a USB device can also be logically hot-plugged without physically removing the device. This scenario is convenient when you are working remotely and you need to disable or reset a non functioning USB device. The cfgadm command also provides a way to display the USB device tree, including manufacturer and product information.
The cfgadm command displays information about attachment points, which are locations in the system where dynamic reconfiguration operations can occur. An attachment point consists of the following:
An occupant, which represents a hardware resource, such as a USB device, that might be configured into the system
A receptacle, which is the location that accepts the occupant, such as a USB port
Attachment points are represented by logical and physical attachment point IDs (Ap_Ids). The physical Ap_Id is the physical path name of the attachment point. The logical Ap_Id is a user-friendly alternative for the physical Ap_Id. For more information on Ap_Ids, see cfgadm_usb(1M).
The cfgadm command provides the following USB device status information.
|
The following sections describe how to hot-plug a USB device through the software with the cfgadm command. All of the sample USB device information in these sections has been truncated to focus on relevant information.
For examples of using the prtconf command to display USB configuration information, see How to Display USB Device Information.
For example:
% cfgadm Ap_Id Type Receptacle Occupant Condition usb0/4.5 usb-hub connected configured ok usb0/4.5.1 usb-device connected configured ok usb0/4.5.2 usb-printer connected configured ok usb0/4.5.3 usb-mouse connected configured ok usb0/4.5.4 usb-device connected configured ok usb0/4.5.5 usb-storage connected configured ok usb0/4.5.6 usb-communi connected configured ok usb0/4.5.7 unknown empty unconfigured ok
In the preceding example, usb0/4.5.1 identifies a device connected to port 1 of the second-level external hub, which is connected to port 5 of first-level external hub, which is connected to the first USB controller's root hub, port 4.
For example:
% cfgadm -l -s "cols=ap_id:info" Ap_Id Information usb0/4.5.1 Mfg: Inside Out Networks Product: Edgeport/421 NConfigs: 1 Config: 0 : ... usb0/4.5.2 Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 ... usb0/4.5.3 Mfg: Mitsumi Product: Apple USB Mouse NConfigs: 1 Config: 0 ... usb0/4.5.4 Mfg: NMB Product: NMB USB KB/PS2 M NConfigs: 1 Config: 0 usb0/4.5.5 Mfg: Hagiwara Sys-Com Product: SmartMedia R/W NConfigs: 1 Config: 0 : ... usb0/4.5.6 Mfg: 3Com Inc. Product: U.S.Robotics 56000 Voice USB Modem NConfigs: 2 ... usb0/4.5.7
You can unconfigure a USB device that is still physically connected to the system. However, a driver will never attach to the device. Note that a USB device remains in the prtconf output even after that device is unconfigured.
For example:
# cfgadm -c unconfigure usb0/4.7 Unconfigure the device: /devices/pci@8,700000/usb@5,3/hub@4:4.7 This operation will suspend activity on the USB device Continue (yes/no)? y
For example:
# cfgadm Ap_Id Type Receptacle Occupant Condition usb0/4.5 usb-hub connected configured ok usb0/4.5.1 usb-device connected configured ok usb0/4.5.2 usb-printer connected configured ok usb0/4.5.3 usb-mouse connected configured ok usb0/4.5.4 usb-device connected configured ok usb0/4.5.5 usb-storage connected configured ok usb0/4.5.6 usb-communi connected configured ok usb0/4.5.7 unknown empty unconfigured ok usb0/4.6 usb-storage connected configured ok usb0/4.7 usb-storage connected unconfigured ok
For example:
# cfgadm -c configure usb0/4.7
For example:
# cfgadm usb0/4.7 Ap_Id Type Receptacle Occupant Condition usb0/4.7 usb-storage connected configured ok
If you want to remove a USB device from the system and the prtconf output, but you are not physically near the system, just logically disconnect the USB device. The device is still physically connected. However, the device is logically disconnected, unusable, and not visible to the system.
For example:
# cfgadm -c disconnect -y usb0/4.7
For example:
# cfgadm usb0/4.7 Ap_Id Type Receptacle Occupant Condition usb0/4.7 unknown disconnected unconfigured ok
Use this procedure to logically connect a USB device that was previously logically disconnected or unconfigured.
For example:
# cfgadm -c configure usb0/4.7
For example:
# cfgadm usb0/4.7 Ap_Id Type Receptacle Occupant Condition usb0/4.7 usb-storage connected configured ok
The device is now available and visible to the system.
Use this procedure to disconnect a USB device subtree, which is the hierarchy (or tree) of devices below a hub.
For example:
# cfgadm -c disconnect -y usb0/4
For example:
# cfgadm usb0/4 Ap_Id Type Receptacle Occupant Condition usb0/4 unknown disconnected unconfigured ok
If a USB device behaves erratically, use the cfgadm command to reset the device, which logically removes and re-creates the device.
For example:
# cfgadm -x usb_reset -y usb0/4.7
For example:
# cfgadm usb0/4.7 Ap_Id Type Receptacle Occupant Condition usb0/4.7 usb-storage connected configured ok
Keep the following in mind when working with multi-configuration USB devices:
A USB device configuration defines how a device presents itself to the operating system. This method is different from system device configurations discussed in other cfgadm sections.
Some USB devices support multiple configurations, but only one configuration can be active at a time.
Multi-configuration devices can be identified by examining the cfgadm -lv output. Nconfigs will be greater than 1.
The default USB configuration is configuration 1. The current configuration is reflected in cfgadm -lv output as Config.
Changes to the default configuration persist across reboots, hot-removes, and the reconfiguration of the device, as long as the device is reconnected to the same port.
For example:
# cfgadm -x usb_config -o config=2 usb0/4 Setting the device: /devices/pci@1f,0/usb@c,3:4 to USB configuration 2 This operation will suspend activity on the USB device Continue (yes/no)? yes
For example:
# cfgadm -lv usb0/4 Ap_Id Receptacle Occupant Condition Information When Type Busy Phys_Id usb0/4 connected unconfigured ok Mfg: Sun 2000 Product: USB-B0B0 aka Robotech With 6 EPPS High Clk Mode NConfigs: 7 Config: 2 : EVAL Board Setup unavailable usb-device n /devices/pci@1f,0/usb@c,3:4
Note that Config: now shows 2.