Contribute
Register

New Intel NUC NUC8i7BEH compatibily

Status
Not open for further replies.
They released an update 3 days ago.

Not available in latest release.
You might want to try building master and see if it makes any difference

I will check it, but I think the issue I'm seeing is related to CPU detect.
 
This is what I am planning to get as soon as someone finds a way to get Iris 655 running on it.
Have you got it running? If not, here is a list of things I would test
  • Mojave
  • IntelGFX 0x3EA58086 Fake ID
  • ig-platform-id 0x3EA50000 / 0x3EA50004 / 0x3EA50009
  • SMBIOS MacBookPro15,1 / MacBookPro15,2
  • update to latest BIOS

I finally got Mojave freshly installed. Previously I was stuck at "12 minutes left" in the installation process seems to be caused by corrupted file / bad usb disk. This time I used a .dmg file and write the whole file to usb disk with "dd".

During the install, the system will reboot 2 times. The first time is at "2 minutes left", and the second time at "less than a minute left". Since I haven't figured out how to make the power management work, the installer just freeze at the reboot point and I have to manually long press the power button to shut it down.

Screen Shot 2018-10-10 at 6.41.27 PM.png

However, I still wasn't able to get Iris 655 running with acceleration. Tried many different ways, different config, kext, ids, and I saw at least 5 different panic errors.

NUC8i5BEK Tests.png

Sometimes during the boot process, I can see something like "Using 3D Driver", "Render Compression Enabled". Looks like the graphic driver almost worked, but the system just freeze there.

IGPU Message.png

I agree with RehabMan that the Coffee Lake system is too new to be stable. Maybe next BIOS update or next WhateverGreen version can fix some issues. Thanks.
 
I finally got Mojave freshly installed. Previously I was stuck at "12 minutes left" in the installation process seems to be caused by corrupted file / bad usb disk. This time I used a .dmg file and write the whole file to usb disk with "dd".

During the install, the system will reboot 2 times. The first time is at "2 minutes left", and the second time at "less than a minute left". Since I haven't figured out how to make the power management work, the installer just freeze at the reboot point and I have to manually long press the power button to shut it down.

View attachment 357298
However, I still wasn't able to get Iris 655 running with acceleration. Tried many different ways, different config, kext, ids, and I saw at least 5 different panic errors.

View attachment 357299

Sometimes during the boot process, I can see something like "Using 3D Driver", "Render Compression Enabled". Looks like the graphic driver almost worked, but the system just freeze there.

View attachment 357300

I agree with RehabMan that the Coffee Lake system is too new to be stable. Maybe next BIOS update or next WhateverGreen version can fix some issues. Thanks.

I finally gave up with the installer. Ended up installing 10.12.6, 10.13.6, 10.14.0 (and even a 10.14.1 beta release). Installed all with my NUC7, then moved the SSD (a WD Black NVMe 256GB, set to 4k LBA) to the NUC8i7BEH, so I could start experimenting with full QE/CI, USB, and audio.

IGPU memory should be set 64mb. It is usually adequate for most ig-platform-id values. It is strange though that BIOS does not allow for larger values.

QE/CI works two ways:
- native CFL: no device-id injection needed, AAPL,ig-platform-id=<0000a53e> (0x3ea50000)
- spoofed KBL: device-id=<59270000>, AAPL,ig-platform-id=<00002759> (0x59270000)+WhateverGreen.kext

In the native CFL case, WhateverGreen.kext is not actively patching the framebuffer (it is patching the QE kext, as it is same kext used in KBL) because the CPU is being mis-identified as KBL instead of CFL. That needs to be fixed. Will be looking at that next.

Audio works with layout-id=3, AppleALC.kext, and a slightly modified FakePCIID_Intel_HDMI_Audio.kext (+FakePCIID.kext). Will update the official FakePCIID kexts soon. The modified FakePCIID kexts keep AppleGFXHDA.kext (it is an alternate/specific AppleHDAController class) from loading, which allows AppleHDAController to load instead. HDMI audio as well as onboard (just tested headphones) is working... haven't paid much attention to quality.

I have a UIAC configuration for USB already done too. The USB controller is native in Mojave, but 10.13 and 10.12 require XHCI-300-series-injector.kext.

The SATA controller (even though I'm not using it, using NVMe instead) is unsupported (by all versions) and needs SATA-300-series-unsupported.kext.

Ethernet with IntelMausiEthernet.kext, of course.

So, far, it seems stable when running (limited testing obviously), but ...

The main problem I have at this point is that shutdown or restart causes a hang (sleep too). I doubt fixing WhateverGreen.kext will help, but I'll do that first before continuing. Then I have a bunch of other things to try...

Do you have the lockup problem on restart/shutdown on your system?
 
Last edited:
I finally gave up with the installer. Ended up installing 10.12.6, 10.13.6, 10.14.0 (and even a 10.14.1 beta release). Installed all with my NUC7, then moved the SSD (a WD Black NVMe 256GB, set to 4k LBA) to the NUC8i7BEH, so I could start experimenting with full QE/CI, USB, and audio.

IGPU memory should be set 64mb. It is usually adequate for most ig-platform-id values. It is strange though that BIOS does not allow for larger values.

QE/CI works two ways:
- native CFL: no device-id injection needed, AAPL,ig-platform-id=<0000a53e> (0x3ea50000)
- spoofed KBL: device-id=<59270000>, AAPL,ig-platform-id=<00002759> (0x59270000)+WhateverGreen.kext

In the native CFL case, WhateverGreen.kext is not actively patching the framebuffer (it is patching the QE kext, as it is same kext used in KBL) because the CPU is being mis-identified as KBL instead of CFL. That needs to be fixed. Will be looking at that next.

Audio works with layout-id=3, AppleALC.kext, and a slightly modified FakePCIID_Intel_HDMI_Audio.kext (+FakePCIID.kext). Will update the official FakePCIID kexts soon. The modified FakePCIID kexts keep AppleGFXHDA.kext (it is an alternate/specific AppleHDAController class) from loading, which allows AppleHDAController to load instead. HDMI audio as well as onboard (just tested headphones) is working... haven't paid much attention to quality.

I have a UIAC configuration for USB already done too. The USB controller is native in Mojave, but 10.13 and 10.12 require XHCI-300-series-injector.kext.

The SATA controller (even though I'm not using it, using NVMe instead) is unsupported (by all versions) and needs SATA-300-series-unsupported.kext.

Ethernet with IntelMausiEthernet.kext, of course.

So, far, it seems stable when running (limited testing obviously), but ...

The main problem I have at this point is that shutdown or restart causes a hang (sleep too). I doubt fixing WhateverGreen.kext will help, but I'll do that first before continuing. Then I have a bunch of other things to try...

Do you have the lockup problem on restart/shutdown on your system?

Yes, I have the same problem on restart/shutdown. After I click restart or shutdown, the system just freeze (cpu halted) after I saw those messages:

Shutdown Message.png


No error messages or "MACH Reboot". I have no clue how to debug this.

Another thing I've tried is to boot into single user mode and restart/shutdown using "shutdown" command. Surprisingly the system can be shutdown or reboot normally without any issues.

About the SATA controller, I just disabled it in BIOS since I only use NVMe. This way the SATA-300-series-unsupported.kext may not be needed.

Hope those information helps. Thanks.
 
Yes, I have the same problem on restart/shutdown. After I click restart or shutdown, the system just freeze (cpu halted) after I saw those messages:

View attachment 357725

No error messages or "MACH Reboot". I have no clue how to debug this.

Another thing I've tried is to boot into single user mode and restart/shutdown using "shutdown" command. Surprisingly the system can be shutdown or reboot normally without any issues.

About the SATA controller, I just disabled it in BIOS since I only use NVMe. This way the SATA-300-series-unsupported.kext may not be needed.

Hope those information helps. Thanks.

OK, at least we're in the same boat.

BTW, I have created a branch (nuc8bc) of my NUC github repo for this NUC8i7BEH (and likely the other NUC8 Bean Canyon models).

Will probably merge it to master soon (actually: DONE), but not sure if I'll publish a full guide until the shutdown/sleep/restart problem is solved.
https://github.com/RehabMan/Intel-NUC-DSDT-Patch

The guide for the NUC7 can be used as a base if you're wondering how to use the repo.
Only difference is different config.plist files: config_install_nuc8_bc.plist, config_nuc8_bc.plist and different ACPI installer in the makefile: 'make install_nuc8bc'.

There are still a few other things (besides the restart/shutdown/sleep issue) to test/fix but it is pretty close.
 
Last edited:
I will check it, but I think the issue I'm seeing is related to CPU detect.

It is as I suspected. Lilu does not detect the i7-8559U as CoffeeLake.
It detects it as KabyLake.
The work around is to use kernel flag lilucpu=10 to force detect as CoffeeLake.

With that you can use WhateverGreen to patch the CFL framebuffer connectors/etc.
 
OK, at least we're in the same boat.

BTW, I have created a branch (nuc8bc) of my NUC github repo for this NUC8i7BEH (and likely the other NUC8 Bean Canyon models).

Will probably merge it to master soon (actually: DONE), but not sure if I'll publish a full guide until the shutdown/sleep/restart problem is solved.
https://github.com/RehabMan/Intel-NUC-DSDT-Patch

The guide for the NUC7 can be used as a base if you're wondering how to use the repo.
Only difference is different config.plist files: config_install_nuc8_bc.plist, config_nuc8_bc.plist and different ACPI installer in the makefile: 'make install_nuc8bc'.

There are still a few other things (besides the restart/shutdown/sleep issue) to test/fix but it is pretty close.

Thank you for updating the NUC GitHub repo. I just tried it on my NUC8i5BEK followed your NUC7 guide:
Code:
./download.sh
./install_downloads.sh
make
make install_nuc8bc
./mount_efi.sh
cp config_nuc8_bc.plist /Volumes/EFI/EFI/Clover/config.plist

Here is my test result:
  1. Graphic Acceleration still not work
  2. Audio still not work
  3. Restart/Shutdown still not work, of course
I assume Lilu and WhateverGreen still have some issues to be fixed, so the graphic not working isn't a surprise for me. I also tried lilucpu=10 kernel parameter, but it just gives me different kernel panics.

Initially after I installed your nuc8bc patch, the system hangs during boot. I tried multiple ways. Currently the only way to get my system booted (still without graphic acceleration) is to delete the ACPI/Patched folder.

NUC8_bc_tests.png


Regarding Audio, neither headphone jack nor HDMI audio worked. There is no audio device in the System Report. During boot, there is a message:
Code:
CodecCommander: stopping due to codec profile Disable flag

I didn't see any audio related stuff, such as -ccoff, in kernel parameters. Maybe I need to edit config file of the kext CodecCommander. I haven't looked that far yet.

Let me know if there are anything I did wrong during the test. I can provide gen_debug dump if it helps. Thank you.
 

Attachments

  • NUC8_bc_panic.png
    NUC8_bc_panic.png
    2.2 MB · Views: 276
Last edited:
I can provide gen_debug dump if it helps.

Required, as per guide post #1.

Also, I don't know if it matters, but I'm currently using WhateverGreen.kext 1.2.4 (built from sources), not the WhateverGreen.kext on the github Releases page. The download.sh script will download from github. Eventually, the WhateverGreen.kext there will be updated and then you would not need to custom install the latest build.

I had a KP initially (really a reboot)... but was able to boot with -liluoff, then rebuild cache, then reboot... Maybe because we don't have a properly created LiluFriend.kext (I'm working on a script that will automatically create an appropriate LiluFriend or LiluFriendLite based on Lilu kexts in /L/E and /S/LE).
 
Last edited:
Required, as per guide post #1.

Also, I don't know if it matters, but I'm currently using WhateverGreen.kext 1.2.4 (built from sources), not the WhateverGreen.kext on the github Releases page. The download.sh script will download from github. Eventually, the WhateverGreen.kext there will be updated and then you would not need to custom install the latest build.

I had a KP initially (really a reboot)... but was able to boot with -liluoff, then rebuild cache, then reboot... Maybe because we don't have a properly created LiluFriend.kext (I'm working on a script that will automatically create an appropriate LiluFriend or LiluFriendLite based on Lilu kexts in /L/E and /S/LE).
Thank you for the info. Here is the gen_debug dump. I was using WhateverGreen.kext v1.2.3 release. I suspect that was the reason. I'll try to use v1.2.4 build when I get a chance. Thanks.
 

Attachments

  • debug_20959.zip
    3 MB · Views: 142
Thank you for the info. Here is the gen_debug dump. I was using WhateverGreen.kext v1.2.3 release. I suspect that was the reason. I'll try to use v1.2.4 build when I get a chance. Thanks.

Yeah, and your current EFI/Clover cannot be expected to work. For example, you're patching _OSI->XOSZ but have no XOSI method. It is in SSDT-NUC8-BC.aml, but your SSDT-NUC8-BC.aml is not loading as you have no ACPI/patched with it.

Also, your config.plist has a lot of diffs from the github plist... maybe because it was manged by Clover Configurator (don't use Clover Configurator, as you never know what it is going to change).

But yeah, I haven't tested with 1.2.3... as I'm building current WhateverGreen locally and using that. And I think we do need LiluFriend (going with my LiluFriendLite initially to see if works without having an actual LiluFriend binary). Otherwise you need the -liluoff, rebuild cache, reboot sequence to get a stable kernel cache for Lilu plugins.

The changes for LiluFriend are almost ready.

Check your BIOS settings/BIOS version too.
 
Status
Not open for further replies.
Back
Top