x.di Posted July 2, 2017 Share Posted July 2, 2017 System : Supermicro x9dri-f, 2 x e5-2670 , nvidia gtx 1060Mac os 10.12 is working perfectly. 10.13 panic https://dl.dropboxusercontent.com/s/f6fh0culodk5dyx/Panic_Mac_Os_10.13.jpeg The only way to boot 10.13 is to use AppleACPIPlatform.kext from Mac Os 10.12.5 . Link to comment Share on other sites More sharing options...
MNSiw Posted July 2, 2017 Share Posted July 2, 2017 System : Supermicro x9dri-f, 2 x e5-2670 , nvidia gtx 1060 Mac os 10.12 is working perfectly. 10.13 panic https://dl.dropboxusercontent.com/s/f6fh0culodk5dyx/Panic_Mac_Os_10.13.jpeg The only way to boot 10.13 is to use AppleACPIPlatform.kext from Mac Os 10.12.5 . And with this kext from 10.12 it booted and installed? Sent from my XT1060 using Tapatalk Link to comment Share on other sites More sharing options...
TheRacerMaster Posted July 2, 2017 Share Posted July 2, 2017 Can you post the panic output with keepsyms=1? Link to comment Share on other sites More sharing options...
byzyn4ik Posted July 3, 2017 Share Posted July 3, 2017 Have the same problem on ASUS Z9PE-D8 WS 2 x Intel Xeon 2680 ( v1). Will try to install with replaced kext. Link to comment Share on other sites More sharing options...
FredWst Posted July 14, 2017 Share Posted July 14, 2017 Hi, If this is this error you get, I solved it by dropping BGRT table I know strange ,,, but works for me. Try Pike trick but doesn't work for me. Fred Link to comment Share on other sites More sharing options...
TheRacerMaster Posted July 14, 2017 Share Posted July 14, 2017 Oh. That doesn't really have to do with AppleSMCRTC, that's just the AppleACPIPlatform bug with 10.13 (broken ACPI table header causes a panic). Link to comment Share on other sites More sharing options...
x.di Posted August 1, 2017 Author Share Posted August 1, 2017 Oh. That doesn't really have to do with AppleSMCRTC, that's just the AppleACPIPlatform bug with 10.13 (broken ACPI table header causes a panic). Is there a way to fix it? Tried to drop BGRT table , didn't worked. Here is the Darwin dump from High Sierra with replaced AppleACPIPlatform.kext from Mac Os 10.12.5 No way to boot with original AppleACPIPlatform.kext Maybe someone can point me in right direction ... DarwinDumper_3.0.3_29.06_04.56.32_MacPro61_AMI_X64_4097_Unknown_17A291j_lex.zip Link to comment Share on other sites More sharing options...
x.di Posted August 3, 2017 Author Share Posted August 3, 2017 Bump! Anyone ? Link to comment Share on other sites More sharing options...
x.di Posted August 6, 2017 Author Share Posted August 6, 2017 Meh... Link to comment Share on other sites More sharing options...
x.di Posted August 7, 2017 Author Share Posted August 7, 2017 Really need some help here Link to comment Share on other sites More sharing options...
Rocky12 Posted August 7, 2017 Share Posted August 7, 2017 Do Not Change the original AppleACPIPlatform.kext leave IT as IT is but u can copy the original AppleACPIPlatform.kext and Put into clover kext Folder 10.13 Link to comment Share on other sites More sharing options...
x.di Posted August 7, 2017 Author Share Posted August 7, 2017 Do Not Change the original AppleACPIPlatform.kext leave IT as IT is but u can copy the original AppleACPIPlatform.kext and Put into clover kext Folder 10.13 Tried , same AppleSmcRtc Panic Link to comment Share on other sites More sharing options...
Rocky12 Posted August 7, 2017 Share Posted August 7, 2017 APPLESMCRTC.KEXT PANICS Are you getting panics with some text about AppleSMCRTC.kext (adds support for boot argument rtc=0x03) and some dependancy failures for AppleSMC.kext (supports boot arguments smc= and smcdebug=0xf0) and AppleACPIPlatform.kext? Well. Someone asked me to look into this, and I did. Let’s start by showing you the ACPI device that Apple started to use (taken from the DSDT from the iMac19,1): Device (ARTC) { Name (_HID, "ACPI000E") Method (_GCP, 0, NotSerialized) // Get Capability (AppleACPIPlatform.kext) { // Bit [0] - 1 = AC wake implemented, 0 = not supported // Bit [1] - 1 = DC wake implemented, 0 = not supported // Bit [2] - 1 = Get/Set real time features implemented, 0 = not supported // Bit [3] - 1 = Real time accuracy in milliseconds, 0 = Real time accuracy in seconds // Bit [4] - 1 = _GWS returns correct values for wakes from S4/S5 caused by timer. 0 = not supported // Bit [5] to Bit [31] are reserved and must be 0. Return (0x05) } Method (_GRT, 0, Serialized) // Get Real Time (AppleACPIPlatform.kext) { Name (BUFF, Buffer (0x10) {}) Store (^^EC.YRLB, Index (BUFF, Zero)) Store (^^EC.YRMB, Index (BUFF, One)) Store (^^EC.MNTH, Index (BUFF, 0x02)) Store (^^EC.DAYB, Index (BUFF, 0x03)) Store (^^EC.HOUR, Index (BUFF, 0x04)) Store (^^EC.MINT, Index (BUFF, 0x05)) Store (^^EC.SECD, Index (BUFF, 0x06)) Store (^^EC.PAD0, Index (BUFF, 0x07)) Store (^^EC.MSLB, Index (BUFF, 0x08)) Store (^^EC.MSMB, Index (BUFF, 0x09)) Store (^^EC.TZLB, Index (BUFF, 0x0A)) Store (^^EC.TZMB, Index (BUFF, 0x0B)) Store (^^EC.DAYL, Index (BUFF, 0x0C)) Store (^^EC.PAD1, Index (BUFF, 0x0D)) Store (^^EC.PAD2, Index (BUFF, 0x0E)) Store (^^EC.PAD3, Index (BUFF, 0x0F)) Return (BUFF) } Method (_SRT, 1, Serialized) // Set Real Time (AppleACPIPlatform.kext) { Store (Index (Arg0, Zero), ^^EC.YRLB) Store (Index (Arg0, One), ^^EC.YRMB) Store (Index (Arg0, 0x02), ^^EC.MNTH) Store (Index (Arg0, 0x03), ^^EC.DAYB) Store (Index (Arg0, 0x04), ^^EC.HOUR) Store (Index (Arg0, 0x05), ^^EC.MINT) Store (Index (Arg0, 0x06), ^^EC.SECD) Store (Index (Arg0, 0x08), ^^EC.MSLB) Store (Index (Arg0, 0x09), ^^EC.MSMB) Store (Index (Arg0, 0x0A), ^^EC.TZLB) Store (Index (Arg0, 0x0B), ^^EC.TZMB) Store (Index (Arg0, 0x0C), ^^EC.DAYL) Return (Zero) } Method (_STV, 2, Serialized) // Set Timer Value (AppleSMCRTC.kext) { Store (And (Arg1, 0xFF), ^^EC.ALR0) Store (And (ShiftRight (Arg1, 0x08), 0xFF), ^^EC.ALR1) Store (And (ShiftRight (Arg1, 0x10), 0xFF), ^^EC.ALR2) Store (And (ShiftRight (Arg1, 0x18), 0xFF), ^^EC.ALR3) Return (Zero) } Method (_CWS, 1, Serialized) // Clear Wake alarm status (AppleSMCRTC.kext) { Store (Zero, ^^EC.TMRF) Store (Zero, ^^EC.TMRW) Return (Zero) } } Our hacks do not have such device and thus AppleSMCRTC.kext will fail. What I did notice is that there was no problem when I used the prelinkedkernel, but when I tried to boot without a prelinkedkernel, and let RevoBoot load the individual kexts, then it failed to boot. A real Mac boots with the prelinkedkernel. Not by loading individual kexts. That explains why it works on a Mac. The next thing I did was to run: LZVN -d /System/Library/Prelinkedkernels/prelinkedkernel list Low and behold. AppleSMC.kext is included. This despite the fact that the OSBundleRequiredis set to “Safe Boot“. Hmm. Interesting. Note: IOBluetoothHostControllerTransport.kext, IOBluetoothHostControllerUSBTransport.kext and IOBluetoothFamily.kext are three other kexts that are included in the prelinkedkernel – with OSBundleRequired set to “Safe Boot”. This breaks the load of individual kexts, because then it won’t get loaded. Not if you boot without a prelinkedkernel. Which is what I do most of the time. Anyway. Adding a few lines of new code to RevoBoot worked around this problem (for me). In short. It turned out that DP-2 was changed and as a result AppleSMC.kext no longer loads – on certain computers – due to the fact that the OSBundleRequired is set to “Safe Boot“. Changing it into “Root” solved the problem. As a workaround. Forcing it to load from the boot loader solved it – with the OSBundleRequired set to “Safe Boot”. Note: The OSBundleRequired this did not change, but it no longer loads in High Sierra. There may be other reasons that AppleSMC.kext isn’t loading, but you should try the work around. Or in case Chameleon or Clover – whichever boot loader you use – can force a kext to load. Then use that. You may also check your ACPI tabled for Name (_HID, "ACPI000E") because if you have that set on a different kind of device, which shouldn’t be the case, then that driver will try to load for the wrong kind of device Edit: The exact cause of the error will (hopefully) be documented later. My first thought is that the kextd (daemon) has changed, and now no longer loads the kexts that we need for our hardware. Apple may also have changed kextcache (command line tool) to make it include all kexts that are required, but I have yet to check this myself. I also added a tiny SSDT, to inject the missing ACPI device, and used boot arguments rtc=0x03and smcdebug=0xf0 to find the output of the kexts in the log. credit goes to PikerAlpha Link to comment Share on other sites More sharing options...
x.di Posted August 15, 2017 Author Share Posted August 15, 2017 @Rockey12 that didn't worked for me Link to comment Share on other sites More sharing options...
cheneyveron Posted August 31, 2017 Share Posted August 31, 2017 hi, have a try of my method: http://www.insanelymac.com/forum/topic/326200-new-possibilities-for-x79-appleacpiplatform-panic Link to comment Share on other sites More sharing options...
x.di Posted September 3, 2017 Author Share Posted September 3, 2017 @cheneyveron you are my hero! Solved "Still waiting for root device" My apfs.efi was old . Successfully booted HighSierra with fully working Power Managment I made patches to dsdt via clover (not a fun of extracting DSDT) <dict> <key>Comment</key> <string>CUU0</string> <key>Disabled</key> <false/> <key>Find</key> <data> cA1DUFVTQ0swAENVVTA= </data> <key>Replace</key> <data> AAAAAAAAAAAAAAAAAAA= </data> </dict> <dict> <key>Comment</key> <string>CUU1</string> <key>Disabled</key> <false/> <key>Find</key> <data> cA1DUFVTQ0sxAENVVTE= </data> <key>Replace</key> <data> AAAAAAAAAAAAAAAAAAA= </data> </dict> <dict> <key>Comment</key> <string>CUU2</string> <key>Disabled</key> <false/> <key>Find</key> <data> cA1DUFVTQ0syAENVVTI= </data> <key>Replace</key> <data> AAAAAAAAAAAAAAAAAAA= </data> </dict> <dict> <key>Comment</key> <string>CUU3</string> <key>Disabled</key> <false/> <key>Find</key> <data> cA1DUFVTQ0szAENVVTM= </data> <key>Replace</key> <data> AAAAAAAAAAAAAAAAAAA= </data> </dict> 2 Link to comment Share on other sites More sharing options...
Recommended Posts