Jump to content
Allan

macOS High Sierra - Final Release is out! (17A365)

448 posts in this topic

Recommended Posts

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....   

Share this post


Link to post
Share on other sites
Advertisement

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! :-)

 

Slice made option to can use manual kernel patch and fakecpuid. Enjoy

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

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에서 보냄

Share this post


Link to post
Share on other sites

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

 

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....   


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

 

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에서 보냄

Share this post


Link to post
Share on other sites

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?

post-1362934-0-03426200-1508307772_thumb.png

post-1362934-0-91053900-1508307930_thumb.png

Share this post


Link to post
Share on other sites

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에서 보냄

Share this post


Link to post
Share on other sites

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... 

Share this post


Link to post
Share on other sites

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에서 보냄

Share this post


Link to post
Share on other sites

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"...

Share this post


Link to post
Share on other sites

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에서 보냄

Share this post


Link to post
Share on other sites

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

 

 

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"...

Share this post


Link to post
Share on other sites

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..!!!  ;)

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

And how one can apply thus extensive cosmetics? Instructions please!!!!  :thumbsup_anim:

Hmmb..??? I think U didn't read @Shanee's guide carefully.  :rolleyes:

Share this post


Link to post
Share on other sites

I did not read it at all  :P  Can you please provide a link ?

I actually give the link, not sure if U missed it bcoz ur mach is too fast, or ur internet.. even with my old phone I could click it hah haaa  :lol:

Share this post


Link to post
Share on other sites

Hey guys, how goes.
I'm trying to install High Sierra on an external USB here, and it doesn't seem to work.
I've got the installer going, that completes fine to an external USB on APFS.
Then there's an initial reboot, at that time you need to boot the partition to continue the installation. That seems to reboot quickly.
I boot again to continue the installation, then that completes successfully in ~15 minutes.

But then when I try to boot the installed system, I get errors at the Clover level, in the apfs.efi  layer:

 

fs_read_stream:12997: failed to lookup pos 0 in obj 18
can't read cache..
read error 0x7

fs_get_inode_with_hint:7825: failed to load inode 764087 ret 22.

Anybody has an idea?

Share this post


Link to post
Share on other sites

Hey guys, how goes.

I'm trying to install High Sierra on an external USB here, and it doesn't seem to work.

I've got the installer going, that completes fine to an external USB on APFS.

Then there's an initial reboot, at that time you need to boot the partition to continue the installation. That seems to reboot quickly.

I boot again to continue the installation, then that completes successfully in ~15 minutes.

 

But then when I try to boot the installed system, I get errors at the Clover level, in the apfs.efi  layer:

 

fs_read_stream:12997: failed to lookup pos 0 in obj 18

can't read cache..

read error 0x7

 

fs_get_inode_with_hint:7825: failed to load inode 764087 ret 22.

 

Anybody has an idea?

make a signature of the hardware

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
    • By t0mmenhansen
      I havent used my hackintosh in a while. I wanted to boot to my mac drive. This error comes up when i try to boot. Ive tryed using explorer++ and update the lilu kext and whatevergreen kext, no luck yet. Any ideas?
       
      9700k
      16GB corsair
      1080 nvidia card
      z370-f mobo
      mac drive is an SSD from kingston
      Display port outpoot
       
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
×