Jump to content
MaLd0n

[Guide] Sierra / High Sierra / Mojave on Intel 5, 6, 7, 8, 9 Chipset Series / Nehalem, SandyBridge, IvyBridge, Haswell, Broadwell

2,335 posts in this topic

Recommended Posts

Advertisement

same files for both system ;)

 

CodecCommander for Alc1150 is a good idea, go to Sierra 10.12.4 and let me know

Share this post


Link to post
Share on other sites

Do I use the Clover folder you sent me for the Sierra install (on the USB), but replace the DSDT with the one you sent me that works?

 

The screenshot you took of the Clover Screen.  What is checked to install inside of the "Drivers64UEFI"  Option?  In the past I have just used OsxAptioFix2Drv-64

Share this post


Link to post
Share on other sites

after install Sierra

Install Clover with options above, dont need check in drivers, my folder have all u need, just replace

http://www.insanelymac.com/forum/topic/323052-sierra-on-intel-5-6-7-8-9-and-10-chipset-series-nehalem-sandybridge-ivybridge-haswell-skylake/?p=2413230


if u have problem, use same folder but changed DSDT, use it

http://www.insanelymac.com/forum/topic/323052-sierra-on-intel-5-6-7-8-9-and-10-chipset-series-nehalem-sandybridge-ivybridge-haswell-skylake/?p=2413304

but use only if u have problem, all u need have inside Clover folder

Share this post


Link to post
Share on other sites

Hey hey,

 

Mind lending me a hand with my DSDT / checking it over?

 

Changes made to the DSDT:

- Injected layout-id (probably incorrectly as I still need the HDAEnabler)

- Fixed codepaths not returning a value by appending return (Zero)

- Removed random Arg0 after a return statement causing an unexpected end of file

- Fixed possible timeout error by changing 0x0FFF to 0xFFFF

- Removed unused locals

- Removed 20+ lines of Zero repeated

 

The SSDT.aml is the output from the latest version of ssdtPRGen.sh.

 

System: Dell Inspiron 3847

Graphics card: r9 270

CPU: i5-4440

Memory: 8gb

SSD: 1x Samsung Pro

HDD: 1x WD Black 3tib

Lan: RTL8168G / 8111G via Realtek8111.kext

Audio: ALC662v2 via AppleALC.kext

 

Links:

System specs (for reference): https://downloads.dell.com/manuals/all-products/esuprt_desktop/esuprt_inspiron_desktop/inspiron-3847-desktop_reference%20guide_en-us.pdf

IOReg: https://mega.nz/#!lNpiUYJB!XlaNWUyYgacLCsbSKMfBQLebihFHYbexzl9PchV2kvs

App output: https://mega.nz/#!xdoXkSqb!HXgXo1M13QuhppHfZs5eBPODlM0UHzRYMzl_Z2U0-4g

Clover: https://mega.nz/#!5RQwlLZI!8_HBy9jqLCh7RJPr_wF3yErUgVQ97yrqI-3jjWII7Y0

Share this post


Link to post
Share on other sites

System: Dell Inspiron 3847

CLOVER.zip

for Alc662 u can try id 5, 7, 11 and 12, if dont work native, u need a AppleHdaPatcher, yes!

MaLd0n, wow, wow and more Wow.

 

Everything under 10.12.4 works like a complete charm, and the rig is smoking fast in booting up.

 

So Smoooooooth!

 

Thank you ever so much.

Welcome!

Enjoy!

Share this post


Link to post
Share on other sites

attachicon.gifCLOVER.zip

for Alc662 u can try id 5, 7, 11 and 12, if dont work native, u need a AppleHdaPatcher, yes!

Welcome!

Enjoy!

 

Wow! I am floored by how much of a change a proper DSDT / clover configuration can make. I can't test HDMI audio out unfortunately so I can't comment on if that's working or not. The audio is working just fine without the hda enabler loading. The only issue I have left to fix on my system is the graphics not waking from boot, but that's a known AMD issue from the looks of it on <= 10.11.

 

Thanks a lot for taking a look at my setup MaLd0n!

 

Edit:

 

Looking at hwmonitor from rehabman / fakesmc it looks like only drive temps and ssd life remaining is showing. It use to include fan speeds, temps, etc. This could be due to my ssdt changes from earlier. Should I try adding the other ssdt-# files into my patched folder (after fixing any errors of course)?

Edited by FFForever

Share this post


Link to post
Share on other sites

fakesmc sensors cause many problems in many cases, but if u can test use it

Just replace in Clover/Kexts/Other

attachicon.gifFakeSMC.SENSORS.zip

and Check with HWMonitor

attachicon.gifHWMonitor.app.zip

 

Ah. I was using hwmonitor as a way to test speedsteping / monitor temperatures. Do you have a recommendation on something else to use?

 

I noticed in my verbose boot output I have ACPI errors relating GPX0 with a note on AE_NOT_FOUND. I tried searching console for ACPI, and found nothing. Is there a log file I can check to get the exact error?

Share this post


Link to post
Share on other sites

AE_NOT_FOUND

it is common to see these in 10.12 with this new version of AppleACPIPlatform.kext. Older versions of OS X didn't do checks like this. ;)

 

Check ur speedstep use IGP

Intel® Power Gadget SIERRA.zip

 

Send me new ioreg

IORegistryExplorer 3.app.zip

Share this post


Link to post
Share on other sites

it is common to see these in 10.12 with this new version of AppleACPIPlatform.kext. Older versions of OS X didn't do checks like this. ;)

 

Check ur speedstep use IGP

attachicon.gifIntel® Power Gadget SIERRA.zip

 

Send me new ioreg

attachicon.gifIORegistryExplorer 3.app.zip

 

ioreg: https://mega.nz/#!xUxHVDaT!G3mHO3-sE8zHz3dZ1NmWMOjarLipUAxYFDXCb4mC-W0

 

Does this look like it's stepping correctly? Even with a 90%+ idle system it's still hovering around the max frequency with minor drops.

 

f9jiWRb.png

Share this post


Link to post
Share on other sites

generate NEW SSDT PM with Pike script

attachicon.gifssdtPRGen.command.zip

replace SSDT

run it

attachicon.gifOlarila.command.zip

reboot

 

Check again

 

Looks like it's still favoring the high frequency. I've attached ~/library/ssdtprgen's content, the ACPI folder contains the original ssdt/acpi, and the patched dsdt. It was complaining that they didn't exist so I copied them in, and ran it again.

 

Should I ignore the error, and run it again with the files deleted?

 

ssdtPRGen: https://mega.nz/#!EM5FWIpT!mxugJtnLgR8pNwcGZyF4CFXMaIjg_Z5rvKYS2eJN_Qk

 

MtDnJpn.png

Share this post


Link to post
Share on other sites

test it, just replace

attachicon.gifconfig.plist.zip

let me know

 

need sleep now, 2:50am, tomorrow we check it

 

Good Nit!

 

Thanks again for all of your help last night :).

 

The new config doesn't seem to change the speedstepping. Even with idle loads I'm still seeing the same frequencies for the most part.

Share this post


Link to post
Share on other sites

very strange

take a test with Clover PM

Remove SSDT and replace config.plist

attachicon.gifconfig.plist.zip

 

Hmm it still doesn't appear to be stepping correctly. Should I try clearing the nvram? 

 

I checked the power widget in Windows (and recorded a log) to verify speed stepping is working correctly / there's no MSR lock.

 

PwrData csv: https://mega.nz/#!IchWTYKB!K-bDnOC0UjIUEjR04PLy-vp2JEY71EZgYOy1zidSB1Y

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 fighttoby
      I have tried to install clover via no UEFI legacy mode (and with UEFI method) using the method here (http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html)
      both times I can get to just past the clover boot screen and it freezes after that.
      I have verbose (-v) selected in boot options: On the non-UEFI install then it hangs on:
      "Waiting on <dict ID="0"><key>IOProviderClass</key>...."
       
      I have had a lot of issues with trying to get the installer working and many different things that had to be disabled but now it just gets to here and stops. Some times it will glitch out on this screen and give me a the circle with the line through it and text garbage around it where the text in the pictures are.
       
      Need help please.
       
      This is the laptop im using the specs are the same nothing has changed.
      https://www.asus.com/Laptops/ASUS_VivoBook_X202E/


      config.plist
    • By Mieze
      This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
       

       
      A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
      I219LM I219V 200 Series (since V2.3.0d0)
      I219LM I219V 300 Series (since V2.4.0d0)
      I219LM I219V  
      Key Features of the Driver
      Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.  
      Current Status
      The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS.   Known Issues
      There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer.  
      FAQ
      Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Installation
      Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
      Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
      The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
      Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
      Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
    • By Gorec
      Hi.
      I apologize in advance if I didn't post in the right category and if my title and description aren't specific enough :c
       
      My config in a nutshell:
      CPU: i7 5820k GPU: MSI GTX 1060 3GB RAM: 16 GB MOBO: MSI X99 SLI PLUS I attached RunMe output with all the details of my built.
       
      Some background:
      I have my Hackintosh for about half a year. That time I managed to make it works and fix major issues, but some of them left unresolved since then and I ignored them until now.
      I use my Hackintosh for Adobe projects (PR, AE, PS, IL, AU and a lot more) - most of them connected with video editing of course browsing with Chrome and other small tasks.
       
      Problems:
      Random restarts - this is the biggest one. I'm starting to work on bigger and bigger projects and at this time I think I can't allow this to happen that often. In the past, they happened like once a day or a couple of times a week. However, now it's just frustrating when it happens even 5 or more times a day. I've tried to observe and find out what can be the cause but I haven't managed to find any connections. I thought it happens when Premiere or another app is using GPU, but I haven't seen increased usage when it restarts. I think that it can be connected with GPU, memory or PSU or... meh, anything else. I don't have resources to check if it'll work with other components. There should be some fix for this. I will really appreciate any help with this :c Restart instead of shutdown & sleep doesn't work. I've tried to look through some Google results for this and tried many solutions (as you can see in attached Clover folder), but I think the right one for many of these issues is to make my own DSDT. Glitches, freezes and other things while encoding a video. It happens very often when I try to do this. Maybe it is an issue with GPU or (hopefully) only with GPU drivers which can be fixed with some patch. Today my headphones stopped working. I have a multi-output device configured in the Audio MIDI Setup app which includes my headphones (HyperX Cloud via USB) and Soundflowerbed virtual audio device for capturing system audio. Today while I was trying (like 15 times) to encode a video in Media Encoder in the background and watch video on YouTube I stopped hearing anything from my system. Of course, it restarted a couple of times as always, but even this didn't solve this. If I plug them directly with mini jack (not via USB Soundcard which was in the box and which I always used) in the front IO or the back I only hear some loud noise It takes EX-Fat formatted volumes a few minutes to mount after each restart. I found a workaround to format it with NTFS since I have Tuxera installed and I will reformat these volumes when I will find time for this, but maybe there is some fix for this. GPU is a little bit hot. HW Monitor shows it is only 45-55 degrees, but for my hand is a little bit hot, idk. Also related to GPU - glitch after POST but before entering Clover boot menu. It is a black screen with little white squared glitches for a few seconds. Maybe it indicates the GPU drivers are loading, but maybe it shouldn't be like this. And if I can ask about that - I can't make all applications hide on startup. I, obviously, have "Hide" checkbox checked on every login item in settings, but it doesn't work, none of the apps is hidden in the dock. Is there a way to fix this? Also a small but annoying problem - I can't turn off permanently Mojave update notification (since I tried to install it, and I had to reverse to High Sierra because I had a black screen and I didn't have time for repairing all of them. Tags are not working in Finder - every time I tag a file or folder and make a change in it (for example save a text file) the tag disappears.  
      So, with knowing all of that, is there a way to make a proper DSDT file for my Hackintosh? I tried to look through some guides on how to make it but I think I reached my abilities to understand how Mac OS works and what all of these things are, so I'm asking you guys politely, would someone like to help me? At least with these random restarts? :/
      I really begin to think that I'm a newbie in configuring all of that Clover things - even after what I managed to do with my PC. Help me, pleease... :c
       
      If you have any questions post it below, I will really appreciate any help <3
      Send me MBP-Gorec.home.zip
×