Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • Just because the spec says it's possible for USB 3.0 doesn't mean common PC USB 3.0 host adapters actually implement this part of the spec. And then the host adapter kernel driver will also have to support it (and I don't know of any Linux driver that does that). So chances that it will actually work on your hardware are pretty slim. Commented Jun 7, 2017 at 7:20
  • @dirkt Then I could write a kernel driver... how would I address the port that way? Also what you say basically implies that the cable is completely useless, and that makes no sense. Also this certainly is not a hardware problem... my windows computer can actually recognize the connection to a linux computer via this cable. Commented Jun 7, 2017 at 13:22
  • So you have connected two PCs under Windows this way? What information does the device manager give in this mode? As what kind of USB device does the host controller act? If you connect in to Linux, what do lsusb and dmesg say?I mean, if you got it to work under Windows, that's great news, and will give hints how to implement it in Linux. So please add details to your question. :-) The only usage I've seen for this cable type so far is for debug ports, so it's clearly not useless ... Commented Jun 7, 2017 at 16:09
  • 1
    Please add details to the question, this is all very vague, and nothing to work with. For starters, output of lspci -nn to identify the host adapter hardware, content of dmesg after you plug in the cable (with other plugged into windows machine), screenshots of the Properties window of the USB host adapter in the Windows device manager, all tabs if possible. With that information, I can at least google for datasheets. And yes, if something works under Windows, it gives a lot of hints. How do you think reverse engineered device drivers get written? Commented Jun 7, 2017 at 17:10
  • 1
    Judging from the error messages, your hardware doesn't support it all: You just get errors on both sides. So Windows doesn't "recognize your cable when connected to Linux". If you can show me a working Windows-to-Windows configuration with that cable, maybe one can figure out something from that, but from what you have right now, it just won't work. Commented Jun 7, 2017 at 18:13