[Guide] Intel Broadwell NUC5 using Clover UEFI (NUC5i5MHYE, NUC5i3MYHE, etc)

[esa007]

Your config.plist is not up-to-date with respect to current github content.

I made an update and changed to the last config.plist.

The behavior of start process changes a little:

nuc)miniDP ---------- DP(LG) Resolution 3840x2160 / 60 Hz
- BIOS ok, Clover ok,
- OS-Boot at the end the Logo gets bigger
- switch to the Login Screen for a short Moment and then the Monitor gets dark
- wating around 1 minute and the login screen comes back.

 

[RehabMan]

I made an update and changed to the last config.plist.

The behavior of start process changes a little:

nuc)miniDP ---------- DP(LG) Resolution 3840x2160 / 60 Hz
- BIOS ok, Clover ok,
- OS-Boot at the end the Logo gets bigger
- switch to the Login Screen for a short Moment and then the Monitor gets dark
- wating around 1 minute and the login screen comes back.

No ioreg in your debug zip. Please check your files prior to upload.

 

[esa007]

No ioreg in your debug zip. Please check your files prior to upload.

I followed all procedures to create a debug file and used your tool gen_debug.
The tool failed to add the ioreg, why ever... and it adds a generic IOREG report.




Here is one generated manually, but i am not sure if it's correct.

 

[RehabMan]

I followed all procedures to create a debug file and used your tool gen_debug.
The tool failed to add the ioreg, why ever... and it adds a generic IOREG report.

View attachment 369615

But reports for gen_debug.sh should be reported to its author, not me.

Here is one generated manually, but i am not sure if it's correct.

Your NUC has what kind of external connectors?
One HDMI, one DP?
If it has any HDMI ports, you must enable the matching patch (framebuffer-con1-enable or framebuffer-con2-enable, depending on which is the HDMI).

Also, for the 4k connected to DP, you might want to set a resolution via SysPrefs. Maybe that will help.

You may need larger VRAM setting (some report that as helping with Skylake/KabyLake, for example). You can patch it with WhateverGreen (framebuffer-unifiedmem).

 

[esa007]

Your NUC has what kind of external connectors?
..

You may need larger VRAM setting (some report that as helping with Skylake/KabyLake, for example). You can patch it with WhateverGreen (framebuffer-unifiedmem).

My Nuc has 2 connectors: 1. miniHDMI and 2. mini DP
I have enabled the hdmi patch for con-1 now, as ist was already described in this thread

Some tests with the sysPrefs dosen't change the boot behavior

I will make some tests with the vram settings, after reading some more informations about WhateverGreen, because this is all new for me.

thanks again for your support.

 

[RehabMan]

My Nuc has 2 connectors: 1. miniHDMI and 2. mini DP
I have enabled the hdmi patch for con-1 now, as ist was already described in this thread

The ioreg in #53 proves your assertion false:

 

[charlieroot]

Hello,
on my NUC5i7RYH system exits abnormally from S1/S2/S3 sleep. More specifically even if the power led turns blue (so system wakes) display doesn't show anything (black screen), usb ports are dead (ie: keyboard unresponsive) and networking never starts (icmp/tcp connections to the host going in timeout).

S4 disabled as described in post #1 (/var/vm/sleepimage/ workaround)

Report files attached, thanks

 

[esa007]

The ioreg in #53 proves your assertion false:
View attachment 369849

yes in #53 it was wrong, after the update to the new config.plist I forgot update this settings
Now it looks like this:

 

[RehabMan]

Hello,
on my NUC5i7RYH system exits abnormally from S1/S2/S3 sleep. More specifically even if the power led turns blue (so system wakes) display doesn't show anything (black screen), usb ports are dead (ie: keyboard unresponsive) and networking never starts (icmp/tcp connections to the host going in timeout).

S4 disabled as described in post #1 (/var/vm/sleepimage/ workaround)

Report files attached, thanks

Check BIOS settings (make sure latest BIOS, correct BIOS settings as per post #1).
Remove unneeded software: com.nomachine.driver.nxau, Virtualbox

 

[RehabMan]

yes in #53 it was wrong, after the update to the new config.plist I forgot update this settings
Now it looks like this:
View attachment 369853

Any change requires new problem reporting files. None attached.