4 ms·
You don't have to do this. You can tell the kernel to read the EDID data from a file instead of from the device. I have two identical ASUS monitors; the EDID on
by PaulDavisThe1st 4y ago
You don't have to do this. You can tell the kernel to read the EDID data from a file instead of from the device. I have two identical ASUS monitors; the EDID on one of them failed, so my boot sequence tells the kernel to fetch the EDID from a file I created from the working one.
- pabs3 4y agoThat means the monitor is still broken if you move it to a new system, or even just reinstall your system and forget to copy the file over. Better to update the monitor itself. Also good to keep a backup in case the issue happens again.
- washadjeffmad 4y agoThis doesn't help if the cause is that the EEPROM has failed or is no longer writable, a not uncommon cause of EDID errors.
- toast0 4y agoAdding to the sibling, what if you want proper edid during boot?
- Aissen 4y agoDuring boot, on a machine you never touched. This is absolutely useful.
- gnull 4y agoAlso you need to identify the monitor somehow for kernel to do what you propose. If your monitor setup is not static, say, you connect monitors in different order or through different ports each time, you won't be able to tell which edid should go for which monitor. (Unless you're willing to script some heuristics to guess that.)
- detaro 4y agoUnless I misunderstand something, writing it this way afterwards also works on other platforms, which are not as flexible in that regard.
- eulenteufel 4y agoBecause I have a display whith broken edid I tried setting the edid with the kernel command line, but unfortunately that did not work for me. It might be because I use a nvidia graphics card, but I'm not sure.
- IshKebab 4y agoHow do I do that on Mac?
- no_time 4y ago>the EDID on one of them failed Can it just do that out of the blue? How did you even nail down that as the root cause?