Hi all ~ First off, thanks so much to joevt for compiling on the information on these monitors and being so responsive across several forums.
I purchased a LG UltraFine 4K 22MD4k (the older, 21.5" 4K sku) recently and so far have been unsuccessful in getting an image to display on screen - it remains resolutely black whenever I plug it into a computer - and I wondered if this was something others have encountered or been able to solve.
Setup and steps I've taken:
- Plugged the monitor into my Linux-running ThinkPad Yoga 370's USB-C port via the cable that came with the monitor
- xrandr recognized the monitor and I could set it as a 2nd screen, but the screen remains black, ddcutils reports the brightness as 0, and I get an error any time I attempt to set the brightness via ddcutils.
- Plugged the monitor into an AMD graphics card in a desktop computer running the latest Windows 10 via the recommended Amazon Basics bi-directional USB-C to DisplayPort cable
- Both Windows display properties and ClickMonitorDDC recognize the monitor (and Windows recognizes the correct display resolution as well). I've had two experiences with this: first, ClickMonitorDDC showed the monitor checkbox with a checkmark in it (I'm using a 2nd monitor for troubleshooting this) and reported the brightness as 0 - whenever I tried to change the brightness then clicked away, it would always reset down to 0 (and of course there was no change on the monitor itself). After unplugging, replugging, and rescanning, ClickMonitorDDC now shows the box as unchecked (does this mean it thinks the monitor is off..??) and the brightness slider will now move up and down without re-setting to 0, but again, the monitor stays black and nothing changes. If I shift click the empty check-box, the monitor disappears from ClickMonitorDDC's list, stays gone for a couple seconds, then re-appears, showing brightness of 0 - and the box is still not checked.
- I just tried using EasyMCC, and when I select the LG monitor, I get "ErrorCode: 0xC0262589" in a message box. Googling seems to indicate that this is an "ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_COMMAND" error code? Not sure what that indicates here.
- I've successfully installed the Boot Camp drivers using brigadier, and have the Boot Camp Control Panel open. When I plug the monitor into the motherboard's USB-C port, the Display tab of the Boot Camp Control Panel detects the external display and shows a blank drop-down menu + brightness slider bar & "Adjust brightness automatically" checkbox. However, the brightness slider does not affect the monitor at all -- still black -- and Windows doesn't recognize it as a 2nd display in Display settings (which I think is an issue with the motherboard's USB-C port or something. however the speakers & HID Ambient Light Sensor do work / show up as working in the device manager, lol)
I'm stumped! Any ideas?
Update: for the
briefest of seconds, the monitor actually worked! I'd rebooted after installing the boot camp drivers, then switched the displayport cable out for the USB-C cable (obviously didn't work, as above) -- but when I switched
back to the displayport cable, the monitor turned on! I opened ClickMonitorDDC, and it was responding to the commands as expected - changing brightness levels to match the ClickMonitorDDC settings.
Strangely, when I went into Windows' display settings to switch the resolution from the recommended 3090x?? to the full 4096px resolution, the monitor blacked out - and then would turn on again when I clicked "revert settings". Then I applied the higher res, the monitor blacked out, and didn't come back on when I reverted down & applied again. Plugged & unplugged, still doesn't turn on. I'm
so confused, but at least I know the physical screen itself isn't broken (bought it off ebay so only ever getting a black screen was freaking me out).
I'd still love to know how to consistently get the monitor to turn on! Kinda hard to use it otherwise. No idea what caused it to start working for that brief moment, or why it would black out when I changed the resolution.