Which Linux distro are you using?
openSUSE Tumbleweed
Which release version?
(if rolling release without a release version, skip this question)
(If rolling release, last date updated?)
Rolling release: last updated yesterday
Which kernel are you using?
6.16.1 - though this issue is already there from the start (so at least from 6.14 onwards)
Which BIOS version are you using?
03.09
Which Framework Laptop 13 model are you using? (AMD Ryzen™ AI 300 Series, AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD Ryzen™ 7040 Series
I have successfully connected my framework 13 to some Thunderbolt 3 docks, includings Dell’s WD19TB, using it to charge the laptop, some peripherals and to connect a 4K screen.
However, on my Dell UP2710Q - which has a Thunderbolt 3 dock built-in to the screen - I observe the following (I connect with a Framework USB-C modules in one of the USB-4 ports closest to the screen):
- 90+% of the time, the screen is detected as having a DP connection with 1024 x 768 resolution. When this is the case, the screen shows nothing at all when extending to it
- Stubbornly replugging the screen to the laptop eventually leads to the right detection (DP connection with 3840 x 2160 pixels). The latency between plugging in the USB cable and xrandr showing the external screen is much lower in the successful case (~ 2 secs) than in the error case (~ 7 secs)
- I got the impression that plugging in the charger in the other USB-C port increases my chances to have a right detection, though it still goes wrong in 50+% of the time.
- Plugging certain USB-A devices in the screen (like a Jabra Speak) often do not work (not even when the screen is detected correctly). It works when I plug in the Jabra Speak directly using a framework USB-A module in a different port on the laptop directly. Other devices (with lower bandwidth requirements I presume) like mouse and keyboard work all the time when connected to the screen.
- Booting to Windows on the same laptop using the same setup, this all works flawlessly, all the time.
- This setup worked perfectly for years on my old laptop with an intel chip.
Does anyone know how to debug this further? My suspicion is that the OS makes the wrong call assigning the right number of thunderbolt lanes to each device connected to the internal dock of the screen. I have no idea though how I can further debug this or guide the OS into giving the screen a higher ‘priority’.
Upon successful connection, boltctl list -a shows:
● Dell UP2720Q
├─ type: peripheral
├─ name: UP2720Q
├─ vendor: Dell
├─ uuid: c0030000-0080-840e-8318-442766b15025
├─ generation: Thunderbolt 3
├─ status: authorized
│ ├─ domain: 37b93804-40fe-9ec5-ffff-ffffffffffff
│ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ └─ authflags: none
├─ authorized: Tue 19 Aug 2025 06:35:32 AM UTC
├─ connected: Tue 19 Aug 2025 06:35:32 AM UTC
└─ stored: Tue 19 Aug 2025 06:35:32 AM UTC
├─ policy: iommu
└─ key: no
dmesg shows nothing when I replug the USB cable.
Any help or thoughts would be appreciated 