Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

896 posts in this topic

Recommended Posts

 

Here is a short list of things to test:

1.) Boot

2.) IP address acquisition via DHCP.

3.) Cable unplug and replug. (Test several times!)

4.) Sleep/wake cycles (Test several times!).

 

 

 

Mieze

 

THANKS Mieze! As for now all the 4 points are working as expected here. Asus Z370 Prime A and i7-8700K. In case of malfunctioning I'll report back. 

 

Have a nice day  :)

Share this post


Link to post
Share on other sites
Advertisement

This is the first test build of version 2.4.0 of IntelMausiEthernet which updates the underlying Linux sources and adds official support for Coffee Lake. All users are encouraged to test it thoroughly. Although I tested it successfully on my I218V, you should keep in mind that this is work in progress which can't be expected to be 100% stable. In case things go wrong and you end up with a kernel panic, you should be prepared to recover your system from that situation.

 

Here is a short list of things to test:

1.) Boot

2.) IP address acquisition via DHCP.

3.) Cable unplug and replug. (Test several times!)

4.) Sleep/wake cycles (Test several times!).

 

In any case, please report back with attached kernel logs of the test run including the boot sequence. In case you need instructions how to retrieve them, please refer to post#1 of the driver's thread in the forum.

 

Good luck!

 

Mieze

     Yay! Well done! Really fulfilled my wish, accidentally solved my problem. 
    This version of the driver works fine on my laptop, and I tested it against the list you provided. every one passed. The attachment is a log of the startup process and the process of plug and unplug cable three times. There is a small detail, that is, plug the cable for the first time after boot, there will be a chance to Auto-negotiation in 10M full-duplex state.
    thanks again!

bootlog1.zip

Share this post


Link to post
Share on other sites

Hello Mieze and greetings from Austria :-) Thank you for developing your driver, I appreciate that I can just download drivers such as your kexts for free when you surely put quite some time into it.

 

Now I have a new mainboard with the new 300 coffee lake series, the Supero C7Z370-CG-L. It uses the i219 (v2) with device ID 0x15b8. Neither your 2.3.0 version nor your newest 2.4.0d0 works, unfortunately.

 

With both versions, the kext enables the NIC and recognizes when I plug in the network cable. But there is no actual connection, it does not receive an IP address via DHCP and when I configure the IP address settings manually, no connection can be established.

 

With Windows 10 on a second drive, the NIC works just fine. I tried unplugging and plugging in the cable several times. Furthermore I also tried the E1000 driver and the exact same behaviour occurs. Cable is recognized when connected, but no actual connection is established.

 

macOS autoconfigures to: 1000baseT, full-duplex, energy-efficient-ethernet, MTU Standard 1500. Playing around with those settings and reverting to 100Mbit/s does not change the behaviour.

 

Now I will try to figure out how to get the log files you asked for in your previous post about the 2.4.0d0 version and I'll write another post with the logs attached. I haven't checked them yet and I am not sure how to get them, yet.

 

Since the kext seems to respond to the device ID and macOS tries to use your kext for the NIC, I am afraid that maybe your driver just does not contain the code to run this NIC properly :( It's a very new mainboard and even though the i219v2 isn't such a new NIC, perhaps my mainboard has a new version of this NIC that isn't known yet?

 

I disabled the NIC in the UEFI, but the UEFI is a mess compared to Asus and Gigabyte, settings aren't explained at all (the user guide that comes with it does not contain them either, and that's supposed to be a professional supermicro product...) and so I am not sure if that is all done correctly. Perhaps I am missing a UEFI setting?

 

Thanks!

Share this post


Link to post
Share on other sites

Hello Mieze and greetings from Austria :-) Thank you for developing your driver, I appreciate that I can just download drivers such as your kexts for free when you surely put quite some time into it.

 

Now I have a new mainboard with the new 300 coffee lake series, the Supero C7Z370-CG-L. It uses the i219 (v2) with device ID 0x15b8. Neither your 2.3.0 version nor your newest 2.4.0d0 works, unfortunately.

 

With both versions, the kext enables the NIC and recognizes when I plug in the network cable. But there is no actual connection, it does not receive an IP address via DHCP and when I configure the IP address settings manually, no connection can be established.

 

With Windows 10 on a second drive, the NIC works just fine. I tried unplugging and plugging in the cable several times. Furthermore I also tried the E1000 driver and the exact same behaviour occurs. Cable is recognized when connected, but no actual connection is established.

 

macOS autoconfigures to: 1000baseT, full-duplex, energy-efficient-ethernet, MTU Standard 1500. Playing around with those settings and reverting to 100Mbit/s does not change the behaviour.

 

Now I will try to figure out how to get the log files you asked for in your previous post about the 2.4.0d0 version and I'll write another post with the logs attached. I haven't checked them yet and I am not sure how to get them, yet.

 

Since the kext seems to respond to the device ID and macOS tries to use your kext for the NIC, I am afraid that maybe your driver just does not contain the code to run this NIC properly :( It's a very new mainboard and even though the i219v2 isn't such a new NIC, perhaps my mainboard has a new version of this NIC that isn't known yet?

 

I disabled the NIC in the UEFI, but the UEFI is a mess compared to Asus and Gigabyte, settings aren't explained at all (the user guide that comes with it does not contain them either, and that's supposed to be a professional supermicro product...) and so I am not sure if that is all done correctly. Perhaps I am missing a UEFI setting?

 

Thanks!

According to the specs, there shouldn't be any problems with this chip. Get me the kernel logs with at least one complete boot sequence and we will se what's going on.

 

Mieze

Share this post


Link to post
Share on other sites

Thank you for the quick reply. Here is the log for "log show --predicate "processID == 0" --debug"

 

The ethernet cable was plugged in from the beginning, at around time 23:24:49 I unplugged it and at around 23:25:10 I plugged it in again.

 

I will look through the log now myself, but unless it's something trivial and especially if the driver itself needs a change, I'll surely need help. Thanks for your time!

logoneboot.txt

Share this post


Link to post
Share on other sites

Thank you for the quick reply. Here is the log for "log show --predicate "processID == 0" --debug"

 

The ethernet cable was plugged in from the beginning, at around time 23:24:49 I unplugged it and at around 23:25:10 I plugged it in again.

 

I will look through the log now myself, but unless it's something trivial and especially if the driver itself needs a change, I'll surely need help. Thanks for your time!

There is no indication for a driver problem in the kernel logs. The NIC seems to work fine. Please check the network configuration as it might be messed up causing such strange behavior.

 

By the way, your ACPI data needs some attention as there are several ACPI related errors in the log file.

 

Mieze

Share this post


Link to post
Share on other sites

Thank you - I will check on the ACPI errors, I saw those too. It might be due to me simply installing a fresh system with Clover and not installing any DSDT patches or what is sometimes done afterwards since the system works just fine as it is (except for the NIC). I just intalled vanilla High Sierra with nvidia web drivers and then made it bootable with Clover, that worked on my other (older) hackintosh just fine.

 

Unfortunately there isn't anything with the network config that I can check, I use good quality managed switches and have dozens of computers in the network including the other hackintosh and several real Macs, and all work well.

 

I just tried attaching another computer NIC <-> NIC with a static IPv4 address config and tried pings, but unsuccessfully. I can try to further check with Wireshark to see what happens, but I see no DHCP discovery packet received on my pfsense firewall/router, so not even the initial DHCP packet makes it out of the NIC.

 

I agree that there are no errors related to your driver visible in the log, so it should be working just fine. But since 0 packets make it across the wire, the NIC obviously isn't working properly, for whatever reason...

Share this post


Link to post
Share on other sites

I just tried attaching another computer NIC <-> NIC with a static IPv4 address config and tried pings, but unsuccessfully. I can try to further check with Wireshark to see what happens, but I see no DHCP discovery packet received on my pfsense firewall/router, so not even the initial DHCP packet makes it out of the NIC.

 

I agree that there are no errors related to your driver visible in the log, so it should be working just fine. But since 0 packets make it across the wire, the NIC obviously isn't working properly, for whatever reason...

No, but I doubt that any packet has ever made it too the NIC. In case of a transmitter hang, the driver resets the chip so that there would be log messages indicating a chip reset every few seconds but there isn't anything like that. Please check the network statistics of the NIC and report back.

 

Mieze

Share this post


Link to post
Share on other sites

That crossover cable hasn't been required anymore for years, NICs automatically switch it over nowadays. In any case, you are correct, Mieze, there are actually dhcp discover packets reaching the pfsense firewall/router, and it responds with a dhcp offer packet in return. Then this starts over, DHCP never completes. I was checking the wrong log before, sorry about that.

 

I see a curious behaviour with a static configuration: When I ping the static IP address, the received packets count in the statistics counts up for each ping that I send. So apparently the NIC receives packets. But on the host I send the pings from, I get a timeout, so the reply packet for my ping is not being sent out.

 

To sum this up: The NIC seems to be receiving packets but not sending out packets, other than that initial request for DHCP when it's enabled. At least that describes the problem enough for searching for it on google...

Share this post


Link to post
Share on other sites

To sum this up: The NIC seems to be receiving packets but not sending out packets, other than that initial request for DHCP when it's enabled. At least that describes the problem enough for searching for it on google...

In case of a transmitter hang, the driver would reset the NIC every few seconds and unless there are those messages there is no indication for a driver bug. Looks more like a DHCP or routing problem. You might also want to try to disable EEE (select medium manually) as it sometimes causes strange things

 

Mieze

Share this post


Link to post
Share on other sites

Oh. God. I just resolved it. You were right all along, it was my networking equipment. Reason was: I installed this new hardware, needed a longer ethernet cable and thus used a different switch port to plug it in, that switch port had the VLAN set to tagged instead of untagged. While Windows was able to handle this - or rather, Windows ignored it - macOS was obviously not happy.

 

...immediately after I set that switch port from tagged to untagged, DHCP received the address and it's resolved. So now I am one of those people "my stuff is fine, i know my stuff, it can't be my stuff... oh it was my stuff..."

 

Thanks for making the time. I might not have found the issue without your hint.

Share this post


Link to post
Share on other sites

Hi Mieze,

after several weeks of using I must say there is something unusual: after wakeup my rig (the one in signature) often freezes, it happens mainly in Safari and after that only mouse is working and nothing else. And that point I have the only chance to hard reboot the machine. 

So I reverted back to v. 2.3.0 that still works with my mobo and these behaviours have almost disappeared. 

But As I cannot be sure it depends on your ethernet kext, before sending you any log or other data I kindly ask you to point me to some tutorial where I can learn how to make a diagnostic report from the console and its log files. I really know nothing about them. 

After that if I find some evidence that the problem can be truly related with your kext, I'll send the proper data to you. In the meanwhile if you have new betas to test I'd glad to give it a try. 

Thank you! 

Share this post


Link to post
Share on other sites
3 hours ago, hackaro said:

Hi Mieze,

after several weeks of using I must say there is something unusual: after wakeup my rig (the one in signature) often freezes, it happens mainly in Safari and after that only mouse is working and nothing else. And that point I have the only chance to hard reboot the machine. 

So I reverted back to v. 2.3.0 that still works with my mobo and these behaviours have almost disappeared. 

But As I cannot be sure it depends on your ethernet kext, before sending you any log or other data I kindly ask you to point me to some tutorial where I can learn how to make a diagnostic report from the console and its log files. I really know nothing about them. 

After that if I find some evidence that the problem can be truly related with your kext, I'll send the proper data to you. In the meanwhile if you have new betas to test I'd glad to give it a try. 

Thank you! 

According to the problem description I can almost rule out a driver bug. Sounds more like a messed up system (system caches, in particular as 2.3.0. doesn't exhibit this behavior) or a general wakeup issue (DSDT, etc.). Anyways, see post#1 of this thread for instructions how to collect kernel logs in case you find something contradicting my thesis.

Mieze

Share this post


Link to post
Share on other sites
41 minutes ago, Mieze said:

I'm sorry but the X550 is a device with a completely different architecture. :(

Mieze

Is it possible to use the " dsdt " method. Seeking guidance:blush:

Share this post


Link to post
Share on other sites
Just now, liuhongxin1993 said:

Is it possible to use the " dsdt " method. Seeking guidance:blush:

As already stated, the X550 has a completely different architecture and can't be supported by IntelMausiEthernet. Sorry!

Mieze

Share this post


Link to post
Share on other sites
On ‎2018‎年‎4‎月‎7‎日 at 8:04 PM, Mieze said:

As already stated, the X550 has a completely different architecture and can't be supported by IntelMausiEthernet. Sorry!

Mieze

x540 driver ,Can modify it?Seek guidance。。。。。:blush::blush:

 SmallTreeIntel8259x.kext.zip

Linux:ixgbe-5.3.6.tar.zip

https://www.small-tree.com/support/download_category?cat_id=6

Adding 10 gigabit ethernet networking to your hackintosh is now extremely easy. You simply need to add these three kexts to your EFI/CLOVER/KEXTS/OTHER folder and you will have a working card! This method works so far on the following cards:

Supported devices for SmallTreeIntel8254x.kext:

  • 8086:1010 82546EB Gigabit Ethernet Controller (Copper)
  • 8086:1011 82545EM Gigabit Ethernet Controller (Fiber)
  • 8086:1012 82546EB Gigabit Ethernet Controller (Fiber)
  • 8086:101d 82546EB Gigabit Ethernet Controller
  • 8086:1026 82545GM Gigabit Ethernet Controller
  • 8086:1027 82545GM Gigabit Ethernet Controller
  • 8086:1028 82545GM Gigabit Ethernet Controller
  • 8086:105e 82571EB Gigabit Ethernet Controller (Also covered by AppleIntel8254XEthernet.kext)
  • 8086:105f 82571EB Gigabit Ethernet Controller
  • 8086:1079 82546GB Gigabit Ethernet Controller
  • 8086:107a 82546GB Gigabit Ethernet Controller
  • 8086:107b 82546GB Gigabit Ethernet Controller
  • 8086:107c 82541PI Gigabit Ethernet Controller
  • 8086:107d 82572EI Gigabit Ethernet Controller (Copper)
  • 8086:107e 82572EI Gigabit Ethernet Controller (Fiber)
  • 8086:10a4 82571EB Gigabit Ethernet Controller
  • 8086:10b5 82546GB Gigabit Ethernet Controller (Copper)
  • 8086:10b9 82572EI Gigabit Ethernet Controller (Copper)
  • 8086:10bc 82571EB Gigabit Ethernet Controller (Copper)

SmallTreeIntel82576.kext:

  • 8086:1521 I350 Gigabit Network Connection
  • 8086:1522 I350 Gigabit Fiber Network Connection
  • 8086:1533 I210 Gigabit Network Connection (Also covered by AppleIntelI210Ethernet.kext)

SmallTreeIntel8259x.kext:

  • 8086:10c6 82598EB 10-Gigabit AF Dual Port Network Connection
  • 8086:10c7 82598EB 10-Gigabit AF Network Connection
  • 8086:10c8 82598EB 10-Gigabit AT Network Connection
  • 8086:10ec 82598EB 10-Gigabit AT CX4 Network Connection
  • 8086:10d8 82599EB 10 Gigabit Network Connection
  • 8086:10fb 82599ES 10-Gigabit SFI/SFP+ Network Connection
  • 8086:10f1 82598EB 10-Gigabit AF Dual Port Network Connection
  • 8086:151c 82599 10 Gigabit TN Network Connection
  • 8086:150b 82598EB 10-Gigabit AT2 Server Adapter
  • 8086:1528 Ethernet Controller 10-Gigabit X540-AT2
  • 8086:10fc 82599 10 Gigabit Dual Port Network Connection
  • 8086:1560 Ethernet Controller X540

Share this post


Link to post
Share on other sites

@liuhongxin1993: This is off-topic. Please create a new thread in order to keep this one focused on IntelMausiEthernet.

Share this post


Link to post
Share on other sites

Hello,

The new B360 motherboard now uses the new Intel I219-V with Device ID 8086_15BC. I tried adding the Device ID to the current 2.3.0 release but as expected, it wouldn't work. Would you mind take a look at it ?

Edited by vusun123

Share this post


Link to post
Share on other sites
2 hours ago, vusun123 said:

Hello,

The new B360 motherboard now uses the new Intel I219-V with Device ID 8086_15BC. I tried adding the Device ID to the current 2.3.0 release but as expected, it wouldn't work. Would you mind take a look at it ?

Try version 2.4.0d0 which can be found here in this thread because it already supports this chip.

Mieze

Share this post


Link to post
Share on other sites

Here is a new development version of the driver (2.4.0d2) which changes interaction with the ME during sleep/wake and cable plug cycles in order to resolve problems with LM chips which support AMT. All users are encouraged to test it thoroughly, in particular those with LM versions of the supported NICs. Tests should focus on sleep/wake and cable plug/unplug events.

Good luck!

Mieze :cat:

IntelMausiEthernet-V2.4.0d2.zip

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 Bahaa
      Need help here
      My graphic card is detached 7mb
      and I try a lot of solution and no one work 
      can any one help
       

    • By Angelo_
      Just recently installed Mojave on my yoga 730(i5-8250u, 8gb of ram and 1080p 13.3" touchscreen) and got many features working, now the only issues are that my igpu is shown as only 7mb(and not metal capable, not sure whether it is or not) even tho I should've changed it from 5917 to 5916 (added both EFI folder and send me), the screen is shown as a 30.5" in system information and the cpu even tho I extracted the ssdt for it with ssdtPRGen.sh and appleintelinfo.kext to get low frequency info (ssdt was done with info 15,400,1600,3400 so it should go between 16-3400mhz and down to 400 in idle), idk what is wrong with my installation, can you guys help me or linke me something to fix those issues?
       
      Ps thunderbolt shows as no device found, is it regular for hackintoshes to be that way or do I need something for that too? Laptop has 2 tb3 ports as x4 pcie 3
      EFI.zip
      Send me Angeloss-MacBook-Pro.zip
    • By Gymnae
      Introduction
      The H370 chipset powers 8th generation Intel Core-i CPUs. Even though the name H370 rings comparable to Z370, the H370 is based on newer silicon. This it also requires some new approaches compared to the Z370. An example would be on-die USB 3.1 and WiFi support.
       
      Since this guide is not a "hold-your-hand-every-step" guide, I assume you know:
      Clover installation and configuration How to create an install medium for MacOS Access and configure the BIOS Have heard of ACPI patching (I'm a newb at this myself)  
      What works
      Sleep (via DSDT edits and emulated NVRAM) On-board Audio (via AppleALC and native AppleHDA) Native power management (without any kext or patch) All USB ports (and only those present are active) iGPU for both acceleration and display dGPU (I'm running an Nvidia GTX 1080)  
      Untested
      NIC --> I'm using WiFi only  
      What doesn't work
      Native NVRAM via AptioMemoryFix.efi DMVT Pre-alloc higher than 64MB (but not necessary)  
      Community additions
      User @Panzerschiffe added a helpful post, altering this guide for user with AMD cards and not needing on-board sound.
      He also runs Mojave, which I don't run yet.
       
       
      Changes to the guide:
      22.5.18: Added SSDT hot-patching to enable sleep, replacing DSDT static patching as an alternative.
      23.5.18: Add iMac18,1 as alternative SMBIOS config for those relying on the iGPU for output
      25.6.18: Added update info
      28.8.18: Small changes for clarity, changed info for afps loading & updated USB patch for 13.6
      04.10.18: Update to Mojave will come once Mojave is more mature
      02.12.18: Removed unnecessary patches, fakepciid and audio patch method & linked to AMD post & added whatevergreen.kext as replacement for previous GPU kexts
      02.03.19: Removed unnecessary fakeid and ig_platform_id injections, ACPI patches - this is all handled by whatevergreen & lilu. In testing is a Framebuffer patch, see this post.
      04.03.19: Added Germany keyboard layout and updated pre-patched DSDT.aml removed DSDT patching
       
       
      1. Installation
      This guide heavy inspired by the work of /u/corpnewt of /r/hackintosh and his (sorta) Vanilla guide
       
      1.1 Create the install media for MacOS
      Follow this, if you are using a Mac to start off with. If you are totally new to MacOS, then please check the basic guide Creation of an installer media in windows or linux
       
      1.2 Install Clover on the install media
      Using the Clover installer, ensure you are installing to the USB medium you are using for the installer.
      Chose the following options, leaving the others on default: 
       
      UEFI driver: AptioMemoryFix UEFI driver: ApfsDriverLoader UEFI booting only Install to ESP  
      You have to get your hands on an apfs.efi. A google search can help, or extracting it from the Installer package. Make sure you procure a version matching the MacOS version you are about to install. Place the apfs.efi in drivers64UEFI.
       
      1.2 Adjust the config.plist for the installer
      You can use the config.plist attached as a guideline, but take a look at it before and at least adjust the SMBIOS - otherwise it won't boot.
      Attention: The attached plist contains audio patches introduced by a post-install step. If you run into problems, you might remove those. It also contains a manual slide value, which should normally not be needed, but works fine for me. It is also tuned for usage with an Nvidia Pascal dGPU as main GPU.
       
      The config you create now should serve you nicely for install and running the system.
       
      Take care of adding the following basics:
      SMBIOS: iMac18,3 - You can generate a serial number via Clover Configurator. The creation of a proper SMBIOS is covered in many guides to good extend Note: If you aim at using the iGPU for output, a user reported that iMac18,1 works better - since iMac18,3 produces severe flicker. I'm now also testing 18,1 Look at the graphics section and adjust the injection for Intel to your situation  
      Fixes

      Patches

      Devices

      Graphics
      Important:
      Change 0x59120003 to 0x59120000 if you don't use a dGPU as your main display Driver and instead use the iGPU for output.
      Also note. SMBIOS iMac18,1 has been reported to work better in this configuration. But 18,3 works fine for me.

      Kernel and Kext patches
       
      1.3 kexts and friends
      Add the supplied SSDT-UAIC.aml to "patched" - it limits the injected USB Ports to the actual number and ports valid for this board.
       
      Required kexts on "Other":
      FakeSMC.kext Whatevergreen.kext Lilu.kext AppleALC.kext IntelMausiEthernet.kext in case you're running Ethernet USBInjectAll.kext with the HCI-300-series-injector.kext --> These two should be installed to /L/E after install  
      We are leaving sound out at the moment, this is something for post-install.
       
      1.4 Check BIOS and install
      You should be ready for install. But before you reboot, please take a look at your BIOS and set it up accordingly (copied from the aforementioned guide and adapted):
      Load Optimized Defaults Disable VT-d setting If your system has Secure Boot Mode, disable it Enable CSM - This is sometimes needed to dual screens to work Set OS Type to Windows 8/10 or OtherOS - I have not seen a difference Turn off internal Serial and Parallel port Turn off Network stack for boot Turn off wake-on-lan (for now) Set XHCI Handoff to enabled Don't enable decode over 4G Depending on your GPU, set priority for boot Set internal GPU (iGPU) to enable - not auto or disabled Set DMVT pre-alloc min to 64MB and max to 128MB. For this selection to appear you might need to reboot after setting iGPU to enable Set USB legacy to enabled Activate XMP profile 1 f your Ram has it (mine doesn't and I added the timings manually) Set ERP to enable, disable platform power management (I need to do more research if this could be enabled)  
      I've attached my current BIOS config "hack2". You can place that on a fat32 drive (the EFI partition of your install USB drive might be an idea) and see if it loads. It's made for and with the F2 BIOS.
       
      The install itself should be like other MacOS Hackintosh installs with it several reboots and ensuring to select the correct boot device in Clover.
       
      2. Post-install
       
      2.1 Install clover on target
      This is a no-brainer, but install a fresh copy of Clover on your target medium.
       
      During install select again AptioMemoryFix but also additionally
      EmuVariableUefi-64.efi Install RC scripts on target volume because otherwise NVRAM doesn't seem to work
       
      After the install, copy
      config.plist contents of "Other" content of "patched" to your new clover install.
       
      2.2 Edit ACPI for slumber
      Choose one option, not both. The hot-patch is experimental, but for the moment it is stable.
       
      2.2.1 Edit DSDT
      No more need for manual DSDT patching. If you still do it, you might run into unstable sleep. SSDT hot-patching + sane clover.config edits are enough
       
      This is necessary only once on initial install and every time, you edit or upgrade the BIOS. The DSDT.aml attached to this post might work for your system or give you a file to compare to. Don't expect it to work for you, though.
      EDIT: Since moving from F2 BIOS to F12 I did not repatch and sleep is still somewhat reliable. But to be 100% sure, you can still follow these steps.
      I won't go into the details of DSDT extraction and patching. There are better guides (the linked guide is a rip-off of rehabman's guide from a different forum). Please follow such a guide to extract your ACPI data.
       
      Locate and disassemble the DSDT with the newest iasl binary you can put your hands on, then open it with MacIASL in its newest version you can find (Hint: Here is a good source) You can check if the version is new enough if MacIASL doesn't throw error upon compiling a freshly extracted DSDT.aml or DSDT.dst
       
      Add rehabmans repo (as per linked guide) and apply the following patches:
      Rename _DSM to _XDSM Fix _WAK Arg0 v2 USB3 _PRW 0x6D Skylake (instant wake) Find the CNVW device and remove the _PWR function there.
       
      Compile the DSDT and place it in "patched".
       
      2.2.2 Use SSDT hot-patching
      Instead of having to re-extract and re-patch the DSDT on every BIOS change or update, Hardware change one can also use ACPI hot-patching.
      It's a combination of config.plist patches and an SSDT, which is hot-patched into the ACPI (if I understand the process correctly)
       
      You need to add this SSDT-GPRW.aml to your Clover folder in the designated position at Clover/ACPI/patched You need to add this patch to your config.plist. It goes into the DSDT patch section  
      Note: This works for me, but the patch removes the _PRW method from all devices in the DSDT. This could have side-effects. So far, I have seen none. At the moment I'm also not applying any other patch, compared with the additional edits I made to the DSDT method before.
       
      2.3 Install kexts to system
      As mentioned in the install section, it's better to follow rehabman's instruction and install USBinjectAll.kext to /L/E:
      sudo cp -R Release/USBInjectAll.kext /Library/Extensions sudo touch /System/Library/Extensions && sudo kextcache -u / 2.4 Enable onboard Audio - Install AppleALC kext
      Make sure your EFI partition is mounted and that you have a vanilla AppleHDA kext available. See below for a guide how to get a vanilla AppleHDA if needed
      Note: Our Audio codec is ALC887 and it's running with layout ID 1.
      Download the newest AppleALC kext from here and install it together with lilu.kext from here into your usual /clover/kexts/others location. Done. No scripts or config.plist patches necessary.
      Add layout ID 1 to config.plist, if it's not there yet:
      <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> <key>ResetHDA</key> <true/> </dict> If you previously  installed any  audio patches, please follow this guide to "vanilla-ize" your install.
       
      2.5 Optional steps for Graphics
      If you have a dGPU, now it's the time to install its drivers and adjust the config.plist for it. The detaisl are specific to your GPU and thus of scope of this guide. Yet, my supplied config.plist is ready to be used with Nvidia Pascal cards and using the Nvidia web driver.
      Whatevergreen.kext helps with Intel iGPU and NVIDIA dGPU fixes.
       
      At the moment I'm also testing out a special bootflag: 'shikigva=12' to enable faster rendering in Final Cut Pro X. Without whatevergreen.kext and a shikigva bootflag, rendering in final cut seem very slow.
       
      2.5.1 Framebuffers
      If you're facing problems with output from your internal GPU, you can try the framebuffer patches listed by @BackwardMac:
       
      2.6 Install a proper keyboard layout
      You might not be using a fancy Apple branded keyboard. If you use a PC keyboard, you might be annoyed by the differing layout and usage of keys. As a German, you might find yourself quitting applications, since alt gr + Q won't add an @, but quit your current application. To fix this, you can simply install a different keyboard layout. Copy it to /Library/Keyboard Layouts/ and chose the layout in System Preferences, Keyboard in the section "Other". Deleting the previously selecting layout makes sure that only this one is used. Nice little trick.
       
      A keyboard layout for German keyboards is attached and works wonders
       
      3. Updating
      Updating inside 10.3.x/ 10.4.x point updates doesn't require much attention:
      Download the update from the AppStore as any Mac would do Allow the system to reboot Before booting MacOS with Clover, make sure to disable extra drivers for dGPUs which require non-native support. If using an Nvidia dGPU: Remove "nvda_drv=1"  from your boot arguments and disable Nvidia injection If using a non natively supported AMD card, do the same for AMD (I'm not using AMD, thus I cannot be specific) Boot into the newly created Install MacOS partition Repeat this process until the Install partition is gone Boot MacOS again, still following 3., and potentially install updated drivers Your Audio might require re-patching  
      4. ToDo
      Move away from static DSDT patching to SSDT hotpatching --> requires my work Native NVRAM --> requires developer work Audio without AppleHDA patching --> requires developer work  
      5. Thanks to
      @MaLd0nfor helping finding the right way with the DSDT
      @RehabMan, for being a legend and helping me out patching
      @toleda, for audio patches for the 300 series
      /u/corpnewt, for his superb vanilla guide
      @wmchris for his super XPS 9550 guide and introducing me to hot-patching
      @Panzerschiffe for his addition to this guide
      all the developers of clover and it's awesomeness
       
      SSDT-UIAC.aml
       
       
       
      win-germany.keylayout
       
    • By PixelLover
      I'm in the middle of my first hackintosh (High Sierra) on my ZenBook Pro UX501VW-US71 laptop using the Vanilla Install. I've tried using different config.plst files and I've gotten the furthest with RehabMan's own (linked here). It hangs at error message IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0.   Can anyone help me figure out what changes to make to the config.plst file for my specific laptop (which is where I assume the problem lies)   System Specs: Intel Skylake Core i7­-6700HQ 2.6 GHz Quad­core
      Intel® HD Graphics 530 Nvidia GTX 960M 2G 15.6" Touch IPS 4K Ultra­-HD display, 3840 x 2160 resolution   Kexts: AppleALC.kext FakeSMC.kext Lilu.kext USBInjectAll.kext WhateverGreen.kext  
    • By grisno
      Hi people,
       
      Installer to activate the sound card REALTEK ALC282-v2 (10ec:0282) with LayoutID 1 or 3 in MacOS. This installer does not contain AppleHDA patched Kext. To work properly, it must be installed over vanilla AppleHDA.kext.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      Speakers : OK Headphones : OK HDMI Audio : OK (Intel HD4K Tested) LineIn : N/A (Model Without LineIn) MicInt : OK MicIntNoiseReduction : OK MicExt : N/A (Model Without MicExt) AutoDetectLineIn : N/A (Model Without LineIn) Sleep : OK WakeUp : OK AutoSleep : OK Hibernate : OK Siri : OK   Tested Laptops:
       
      - HP Pavillion 15-D002SS
       
      Coming Soon:
       
      - Unified installer for the different supported operating systems.
      - Support model with LineIn jack.
       
      Modified Verbs:
      01271C20 01271D00 01271EA0 01271F90 01471C10 01471D00 01471E17 01471F90 01871CF0 01871D00 01871E00 01871F40 01E71CF0 01E71D00 01E71E00 01E71F40 02171C30 02171D10 02171E21 02171F00 01470C02   DSDT:
       
      Patch to apply with MaciASL in your DSDT
      ######################################### HDEF v1.00######################################## into method label _DSM parent_label HDEF remove_entry;into device label HDEF insertbeginMethod (_DSM, 4, NotSerialized)\n{\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "layout-id", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n //"layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 },\n "hda-gfx", Buffer() { "onboard-1" },\n "PinConfigurations", Buffer() { },\n })\n}\nend;  
×