Jump to content
MaLd0n

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

2,456 posts in this topic

Recommended Posts

Advertisement

attachicon.gifClover_v2.4k_r4344.zip

run it

attachicon.gifRunMe.app.zip

send me files

sorry, I missunderstood, I think you meant that I have to edit the DSDT once I have acces to my hackintosh desktop. Am I wrong?
But unfortunetly, I still have problem with the bootable usb, even with the new kext. Now when I boot from the usb, I get an error about 'Waiting on <dict ID="0"> ...' as you can see in the image, than after some second the screen crash. Which should be the problem? When I boot, I'm using the following boot flags: -v, kext-dev-mode=1, dart=0, npci=0x2000, if this can help.
 
 
 
Thanks you.

Share this post


Link to post
Share on other sites

EDIT: Installed clover 4344 and I've put your config and kexts on EFI and I get this:

post-1325453-0-67222300-1512921664_thumb.jpg

 

EDIT2: After 15 min waiting on this screen it finally boot and I'm installing the system right now.

Share this post


Link to post
Share on other sites

 

sorry, I missunderstood, I think you meant that I have to edit the DSDT once I have acces to my hackintosh desktop. Am I wrong?
But unfortunetly, I still have problem with the bootable usb, even with the new kext. Now when I boot from the usb, I get an error about 'Waiting on ...' as you can see in the image, than after some second the screen crash. Which should be the problem? When I boot, I'm using the following boot flags: -v, kext-dev-mode=1, dart=0, npci=0x2000, if this can help.
 
 
 
Thanks you.

 

what ur GPU?

EDIT: Installed clover 4344 and I've put your config and kexts on EFI and I get this:

 

attachicon.gif1512921497568_camera.jpg

 

EDIT2: After 15 min waiting on this screen it finally boot and I'm installing the system right now.

very slow, but if work, ok, go to install

Share this post


Link to post
Share on other sites

attachicon.gifCLOVER.zip

replace, reboot, send me new ioreg

stuck here for a while and then reboot for itself.

 

post-1325453-0-33747300-1512942090_thumb.jpg

 

sometimes I can login but after the desktop is loaded it show a kernel panic with something about AppleIntelCPUPowerManagement, but I can't photo it, it's too fast.

 

EDIT: I've set don't reboot on kernel panic option and then I can photo the kernel panic.

 

post-1325453-0-86332200-1512942461_thumb.jpg

Share this post


Link to post
Share on other sites

stuck here for a while and then reboot for itself.

 

attachicon.gif1512941928307_camera.jpg

 

sometimes I can login but after the desktop is loaded it show a kernel panic with something about AppleIntelCPUPowerManagement, but I can't photo it, it's too fast.

 

EDIT: I've set don't reboot on kernel panic option and then I can photo the kernel panic.

 

attachicon.gif1512942344439_camera.jpg

Use Null Kext

http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=274808

 

u video work in Hackintosh?

Share this post


Link to post
Share on other sites

ok, video works but without QE/CI.

send me new ioreg with new files

I have an Nvidia Geforce gtx 760. You think that the gpu is the problem?

use nvdisable=1

Share this post


Link to post
Share on other sites

Quick question for you all.  Running High Sierra 10.13.2 and the only issue I have is the Display waking from Sleep mode.  The system wakes, but not the display.  Any ideas.  I have tried the FixEDID trick and some other Backlight fix tries, but nothing resolves it.

 

HP All-In-One g013w

Intel i5 4690T

Intel 4600 HD (GT2) - CPU integrated

23" Integrated screen

16 Gig Ram

1 TB SSD (Samsung)

 

https://support.hp.com/us-en/document/c04126402

 

Everything works, and I mean everything including TRIM.  Just the stupid wake on the display will not work.  The system wakes, but the display stays black.

 

I am essentially loading the following kext files from /Library/Extensions:

 

Lilu.kext

AppleALC.kext

FakeSMC.kext and sensor files

IntelGraphicsFixup.kext

RealtekRTL811.kext

CLOVER.zip

gatesjunior-ioreg.zip

Share this post


Link to post
Share on other sites

no

 

No, I'm not SOL ?  Or no, it did not start happening with High Sierra.  I know it's a native card they support.  So it leaves me a little confused.

Share this post


Link to post
Share on other sites

have a native support, but in many cases with IntelHD have problem with sleep ;)

u can try a DSDT, i apply all patches

Share this post


Link to post
Share on other sites

have a native support, but in many cases with IntelHD have problem with sleep ;)

u can try a DSDT, i apply all patches

 

Hmmm.. I suppose I could.  I already decompiled and tried some of them, try to only use what I need..

Share this post


Link to post
Share on other sites

send me new ioreg with new files

use nvdisable=1

I've already tried with nv_disable=1, but got the same error. You think that error is related to the gpu?

 

Thanks you.

Share this post


Link to post
Share on other sites

I've already tried with nv_disable=1, but got the same error. You think that error is related to the gpu?

 

Thanks you.

idk

 

need tests

new ioreg attached, the system can be updated without problems?

 

attachicon.gifMac mini de pedro.zip

i'ts work good, but without power management, u can try add Generate P and C States in config.plist

 

ye, u can update

Share this post


Link to post
Share on other sites

i'ts work good, but without power management, u can try add Generate P and C States in config.plist

 

ye, u can update

 

Generate P and C States was already active on clover when I exported the ioreg file.

Share this post


Link to post
Share on other sites

idk

 

need tests

i'ts work good, but without power management, u can try add Generate P and C States in config.plist

 

ye, u can update

Can you give me some advice on which test should I do in this case? I used all my hackintosh knowledge and tried pretty much everything I know.

You're my last chance  ^_^

 

Thanks

Share this post


Link to post
Share on other sites

I had a fully working build up until 10.13.2. Now, if I shutdown the macOS, it just reboots.

Neither 

<key>FixShutdown</key>
<true/>

nor

<key>HaltEnabler</key>
<true/>

did help. Did something change with the latest macOS version with interpreting ACPI?

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 soumaxetuirk
      If you have a working Brightness Slider and you might be using Brightness slider or manual hotkeys to control brightness then this guide may help you to use your Native hotkeys of laptop.
       
      (All the Credits goes to @RehabMan     For OS-X-ACPI-Debug Kext and DSDT Patches.)
       
       
      This step assumes that you are using RehabMan's VoodooPS2Controller
      Install the kext: https://github.com/RehabMan/OS-X-ACPI-Debug Open MaciASL and click on patch.(Add rehab man repo) Apply "Add DSDT Debug Methods" and "Instrument EC Queries" that are under Brightness Fix. Save the DSDT and restart Look in Syslog as you press the key corresponding to brightness to determine which _QXX methods handle the keys (UPDATE: From Sierra Apple changed logging process. So you won't find ACPIdebug result using syslog command. Instead use following command )
      log show --last 5 | grep ACPIDebug 6. Then patch DSDT:
      into method label _Q1D replace_content begin // Brightness Down\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0205)\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0285)\n end; into method label _Q1C replace_content begin // Brightness Up\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0206)\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0286)\n end; Change the variable _Q1D/_Q1C as per the log. 

      7. Try compiling and check if it generates errors
      8. If it does, then change the PS2M to PS2X according to the one found in your DSDT
      9. Save and place the compiled DSDT.
      10. Now you should see that you have your corresponding keys to change your brightness 
       
       
       FOR  more detail and Queries,Check Out original Post of @RehabMan Here;
      http://www.insanelym...18#entry1997112
      Get Latest Version of  OS-X-ACPI-Debug kext here:
      https://bitbucket.org/RehabMan/os-x-acpi-debug/downloads
    • By AntoineWill
      Hello Everyone.

      I would like to know if anybody here got the correct custom USB SSDT for the Gigabyte Z390 Pro motherboard ?
      I got a Corsaire Carbide 275R case which got 2 extra USB 3.1 Gen 1 ports connected to the motherboard.
       
      I use my hackintosh for 4 months from now. I followed the Glasgood installation guides (attached at the bottom).

      I can't figure out how to clean the total mess I got when I plug my usb devices... And the process that I found here and there is a true nightmare for my noob skills. Any help would be awesome !!

      Links if needed :
      https://www.corsair.com/ww/en/Categories/Products/Cases/Carbide-Series-275R-Mid-Tower-Gaming-Case/p/CC-9011130-WWhttps://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#kf
      Thanks guys !
       
       
    • 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.5.0 (2019-10-15) Reworked interrupt throttling code and added new configuration parameters. 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 hungdv
      Hello guys,
      I was try to install MacOS Mojave on my new machine but no luck. Can anyone show me which guide to fit my system, please?please?please?
      + Mobo: GIGABYTE Z390 AORUS ELITE LGA1151v2
      + CPU: Intel Core i5-9600K 3.7GHz
      + iGPU: Sapphire RX 580 Pulse 8GB
      + Drives: SSD Samsung 970 Pro PCIe NVMe V-NAND M.2 2280 512GB
      + Ram: Crucial Ballistix Sport LT 2x8GB Bus 2666 DDR4
      + PSU: Corsair RM650 80 Plus GOLD
      + Case: Corsair 220T White RGB Airflow Tempered Glass
      + Cooler: Cooler Master HYPER 212 BLACK EDTION
      + Dual Band Network Card Broadcom Bcm94360 867Mbps.
×