Contribute
Register

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

Leesureone said:
Its a different generation CPU, different graphics etc. so quite different. I notice you are not using Rehabman's config.plist for your device, not sure where you got the version you are using but is been modified. I would try his
Click to expand...
Ehm I didn’t use this one Bc I have the nuc7dc not the normal one so I’m using the DC version basically, but I tried it with both and even with the unchanged one (mine is now a bit changed) but I can try it, maybe it’s working now with all the fixes who knows.

EDIT 06:40 PM:

I tried the Nuc7.plist and Nuc7dc.plist but none of them worked (same as with mine but without sleep)

EDIT 2 @10:30 PM:
There is a small change that I found the issue, Intel releases a HDMI Firmware Update Bc the version before was buggy at the point sleeping (S3 State), so the device didn’t wake up anymore. I have to install now W10 on the other SSD and install it (Bc there is no other option to install it). Maybe this fixes this problem. When not I’m out of ideas.

greetings,
 
Last edited:
Nemphys said:
Good news, I just managed to sort the internal Bluetooth issue.

It is kind of a hack, but I couldn't find the time to go through the proper way (eg. creating a kext or something).

You just have to copy the files in the attached zip to the respective directories (just follow the directory structure inside the zip file; I suppose you will have to chown all copied files to root:wheel).

I don't know if the /opt dir selection for the binaries/firmware is optimal, but it works.

This solution uses an rc.boot script that checks if the firmware is already present (eg. after warm boot) and does the uploading using https://github.com/wulf7/iwmbt-firmware if it is not.

There is a small 4-5 seconds delay at the login window before bluetooth actually works, so be patient (this does not apply after a warm boot, since the firmware is already OK and the script does nothing).

In my case this makes internal bluetooth fully usable (and also improves some sleep issues I had with the Asus BT-400 bluetooth dongle)!

Confirmed working on NUC8i7BEH (Mojave), no idea if it works for older/other NUCs (I included a few firmware files apart from the one actually used for my hardware, one can always find more in the linux-firmware package).
Click to expand...

Thanks for the reply. It would be good to have bluetooth working. Thanks for the attached files I'll have a play today. It will be easy to reverse if it doesn't work I'll make a backup of my drive first.

I had read about having to reboot into windows/linux first for BT to work and that seemed a hassle and not worth it. Question about booting into Windows/linux if you go that road does that mean you only have to do that once as long as power remains on to the NUC?

Or does a reboot of the Apple OS break BT working and you have to again boot into say Windows for example. If BT kept working through restarts then that wouldn't be hard as I do have dual boot with Window 10 on seperate drives so that would be easy. I always presumed restarts would reset BT?

I'm running Catalina so I'll tell you if it works thanks again for the reply.
 
spottsy said:
Thanks for the reply. It would be good to have bluetooth working. Thanks for the attached files I'll have a play today. It will be easy to reverse if it doesn't work I'll make a backup of my drive first.

I had read about having to reboot into windows/linux first for BT to work and that seemed a hassle and not worth it. Question about booting into Windows/linux if you go that road does that mean you only have to do that once as long as power remains on to the NUC?

Or does a reboot of the Apple OS break BT working and you have to again boot into say Windows for example. If BT kept working through restarts then that wouldn't be hard as I do have dual boot with Window 10 on seperate drives so that would be easy. I always presumed restarts would reset BT?

I'm running Catalina so I'll tell you if it works thanks again for the reply.
Click to expand...

If you boot Windows/Linux once, then the firmware will stay on the adapter after reboot/power off. Only when you cut the power to the NUC (ie. pull the plug), does it get invalidated.

Using my fix, though, this does not apply; it works in macOS just like it does in Windows/Linux.
 
Nemphys said:
Good news, I just managed to sort the internal Bluetooth issue.

It is kind of a hack, but I couldn't find the time to go through the proper way (eg. creating a kext or something).

You just have to copy the files in the attached zip to the respective directories (just follow the directory structure inside the zip file; I suppose you will have to chown all copied files to root:wheel).

I don't know if the /opt dir selection for the binaries/firmware is optimal, but it works.

This solution uses an rc.boot script that checks if the firmware is already present (eg. after warm boot) and does the uploading using https://github.com/wulf7/iwmbt-firmware if it is not.

There is a small 4-5 seconds delay at the login window before bluetooth actually works, so be patient (this does not apply after a warm boot, since the firmware is already OK and the script does nothing).

In my case this makes internal bluetooth fully usable (and also improves some sleep issues I had with the Asus BT-400 bluetooth dongle)!

Confirmed working on NUC8i7BEH (Mojave), no idea if it works for older/other NUCs (I included a few firmware files apart from the one actually used for my hardware, one can always find more in the linux-firmware package).
Click to expand...

Great work!

Does this mean we can't login with bluetooth keyboard at the first boot?
 
Nemphys said:
If you boot Windows/Linux once, then the firmware will stay on the adapter after reboot/power off. Only when you cut the power to the NUC (ie. pull the plug), does it get invalidated.

Using my fix, though, this does not apply; it works in macOS just like it does in Windows/Linux.
Click to expand...

Thanks again for the reply. Will see if I can get it to work with catalina then. I'll let you know how I go thanks for the files too gives me a head start on what works for you.
 
ta_orz said:
Great work!

Does this mean we can't login with bluetooth keyboard at the first boot?
Click to expand...

No, login works fine on first boot (that is the whole point, after all); it just takes 4-5 seconds after the login screen appears for the keyboard/mouse to become active.
 
Nemphys said:
No, login works fine on first boot (that is the whole point, after all); it just takes 4-5 seconds after the login screen appears for the keyboard/mouse to become active.
Click to expand...

Great!

Your script in bluetooth_fix.zip works on Catalina (NUC8i5BEH). I'm going to test if it works at boot.

I needed rc.clover.lib from Clover to run the script.
And I needed to install libusb from homebrew for loading the firmware.

Thanks a lot!
 
ta_orz said:
Great!

Your script in bluetooth_fix.zip works on Catalina (NUC8i5BEH). I'm going to test if it works at boot.

I needed rc.clover.lib from Clover to run the script.
And I needed to install libusb from homebrew for loading the firmware.

Thanks a lot!
Click to expand...

rc.clover.lib is from the Clover rc scripts (can be installed using the installer). I already had them installed, but I think that the top part of the script (that sources rc.clover.lib) is not needed anyway. It should be safe to delete this part of the script and get rid of rc.clover.lib dependency. I will post an updated version if I find the time.

As for libusb, I already had this installed, too (the firmware downloader won't build without it). Didn't realise it would be needed at runtime, though.
 
Adding to this thread's activity lately—it's me again with my NUC's newly developed sleep problems:

They still exist, even without any Shimo tasks running. My machine managed 4 sleeps in the last two days and now it refuses to sleep again. In between I didn't change anything, didn't run any new apps. Every time I try to put it to sleep now, it takes really long until it reacts at all, at least 20 seconds (that was also the case when it used to work though), then it powers down into sleep for no more than one second, only to wake up again immediately. The system.log is incredibly unhelpful. This time there is not even a mention of "sleep" in there, even though I tried it multiple times. (I've attached a text file copy of the time period none the less.)

So yeah, it's pretty frustrating. I seem to never have any luck with my hackintosh builds.

I'm contemplating wiping the disk and redoing my whole installation, but this time living with no native digital sound output, but proper sleep instead. :-/
 

Attachments

  • systemlog-2019-12-10.txt
    7.2 KB · Views: 92
fourk said:
Ehm I didn’t use this one Bc I have the nuc7dc not the normal one so I’m using the DC version basically, but I tried it with both and even with the unchanged one (mine is now a bit changed) but I can try it, maybe it’s working now with all the fixes who knows.

EDIT 06:40 PM:

I tried the Nuc7.plist and Nuc7dc.plist but none of them worked (same as with mine but without sleep)

EDIT 2 @10:30 PM:
There is a small change that I found the issue, Intel releases a HDMI Firmware Update Bc the version before was buggy at the point sleeping (S3 State), so the device didn’t wake up anymore. I have to install now W10 on the other SSD and install it (Bc there is no other option to install it). Maybe this fixes this problem. When not I’m out of ideas.

greetings,
Click to expand...
I got news: The firmware update didn’t work and the sleep at all still not working .. I will reproduce the power management just in case.

I keep you informed.

greetings,
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top