![]() Windows dual boot), it can make some trouble. However, with firmware updates or multiple OSs on the machine (e.g. The recomended (default) setting is secure connect due to the "signed" communication path. the device acts as a display extension (output) only and the rest is deactivated Secure connect, where PC and device exchange keys for authentication, making forging harder (a process to be done by the admin).User authorization, kind of a admin password required to use it.No security, all devices authorized by default and no user interaction needed.It may be that authorization doesn't work on older LTS versions.Īs many others said, there are multiple levels of authorization you can set. ![]() This may depend on what kernel version you're running I read somewhere that thunderbolt authorization stuff was added in 4.13. A quick boltctl authorize, and now everything is working, no BIOS fiddling required. ![]() Running boltctl obviously gave the TB bus a needed kick.) Still no USB though, but I'm not done yet. (Possibly the only reason the display didn't work immediately is because I didn't have boltctl installed previously. Installed and ran that (no arguments yet), and wham, display turns on. (I wouldn't be surprised if the GUIs are using boltctl under the hood.) Apparently the only thing Fedora packages is the CLI boltctl. Well, I'm also running KDE and have nothing like the "thunderbolt devices" shown in the question, so I asked my package manager for anything related to "thunderbolt". I had no idea "thunderbolt authorization" was a thing until I saw this question. I have a 7380 and had similar problems (on Fedora, though, not Ubuntu).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |