Morpheus NS Posted October 15, 2017 Share Posted October 15, 2017 (edited) My High Sierra installation suddenly stopped working this morning. I get only the stop sign, verbose mode shows this: 736D62F8-DF22-4F06-843D-E135CCF8F63D.jpeg followed by “Still waiting for root device”. It doesn’t matter how I try to boot, from SSD or USB... any suggestions? I will answer to myself, maybe it helps someone down the road: 1) Don't touch UEFI options if everything works! 2) If you do, use "-x NoCaches" and rebuild kextcache, because it is corrupted EDIT: replaced -f with NoCaches. Replaced kernel cache with kextcache. What the h*ll was I thinking, Chameleon? Edited October 16, 2017 by Morpheus NS 3 Link to comment Share on other sites More sharing options...
Allan Posted October 15, 2017 Author Share Posted October 15, 2017 1) Don't touch UEFI options if everything works! 2) If you do, use -x -f and rebuild kernel cache, because it is corrupted That's a very useful hint. Thanks buddy 1 Link to comment Share on other sites More sharing options...
surfinchina Posted October 15, 2017 Share Posted October 15, 2017 I will answer to myself, maybe it helps someone down the road: 1) Don't touch UEFI options if everything works! 2) If you do, use -x -f and rebuild kernel cache, because it is corrupted Are you using an nvme drive? I get a boot fail on my 960 evo after any changes. The SSD is always good though. Exactly the same EFI. Now I use the EFI from my 850 evo (backup SSD) and the 960 as boot drive. Another thing, I went back the the Mac os extended format and the boot times are way quicker, plus it plays better with clover. Link to comment Share on other sites More sharing options...
Morpheus NS Posted October 15, 2017 Share Posted October 15, 2017 No, I am using Samsung 750 EVO SSD. I was trying to experiment with CSM option (without fully understanding it) to get the full resolution in bootloader with my Asus Geforce 210. The next morning I couldn't boot from my SSD or USB with an error message I've never seen before (6 years of hackintosh "experience"). After countless hours of trying different things and failing, I tried booting with "-x -f" and got to the macOS. Then I repaired kernel cache and everything seems to be fine for now. My APFS is very fast, the improvement is noticeable over HFS+, I am very happy with it so far. 1 Link to comment Share on other sites More sharing options...
MICKHAEL Posted October 15, 2017 Share Posted October 15, 2017 Hm could be my cpu/motherboard then. What clover version? just tested one and a half hour sleep without problem 1 Link to comment Share on other sites More sharing options...
Balamut Posted October 16, 2017 Share Posted October 16, 2017 I'm getting instant reboot from wake... back to digit I guess. Link to comment Share on other sites More sharing options...
Pedro Simão Posted October 17, 2017 Share Posted October 17, 2017 Hello, I have installed an NVME disk on my Macbook Pro 15 retina (late 2013). It is recognized by the system with no problem.But as my original SSD disk was broken I couldn't first install in an internal drive and as a consequence I didn't get the Firmware upgrade. I really need the firmware upgrade as I want to boot from the NVME disk. I have tried running the post_install scripts that are inside the FirmwareUpdatePackageExpanded folder of the HighSierra installer but I get the following error: "usbcupdater[1291:52855] Error reading plist: No files to support boardID: Mac-2BD1B31983FE1663" Does anyone know a way to have a Firmware upgrade on macbook without installation on the internal drive?Regards, Pedro Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 17, 2017 Share Posted October 17, 2017 We can confirm NATIVE XCPM Power Management for Skylake-X i7-7820X and i9-7900X under macOS High Sierra 10.13 SU with SMBIOS iMac17,1 2 Link to comment Share on other sites More sharing options...
Balamut Posted October 18, 2017 Share Posted October 18, 2017 .13 not .13.1 beta? No Kernel, Kext Patches? Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 .13 not .13.1 beta? No Kernel, Kext Patches? .13 not .13.1 beta? No Kernel, Kext Patches? no xcpm KernelToPatch entries and no ssdt.aml or ssdt_xcpm.aml injection... yet FakeCUPID and CPU Type.... with my i9-7980XE I still need the ssdt.aml to make xcpm work at all... and yes 10.13. SU not 10.13.1.. Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 try an old clover version... I mean before auto patching feature Why should I do that? I mean with ssdt.aml, XCPM with my i9-7980XE works absolutely flawless. It was just surprising to me that with the i7-7820X and i9-7900X, ssdt.aml seems not necessary to make XCPM work at all.. However, I admit that the guys did not test yet further implications when omitting the ssdt.aml with the latter processors. Power nap and the correct association of C and P states might not properly work in the latter case... We have to see and test to know further details.... Link to comment Share on other sites More sharing options...
Sherlocks Posted October 18, 2017 Share Posted October 18, 2017 try an old clover version... I mean before auto patching featureSlice made option to can use manual kernel patch and fakecpuid. Enjoy 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 18, 2017 Share Posted October 18, 2017 I Sherlocks I am trying to understand why patches I use with rev 4128 do not work with rev 4251 and also I would like to understand if I also automatic fakecpuid is removed as features (ops you say yes also for this) In this thread I was replaying to KGP-99 because his "vanilla" rig..is Clover Vanilla auto patching related! :-) Still not work on 4251? I dont know your conversation with KGP-99. just inform clover now disabled default autopatch. Its good news to have problem like you. 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 Slice made option to can use manual kernel patch and fakecpuid. Enjoy 나의 LG-F800S 의 Tapatalk에서 보냄 Concerning FakeCPUID it seems that one can either use '05606E4' for all Skylake-X processors without any further implication or '0560654' with xcpm bootstrap. However, the Skylake-X CPUID of '0560650' (suggested by Pike Alpha) seems not to work at all. While on all other Skylake-X CPUs '05606E4' properly implements the main CPU characteristics in Apple's System Report (About This Mac), with the i9-7980XE I just obtain the following (see Overview.png)... Although under "Hardware", the i9-7980XE seems properly implemented (see Hardware.png) @Sherlocks, do you know how to fix the "About This Mac" CPU unknown error for i9-7980XE? 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 18, 2017 Share Posted October 18, 2017 You say NATIVE XCPM it is not vanilla but it is related to auto patching feature in new clover before some devs listened our request to have the chance to eliminate xcpm auto patch for now I can't boot with rev 4251 with usual patches I use in 4128 to boot with 4251 I have to flag Kernel XCPM Strange. 나의 LG-F800S 의 Tapatalk에서 보냄 Concerning FakeCPUID it seems that one can either use '05606E4' for all Skylake-X processors without any further implication or '0560654' with xcpm bootstrap. However, the Skylake-X CPUID of '0560650' (suggested by Pike Alpha) seems not to work at all. While on all other Skylake-X CPUs '05606E4' properly implements the main CPU characteristics in Apple's System Report (About This Mac), with the i9-7980XE I just obtain the following (see Overview.png)... Although under "Hardware", the i9-7980XE seems properly implemented (see Hardware.png) @Sherlocks, do you know how to fix the "About This Mac" CPU unknown error for i9-7980XE? Did you set cpu type in config.plist? If you want to use 'i9', maybe we have to wait imacpro release. 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 Strange. 나의 LG-F800S 의 Tapatalk에서 보냄 Did you set cpu type in config.plist? If you want to use 'i9', maybe we have to wait imacpro release. 나의 LG-F800S 의 Tapatalk에서 보냄 Yes: "0x0a05", which in principle works for all Skylake-X processors... Link to comment Share on other sites More sharing options...
Sherlocks Posted October 18, 2017 Share Posted October 18, 2017 Yes: "0x0a05", which works for all Skylake-X processors...0x0a05 shown i9 processor? Or shown xeon? Edit1. Aha you setted 0x0a05, but shown unknown. Hmm.. I think this is cosmetics. Untill release imacpro, recommend 0x0a02 if you dont want to use 'unknown' 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 0x0a05 shown i9 processor? Or shown xeon? Edit1. Aha you setted 0x0a05, but shown unkown. Hmm.. 나의 LG-F800S 의 Tapatalk에서 보냄 The "CPU unknown" issue only appears with the i9-7980XE... 0x0a05 else reveals for all other Skylake-X processors the proper CPU characteristics (frequency, cores, etc.. ) in "About This Mac", but indeed also all other Skylake-X CPUs appear as "XEON" instead of "i9"... Link to comment Share on other sites More sharing options...
Sherlocks Posted October 18, 2017 Share Posted October 18, 2017 Only with i9-7980XE... 0x0a05 else reveals for all other Skylake-X processors the proper CPU characteristics (frequency, cores, etc.. ) in "About This Mac", but indeed also all other Skxlake-X CPUs appear as "XEON" instead of "i9"...Okay. Good info. We have to wait imacpro smbios data.Thanks. 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 18, 2017 Share Posted October 18, 2017 The "CPU unknown" issue only appears with the i9-7980XE... 0x0a05 else reveals for all other Skylake-X processors the proper CPU characteristics (frequency, cores, etc.. ) in "About This Mac", but indeed also all other Skylake-X CPUs appear as "XEON" instead of "i9"... Not so bad for cosmetic, DWYOR..!!! Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 Your core's CPU number is not present in a real Mac so for now you can only fake that data in about my mac If you IE have a 12 core or less also unknown for real Mac you can 0x0xxxx to see 12 core xeon or similar o.k. I see but if you have a processor with more than 12 cores the cosmetics don't work, right? Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 and this is cosmetic you can apply And how one can apply thus extensive cosmetics? Detailed instructions please!!!! Link to comment Share on other sites More sharing options...
Badruzeus Posted October 18, 2017 Share Posted October 18, 2017 And how one can apply thus extensive cosmetics? Instructions please!!!! Hmmb..??? I think U didn't read @Shanee's guide carefully. Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 Hmmb..??? I think U didn't read @Shanee's guide carefully. I did not read it at all Can you please provide a link ? Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted October 18, 2017 Share Posted October 18, 2017 Search here and then if you use in other forum...:-))) change CPU name in this site and you will find http://www.insanelymac.com/forum/topic/323469-change-cpu-name-in-about-this-mac/?hl=cpu+name&do=findComment&comment=2488297 Gorgeous!!! Grazie mille, @fabiosun! Link to comment Share on other sites More sharing options...
Recommended Posts