Just because it works on an Intel Mac does not mean the cable isn’t the issue! Happy to demonstrate in a live video along with oscilloscope readings to prove it is in fact the cable to blame.

I would like to see this. Mostly to see what kind of an absolute beast of an oscilloscope can keep up with the data rate.

Also I don't understand why people are disagreeing with you. If a cable is not within spec it's absolutely possible for it to work in one circumstance because for example the port is more lenient and completely fail with a port that is more strict.

> Mostly to see what kind of an absolute beast of an oscilloscope can keep up with the data rate.

You can prove a cable faulty without being able to fully observe/measure the entire frequency range at once.

> Also I don't understand why people are disagreeing with you. If a cable is not within spec it absolutely possible for it to work in one circumstance because for example the port is more lenient and completely fail with a port that is more strict.

I’m kinda baffled too. I thought this was common knowledge among the folks on HN, but maybe not?

What's your theory as to why the cable would be at fault, despite working perfectly well in a different machine?

Seems like the simplest counterpoint would be to demonstrate a M1 mac transmitting at the full data rate using a different cable.

> Seems like the simplest counterpoint would be to demonstrate a M1 mac transmitting at the full data rate using a different cable.

Which I’d be happy to do assuming I knew the exact specs (brand/model) of the drives OP was using.

If you’d like me to demonstrate that MacOS on Apple Silicon correctly supports USB 3.2 gen 2 devices at 10Gb/s using multiple brands of drives/models, happy to do as well.