Summary: | Thinkpad X1 tablet 3rd gen: USB-C does not work | ||
---|---|---|---|
Product: | Base System | Reporter: | Mathias.Picker |
Component: | usb | Assignee: | freebsd-usb (Nobody) <usb> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | hselasky, markusalbertgraf, scottl |
Priority: | --- | ||
Version: | 12.1-STABLE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Mathias.Picker
2020-02-29 09:23:40 UTC
Same here on my X1. (In reply to Mathias.Picker from comment #0) I meant to write "Charging works fine through USB-C" Not a native speaker ;) Cheers, Mathias Scott Long, CC'ed is working on this. Hi, I'm assuming that this is a Thunderbolt 3 port, since it's a USB-C connector and your devices aren't showing up in the OS. There are some unfortunate and confusing hardware design decisions with TB3 that make it hard to work with. I'm finishing up a driver right now and intend to make it available for testing in the next few days. In the mean time, I recommend that you open up the BIOS on the laptop and see if there are any controls related to Thunderbolt 3. If there are, you might find a control for the hardware security model, with options for "none", "user", "display port", and "key exchange", or some similar words. You can try setting the security model to "none" and see if that allows your USB hardware to show up when you plug it in. Even if it does, there might still be some problems with the hardware not working or invoking endless internal resets, but it'll at least be some good data to collect. I'll update this bug report once I have some code that can be tested. After setting the video ram down to 256Gb I could change the Thunderbold security to "none", but devices on the USB-C still do not show up :( Thanks for the suggestion, though. / Mathias I switched to -CURRENT and did a BIOS update on Jan 3, now USB-C works. Since I did a BIOS update at the same time, I really do not know what's the actual reason for it to work now. I have switched off Thunderbolt in BIOS, and I don't think I could do this before, so it might well be the bios. |