![]() I've not run into any black screen issues with the DVI monitors I've tried. a HDMI to DVI cable, to a computer monitor seems to work fine. The fact that this issue seems to be a more general one (one which you'll be able to run into just booting one of the most popular Linux distributions) makes it pretty severe.Ĭheck the comments on this article for more people reporting this issue: Skylake Core i3-6100U (NUC6i3SYK) running Ubuntu 17.10 (desktop) Apollo Lake Pentium J4205 (using the native HDMI 1.4 output), running Ubuntu 16.10 Server or 17.10 Server This TV has no such issues with the following hardware: There are two ways to recover: disconnect and reconnect the HDMI plug OR power off and then on the TV. However, as soon as the system loads i915 and switches mode the screen goes black. Ubuntu starts to boot up and you get to see the first lines of console print-outs.ģ. When you boot the system, the boot screen ("Intel NUC") is shown, as it should be.Ģ. I have this issue on my NUC7PJYH (Gemini Lake Pentium J5005) with a completely stock Ubuntu 18.04 Server installation using a Samsung 22" 1080p TV (I'll come back with the exact model number). I am not sure how HF-VSDB block is changing every probe, that to in an incremental supported way :) *ERROR* YCBCR420 (also) supported =YĪnd the third probe says both 420_also as well as 420_only supported: Second probe says 420_also modes supported but no 420_only mode: ![]() There is something fishy with the EDID's extension blocks for this monitor.įirst probe, EDID says neither 420_only nor 420_also supported: (In reply to Jani Saarinen from comment #6) Scope shot of input and output of level shifter
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |