Does the framework laptop support LG UltraFine 5K monitor. From what I read on other sites it should then support 5K resolution over USB-C ( (DP 1.4 Alt Mode).
5k monitors (and even 8k monitors) should work fine over the USB-C Expansion Card or DP Expansion Card.
The HDMI Expansion Card is limited to 4k and similar resolutions like 5120 x 1440.
Can anybody confirm that they have it working with an LG Ultrafine 5K monitor?
I’m Batch 2, but I have the LG Ultrafine 5K and will test it once I get it.
Thank you! How’d the test turn out?
LG UltraFine 5K uses two DisplayPort 1.2 connections over Thunderbolt 3 for 5K60 mode (allows 10bpc RGB). The Framework Laptop can do Thunderbolt 4 so it should work.
The current version of LG UltraFine 5K (27MD5KL) also supports USB-C (non-Thunderbolt connection). The previous version (27MD5KA) can only work with Thunderbolt.
Thunderbolt connection is required for USB 3.0 speed.
With a USB-C (non-Thunderbolt connection) you can get 4K60 and USB 2.0. You might be able to get 5K39 with a custom timing (it has a ≈600 MHz max pixel clock even though DisplayPort 1.2 should be able to support more). I’ve only seen one person try 5K39.
With a DisplayPort connection (not Thunderbolt or USB-C), you can use a Belkin Charge and Sync cable or Wacom Link Plus or other method to include USB 2.0.
USB is used by the display for USB ports, audio, camera, and brightness control (with Boot Camp driver or you can try a method that communicates with DDI/CI for brightness control). I think you can get the Boot Camp driver even if you don’t have a Mac (see the Brigadier GitHub project).
Can anybody confirm that they have the framework laptop working with the LG Ultrafine 5K monitor?
It should work just fine with that monitor, I have ran the 5k with a Thinkpad that had TB3/USB-C and it worked great. Considering that the framework has Thunderbolt (just not advertised) it will work. Just like @joevt stated. Framework has an advantage that the USB-c ports are not just USB-C ports but they are TB4 ports so either model of the LG 5K will work.
Have an LG Ultrafine 5k and installed stock pop_os. Unfortunately, autodetect doesn’t work, and what is displayed on the Ultrafine is not usable. All rendering is shifted to the upper left quadrant of the screen.
Can’t promise I’ll get back to this, but if I do, will report here. Am optimistic.
Did anyone try this? I would like to use 2x LG Ultrafine 4K with the Framework, if I buy one.
My experience with recently purchase LG 38WN95C-W monitor. The LG supplied Thunderbolt 3 Cable did not work with the Framework Laptop. I purchased a Cable Matters 40Gbps USB4 Thunderbolt 4 Cable and it successfully connected at 3840x1600@120Hz. I am using SwayWM on Arch Linux.
EDIT: The LG UltraFine 5K works perfectly under Windows 10 at full resolution stably and with no tearing issues. This tells me the Framework firmware is fine as of now. I’m using the Apple’s 0.8m Thunderbolt Cable.
On Linux, I can confirm that it works great using Apple’s 0.8m Thunderbolt Cable. Longer cables, including the supplied cable with the monitor, did not work. This seems to be a firmware issue with a fix in the pipeline.
EDIT: I’ve found that on Wayland on Linux, there is screen tearing vertically in the middle when scrolling and moving content. In addition, night light only applies to half of the screen. There is an open issue on mutter and a in-progress merge request to fix it.
EDIT: Not so great on Linux with Wayland. Occasionally, the second display port stream stops working and it takes a mix of reconnecting and power cycling the screen to make it work again.
EDIT: Tracking the issue on drm/intel bug tracker.
Without that TB4 certification for the Framework laptop, anything that uses TB connectivity is a YMMV IMO…because as nrp mentioned, they (the certification body) still need to come up with /develop the test cases. Without the certification, there’s less assurance as to whether TB is functioning correctly on the Framework laptop…or if any TB connectivity issue is caused by some other factors.
Reference: the later part of this post…
I actually tested this with Windows and it works perfect, so it must be some Linux/Wayland specific issue I’m having.