Jump to content
Allan

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

448 posts in this topic

Recommended Posts

Advertisement

Just updated to High Sierra successfully (from Appstore).. Spent almost all day trying to figure things out..

 

MSI Z170-A

I7-6700K

Nvidia GTX 1080

 

Got OSInstall issue.. Updated Clover.. Still happened.. Ran Installer again from /Applications so that the install starts over instead of just from second phase.

Got the encountered an error verifying firmware.. Solved it by adding a Firmware Feature and Mask that matches my BoardID (needed it even with latest clover).

Got the kext[0] stall ACPICPU.. Solved it by moving FakeSMC and all kexts from "10.12" folder to "Other".

Got graphics stuttering no hardware acceleration.. Updated Nvidia Web Drivers.

Got the black screen when booting Nvidia GTX 1080.. Solved it by installing the latest Lilu.kext and NvidiaGraphicsEnabler.kext.

USB ports didn't glitching sometimes.. Downloaded RehabMan USBInjectAll source code and compiled it with Xcode 9 and 10.13 SDK.

Audio always worked with patched AppleALC (Same .kext from Sierra works on High Sierra for me)..

 

 

Only thing is that I wish I didn't have to use Lilu and NvidiaGraphicsEnabler.. It's annoying to have to update it every time a new OS update comes out (sometimes I forget and can't see anything on screen). Somehow GPU works out of the box with an older SMBIOS board.. but with new 5K iMac17,1 nope.. requires these kexts.

Share this post


Link to post
Share on other sites

It's still possible to create a HFS+ bootable media in a APFS system?

 

Well, in my first successfully installation I've formatted a single partition (from a external HD) from HFS+ to APFS, and then, when i tried do roll back it's no more available — partition is gone :w00t: , only visible on APFS system. So, appears that once you have a drive/partition with HFS+ u can continue with this one, but once u change it to APFS there's no way to get HFS+ back on a APFS system without formatting entire disk.

 

 

Problem now is, that apparently my system isn't allowrd to pass the Firmware check even with using current SMBIOS Settings that i posted earlyer.

 

Just tried it again. It don't let me pass the firmware check. I tried to install it on a different HDD.

I can do everything i want and change everything i want in the SMBIOS Settings, it just won't let me pass it.

I've tried the default value posted here and no way to pass the firmware check. But, Clover Configurator has automatically added this value on a smbios that I need to create and 'Voilà' – system installed and running.

 

 

when download High Sierra it downloads just 15 MB and after I start the installer it gets the other 4 GB part..

 

This also happened to me and I've to do a fresh install of El Cap and download High Sierra again – now with 5.19gb

Share this post


Link to post
Share on other sites

This also happened to me and I've to do a fresh install of El Cap and download High Sierra again – now with 5.19gb

 

There might be an easier way to do that. Check out this post. :) 

 

Just something to keep in mind next time you encounter this issue.

Share this post


Link to post
Share on other sites

I had 3 problems that kept me from running High Sierra on my main macOS partition:  1. No working sleep; 2. No working power off; and 3 No working brightness control.  I haven't a clue what actually was preventing sleep or poweer off but I do have a reminder to those who have been in the OSx86 community for a long time like me.

 

When I couldn't figure out what was the problem, I went back to basics.  I threw out my custom DSDT that I had spend years customizing and started fresh with my native DSDT.  I added only those patches I knew I needed and did not attempt to patch those things I knew Clover now did by default, such as Intel GFX0 patches.  I basically added only those patches for USB, IGPU, Battery, Brightness keys, and Syntax errors necessary to get my native DSDT to compile and do the things I knew I needed it to do that it couldn't do without patches.  That worked.

 

Although I don't know what was preventing sleep or powering off, the problem was resolved.  Now, I just need to figure out why RehabMan's brightness injector kext, along with his SSDT and kext patch don't work for me.  Hopefully, reading his post on that other forum for the umpteenth time will make re realize either what I am doing wrong or what is different about my system than the one for which he designed the brightness adjustment fix.  Either way, using his injector kext, SSDT and kext patch does not work. Any ideas?

00

P.S. - I celebrated my fixes of sleep and power off with a bottle of 15.9% bottle of red wine.  Forgive the typos.  W00t, w00t!

Share this post


Link to post
Share on other sites

I had 3 problems that kept me from running High Sierra on my main macOS partition: 1. No working sleep; 2. No working power off; and 3 No working brightness control. I haven't a clue what actually was preventing sleep or poweer off but I do have a reminder to those who have been in the OSx86 community for a long time like me.

 

When I couldn't figure out what was the problem, I went back to basics. I threw out my custom DSDT that I had spend years customizing and started fresh with my native DSDT. I added only those patches I knew I needed and did not attempt to patch those things I knew Clover now did by default, such as Intel GFX0 patches. I basically added only those patches for USB, IGPU, Battery, Brightness keys, and Syntax errors necessary to get my native DSDT to compile and do the things I knew I needed it to do that it couldn't do without patches. That worked.

 

Although I don't know what was preventing sleep or powering off, the problem was resolved. Now, I just need to figure out why RehabMan's brightness injector kext, along with his SSDT and kext patch don't work for me. Hopefully, reading his post on that other forum for the umpteenth time will make re realize either what I am doing wrong or what is different about my system than the one for which he designed the brightness adjustment fix. Either way, using his injector kext, SSDT and kext patch does not work. Any ideas?

00

P.S. - I celebrated my fixes of sleep and power off with a bottle of 15.9% bottle of red wine. Forgive the typos. W00t, w00t!

Congratz.

Did you add the plnf ssdt to the sorted order list in config.plist?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Congratz.

Did you add the plnf ssdt to the sorted order list in config.plist?

 

Sent from my SM-G930F using Tapatalk

 

I did.  I put the SSDT-PNLF.aml in second position behind a native ssdt that I had to change from GFX0 to IGPU.  I get the slider in SysPrefs-Display but it doesn't change the brightness when I move the slider button.  (I'm assuming that you need to put the full name of the ssdt in sort order (e.g., SSDT-PNLF.aml) but that you don't need to put in the path.)

Share this post


Link to post
Share on other sites

I did. I put the SSDT-PNLF.aml in second position behind a native ssdt that I had to change from GFX0 to IGPU. I get the slider in SysPrefs-Display but it doesn't change the brightness when I move the slider button. (I'm assuming that you need to put the full name of the ssdt in sort order (e.g., SSDT-PNLF.aml) but that you don't need to put in the path.)

Yes that's correct. And have you got AppleBacklightInjector.kext in S/L/E?AppleBacklightInjector.zip

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Yes that's correct. And have you got AppleBacklightInjector.kext in S/L/E?attachicon.gifAppleBacklightInjector.zip

 

Sent from my SM-G930F using Tapatalk

 

I had the injector kext in L/E.  I tried the one you posted (thank you very much) in S/L/E.  No change.  I still have the slider but it doesn't adjust the brightness of the screen.

Share this post


Link to post
Share on other sites

My High Sierra installation suddenly stopped working this morning. I get only the stop sign, verbose mode shows this:

 

post-626651-0-71459900-1507836001_thumb.jpeg

 

followed by “Still waiting for root device”.

 

It doesn’t matter how I try to boot, from SSD or USB... any suggestions?

Share this post


Link to post
Share on other sites

My High Sierra installation suddenly stopped working this morning. I get only the stop sign, verbose mode shows this:

 

attachicon.gif736D62F8-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?

check ACPI bios settings. 

Share this post


Link to post
Share on other sites

I had the injector kext in L/E.  I tried the one you posted (thank you very much) in S/L/E.  No change.  I still have the slider but it doesn't adjust the brightness of the screen.

Hi @mnfesq

For me the Brightness Slider.app from App store made the exact same work as the slider in system preferences

I have not seen diferances

Share this post


Link to post
Share on other sites

check ACPI bios settings.

 

Anything in particular? I’ve checked and rechecked multiple times, I cannot find anything wrong. I did go into UEFI settings last night, but I don’t remember changing anything related to ACPI. And I successfully booted after that... weird.

Share this post


Link to post
Share on other sites

Hi @mnfesq

For me the Brightness Slider.app from App store made the exact same work as the slider in system preferences

I have not seen diferances

 

I have that app too.  The thing is, even though I have a slider and I can move the slider button, doing so does not change screen brightness.  That's the problem.  I'm beginning to wonder if, for some reason, the patched AppleBacklight.kext is not loading properly or if the patch is not working for me.

Share this post


Link to post
Share on other sites

I have that app too.  The thing is, even though I have a slider and I can move the slider button, doing so does not change screen brightness.  That's the problem.  I'm beginning to wonder if, for some reason, the patched AppleBacklight.kext is not loading properly or if the patch is not working for me.

Ha ok  ;)

The Brightness Slider.app works for me but not the one from the preference System

I have installed Sierra 10.12.3 today to see the diferance because in 10.12.3 it works

I saw that there was no difference

Share this post


Link to post
Share on other sites

I had the injector kext in L/E.  I tried the one you posted (thank you very much) in S/L/E.  No change.  I still have the slider but it doesn't adjust the brightness of the screen.

This is my clover folder that i use successfully to boot High Sierra with working brightness, battery etc...

https://www.dropbox.com/s/v4d0jtgt3sr5ur8/CLOVER.zip?dl=0

Share this post


Link to post
Share on other sites

This is my clover folder that i use successfully to boot High Sierra with working brightness, battery etc...

https://www.dropbox.com/s/v4d0jtgt3sr5ur8/CLOVER.zip?dl=0

Thanks for posting it.  It looks pretty similar to mine but mine is an Ivy Bridge (old, like me.). I'll have to try some of your patches/kexts but I don't think they will make any difference.  I'm wondering if I am missing some OEM SSDT that defines BCL, BCM, etc. that I haven't found and patched to replace GFX0 to IGPU.  There must be something about my setup that keeps it from working when I follow the instructions for the tutorial to the letter.  That was why I started with a new DSDT.  Maybe I should try extracting my OEM ACPI files from scratch and start over with everything fresh.  Tomorrow is another day, and with another day, new things to try out.

Share this post


Link to post
Share on other sites

If you want to try you can create a ssdt to avoid using those kext

attached is one it is working for my system

 

http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10062017/page-31?do=findComment&comment=2514299

 

you have to do some changement in it (slot 1080 number and maybe HDMI part)

 

 

 

Just updated to High Sierra successfully (from Appstore).. Spent almost all day trying to figure things out..

 

MSI Z170-A

I7-6700K

Nvidia GTX 1080

 

Got OSInstall issue.. Updated Clover.. Still happened.. Ran Installer again from /Applications so that the install starts over instead of just from second phase.

Got the encountered an error verifying firmware.. Solved it by adding a Firmware Feature and Mask that matches my BoardID (needed it even with latest clover).

Got the kext[0] stall ACPICPU.. Solved it by moving FakeSMC and all kexts from "10.12" folder to "Other".

Got graphics stuttering no hardware acceleration.. Updated Nvidia Web Drivers.

Got the black screen when booting Nvidia GTX 1080.. Solved it by installing the latest Lilu.kext and NvidiaGraphicsEnabler.kext.

USB ports didn't glitching sometimes.. Downloaded RehabMan USBInjectAll source code and compiled it with Xcode 9 and 10.13 SDK.

Audio always worked with patched AppleALC (Same .kext from Sierra works on High Sierra for me)..

 

 

Only thing is that I wish I didn't have to use Lilu and NvidiaGraphicsEnabler.. It's annoying to have to update it every time a new OS update comes out (sometimes I forget and can't see anything on screen). Somehow GPU works out of the box with an older SMBIOS board.. but with new 5K iMac17,1 nope.. requires thes

Share this post


Link to post
Share on other sites

rx 580 works fine on my rig..it is time to use amd graphics..

I always was a fan of AMD graphics but the black screen issue forced me to switch to nVidia (it was before I knew that the WhateverGreen kext is being developed); But know that the AMD GPUs are back in the game it seems logical to switch back to them.

Share this post


Link to post
Share on other sites

I always was a fan of AMD graphics but the black screen issue forced me to switch to nVidia (it was before I knew that the WhateverGreen kext is being developed); But know that the AMD GPUs are back in the game it seems logical to switch back to them.

disable csm on bios or delete csm.efi from clover can solve black screen problems....

Share this post


Link to post
Share on other sites

Is anyone having issues with the instant reboot from wake on Browadwell cpus?

Need to try. After short sleep no issues

 

Sent from my Nexus 4 using Tapatalk

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 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
    • 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))
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

    • By fusion71au
      Clover r4961 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4961 for VMware.zip". Mount Clover-v2.4k-4961-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×