Hello:

On 27 Oct 2023 at 16:48, Gregory Nowak via Dng wrote:

> Thanks ...
You're welcome.

> ... a regular bus powered hub.
> ... hub is not externally powered.
My apologies.

Missed the *bus* part of *bus powered*.
Too early, not enough espresso.

> This is the first time a USB3 device had a problem ...
Not unheard of.

I have seen it happen many times, even with what can be thought of as
*good quality* hardware.

eg:
Two identical Samsung 500Gb USB3.0 external drives connected to a
4-port PCIe USB3.0 card in my Sun Utra 24 WS which only has USB2.0
ports.

One drive would negotiate 3.0 speeds and the other would fall back to
USB 2.0 speeds.

The problem? One of the OEM cables probably causing voltage drop.

But *both* units worked perfectly well (with the OEM cables) when
plugged into the USB2.0 ports or when used with *other* USB2.0
cables.

> Every other USB3 device I've used ...
You are assuming that every USB3.0 device is built to the same
standards and quality, something that *should* be the case.
But is not, not by a long shot.

> ... has a micro USB type b socket ...
Those *micro* cables are notorious for their failure rate.

They are flimsy, quite fragile and the plug/socket contact surface is
far too small for the power they need to deliver, requiring perfect
mating surfaces.

Invisible corrosion or a spec of dust will affect them.
Many times the cables are not the appropiate AWG# for their length.

> Both cables work just fine with other devices.
Like I mentioned in my previous post, this is a problem related to
the hardware not being able to supply enough (needed) power to the
USB 3.1 device.

Hence the *unable to enumerate USB device* and *attempt power cycle*
entries in the log.

I'd check that *on-board USB 3.1 port on the IO panel* for a loose
connector cable to the motherboard and lint/dust in the socket.

My WS box needs a cleaning every so often.

Run out of ideas, sorry.

Best,

S.