Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

896 posts in this topic

Recommended Posts

Mieze: should we still use the ssdt patch or new release of drivers can be installed with no ssdt injection?

No, the SSDT-patch is obsolete now!

 

Mieze

Share this post


Link to post
Share on other sites
Advertisement

I'm a little out of the loop, just installed version 2.2.0d4 on Sierra. How/where do I find the driver output? There seems to be absolutely no output in any of the Console views.

Share this post


Link to post
Share on other sites

I'm a little out of the loop, just installed version 2.2.0d4 on Sierra. How/where do I find the driver output? There seems to be absolutely no output in any of the Console views.

I knew this question would be posted here one day because Apple reworked logging in Sierra completely. In Terminal type

log show --predicate "processID == 0" --debug

in order to retrieve kernel logs. See "man log" for further information.

 

Mieze

Share this post


Link to post
Share on other sites

I decided to make version 2.2.0d4 the official version 2.2.0 and updated the prebuilt binary in the download section. As always, source code can be found on GitHub.

 

Have fun!

 

Mieze  :cat:

 

Thanks great works on this and your Realtek8111 both are rock solid and if the drives being copied too support the writing speed just about fully saturate the link when copying. This over a period of about a day it took me to copy 7TB of data between two system my main data storage system and new second backup system I setup both running raidz on zfs filesystem. Anytime I looked at it it was doing 95-105 MB/s the smaller files going the lowest speed for the couple of seconds it was taking for them, the larger getting the highest as the link could get up to full speed then, I was using rsync to copy between the machines. 

Share this post


Link to post
Share on other sites

WoL seems not to work. I'm using the Intel I219V (ASUS z170 pro gaming). 2.2.0d4 on Sierra

In most cases this is due to a:

  • Wrong BIOS setting.
  • DSDT error.

Anyway, please post kernel logs showing a sleep/wake cycle.

 

Mieze

Share this post


Link to post
Share on other sites

In most cases this is due to a:

  • Wrong BIOS setting.
  • DSDT error.

Anyway, please post kernel logs showing a sleep/wake cycle.

 

Mieze

I'm not using DSDT and I think my BIOS settings are correct. WoL is working when i shutdown the PC in Windows and also in Clover. WoL is working on macOS in sleep mode but not after a shutdown.

 

EDIT: I did just read about WoL after a full shutdown on Mac and I think the problem is the missing S5 support. Thank you Mieze ^_^

 

sleep/wake

PMRD: prevent idle sleep list: IODisplayWrangler- (0)
prevent idle sleep list: IODisplayWrangler- (0)
PM response took 146 ms (52, logd)
kern_direct_file(/var/log/SleepWakeStacks.bin): vp size 172032, alloc 172032, mp free 721066917888, keep free 34359738368
max io 0x2000000 bytes
kern_open_file_for_direct_io(0)
kern_open_file_for_direct_io took 0 ms
kern_open_file_for_direct_io took 0 ms
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
polled file major 1, minor 0, blocksize 4096, pollers 5
polled file major 1, minor 0, blocksize 4096, pollers 5
IOOpenDebugDataFile: opened debugdata file
IOHibernateSystemPostWake: Closing debugdata file
kern_close_file_for_direct_io
vnode_close(0)
PM response took 3119 ms (47, powerd)
kern_direct_file(/var/log/SleepWakeStacks.bin): vp size 172032, alloc 172032, mp free 721066917888, keep free 34359738368
max io 0x2000000 bytes
kern_open_file_for_direct_io(0)
kern_open_file_for_direct_io took 0 ms
kern_open_file_for_direct_io took 0 ms
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
polled file major 1, minor 0, blocksize 4096, pollers 5
polled file major 1, minor 0, blocksize 4096, pollers 5
IOOpenDebugDataFile: opened debugdata file
setWakeOnMagicPacket() ===>
Ethernet [IntelMausi]: Wake on magic packet enabled.
setWakeOnMagicPacket() <===
disable() ===>
Ethernet [IntelMausi]: LPIC=0x11000011.
clearDescriptors() ===>
clearDescriptors() <===
Ethernet [IntelMausi]: WUFC=0x00000002.
Ethernet [IntelMausi]: Link down on en0
disable() <===
setPowerState() ===>
Ethernet [IntelMausi]: switching to power state 0.
setPowerState() <===
         0 [Time 1474900674] [Message PMRD: System Sleep
IOCPUSleepKernel
ACPI SLEEP
ACPI S3 WAKE
Wake reason: PWRB XDCI GLAN (User)
Wake reason: PWRB XDCI GLAN (User)
IOPlatformWakeAction -> AppleRTC
IOPlatformWakeAction -> AppleKeyStore
Started cpu 2 (lapic id 00000002)
Started cpu 4 (lapic id 00000004)
Started cpu 6 (lapic id 00000006)
Started cpu 1 (lapic id 00000001)
Started cpu 3 (lapic id 00000003)
Started cpu 5 (lapic id 00000005)
Started cpu 7 (lapic id 00000007)
gIOLastWakeAbsTime: 135131997503
PMRD: System Wake
RTC: PowerByCalendarDate setting ignored
RTC: PowerByCalendarDate setting ignored
****[IOBluetoothHIDDriver][handleWake] -- sending EXIT HID SUSPEND returned 0xe00002be ****

**** [IOBluetoothHIDDriver][handleWake] -- acknowledgeSetPowerState() returned 0x0000 ****
RTC: PowerByCalendarDate setting ignored
RTC: PowerByCalendarDate setting ignored
****[IOBluetoothHIDDriver][setPowerStateWL] -- Wake -- return 10 seconds -- powerStateOrdinal = 1 ****
Previous sleep cause: 5
PMRD: prevent idle sleep list: IODisplayWrangler+ (1)
prevent idle sleep list: IODisplayWrangler+ (1)
setPowerState() ===>
Ethernet [IntelMausi]: switching to power state 1.
setPowerState() <===
enable() ===>
[IOBluetoothHostControllerUSBTransport][SetRemoteWakeUp] -- deviceRequest() failed: 0xE0005000 (0xe0005000 -- Unknown)
setMulticastMode() ===>
setMulticastMode() <===
enable() <===
setWakeOnMagicPacket() ===>
Ethernet [IntelMausi]: Wake on magic packet disabled.
setWakeOnMagicPacket() <===
setMulticastMode() ===>
setMulticastMode() <===
setMulticastList() ===>
setMulticastList() <===
getPacketFilters() ===>
getPacketFilters() <===
kPEDisableScreen 1
kPEEnableScreen 1
kPEEnableScreen 1
kPEDisableScreen 1
kPEEnableScreen 1
Ethernet [IntelMausi]: checkLinkStatus() returned 1.
Ethernet [IntelMausi]: EEE mode = 0x6000, adv=0x0006, lpa=0x0006
Ethernet [IntelMausi]: pollIntervalTime: 170us
Ethernet [IntelMausi]: Link up on en0, 1-Gigabit, Full-duplex, Rx/Tx flow-control, energy-efficient-ethernet
Ethernet [IntelMausi]: requireMaxBusStall(75000ns).
Ethernet [IntelMausi]: CTRL=0x58180240
Ethernet [IntelMausi]: CTRL_EXT=0x995a1027
Ethernet [IntelMausi]: STATUS=0x40080083
Ethernet [IntelMausi]: RCTL=0x04008002
Ethernet [IntelMausi]: PSRCTL=0x00040402
Ethernet [IntelMausi]: FCRTL=0x80005048
Ethernet [IntelMausi]: FCRTH=0x00005c20
Ethernet [IntelMausi]: RDLEN(0)=0x00002000
Ethernet [IntelMausi]: RDTR=0x00000000
Ethernet [IntelMausi]: RADV=0x00000000
Ethernet [IntelMausi]: RXCSUM=0x00002300
Ethernet [IntelMausi]: RFCTL=0x000380c0
Ethernet [IntelMausi]: RXDCTL(0)=0x00010000
Ethernet [IntelMausi]: RAL(0)=0xd5dc562c
Ethernet [IntelMausi]: RAH(0)=0x80007d42
Ethernet [IntelMausi]: MRQC=0x00370001
Ethernet [IntelMausi]: TARC(0)=0x0d800403
Ethernet [IntelMausi]: TARC(1)=0x45000403
Ethernet [IntelMausi]: TCTL=0x3103f0fa
Ethernet [IntelMausi]: TXDCTL(0)=0x01410000
Ethernet [IntelMausi]: TXDCTL(1)=0x01410000
Ethernet [IntelMausi]: TADV=0x0000001c
Ethernet [IntelMausi]: TIDV=0x0000001c
Ethernet [IntelMausi]: MANC=0x00000000
Ethernet [IntelMausi]: MANC2H=0x00000000
Ethernet [IntelMausi]: LTRV=0x88b988b9
Ethernet [IntelMausi]: PBA=0x0006001a
getPacketFilters() ===>
getPacketFilters() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
SandboxViolation: fontd(273) deny(1) file-issue-extension /Network/Library
SandboxViolation: fontd(273) deny(1) file-issue-extension /Network/Library
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
BNBMouseDevice::setPowerState(0xf0be5ab5025d14e3, 0 -> 1) timed out after 10202 ms
BNBMouseDevice::setPowerState(0xf0be5ab5025d14e3, 0 -> 1) timed out after 10202 ms
IOHibernateSystemPostWake: Closing debugdata file
kern_close_file_for_direct_io
vnode_close(0)
****[IOBluetoothHIDDriver][handleWake] -- sending EXIT HID SUSPEND returned 0x0000 ****

**** [IOBluetoothHIDDriver][handleWake] -- acknowledgeSetPowerState() returned 0x0000 ****

Share this post


Link to post
Share on other sites

I knew this question would be posted here one day because Apple reworked logging in Sierra completely. In Terminal type

log show --predicate "processID == 0" --debug

in order to retrieve kernel logs. See "man log" for further information.

 

Mieze

 

Cheers Mieze, I will keep an eye on that. Shame Apple made it so awkward to see whats going on. (esp as my logs are apparently being spammed with "kernel: (Sandbox) SandboxViolation: com.apple.PhotoI(756) deny(1) mach-lookup com.apple.photoanalysisd" warnings). Amongst others.

Share this post


Link to post
Share on other sites

I am jumping on this topic as I am still investigating my unstable Yosemite Hackintosh. The main suspect for hundreds of error messages in the logs ..

 

(from Windows_Server: surface testing not allowed, from iconserviceagent: crashes, from spinball-daemon: numerous messages indicating freezing of several apps for seconds)

 

... was always my frame buffer patches for my ATI RX290 graphics card. However I am observing a particular unstable system when I have mounted one or several disk shares (AFS) from my NAS or other network sources.

Thus I wonder whether the LAN driver AppleIntelE1000e.kext might be the culprit?  To be clear, booting is fine, OSX 10.10.5 works but from time to time it gets very laggy for no apparent reason.

Share this post


Link to post
Share on other sites

Thus I wonder whether the LAN driver AppleIntelE1000e.kext might be the culprit?  To be clear, booting is fine, OSX 10.10.5 works but from time to time it gets very laggy for no apparent reason.

Honestly, I don't understand how you relate the problems to IntelMausiEthernet.kext anyway?

 

Mieze

Share this post


Link to post
Share on other sites

Honestly, I don't understand how you relate the problems to IntelMausiEthernet.kext anyway?

 

Mieze

 

And I would add most times I see these laggy networking post made it is always a GUI problem. Using a GUI method of transferring here when I see useless transfer speed killing it off and doing a rsync or scp most times results in better network transfer speed and no lagging in the Desktop GUI at all. Either that or they are expecting to saturate the network connection (usually gigabit) with hard drives in the system that will at best most times only do half that network connection speed when written too. And if running the OS on that same drive at the time of transfer then good luck on it not being laggy with all the drive I/O going on.

Share this post


Link to post
Share on other sites

So do you use IntelMausiEthernet or AppleIntelE1000e?

AppleIntelE1000e is buggy while IntelMausiEthernet is really working fast and stable.

So if you still using AppleIntelE1000e i suggest to change it.

 

To your graphicsbug:

The HD4600 is a little bit tricky to configure, as special the framebuffer which need to be configured correctly (also a binpatch is suggested from my side) if you want it working 100%.

So i think there could be your problem.

Here is a old link which shows how the framebuffer is assembled: https://pikeralpha.wordpress.com/2014/08/20/yosemite-dp6-with-hd4600/

Share this post


Link to post
Share on other sites

Thanks @wastez but I am using the ATI R290X graphics card. I cannot enable the internal HD4600 graphics as I always get "memory allocation" errors during the Clover boot. I spend millions of hours searching the boards for the best Framebuffer patch. I now have one which is reasonable stable (with 2 monitors) but still shaky as described above.

 

Anyway, I replaced the AppleIntelE1000 with the IntelMaus Kext. It works but no difference to my problem. The search goes on... :unsure:

 

@Mieze: Because I see more freezes when connected to my LAN..

 

@MacUser: Even if it would be a "GUI Problem" I have to search for the cause. I am not building a Hackintosh for working from the command line.

Share this post


Link to post
Share on other sites

Thats a strange thing because the network driver has realy nothing to do with graphics.

The only thing which is imagineable is a irq Problem.

Are you using a good patched dsdt?

Share this post


Link to post
Share on other sites

@haegar33: I'd suggest to move the discussion of the problem over to another thread which is dedicated to graphics.

 

Mieze

Share this post


Link to post
Share on other sites

Thanks @wastez but I am using the ATI R290X graphics card. I cannot enable the internal HD4600 graphics as I always get "memory allocation" errors during the Clover boot. I spend millions of hours searching the boards for the best Framebuffer patch. I now have one which is reasonable stable (with 2 monitors) but still shaky as described above.

 

@MacUser: Even if it would be a "GUI Problem" I have to search for the cause. I am not building a Hackintosh for working from the command line.

 

I use two monitors connected to a HD4600 (for the hell of it tried three for testing all ports at once except vga all three worked fine) with only the inject Intel set in the clover config.plist with iMac14,2 system definition. I think it is the setting to 64mb for size for the graphics in the BIOS that is the key to it working correctly. You can search all you want it is the way the protocols are implemented in the operating system that is the problem something you will never be able to change. When I see junk 25-30MB/s transfer using gui killing it off and doing a rync or scp I get full speed 100+MB/s leaves no doubt in my mind that it is gui/protocol used in that gui operation at the time that is the problem, your loss if you want to spend that extra time waiting because your scared of the command line.

Share this post


Link to post
Share on other sites

Guys i know the first page says the latest pre built in the downloads section is for 10.11 and up but is there anyone using it in Yosemite 10.10.5 ? 

Share this post


Link to post
Share on other sites

hi, Thanks,

 

I'm pretty new to hackintosh. is there a simpler method for installing? using kext util or doesn't that work?

Share this post


Link to post
Share on other sites

@arjanv

 

on the command line is easy - here is a simple example - pretty much what kextutil does:

sudo cp -r ~/Downloads/IntelMausiEthernet.kext /Library/Extensions
sudo chown -R 0:0 /Library/Extensions/IntelMausiEthernet.kext
sudo chmod -R g-w  /Library/Extensions/IntelMausiEthernet.kext
sudo kextcache -i /

Share this post


Link to post
Share on other sites

Guys i know the first page says the latest pre built in the downloads section is for 10.11 and up but is there anyone using it in Yosemite 10.10.5 ? 

 

I'm using 2.2 on two Yosemite installs and haven't had any problems.

Share this post


Link to post
Share on other sites

@tluck, there is no reason to make new permissions for the installed kext when you are using sudo cp. Just do

sudo cp -r ~/Downloads/IntelMausiEthernet.kext /Library/Extensions && sudo touch /L*/E*

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 End3rPower50
      Hi, i've installed on my pc MacOS Mojave but after installation my pc, sometimes, crash giving kernel panic.
      I came to the conclusion that it is a random kernel panic because sometimes it starting up and other times it isn't starting up
       
      My PC:
      CPU: Intel i7 6500U
      LAN: RTL8100
      Wi-Fi & Bluetooth: Dell DW1820A
      USB 3.1
       
      CLOVER.zip
    • By Angelo_
      Hi, I followed the rehabman guide (linked in the vanilla guide on the side of r/Hackintosh, not sure if I can link it) for laptops for my yoga 730ILW13 with an 8265u, Conexant 11870, 8gb of ram, 13.3" fhd and I found that upon booting the installer usb I get this weird issue where the screen displays what it should but the screen is incredibly dim (though it was off before using a flashlight on it) and it flashes every few seconds for a few milliseconds to the correct brightness, I used the plist for hd615-650 (including my 620), not quite sure what could be the culprit, first time hackintoshing a laptop so it might be a stupid brightness kext I forgot but didn't find any in that post or in this forum :c 
      Attached the clover zip so that anyone with more experience than me might give an idea in what could be a way to fix this.
      Thank you in advance 
       
       
       
      CLOVER.zip
    • 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
       
×