Import argparse from functools import reduce import sys def printerr ( * args ): print ( * args, file = sys. The first is the classic unixy “everything is a file” approach you can run: You’ll need an EDID file for you monitor to modify.
Mine is an Acer K272HUL, so I had to do it myself. You might get lucky and find an existing modified EDID binary for your specific monitor, perhaps in this thread. On MacOS, I was able to use this handy script, which snarfs your monitor’s EDID, munges the correct bits, and sticks the resulting EDID binary in a place the kernel cares about. My monitor happily reports 01 for these bits, which tells the GPU it can handle RGB 4:4:4 and YCrCb 4:4:4, after which amdgpu says “thanks, I hereby dub you a TV, now fuck off.” The linked Wiki article gives a detailed explanation of how the various fields are encoded for our purposes, we care about bits 3 and 4 of byte 24, which encode the display type. If you look at the X11 log (on newish Ubuntu it will live at ~/.local/share/xorg/Xorg.0.log), you’ll find a line somewhat like: If you’re on an old card, and are thus on the radeon driver, the property will probably show up in the output from xrandr but if that’s the case, you won’t be having this problem in the first place, as it only shows up with the newer amdgpu driver. X11, however, is aware, and makes the decision based on the graphics driver. Neither the display manager or shell gives you options to change the color signal format. – you just have to switch your output to RGB mode, after which you can happily skip along to whatever grail you’re implementing. And unfortunately, because your monitor was trusting enough to tell amdgpu that it’s capable of both, the driver decided it would be having YCbCr, whether it wants it or not.
ACER K272HUL DRIVER FOR MAC FULL
Your monitor would rather be fed full RGB, but it will settle for YCbCr. With less color space to work with, and slightly different rendering, the edges of things like text get funky, and everything feels slightly out of focus. To save you some suspense, dear reader, I’ll tell you now what the problem is: your GPU has decided that your monitor is a TV, and is feeding it YCbCr colors. If you’ve been using Linux for a while, you sigh deeply, for you know what’s coming: This Is Going To Suck. Your resolution is correct, your refresh rate is fine, and the card has correctly detected your monitor. You pray to the Machine Spirits that it’s a simple resolution or refresh rate issue, and start poking at your display settings. Something is wrong with the graphics driver.
Are your glasses out of focus? Maybe you don’t even wear glasses, but your text is kind of fuzzy and pixelated. You boot that sucker up, log in without issue, and are about to declare victory – when you squint a tad.
ACER K272HUL DRIVER FOR MAC WINDOWS
You’ve already booted into Windows and flexed your F250-sized GPU’s muscles on some games, so now it’s time to make sure things work correctly on your Linux install. Maybe you dual boot Windows and GNU/Linux, the former for gaming and the latter for work.
So you just got yourself a fancy new AMD graphics card. This will be relevant to you if you own a recent AMD GPU (one that uses amdgpu instead of the old radeon driver) and have a monitor displaying inexplicable fuzzy and pixelated text. Or: how Camille ended up learning more than she probably needed about EDID, Linux’s amdgpu driver, and even the boot process. The Tale of the Fuzzy Text Manually overriding the EDID data on GNU/Linux with the amdgpu driver
0 kommentar(er)
