Sorry, you need to enable JavaScript to visit this website.

Primary tabs

NUC5i3RYH - Black screen - Debian

19 posts / 0 new
01 Staff's picture
01 Staff (not verified)

Sep 10, 2015 - 06:07am

  • fledermaus's picture
    fledermaus (not verified)

    Hey Fred - that is interesting - would you mind posting the exact monitor model here? It might be something the devs would want to look into.

    Oct 06, 2015 - 10:16am
  • fez01's picture
    fez01 (not verified)

    Hi Vivek!


    The monitor is a Dell 1709FPt. I didn't get a chance to try that one with DVI so I'm not sure whether the problem was the VGA connection or the monitor itself.



    Oct 06, 2015 - 05:29pm
  • piotrekfronc's picture
    piotrekfronc (not verified)

    Huh ! first success! I went through the

    and couldnt get it working on debian testing.

    ... well I thoughof trying stable kernel... added all apt source entries of stable repos and added 3.16 kernel... AND IT WORKS.


    I can tell now one thing: HD6200 on broadwell is ... fantastic. Im a mazed :)))


    Seems that someone pushed bugs into 4.x kernels.



    My setup:

    uname -a:

     3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux


    In grub and modules:




    in /etc/modprobe.d/i915-kms.conf:

    options i915 enable_rc6=7 enable_fbc=1 modeset=1 preliminary_hw_support=1 

    Some improvements could be done but Im running steam games... and, well, its damn fast ! (for an intel gpu ;-)...)




    Oct 04, 2015 - 03:58pm
  • piotrekfronc's picture
    piotrekfronc (not verified)

    Still - waiting for newest kernel to be fixed - there are some lags when dealing with FS, but nothing major.

    Oct 05, 2015 - 12:51am
  • cchafe's picture
    cchafe (not verified)

    Bingo! That did the trick. Same antique Samsung monitor but I switched from miniDisplay port -> VGA adapter to miniDisplay port -> DVI adapter and the NUC display is fine with current fedora 22.




    Oct 06, 2015 - 08:53am
  • fledermaus's picture
    fledermaus (not verified)

    Chris - in addition to switching the cable, did you have to do anything else? Which kernel did you end up going with?

    Oct 06, 2015 - 10:23am
  • cchafe's picture
    cchafe (not verified)

    I only switched the cable. Kernel presently in use = 4.1.8-200.fc22.x86_64

    Oct 25, 2015 - 11:30am
  • fledermaus's picture
    fledermaus (not verified)

    Ok - thanks - that's a useful piece of information and not one I would have thought of asking for.

    Oct 27, 2015 - 05:02am
  • fledermaus's picture
    fledermaus (not verified)

    Hi guys - not sure if you are still watching this thread but Intel are chasing the bug here:

    and it looks like they could use some more info to help reproduce and pin
    down the problem - So if you see this, it would be great if you could head over
    to the bug and comment.

    Jan 12, 2016 - 09:01am