Contribute
Register

AppleACPICPU timeout before reaching installer

Status
Not open for further replies.
Had the exact same problem, just update the bootloader (clover), I was mistakingly using an old version
 
Absolutely no problem Weezul! Personally with the way you setup your clover bootloader if I am correct in saying you used a system from insanelymac, I would create a bootloader config that is based on your system from scratch; but all to their own.
If you need anything else post in the forums!

Hey,
Sorry I used my own config.plist, based upon my old system, but tweaked for this. Thanks again
 
Help can t reach installer got a nvidia 520 always works out of the box now i got this error
 

Attachments

  • 20160824_224501.jpg
    20160824_224501.jpg
    4.3 MB · Views: 1,143
I've been running into a wall here, I keep getting an error:

busy timeout[0], (240s) kextd wait(0): 'AppleACPICPU'

I've tried with Clover r3577, 3599 & 3602. Used the config files supplied with the OP in the USB creation thread as well as mine, confirmed working, config. Not really sure what's causing it, but I wonder would this possibly prevent me from updating El Cap to Sierra in a few months?
i got this problem after update Sierra 16A201w to DP8.
*Yosemite/Capitan Mode
1.BackUp folder CLOVER in EFI Partition
2.Update latest Clover
3.Replace folder CLOVER to EFI Partition
5.Done
 

Attachments

  • 14195239_10206354970587081_7922899343191481599_o.jpg
    14195239_10206354970587081_7922899343191481599_o.jpg
    144.6 KB · Views: 1,365
  • Screen Shot 2016-09-01 at 9.12.18 PM.png
    Screen Shot 2016-09-01 at 9.12.18 PM.png
    221.9 KB · Views: 1,303
Have the same problem with a successful installation (Sierra and latest Clover). That is, when booting it all halts at
AppleACPICPU and then I get a non-responsive black screen. The way around it is to check Inject kexts in the Clover screen (press pace bar on the HD image before booting).

Now, all I have to do is find the right way to enable kext injection by default in my config.plist.
 
make sure that you are booting from the correct EFI. In my case, I was upgrading from ElCapitan and after installation, I forgot to change the boot device priority. And it started to boot from my ElCap EFI which gave me this error.
 
I had this problem but it was solved by simply using a different USB key (a decent branded one) as opposed to the no name brand I was using.

T
 
Status
Not open for further replies.
Back
Top