Contribute
Register

[Guide] Intel Skylake NUC6 (and Skull Canyon) using Clover UEFI (NUC6i5SYK, NUC6i7KYK, etc)

Status
Not open for further replies.
RehabMan said:
Your problem is caused by using a text editor to edit your config.plist and then breaking plist syntax.
You inserted things in between <key>Trust</key> and <true/> that you should not have.

Using a plist editor such as Xcode or PlistEdit Pro will avoid such mistakes.
Click to expand...

I get that you must sort through heaps of garbage in support of this stuff. It must be incredibly frustrating. I couldn't do it and I am an OS developer by profession.

A known good reference would be hugely helpful. I'd much rather just check against something that is known to work than beg for help on a forum.

Anyway, I've fixed what I assume is the issue. The break between the Trust key and <true> value between the serials. It was a mistake to be sure. I still have a single display. I've attached the new archive.
 

Attachments

  • debug_26028.zip
    2.6 MB · Views: 99
relative78 said:
I get that you must sort through heaps of garbage in support of this stuff. It must be incredibly frustrating. I couldn't do it and I am an OS developer by profession.

A known good reference would be hugely helpful. I'd much rather just check against something that is known to work than beg for help on a forum.

Anyway, I've fixed what I assume is the issue. The break between the Trust key and <true> value between the serials. It was a mistake to be sure. I still have a single display. I've attached the new archive.
Click to expand...

No ioreg in this debug zip. Please check your files before upload.

Also, your drivers64UEFI is not per guide (and is seriously wrong).
Read here:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
Ok, I've cleared out drivers64UEFI to match what's in the post, plus apfs.efi since I wasn't sure if it was just a artifact of the example being an older post.

Attached is the updated debug.zip. Now it has the real ioreg output.
 

Attachments

  • debug.zip
    3.6 MB · Views: 86
relative78 said:
Ok, I've cleared out drivers64UEFI to match what's in the post, plus apfs.efi since I wasn't sure if it was just a artifact of the example being an older post.

Attached is the updated debug.zip. Now it has the real ioreg output.
Click to expand...

apfs.efi should not be placed in drivers64UEFI. That is the job of ApfsDriverLoader-64.efi.

It appears you have deleted or corrupted your native graphics kexts. Use the macOS installer to restore them.
 
Ok, I've moved apfs.efi out of the way. The kexts seem ok though, but they're 10.14.1 not 10.14. I compared the md5sums of all the extensions in /System/Library/Extensions to the extensions on my non-Hack Mac and they match. There aren't any graphics kexts missing. I suppose I can try restoring the extensions from 10.14 and see if that makes a difference.
 
relative78 said:
Ok, I've moved apfs.efi out of the way. The kexts seem ok though, but they're 10.14.1 not 10.14. I compared the md5sums of all the extensions in /System/Library/Extensions to the extensions on my non-Hack Mac and they match. There aren't any graphics kexts missing. I suppose I can try restoring the extensions from 10.14 and see if that makes a difference.
Click to expand...

As suggested in post #54, "run the macOS installer" to restore your system kexts.
 
I've re-run the macOS installer. As expected, no change. The md5sums of all the extensions are identical to what they were before re-running it.
 
I went back and reviewed the BIOS settings. I had IGD Minimum memory and IGD Aperture size both set to 128MB, which worked fine with High Sierra. When I set them to 64/256, I have a working GPU on Mojave. Acceleration works and my mini-DP-attached display lit right up when plugged in.

- Devices->Video, "IGD Minimum Memory" set to 64mb (I found both 64mb and 128mb work fine)
- Devices->Video, "IGD Aperture Size" set to 256mb (I found both 128mb and 256mb work fine)

So it seems that the 128 MB settings no longer work fine.
 
relative78 said:
I went back and reviewed the BIOS settings. I had IGD Minimum memory and IGD Aperture size both set to 128MB, which worked fine with High Sierra. When I set them to 64/256, I have a working GPU on Mojave. Acceleration works and my mini-DP-attached display lit right up when plugged in.

- Devices->Video, "IGD Minimum Memory" set to 64mb (I found both 64mb and 128mb work fine)
- Devices->Video, "IGD Aperture Size" set to 256mb (I found both 128mb and 256mb work fine)

So it seems that the 128 MB settings no longer work fine.
Click to expand...

I'm currently using 128/256 without issue.
 
FYI: NUC7i7KYK (Skull Canyon) updated to 10.14.2 without any apparent issue.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top