Jump to content
Dubesor

Hackintosh - Experiences with Major OSx Updates

6 posts in this topic

Recommended Posts

I know this is kind of broad, but if I build a workstation that's well supported on High Sierra now, how likely is it to still work well with the next major OSx release next fall?

 

If you had to guess, what % chance do I have of encountering major issues when trying to update next fall? The kinds of issues that would seriously interfere with my day to day work of photo and video editing? For example, kext/kernel panics (is that even a thing still?) or major pieces of hardware suddenly not being supported, and so on...

 

Has migrating your Hackintosh to the latest release has gotten easier in recent years? So for those of you who have been making builds for a while, is going from Sierra to High Sierra causing you fewer problems than Mavericks --> Yosemite for example or Yosemite --> El Capitan etc? 

 

Sorry if this is a bit broad and ignorant, but I've been away from the forums for quite a while and just trying to get a sense of how "stable" and "future-proof" Hackintoshes are these days - compared to Apple's own desktops ...

 

I'm OK not updating incrementally ie v13.1 to v13.2 if I need to, but I'm worried about having to start completely from scratch with each new main version.

Share this post


Link to post
Share on other sites
Advertisement

well FWIW, I made my Hackintosh with Mavericks, when that was current, and upgraded it ever since with almost no problems... until the upgrade from Sierra to High Sierra which, after a couple of false starts that just failed but left me with a working system, finally killed it when I tried harder to push the upgrade through. So my Hackintosh is currently not a hackintosh but just a PC running Ubuntu Linux, which has thankfully chosen this moment to finally get usable HiDPI support (with caveats).

 

I may yet try again. Its partition still awaits... According to discussions around here the fault may have been in having an nVidia GPU, so I may try taking that out and doing a fresh install of High Sierra on the onboard Intel HD4600 and then putting the nVidia back in and sorting out its drivers, and finally restoring from the backup I made before the failed upgrade. That's an effort to go through if Ubuntu manages to annoy me too seriously, or I, once again, just want a change in scenery that badly!

 

However, I must say, while the previous upgrades did go through relatively painlessly, the stress and worry about them failing, as eventually happened, was always the biggest fly in the ointment. If Apple made the desktop machine I want, I'd totally buy it, and pay more than I could build the hardware equivalent for, for that peace of mind. But they don't. They're all either underpowered, ridiculously overpowered, or just-right-powered but with an unwanted and expensive screen welded to the side.

 

(After all it's not as if I don't already have two real apple laptops - on which Linux runs OOTB better than it does on this PC too, as it happens... I will buy the Apple kit if the right kit exists.)

Share this post


Link to post
Share on other sites

Thanks for that input, StrangeNoises! Anyone else?

I've had hackintoshes for years. In my experience each new platform lasts for a few major OS upgrades, or more, but as it gets older you have to jump through more hoops. I just upgraded my hardware to X299 and a Vega GPU, both of which are pretty well native with High Sierra and I imagine they'll survive the next 2 or 3 OS upgrades if not more.

One great thing recently is whatevergreen kext which allows most AMD GPUs to work without a lot of hassle.

I'm not an AMD fanboy, but it seems that the Nvidia cards are more trouble and users are stuck with waiting for new drivers every major or sometimes minor upgrade to the OS.

The X299 and the Vega are great for my design work and happen to be very close to the upcoming Mac Pro, so should last for as long as Apple supports that machine.

 

So, to answer your questions, I'm betting on my system to survive the next upgrade 100%, the one after 95% and after that I'll be getting a new machine haha.

In fact, I think the next OS will run my stuff better because that's when the new Mac Pro will be out there and Apple users will be helping my hack to run better (Things like EIST support).

The i9 runs without kernel or kext patches and I only use a few kexts for USB and network, so no panics unless I do too much experimenting with the EFI.

Upgrades are just done through the App Store now.

 

Hope this helps :)

Share this post


Link to post
Share on other sites

Thanks for that input, StrangeNoises! Anyone else?

Well as @StrangeNoises and @surfinchin stated their success stories I can tell you this, I've been using hackintoshes for over 10 years from macOS Tiger to macOS High Sierra and I never used windows for my day to day tasks for past 10 years, I have few PCs and as you can see in my signature and they still work great with macOS (except my oldest build which I haven't installed macOS High Sierra on yet). So to answer your question about the stability and being supported in the future releases of macOS if you choose your hardware wisely (being more compatible with macOS) you can use it until they get really old.

 

There are many great people in the hackintosh scene and they are working nonstop to improve the hackintosh support and they are really doing a great job. There are many success stories under the "Installation Guides" that you can review and find the best config that suits your needs.

 

Building a Hackintosh is not as easy as having to install windows or linux on your PC and it can be frustrating sometimes specially if you are new to this.

 

About the future of the hackintosh I can't say for sure if it's going to go on forever or if Apple decides to use their own processors in their next computers like they did back in the day (before 1996 that they switched to intel from PowerPC Architecture).

 

But for now we can enjoy the elegance of macOS on our computers thanks to our developers and coders.

 

Cheers 

Share this post


Link to post
Share on other sites

Update kext, clover bootloader, apfs.efi (if you use apfs) -> Update nVidia Web Driver (if you use nvidia gpu) -> Download the update -> Reboot -> Select the Installer entry -> Wait -> Done

 

I updated from 10.12.6 -> 10.3 -> 10.3 (with a update). Also, if you install Windows 10 as dual-boot you can install/uninstall/modify kext, config.plist any time you broke your system. You can use Time Machine to restore your system back to the working state, I tried it before

 

edit: also if you have some data on your Mac hard drive, you can use MacDrive from windows to backup it 

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 Andres ZeroCross
      First my Old Threads is here http://www.insanelymac.com/forum/topic/308178-el-capitan-wih-i7-6700-skylake-gigabyte-ga-z170-hd3-palit-jetstream-gtx960/

      My Computer Specifications
      1. Processor : Intel Core i7 6700
      2. Motherboard : Gigabyte Z170-HD3
      3. VGA Card : Palit Jetstream GTX960 4GB DDR5
      4. Wifi Card ; TP-Link TL-WDN4800
      5. PCI-E to Sata = Bafo PCI-e to 2 Sata3 and 2 e-Sata
      6. PCI to USB 2.0 - NEC Chipset
      7. Main Harddisk Harddisk : Fujitsu SSD 120GB + Seagate 500GB that plug into Bafo PCIe to Sata3
      8. Other Harddisk : Natno SSD 12GB, 2x Seagate 2TB, Seagate 500GB, all of it are plug into onboard Sata Chipset Controller (But Unknow at El Capitan / 10th Intel Chipset)
      9. RAM : Team 3000Mhz 8GB (2x4GB)
      10. Display : Asus VN248H
      11. Clover version : 3280

      My Step :
      1. Because Internal Sata Chipset and USB 3.0 are not supported yet, so i clone my Fujitsu 120GB SSD from my Hacbook Asus X455LA that already installed El Capitan Build 15B30a with Carbon Copy Cloner
      2. I use MacPro 6.1 as SMBIOS and use FakeCPUIID of Intel 4790k (0x0306C3)
      3. Remove CPUSensor.kext from "FakeSMC.kext/Contents/Plugins" if you don't do this it will be stuck at ACPI log verbose.
      4. I try boot from USB that already install Clover 3280 and it boot. I use "-v nv_disable=1 dart=0"
      5. Then at desktop, i install nvidia web driver 346.03.02F02 (before that you need to modif it,, use pkgutil --expand bla bla ba,, google it and change required os to "15B" then use pkgutl --flatten bla bla to repackage) then i change info plist from AppleGraphicsControl.kext/Contents/Plugin/AppleGraphicsDevicePolicy.kext/Contents/info.plist and change line that contain board-id of MacPro 6.1 from Config2 to none
      6. Then i install that kext,, and restart
      7. i use "-v dart=0 nvda_drv=1 and it will need more time than usual to get login form,, yeah i did it. But there is some bugs
       
      Bugs :
      1. Internal sata is not function
      2. USB 3.0 is error too,,  at verbose i see "error mantisa log"
      3. Sometimes my system get freeze for a few seconds. I thinks this is error from Nvidia web driver,, i see nvdia error log from "sudo dmesg"

      At last,, sorry for my bad english
      Thanks
       
      This is for screenshots
       

       

      I upload my IOREG and DSDT
       
       
    • By FreeJHack
      MacOS does not support natively the keyboard backlight for non-Apple hardware.
      I wrote an open source Kext project (ClevoService) to perform this task on Clevo laptops.
      It's fully working on my Clevo P9XXEN_EF_ED laptop with Mojave (18G95) and it should works on many other Clevo laptops.
       
      If you own a Clevo laptop with full color backlight keyboard, take a look at:
      https://github.com/FreeJHack/ClevoService
       
      The big advantage is that the backlight function is fully controlled from the numeric keypad and it's saved between boot/reboot and sleep/wake.
      You can change color, backlight level and ON/OFF.
      For the installation, download the kext from release page and follow the instruction given in the GitHub repository.
    • By Vyzantion
      I can not manage to install Catalina on this legacy Asus machine that runs Mojave fine. When the installer boots up, DiskUtility does not see the internal hard-drives, neither the master SATA one or the the slave, ATA one. I have discussed this already on the Clover section with Slice, he told that some kext seems to have changed from Mojave to Catalina, he told me to use IOReg. Since then, I have postponed my work on Catalina due to the issues regarding the Mojave supplemental updates.
      I have decided to start a new topic in here, due to visibility reasons and some new turn. The latest version of the dosdude1 patcher for unsupported Macs, discussed on Macrumors forums, patches the installer so that DiskUtility sees the internal hard-drives, I am able to install Catalina but, on first boot, the OS gets into a kernal panic with the message ”still waiting for root device”. I have searched online for this error, I have found Information regarding previous macOS versions with solutions that seem to have little to no relevance for the present issue.
      Before installation finishes, I receive a message like ”Installation finished on Macintosh HD Data”, instead of ”Installation finished on Macintosh HD”. I admit this split between the two in Catalina still confuses me, perhaps this is how it was suppose to be? Perhaps something that was suppose to end up on Macintosh HD ends in Macintosh HD Data?
      I admit the DVD-Rom and hard-drives are wired kinda of weird by some guy in a PC service, he said this is the optimum combination, something the ATA hard-drive is slave to the DVD-Rom. Perhaps this causes confusion into Catalina? On Mojave this configuration was fine. 
      Probably the solution suggested by Slice is the best, to replace one or more kext from Catalina with the Mojave versions of them. I do not know yet how to identify and replace them. If any other solutions seem possible, I am open to them.
      Specs:
      Asus P5P41TED motherboard.
      Intel Core 2 Duo E 8500 
      2 gb ram DDR 3
    • 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
×