tbtadm(1)
β¨ tbtadm β Thunderbolt(tm) management tool β¨
okay bestie, so this is tbtadm(1), a whole General Commands Manual page, and it's literally your little bestie for talking to the Thunderbolt(tm) kernel module π
π SYNOPSIS π
tbtadm
tbtadm devices
tbtadm peers
tbtadm topology
tbtadm approve [--once] <route-string>
tbtadm approve-all [--once]
tbtadm acl
tbtadm add <route-string>
tbtadm remove <uuid | route-string>
tbtadm remove-all
π DESCRIPTION π
tbtadm is the convenient way to interact with the Thunderbolt kernel module β approving the connection of Thunderbolt devices, handling the ACL for auto-connecting devices, and more π¦
And the cutest part? If you run it with no argument at all, it just prints out all the available commands for you. main character energy, honestly π
π OPTIONS π
devicesβ prints a list of all the currently connected Thunderbolt devices, in exactly this format:
Route-string Vendor Device name Authorized? In ACL?
peersβ prints a list of all the currently connected hosts, in exactly this format:
Route-string Vendor Device name
topologyβ prints all the currently connected Thunderbolt devices as a tree, starting with the controller itself, so it resembles the actual device connection topology πΈ (it's giving family tree but make it hardware)approve [--once] <route-string>β if the Thunderbolt device you picked isn't authorized, this approves it, and (if--oncewasn't specified) adds it to the ACL πapprove-all [--once]β approves all currently connected Thunderbolt devices that aren't authorized yet, and (if--oncewasn't specified) adds them to the ACL. the group-chat mass-approval, if you will β¨aclβ prints the ACL content, in exactly this format:
UUID Vendor Device name Currently connected?
add <route-string>β adds a device to the ACL. The argument picks the device to be added by its route-string π«Ά
ngl bestie, this one doesn't work in SL2 (secure; key-based), because adding to the ACL must be done together with the device authorization β that means withapproveorapprove-allwithout the--onceflag. no cap π
remove <uuid | route-string>β removes an ACL entry. The argument picks the device to be removed by its UUID, or (if it's currently connected) by its route-string πremove-allβ clears the ACL, removing all the entries. it's giving spring cleaning π§Ήβ¨
π¦ SEE ALSO π¦
no SEE ALSO refs on this page, bestie β it's a short and sweet one π
and that's the whole page, periodt π
cute sign-off time π β this little masterpiece was written by Yehezkel Bernat, and the footer was serving 2mtime(2m/2d/2Y) with tbtadm(1) at the bottom. obsessed π
π¦ where this page comes from
- nixos 26.05: thunderbolt 0.9.3
- nixpkgs unstable: thunderbolt 0.9.3
- opensuse-leap 16.0: thunderbolt-user-space 0.9.3-bp160.1.6 Β· BSD-3-Clause
- opensuse-leap 16.0: thunderbolt-user-space 0.9.3-bp160.1.6 Β· BSD-3-Clause
- opensuse-leap 16.0: thunderbolt-user-space 0.9.3-bp160.1.6 Β· BSD-3-Clause
- opensuse-leap 16.0: thunderbolt-user-space 0.9.3-bp160.1.6 Β· BSD-3-Clause
- ubuntu questing: thunderbolt-tools 0.9.3-7build2
- ubuntu resolute: thunderbolt-tools 0.9.3-9build1 Β· BSD-3-Clause
- ubuntu stonking: thunderbolt-tools 0.9.3-9build1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms