1hubd(7D) Devices hubd(7D)
2
6 hubd - USB hub driver
7
9 hub@unit-address
10
13 The hubd is a USBA (Solaris USB Architecture) compliant client driver
14 that supports USB hubs conforming to the Universal Serial Bus Specifi‐
15 cation 2.0. The hubd driver supports bus-powered and self-powered hubs.
16 The driver supports hubs with individual port power, ganged power and
17 no power switching.
18 When a device is attached to a hub port, the hubd driver enumerates the
21 device by determining its type and assigning an address to it. For
22 multi-configuration devices, hubd sets the preferred configuration
23 (refer to cfgadm_usb(1M) to select a configuration). The hubd driver
24 attaches a driver to the device if one is available for the default or
25 selected configuration. When the device is disconnected from the hub
26 port, the hubd driver offlines any driver instance attached to the
27 device.
28
30 /kernel/drv/hubd 32- bit x86 ELF kernel module
31 /kernel/drv/amd64/hubd 64- bit x86 ELF kernel module
34 /kernel/drv/sparcv9/hubd 64-bit SPARC ELF kernel module
37
40 See attributes(5) for a description of the following attributes:
41 ┌─────────────────────────────┬──────────────────────────────┐
46 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
47 ├─────────────────────────────┼──────────────────────────────┤
48 │Architecture │SPARC, x86, PCI-based systems │
49 ├─────────────────────────────┼──────────────────────────────┤
50 │Availability │SUNWusb │
51 └─────────────────────────────┴──────────────────────────────┘
52
54 cfgadm_usb(1M), attributes(5), usba(7D)
55 Writing Device Drivers
58 Universal Serial Bus Specification 2.0
61 System Administration Guide: Basic Administration
64 http://www.sun.com/io
67
69 In addition to being logged, the following messages may also appear on
70 the system console. Messages are formatted in the following manner:
71 WARNING: <device path> <hubd<instance number>): Message...
73 where <instance number> is the instance number of hubd and <device
78 path> is the physical path to the device in /devices directory. Mes‐
79 sages from the root hub are displayed with a usb<instance number> pre‐
80 fix instead of hub<instance number> as the root hub is an integrated
81 part of the host controller.
82 Connecting device on port <number> failed.
84 The driver failed to enumerate the device connected on port <num‐
86 ber> of hub. If enumeration fails, disconnect and re-connect.
87 Use of a USB 1.0 hub behind a high speed port may cause unexpected
90 failures.
91 Devices connected to a USB 1.0 hub which are in turn connected to
93 an external USB 2.0 hub, may misbehave unexpectedly or suddenly go
94 offline. This is due to a documented incompatibility between USB
95 1.0 hubs and USB 2.0 hub Transaction Translators. Please use only
96 USB 2.0 or USB 1.1 hubs behind high-speed ports.
97 Connecting a high speed device to a non-high speed hub (port x) will
100 result in a loss of performance. Please connect the device to a high
101 speed port to get the maximum performance.
102 USB 2.0 devices connected to USB 1.0 or 1.1 hubs cannot run at
104 their highest speed, even when the hub is in turn connected to a
105 high-speed port. For best performance, reconnect without going
106 through a USB 1.0 or 1.1 hub.
107 Cannot access <device>. Please reconnect.
110 This hub has been disconnected because a device other than the
112 original one has been inserted. The driver informs you of this fact
113 by displaying the name of the original device.
114 Port <n> overcurrent.
117 An overcurrent condition was detected. Please remove the device on
119 this port.
120 Devices not identical to the previous one on this port. Please discon‐
123 nect and reconnect.
124 Same condition as described above; however in this case, the driver
126 is unable to identify the original device with a name string.
127 Hub driver supports max of <n> ports on hub. Hence, using the first
130 <number of physical ports> of <n> ports available.
131 The current hub driver supports hubs that have <n> ports or less. A
133 hub with more than <n> ports has been plugged in. Only the first
134 <n> out of the total <number of physical ports> ports are usable.
135 Hub global over current condition, please disconnect the devices con‐
138 nected to the hub to clear the condition. You may need to re-connect
139 the hub if the ports do not work.
140 An overcurrent condition was detected on the hub. This means
142 that the aggregate current being drawn by the devices on the down‐
143 stream ports exceeds a preset value. Refer to section 7.2.1.2 and
144 11.13 of the Universal Serial Bus Specification 2.0. If this mes‐
145 sage continues to display, you may need to remove downstream
146 devices to eliminate the problem. If any port does not work after
147 the overcurrent condition is cleared, re-connect the hub to re-
148 enable the ports.
149 Root hub over current condition, please check your system to clear the
152 condition as soon as possible. You may need to reboot the system if the
153 root hub does not recover automatically.
154 An overcurrent condition was detected on the root hub, indicating
156 that malfunctioning devices on the downstream ports are drawing too
157 much current. Please disconnect the problematic downstream devices
158 to eliminate the problem. If the root hub doesn't work after the
159 overcurrent condition is cleared, you may need to reboot the sys‐
160 tem.
161 The following messages may be logged into the system log. They are for‐
165 matted in the following manner:
166 <device path><hubd<instance number>): message...
168 Local power has been lost, please disconnect hub.
172 A USB self-powered hub has lost external power. All USB devices
174 connected down-stream from this hub will cease to function. Discon‐
175 nect the hub, plug in the external power-supply and then plug in
176 the hub again.
177 Local power has been lost, the hub could draw <x> mA power from the USB
180 bus.
181 A USB self/bus-powered hub has lost external power. Some USB
183 devices connected down-stream from this hub may cease to
184 function. Disconnect the external power-supply and then plug in the
185 hub again.
186 Two bus-powered hubs cannot be concatenated.
189 A bus-powered hub was connected to a bus powered hub port. Please
191 remove this bus-powered hub and connect it to a self-powered hub or
192 a root hub port.
193 Configuration <n> for device <device> at port <m> exceeds power avail‐
196 able for this port. Please re-insert your device into another hub port
197 which has enough power.
198 The device requires more power than is available on this port.
200 Port <n> in over current condition, please check the attached device to
203 clear the condition. The system will try to recover the port, but if
204 not successful, you need to re-connect the hub or reboot the system to
205 bring the port back to work.
206 An overcurrent condition was detected on port <n>. This means the
208 device connected to the port is drawing more current than the hub
209 can supply. If this message continues to display, please disconnect
210 the device to eliminate the problem. If the port doesn't work after
211 the overcurrent condition is cleared, please re-connect the hub or
212 reboot the system to enable the port again.
213SunOS 5.11 6 July 2006 hubd(7D)