Contribute
Register

[Guide] Intel NUC7/NUC8 using Clover UEFI (NUC7i7Bxx,NUC8i7Bxx,etc)

Joined
Nov 30, 2016
Messages
8
Motherboard
NUC8i5BEK
You will need to be very specific regarding what you mean by "change the HiDPI mode".
Show screen images and be very clear about which change you're making that causes the crash.
I cannot guess.
The burden is on you to provide accurate and detailed information.
OK, so I have a 4K monitor, and I want to change the HiDPI Scaling in the System Preferences (see attached screenshot)
It is in the "looks like 1920x1080" mode and when I want to change that into a different mode, the Nuc crashes.
 

Attachments

Last edited:

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
OK, so I have a 4K monitor, and I want to change the HiDPI Scaling in the System Preferences (see attached screenshot)
It is in the "looks like 1920x1080" mode and when I want to change that into a different mode, the Nuc crashes.
You still failed to provide any detail on which one of the 4 possible icons you may be selecting.

When I say you need to be detailed,...
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Any of them will crash the system except the last one (3840x2160)
So, it is any scaling mode (the last mode is native 3840x2160, so no scaling there).
I wonder why I had no issue with any of those scaling modes on my NUC8i7.

Did you try with the 4k monitor connected to HDMI instead of USB-C/DP?
Did you try with *only* the 4k monitor connected?
Just wondering if it is a different result or not.

Also, you might try patching the con1-flags:
In config.plist/Devices/Properties/PciRoot(0)/Pci(0x02,0), add:
framebuffer-con1-enable=1
framebuffer-con1-flags=<87010000>

That sets the flags to match ig-platform-id 0x3ea50000.
No idea what most of the flags mean, so it is just a guess.
 
Joined
Nov 30, 2016
Messages
8
Motherboard
NUC8i5BEK
So, it is any scaling mode (the last mode is native 3840x2160, so no scaling there).
I wonder why I had no issue with any of those scaling modes on my NUC8i7.

Did you try with the 4k monitor connected to HDMI instead of USB-C/DP?
Did you try with *only* the 4k monitor connected?
Just wondering if it is a different result or not.

Also, you might try patching the con1-flags:
In config.plist/Devices/Properties/PciRoot(0)/Pci(0x02,0), add:
framebuffer-con1-enable=1
framebuffer-con1-flags=<87010000>

That sets the flags to match ig-platform-id 0x3ea50000.
No idea what most of the flags mean, so it is just a guess.
Using only the 4K mon and also only this one with HDMi doesn't help.

I changed the config.plist, but did you mean framebuffer-con1-flags or framebuffer-con1-type as in the framebuffer-con0-type?
Also should I set ig-platform-id 0x3ea50000?

I did this all (ig-platform-id 0x3ea50000, framebuffer-con1-enable and tried both, framebuffer-con1-type and framebuffer-con1-flag) and it still crashes
 
Last edited:

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
but did you mean framebuffer-con1-flags or framebuffer-con1-type
I meant what I wrote.

Also should I set ig-platform-id 0x3ea50000?
Requires changes to SSDT-IGPU.dsl.

I did this all (ig-platform-id 0x3ea50000, framebuffer-con1-enable and tried both, framebuffer-con1-type and framebuffer-con1-flag) and it still crashes
I cannot tell what you're actually doing unless you attach PR files.

Note: The only major difference I can see (besides the CPU) between our systems is that you have 16GB RAM, I have 8GB.
 
Last edited:
Joined
Mar 29, 2014
Messages
18
Motherboard
NUC
CPU
i7
Graphics
HD 6100
Mac
Mac Pro
Classic Mac
128K, Color Classic, iMac, Power Mac, PowerBook, SE
Mobile Phone
Android
install_downloads.sh is to be run without 'sudo' as is written in the guide.
If you have a failure, you must provide details.
Using 'sudo' with install_downloads.sh is wrong (and once you do that, you must start over with ./download.sh).

Same goes for mount_efi.sh... if you have a failure, you must provide details. I cannot guess.

If you see no boot targets, your version of Clover is probably wrong or drivers64UEFI is wrong.
ApfsDriverLoader-64.efi is default in my build of Clover (which is the recommended Clover build, as written in the guide).
HFSPlus.efi always must be added manually, as written in the guide.

You are clearly not using the RehabMan build of Clover.

If you have an issue booting, you must provide verbose boot photo and other PR files that represent what you're doing.

You should check your BIOS version (must be latest) and BIOS settings... don't forget to enable "legacy boot" as is required with the NUC8.

Also, you need to provide other applicable details... such as what kind of monitor you're using, and which port it is connected to.
So I totally missed the part about using your Clover build vs. the community version. This made all the previous problems go away.

I created a new USB with your Clover, and put Moajve on and ran through all the post install options. It still seems like something is unstable as I'm still experiencing reboot issues. Yes, I have verified bios setting (using 0048) and legacy is enabled. no errors during install_downloads.sh and no errors during mount_efi.sh this time.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
So I totally missed the part about using your Clover build vs. the community version. This made all the previous problems go away.
It is not really required to use my build of Clover.
But you may get completely untested code if you use Clover from sourceforge.
I try to test Clover with various systems (eg. my guides) before I release a new RehabMan build of Clover.

I created a new USB with your Clover, and put Moajve on and ran through all the post install options. It still seems like something is unstable as I'm still experiencing reboot issues. Yes, I have verified bios setting (using 0048) and legacy is enabled. no errors during install_downloads.sh and no errors during mount_efi.sh this time.
No ioreg in your debug zip. Please check the files before upload.

Also, you will need to provide details on "reboot issues". I cannot guess...
 
Joined
Jul 4, 2013
Messages
64
Motherboard
NUC8i7BNH
CPU
i7 8559U
Graphics
UHD 655
Mac
MacBook Pro
Any of them will crash the system except the last one for the full resolution (3840x2160)
That is the exact behaviour I have. I have tested HDMI and USB-C cables. I will try the framebuffer patches you tell and come back to tell how it goes.
 
Joined
Nov 30, 2016
Messages
8
Motherboard
NUC8i5BEK
I meant what I wrote.



Requires changes to SSDT-IGPU.dsl.



I cannot tell what you're actually doing unless you attach PR files.

Note: The only major difference I can see (besides the CPU) between our systems is that you have 16GB RAM, I have 8GB.
Here's the current debug after setting the framebuffer patches.
..still crashing

Edit:
BTW, my NUC also crashes every time I want to update my invoicing app GrandTotal.
 

Attachments

Last edited:
Top