FW 13 - Intel Core Ultra S1 vs AMD Ryzen *WITH* Thunderbolt / USB4 *WITH* Linux

Lo,

I’m after a recommendation from both a Linux user and someone who is clued into the world of Thunderbolt and USB4! (an answer from Framework themselves would also be nice)

First a bit of background about what we’re hoping to replace…

At the moment… I use a fairly old Dell XPS 9360 running Linux… and my husband uses a MacBook Pro 13” Mid-2017 running macOS (also dual boots Linux… but some stuff is broken and power consumption is also awful).

We’ve got two desks set up… both with 2 x 1080p DP (DisplayPort) monitors each connected to a Dell WD19TB Thunderbolt 3 dock on each desk. The idea is you can use either desk for either lappy (or an external lappy from someone else who pops around the house).

Both current lappies work with both sets of external displays just fine. In order to keep the MacBook happy (as it doesn’t support DisplayPort MST)… the 2nd monitor (of each pair of 2 monitors per desk) is actually converted from DP to TB3 via this little thing and plugged into the TB3 USB-C port of the WD19TB dock. The XPS 9360 running Linux is also fine with this setup… so I don’t need to keep changing the cabling.

Now the capabilities of these existing docks suits me just fine the way they are… I’m not after a better dock or 4k screens or anything like that.

So I’m looking to buy TWO Framework 13 laptops… and originally I had just read this article…

And just presumed to go with Intel. The article doesn’t mention the “Intel Core Ultra S1” (it just mentions the 11th gen getting the certification after the fact… and 12th gen already having it)… but I’m guessing it’d be daft to go with anything older than “Intel Core Ultra S1” ?

Unless there are compatibility reasons to be considered for Linux somehow for going for an older Intel?

But then today I’ve clicked ‘Laptop 13’ at the top of the main Framework website and then ‘Configure now’ and all I see are AMD options… with the Intel ones buried inside the ‘Shop all’ section… so should I be considering AMD Ryzen AI 300 Series … OR … AMD Ryzen 7040 Series ? OR both?

Concerns…

a) Having the WD19TB work generally for things internal to it (like its DP/HDMI ports, audio, ethernet, etc…)

b) Having the 2nd screen (per each desk) stay connected via TB3 (in the fashion described above) to the WD19TB and that still not being an issue (as I may still need the MacBook Pro for occasional Xcode jobs as I write cross-platform software)

That way I can use the two new Framework laptops, plus the older two laptops…

Will USB4 on the AMD stuff be alright with this? Or am I better sticking with certified Thunderbolt?

Non-thunderbolt thoughts…

I prioritise stability and proper compatibility with Linux above all else. I hear AMD supports LVFS more than Intel? But other than that, are they equal in terms of least faff and compatibility trouble? Second priority after that is battery life. All other concerns (including cost) are tied for 3rd priority.

I was tempted go with a Tuxedo laptop until I realised they’d ditched their upcoming ARM laptop (and no one else seems to be doing this properly with Linux)… and so I looked at the x86 options and realised they run their own APT repo for stuff like out of kernel drivers.

I’m not doubting Tuxedo’s commitment… but I really am after something which is absolutely trivial to support in terms of all the drivers being in mainline kernel, no odd quirks or workarounds (so a generic ISO of any Linux distro will do). I generally run either Ubuntu or Debian as a desktop (usually done via debootstrap then I install everything manually)… so I’d prefer that chipsets in the laptop don’t need extra steps to work! I’m hoping with Framework having an emphasis on Linux that this is true? That these chipsets are hassle-free for Linux users?

Thanks for reading my long ramble!

Oh and p.s. I’m getting a Framework 12 too - but this is more for casual use… I’m aware there is no TB3/USB4. Just hope they release the green stylus!

Thanks again!

It might be worth looking through the Dock Megathread to check for compatibility and concerns with the existing docks.

Personally, I have a Kensington Dock from a while back (2019-ish), and while it worked in Windows on my 11th gen, it didn’t on various flavors of Linux. I have the same issues with it, with my AMD 7040 mainboard on Linux. (one display, ethernet, and half the USB ports).

Just another anecdote to help out.

Well in truly confusing fashion the WD19TB seems to be listed under both “Supported” and “Unsupported” tables!

I’m not too worried about the WD19TB if I’m honest… if a MacBook Pro can cope with it (minus the MST support) then I’d say it’s generally a good all rounder.

That part of my question is more about if USB4 can cope with things like all the functionality of a proper TB3 dock… as well as having that “mini dock” (that I’m just using to bridge DP to TB3) daisy chained behind it.

I use a Wd19TB with AMD models and have no issues. I use two 4k monitors connected over DP. I have also used eDP while both are active.

Framework publishes BIOS to LVFS.

Hey Mario :slight_smile: Nice to see you here! (we’ve spoken about Dell things a few times before!)

I guess it’s not a surprise you’d have a few Dell docks laying about and that you’d now back AMD!

But have you ever connected a TB3 monitor (or something which can convert a DP monitor into one… like that AliExpress thing I linked to above) and found that it works too?

I’m not certain if USB4 would work in TB3 mode and allow a TB3 device (that little mini dock) to be daisy chained off the back of the TB3 port on the WD19TB. But it certainly works fine with my Intel based XPS 9360.

I haven’t, but my colleagues have! The only monitor that I know of with problems is the apple 5k one.

It internally advertises “two” DP outputs that are tiled even though it’s one cable. Most tiled monitors output the same capabilities for each tile, but for some reason the left tile supports 12bpc and DSC but right doesn’t. This leads to problems both in amdgpu and mutter.

It’s understood though and being worked on.