Contribute
Register

UtterDisbelief Goes Small - NUC10 i5 UHD630 32GB

@UtterDisbelief .. may you help me, please... i would like little rise CPU power... Did you use anytime this?

  • Package Power Limit 1 (Sustained): The power will not exceed the set value. The value should be set so that it is equal to the thermal design power (TDP) and not higher than the thermal solution cooling limits.
  • Package Power Limit 2 (Burst Mode): If the value is exceeded, the rapid power-limiting algorithms will attempt to limit any spikes above that value.
  • Package Power Time Windows (Tau): An averaging constant used for PL1 exponential weighted moving average (EWMA) power calculation.
TNX, BR SEba
 
@UtterDisbelief ; please, can you do favor to me, can you start system with system report in mics-->debug and see what error it will give you. Because, I used your EFI, and I got same errors that I already had with my EFI.
 
UtterDisbelief said:
Update no.3 - Monterey

With the imminent arrival of macOS Sonoma, Big Sur will no-longer get updates from Apple. They only support the latest three macOS versions.

So that this build will keep up-to-date with security patches I've installed Monterey in preparation, created a new EFI folder and attached it here. The system still uses OpenCore 0.9.3. You can update this if you wish, but at present there is no need.


**As usual the included serial-numbers and UUIDs are dummies. Please create your own unique ones.**

:)
​
Click to expand...
i get this error eb.wl.pwlfnv err(0xe) - rt.gv wake-failure
 
Sebseb82 said:
@UtterDisbelief ; please, can you do favor to me, can you start system with system report in mics-->debug and see what error it will give you. Because, I used your EFI, and I got same errors that I already had with my EFI.
Click to expand...

Hi there.

Sorry to be so late in replying.

At the moment I am running a new hacktintosh - the Gigabyte B760 - which I have been concentrating on. So my NUC is back in it's storage box for the time being.

I didn't have the problems you are experiencing. Everything worked well, including the power-management for wake and sleep. This needs the specific BIOS settings I explain in the build to work properly. I did a lot of rigorous testing before I uploaded the EFI and did not have any wake-failure errors.

Mind you, I did not try to change the CPU power settings for more speed, but just left the defaults in place.

Sorry I am unable to go further at this time. :)
 
UtterDisbelief 2020
Z390 M GAMING |  i5 9600K |  Radeon Other
UtterDisbelief CL
Z370M-DS3H |  i3 8350K |  Radeon Other
UtterDisbelief KL
GA-Z270-Gaming K3 |  i3 7320 |  GeForce GTX 1050 OC
Yep... just done one of these straight to "Monterey" using the updated EFI supplied here.

Sound works straight to HDMI, wifi & BLE work.

Sadly the GPU would not pull you out of the bed in the morning, 7D2D is a bust...
but as a replacement for a Mac Mini 2012 it's fine.
 
Well this is new...
As soon as I removed the USB I use to configure it, it wont boot to the internal SSD.

I put the USB stick back in and it works..., it looks like something funky with the boot loader , needing to be on the USB to kick start the loading from the SSD.
 
hardcorefs said:
Well this is new...
As soon as I removed the USB I use to configure it, it wont boot to the internal SSD.

I put the USB stick back in and it works..., it looks like something funky with the boot loader , needing to be on the USB to kick start the loading from the SSD.
Click to expand...

If it's the original EFI folder you have transferred to the SSD EFI partition, then it sounds like the drive might be formatted incorrectly or corruption has occurred. Otherwise ZIP and attach the SSD EFI folder so we can check it?
 
UtterDisbelief 2020
Z390 M GAMING |  i5 9600K |  Radeon Other
UtterDisbelief CL
Z370M-DS3H |  i3 8350K |  Radeon Other
UtterDisbelief KL
GA-Z270-Gaming K3 |  i3 7320 |  GeForce GTX 1050 OC
I just spent the worst afternoon with a clone....

The NUC just kept saying "no bootable devices found" even though I re-did it a number of times & followed the article.

In the end I suspected faulty hardware, since it was showing the SSD in the BIOS,
but saying not bootable.

So I installed Win 10 and it worked first time... and would boot.

So even when I put the OC & boot folder back in, it went directly to the Windows boot.

folders were
APPLE OC BOOT MICROSOFT
so I renamed the folder "Microsoft" to "zmicrosoft"

same boot problem. "no bootable device"

I renamed the zmicrosoft back to microsoft; and
then I copied the "BOOT" folder again".

It still booted back into MS.
Finally, I went into the MS folder and removed the *.EFI" files,
and bizarrely it now is booting correctly, without a USB and directly into the macOS.

And the EFI partition folder is now called "no name" and works perfectly.

So.....

As regards to your files , corrupting... nope .. I used MD5 to check them all, and they were fine.
What I copied was the same checksum, both sides.

And, if it was the format of the EFI partition being wrong, then it would not boot the Windows...

It's clearly some incompatibility with the NUC boot.
But there is no debug at this stage of the boot process.


anyway ... ill leave it over night, then gradually delete stuff that does not belong in the EFI partition.
 
hardcorefs said:
I just spent the worst afternoon with a clone....

The NUC just kept saying "no bootable devices found" even though I re-did it a number of times & followed the article.

In the end I suspected faulty hardware, since it was showing the SSD in the BIOS,
but saying not bootable.

So I installed Win 10 and it worked first time... and would boot.

So even when I put the OC & boot folder back in, it went directly to the Windows boot.

folders were
APPLE OC BOOT MICROSOFT
so I renamed the folder "Microsoft" to "zmicrosoft"

same boot problem. "no bootable device"

I renamed the zmicrosoft back to microsoft; and
then I copied the "BOOT" folder again".

It still booted back into MS.
Finally, I went into the MS folder and removed the *.EFI" files,
and bizarrely it now is booting correctly, without a USB and directly into the macOS.

And the EFI partition folder is now called "no name" and works perfectly.

So.....

As regards to your files , corrupting... nope .. I used MD5 to check them all, and they were fine.
What I copied was the same checksum, both sides.

And, if it was the format of the EFI partition being wrong, then it would not boot the Windows...

It's clearly some incompatibility with the NUC boot.
But there is no debug at this stage of the boot process.


anyway ... ill leave it over night, then gradually delete stuff that does not belong in the EFI partition.
Click to expand...
normally your EFI partition will have a folder called EFI inside and in that would be the 2 folders OC and BOOT....
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top