Which Linux distro are you using?
Debian
Which release version?
(if rolling release without a release version, skip this question)
Trixie
(If rolling release, last date updated?)
Which kernel are you using?
6.12.21
Which BIOS version are you using?
3.07
Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
Ryzen 7040 Series
Has anyone been able to get thunderbolt networking working with the Framework 13 Ryzen 7040 series? I’m trying to connect mine to a M4 Mac Mini. I know that thunderbolt works on the FW13, boltctl list shows a TB4 drive connected but I can’t get any device at all to show up when connecting to the Mac. The thunderbolt_net module is installed. I’ve tried both a TB4 and a certified USB4 cable in the correct ports, even tried a TB/USB4 Hub with an intel chipset in addition to working every gist I could find online. I’ve about shaved this yak to death but it bugs me that as far as I know this should work?
Just as a sanity check:
rear ports only are TB/usb4
thunderbolt_net i have noticed will stop working after disconnecting cable.
Its all point to point meaning static IP assignment is required to get it all to communicate correctly. Doublecheck if ios has added a networking device
No. For decades now we had standards to auto-configure IP addresses if there is no DHCP server. Windows and sane linux distros implement this world-wide standard. You will get non-conflicting IPs in a /16 network assigned. No need to do that manually. Unless Apple is boycotting that standard as well. But then you’d still only need to give the Apple host a valid ip in the same /16 network.
Irrelevant. Both are USB4 hosts, you are expecting a USB4 connection, not a TB3 connection.
This is expected. Windows and Linux USB4/TB3 device views are only expected to show managed peripherals (i.e. other controllers that are managed by your host controller).
USB4/TB Networking is a “cross-domain” connection that works differently, so it will never appear there in the first place. The thunderbolt_net kernel module will be auto-loaded on first use (for modern linux distros) and a network adapter for it will appear. Its called “thunderbolt0” for me.
If you need to debug, unload the thunderbolt* modules and modprobe thunderbolt dyndbg && modprobe thunderbolt_net dyndbg to get more dmesg reports from those modules about the hotplug events and the network adapter being created.
I have no idea if Apple stuff is broken that you need to configure sth. manually there. But Windows and sane Linux distros are completely plug-and-play for that. The only thing in your way is typically any firewall. Especially Windows refuses to classify the network as anything but Public, so blocks everything incoming.