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.
2 Likes
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.
3 Likes
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…
1 Like
I actually tested this with Windows and it works perfect, so it must be some Linux/Wayland specific issue I’m having.
2 Likes
Hi all,
I have the Lg40 Ultra wide but I have issues connecting VIA usb C on W11. All drivers from both windows and LG are updated, also FW drivers. Been searching for an answer/solution for 3 days. Has anyone found a solution or the pair can only work over DP and HDMI?
Here a link to a video of my issue.
Thanks in advance if someone has a solution!
Looks like most people here haven’t actually tried and reported their success/failure with LG Ultrafine 5k.
I’m using Arch with Sway/Wayland,
When I first connected the LG Ultrafine 5k to my usb-c port the framework display would shut off for a few seconds and then come back on, and this would repeat over and over again.
From the dmesg output this is what I was seeing over and over again (this is just a short snippet of a larger dmesg output):
[148123.707088] thunderbolt 1-0:3.1: retimer disconnected
[148123.719290] thunderbolt 1-3: device disconnected
[148127.598434] thunderbolt 1-0:3.1: new retimer found, vendor=0x8087 device=0x15ee
[148128.250885] thunderbolt 1-3: new device found, vendor=0x1e device=0x1114
[148128.250895] thunderbolt 1-3: LG Electronics UltraFine 5K
[148132.968013] thunderbolt 1-0:3.1: retimer disconnected
[148132.980416] thunderbolt 1-3: device disconnected
[148133.145343] usb 3-5: new high-speed USB device number 79 using xhci_hcd
[148136.789518] thunderbolt 1-0:3.1: new retimer found, vendor=0x8087 device=0x15ee
[148137.441204] thunderbolt 1-3: new device found, vendor=0x1e device=0x1114
[148137.441214] thunderbolt 1-3: LG Electronics UltraFine 5K
[148334.831281] thunderbolt 1-0:3.1: retimer disconnected
[148334.843710] thunderbolt 1-3: device disconnected
[148335.058661] usb 3-5: new high-speed USB device number 81 using xhci_hcd
[148336.078705] usb 3-5: device descriptor read/64, error -71
[148338.658017] thunderbolt 1-0:3.1: new retimer found, vendor=0x8087 device=0x15ee
[148339.312318] thunderbolt 1-3: new device found, vendor=0x1e device=0x1114
[148339.312330] thunderbolt 1-3: LG Electronics UltraFine 5K
[148341.130224] thunderbolt 1-0:3.1: retimer disconnected
[148341.140728] thunderbolt 1-3: device disconnected
[148342.548589] usb 3-5: new high-speed USB device number 83 using xhci_hcd
Note the thunderbolt connects and disconnects. The USB side of things fails to read the device descriptor with error -71. I did a cursory look into the Linux kernel USB drivers to see what was going on, but got lost and couldn’t find these error strings whatsoever.
Anyway the primary monitor kept shutting off every few seconds, presumably to do with those thunderbolt events in dmesg. I did manage to get output to the LG when I was just in VGA console mode, but it didn’t really work all that well (it was a mirrored display) as the LG display was really enlarged and nothing fit on the screen.
So after about 20 minutes of the annoying display cycling I unplugged the display.
My system is usually on hibernate, and when I did the above experiment it was resumed from a previous hibernate. Someone suggested I try with a reboot.
So I reboot and connected the display a second time.
The second time, nothing happened, no display power cycling. I checked dmesg and got the following messages:
[ 152.656573] usb 3-4: new high-speed USB device number 76 using xhci_hcd
[ 153.733249] usb 3-4: new high-speed USB device number 77 using xhci_hcd
[ 155.029908] usb 3-4: new high-speed USB device number 78 using xhci_hcd
[ 157.126575] usb 3-4: new high-speed USB device number 80 using xhci_hcd
[ 160.046578] usb 3-4: new high-speed USB device number 81 using xhci_hcd
[ 162.423321] usb 3-4: new high-speed USB device number 82 using xhci_hcd
[ 163.466663] usb 3-4: new high-speed USB device number 83 using xhci_hcd
[ 165.369892] usb 3-4: new high-speed USB device number 84 using xhci_hcd
[ 166.389962] usb 3-4: device descriptor read/64, error -71
[ 168.609913] usb 3-4: new high-speed USB device number 85 using xhci_hcd
[ 169.693206] usb 3-4: new high-speed USB device number 86 using xhci_hcd
[ 172.619953] usb 3-4: new high-speed USB device number 87 using xhci_hcd
[ 173.663290] usb 3-4: new high-speed USB device number 88 using xhci_hcd
[ 174.679955] usb 3-4: device descriptor read/64, error -71
[ 178.713167] usb 3-4: new high-speed USB device number 89 using xhci_hcd
[ 181.636646] usb 3-4: new high-speed USB device number 90 using xhci_hcd
[ 182.686624] usb 3-4: new high-speed USB device number 91 using xhci_hcd
[ 183.730014] usb 3-4: new high-speed USB device number 92 using xhci_hcd
No thunderbolt diagnostics. So for some reason the thunderbolt wasn’t being detected or not running.
I don’t know what else to do, so I’m seeking support.
I know the LG Ultrafine 5k can work in Linux because this reddit thread shows the poster having it working.
Edit: looks like I needed to charge my battery back up to high levels for the thunderbolt devices to be detected, which is strange because the LG should be doing power delivery.
I filed this exact bug back in June and linked it earlier in the thread: https://gitlab.freedesktop.org/drm/intel/-/issues/6265
Also, do you have a 11th Gen or a 12th Gen board?
1 Like
Sorry for delay in reply (for some reason I don’t get emails when this thread is updated). I have a 12th gen board.
I’ll add to your issue once my gitlab account is approved. Updated your bug report.
I notice you actually have the monitor working and displaying things. I haven’t even gotten that far. Am I missing something in userspace to work with the i915?
I have the same problem as “software_developer”. Also fan goes on high, once you start a few apps on 5k.
Can confirm, video, audio, camera all work on the 11th Generation Framework running Kubuntu (Linux) 22.04 using this cable
1 Like
Can you tell us which other cables you’ve tried that didn’t work? I have tried everything from Apple’s $200 pro cable, to all the other TB4 certified ones, short and long, and none works.
I’m suspecting that it’s Ubuntu that’s doing something different (or Xorg vs Wayland) since all those cables work wonderfully under Windows on the same machine.
Not anymore! It used to work initially, but now, blank screen and lots of errors in dmesg. I upgraded my board to 12th gen. No difference on the 5K display. However, my LG 4K display no longer loses connection if I plug in/out the power next to it. That’s an improvement!
I just used the one recommended above from the previous poster and linked in my post. I didn’t really try any other cables because that one “just worked”.
I just downloaded the Kubuntu and Ubuntu images and neither works with the monitor, using 3 different cables. Something fishy going on here.
I have the USB C adapters on the right side (power button side) of the laptop, the monitor is plugged into the one closest to the touch pad. I’m typing this on that setup now.
Do you mind pasting your dmesg log here?