Sierra update 10.12.2 boot stuck at: busy timeout[0], (60s), kext wait(1)

[Rudi48]

Hello,
Sierra 10.12.1 works without problem.
Mainboard: Gigabyte Z87M-D3H
CPU: I3-4330 Haswell
Graphic: Intel HD4600
Clover is on actual revision 3961.
Clover RTVariables 0x67.

Unfortunately the Sierra 10.12.2 combo update got stuck at boot time with the message:
busy timeout[0], (60s), kextd wait(1): <special characters>, please see at the screen shot.

I have already tried with "Safe boot", but it did not help.

Now I need a hint please, were to look for further trouble schooting.

 

[friseruse]

I had this issue yesterday, but apparently for no reason (no update or whatsoever). I managed to solve this in booting with my Sierra instal USB stick (F12 in Bios and choose to boot from the USB stick).
Then I backed-up the clover files of the EFI directory of my OS X drive, and built a next config file based on the USB clover.
I managed to reboot, and ran multibeast to install the missing drivers.
Hope this helps

 

[Rudi48]

Hello friseruse,
Thank you for the hint, I will try it tommorow.
Regards, Rudi48

 

[RehabMan]

Hello,
Sierra 10.12.1 works without problem.
Mainboard: Gigabyte Z87M-D3H
CPU: I3-4330 Haswell
Graphic: Intel HD4600
Clover is on actual revision 3961.
Clover RTVariables 0x67.

Unfortunately the Sierra 10.12.2 combo update got stuck at boot time with the message:
busy timeout[0], (60s), kextd wait(1): <special characters>, please see at the screen shot.

I have already tried with "Safe boot", but it did not help.

Now I need a hint please, were to look for further trouble schooting.

"Waiting for DSMOS" without a corresponding "DSMOS has arrived" implies that FakeSMC is missing or not loading.

 

[Rudi48]

Hello,
I tried the following:
1. Made a new Sierra 10.12.1 USB boot stick, with UniBeast 7.0.1.
I can boot my Sierra 10.12.1 backup partition, but not the 10.12.2 updated partition (SSD).

2. Updated the FakeSMC.kext in EFI (SSD) from 6.14 (2015-05-04) to actual 6.21-311.
Unfortunately it did not help.

Thank yout your help.

Now I am back to busy using google.de
Regards, Rudi48

 

[RehabMan]

Hello,
I tried the following:
1. Made a new Sierra 10.12.1 USB boot stick, with UniBeast 7.0.1.
I can boot my Sierra 10.12.1 backup partition, but not the 10.12.2 updated partition (SSD).

2. Updated the FakeSMC.kext in EFI (SSD) from 6.14 (2015-05-04) to actual 6.21-311.
Unfortunately it did not help.

Thank yout your help.

Now I am back to busy using google.de
Regards, Rudi48

Make sure you're booting with kext injection.
Make sure FakeSMC.kext is in the correct place (EFI/Clover/kexts/Other).
Make sure you have a good version of Clover.

 

[smixreg]

I think there's more to this than hackintosh specific configuration. I'm getting exactly the same symptoms on a 'real' MacBook Pro and – judging by a few posts that have appeared online today, including in Apple's own discussion forums, this is not an isolated incident.

 

[Rudi48]

After a day trial and error the following can be stated.

I have 3 system partitions:
1. SSD1 (Mac OS 10.12.1 updated to 10.12.2)
2. SYS1 harddisk (Mac OS backup #1, 10.12.1)
3. SYS2 harddisk (Mac OS backup #2, 10.11.5)
Copy tool: Carbon Copy Cloner version 3.4.5

It happens, that after updating SYS2 from SYS1 I also got a "busy timeout" while booting SYS2.
The solution to this problem was to erase partition SYS2 and copy again SYS1 to SYS2.
Then it works with booting.
The same happened while restoring partition SSD1 from partition SYS1.

Now I will stay with 10.12.1 and wait for version 10.12.3.

 

[Rudi48]

The problem is solved:

I had a mismatch of FakeSMC.kext versions in different folders, lets explain:
The kernel extension FakeSMC.kext could be in folders:
1. /Volumes/SSD1/EFI/EFI/CLOVER/kext/10.12/ # older FakeSMC.kext was here
2. /Volumes/SSD1/EFI/EFI/CLOVER/kext/Other/
3. /Volumes/SSD1/System/Library/Extensions/
4. /Volumes/SSD1/Library/Extensions/ # Multibeast 9.0.1 will write here FakeSMC.kext

The FakeSMC.kext version of Multibeast 9.0.1 is 6.21-311, as described in file Changes-9.0.1.txt

It is enough if FakeSMC.kext is in path /Volumes/SSD1/Library/Extensions/ only.

In order to find the version number of a FakeSMC.kext you can use a terminal command (adopt to your system):
$ cat /Volumes/WD1T-SYS1/System/Library/Extensions/FakeSMC.kext/Contents/Info.plist | grep -A 1 CFBundleShort
<key>CFBundleShortVersionString</key>
<string>6.14-291-g6b4497f.1655</string>
In this case the version number is 6.14-291-g6b4497f.1655

The path (Ort of the kernel extension, and the info if loaded (geladen, ja) can be seen with:
Click on Apple icon->About this mac->system report->Software->Extensions

I hope, that it will help somebody.

 

[Rudi48]

even i used the same trick...but after a few the system crash again....tray my kexts...and cross finger

My Mac OS works stable since a week now.

When I look at the "System Informations", those kernel extensions are there, but NOT loaded:
AppleIntelCPUPowerManagement:

Version: 219.0.0
Zuletzt geändert: 30.08.16, 03:06
Paket-ID: com.apple.driver.AppleIntelCPUPowerManagement
Geladen: Nein # not loaded
Erhalten von: Apple
Art: Intel
Architekturen: x86_64
64-Bit (Intel): Ja
Ort: /System/Library/Extensions/AppleIntelCPUPowerManagement.kext
Kext-Version: 219.0.0
Ladbar: Ja # loadable = yes
Abhängigkeiten: Erfüllt # dependencies OK
Signiert von: Software Signing, Apple Code Signing Certification Authority, Apple Root CA

AppleIntelCPUPowerManagementClient:

Version: 219.0.0
Zuletzt geändert: 30.08.16, 03:07
Paket-ID: com.apple.driver.AppleIntelCPUPowerManagementClient
Geladen: Nein # not loaded
Informationen: 219.0.0, Copyright © 2005-2016 Apple Inc. All rights reserved.
Erhalten von: Apple
Art: Intel
Architekturen: x86_64
64-Bit (Intel): Ja
Ort: /System/Library/Extensions/AppleIntelCPUPowerManagementClient.kext
Kext-Version: 219.0.0
Ladbar: Ja # loadable = yes
Abhängigkeiten: Erfüllt # dependencies OK
Signiert von: Software Signing, Apple Code Signing Certification Authority, Apple Root CA

Regards, Rudolf